Migrate from Pega Sales Automation to Zoho CRM

Pega Accounts map to Zoho Accounts as the top-level company record. Accounts have no parent dependencies in Pega's import graph, so they load first in Zoho as the anchor for all subsequent imports. We preserve industry classification, address, annual revenue, and number of employees. Pega's account-level territory assignment maps to a Zoho custom field (Territory__c) if the destination uses Zoho's Territory Management feature.

Pega Contacts map to Zoho Contacts with the AccountId lookup resolved to the migrated Zoho Accounts record. The Pega Contact-to-Account foreign key is resolved at migration time by matching the Pega AccountName to the Zoho Account record created in the first import phase. Contact title, phone, email, mailing address, and reporting structure transfer directly.

Pega Leads (unconverted prospects with Pega-specific disposition codes) map to Zoho Leads. Pega disposition codes migrate to a Zoho custom picklist field (Lead_Disposition__c) because Zoho's standard Lead Status field uses a different value set. We preserve the original Lead score from Pega in a custom field if applicable. If the customer has already converted all Pega Leads before migration, this mapping is a null pass.

Pega Opportunities map to Zoho Deals with stage, amount, close date, and probability preserved. The Opportunity-to-Account lookup resolves to the Zoho Account created in phase one. Pega's opportunity product junction records map to Zoho Products linked to Deals via the Deal-Product association. Forecast category from Pega migrates to a custom field if the customer's Zoho implementation uses Zoho's forecasting module.

Pega's named stage values (Prospecting, Qualification, Proposal, Negotiation, Closed Won, Closed Lost) map to Zoho Stage names on the Deal. Probability percentages from Pega transfer to Zoho Stage Probability values under the Pipeline configuration. We configure the Zoho Pipeline before Deal import so that stage mapping is enforced during load.

Pega Products map to Zoho Products. We preserve product name, SKU, unit price, and product description. The Price Book concept in Zoho (standard and custom price lists) maps to Pega's product pricing configuration. Products must be loaded before Deal-Product junction records.

Pega call Activities map to Zoho Events with the call disposition, duration, and direction preserved in custom fields on the Event. The parent Opportunity, Contact, or Account lookup resolves at migration time. Activity timestamps are preserved to maintain the chronological sales timeline.

Pega email Activities map to Zoho Activities of type Email. Email subject, body content, and sender/recipient addresses transfer. Zoho's email threading model differs from Pega's; we flatten the Pega email chain into individual Activity records linked to the parent record (Contact or Deal) rather than attempting to preserve thread grouping.

Pega task Activities map to Zoho Tasks with Status, Priority, due date, and subject preserved. Task assignment (Pega owner to Zoho User) resolves via email matching against the Zoho User table provisioned before migration. Incomplete tasks from Pega become Open tasks in Zoho.

Pega Sales Team membership (which users have access to a given Account or Opportunity) has no direct Zoho CRM equivalent in the standard object model. We create a custom module Sales_Team__c with a lookup to Accounts and Contacts, storing team membership as individual records. The customer's admin configures Zoho sharing rules to replicate the team-access behavior using Roles and Profiles.

Pega Campaigns map to Zoho Campaigns with campaign name, type, status, start date, and budget preserved. Campaign member records (Contacts and Leads linked to the Campaign) migrate to Zoho Campaign Members with Status (Sent, Opened, Responded) mapped to Zoho's campaign member status values.

Pega custom fields (unlimited properties on any base entity via App Studio or Rule configuration) require manual enumeration entity by entity because no automated schema-discovery endpoint exists. We extract custom property definitions from the customer's Ruleset exports and map each to a Zoho custom field with matching data type (Text, Integer, DateTime, Boolean, Picklist). Unmapped properties are flagged in the scope document for the customer's admin to resolve before migration.