Migrate from Pega Sales Automation to Salesforce Sales Cloud

Pega Accounts (economic decision-making units in the CDM) map directly to Salesforce Account. Accounts are the top-level company record and the primary import anchor with no parent dependencies, so we load them first. Industry classification, address fields, and the Account Number property migrate as standard Account fields. We use Account.Name as the dedupe key during import to prevent duplicate Account creation.

Pega Contacts link to Accounts via a foreign key and load after Accounts to satisfy Pega's referential integrity requirements. We resolve the AccountId reference by matching Pega's Account external ID to the Salesforce Account ID before Contact insert. Contact.Name, email, phone, title, and mailing address migrate as standard fields. Pega disposition codes on Contacts that indicate qualification status map to a custom field pega_disposition__c on Salesforce Contact.

Pega Leads represent unconverted prospects and carry Pega-specific disposition codes. They map directly to Salesforce Lead. We preserve any Pega lead score or qualification status in a custom field pega_lead_score__c. If the customer uses Pega's Lead-to-Account assignment routing, we document the assignment logic for manual Salesforce territory-rule rebuild in Salesforce Assignment Rules.

Pega Opportunities link to Accounts and optionally to Contacts. Stage progression, amount, close date, and probability migrate to Salesforce Opportunity. Pega's stage history becomes a custom field pega_stage_history__c (JSON blob) because Salesforce does not store a native stage-change audit log on the Opportunity object. We create Salesforce Record Types before migration if the customer uses multiple Pega sales processes.

Pega Activities (calls, emails, tasks, meetings) tie to parent entities (Opportunity, Contact, Account) and load after parent records. We map Pega call engagements to Task with TaskSubtype=Call; email engagements to Salesforce EmailMessage linked to a Task; meeting engagements to Event; and task engagements to Task. Activity timestamp preserves the original Pega created datetime for timeline fidelity. We use Salesforce Bulk API 2.0 with chunking for large activity volumes.

Pega Products (sellable items attached to Opportunities via Opportunity-Product junction) map to Salesforce Product2. We create Standard Pricebook entries during migration and preserve the Pega product code as ProductCode. Quantity, unit price, and discount migrate on the junction OpportunityLineItem record after Pricebook2 and Product2 are inserted.

Pega Territories segment Accounts and users by geography or business unit. Pega assigns territory rules that trigger on record creation. We map territory assignments to Salesforce Territory2 (available with Enterprise Territory Management) or to a custom picklist field on Account and User if the customer does not license Enterprise Territory Management. Territory assignment logic is documented for manual rebuild in Salesforce Assignment Rules or Flow.

Pega Sales Teams define which users have access to a given Account or Opportunity. Pega stores team membership as a separate assignment entity. We map team membership to Salesforce AccountTeamMember and OpportunityTeamMember, resolving each Pega operator ID to the corresponding Salesforce User ID via email match. Sharing model configuration is documented for the customer's admin to set in Salesforce Sharing Settings.

Pega Campaigns group Leads and Activities for coordinated outreach. We preserve campaign membership records and campaign status, including linked Opportunities that originated from campaign response. Campaign member status migrates to CampaignMember.Status, and we document the campaign-to-Opportunity influence tracking for rebuild in Salesforce Campaign Influence.

Pega Sales Automation wraps many entities as Cases (Work Objects) under its BPM engine. Cases carry lifecycle states, assignments, and SLA timers. When migrating to Salesforce, we map Cases to the Salesforce Case object. Case status migrates to Salesforce Case.Status, priority maps to Case.Priority, and Pega SLA timer values become custom fields on Case. Case assignment rules are documented for rebuild in Salesforce Flow or Omni-Channel.

Pega Operators (individual users of the application) map to Salesforce User records. We resolve operators by email match. The Pega Reports-to hierarchy maps to Salesforce User.ManagerId if available. Any Pega Operator without a matching Salesforce User goes to a reconciliation queue for admin provisioning before record migration begins.

Pega supports unlimited custom properties on any base entity through App Studio or Rule configuration. There is no automated discovery endpoint listing every custom field across the schema. We enumerate custom fields entity by entity via the Pega API or by reviewing the customer's Ruleset exports. Each custom field is hand-mapped to a Salesforce custom field with the matching data type (Text to Text, Integer to Number, DateTime to Datetime). Pega picklist values become Salesforce picklist values with identical labels.

Pega Sales Automation for Financial Services extends the CDM with industry-specific entities (client segments, compliance records, regulatory flags). We map these to Salesforce custom objects and standard objects with custom fields. We document each vertical entity and its Salesforce replacement as part of the schema design deliverable. Compliance logic (HIPAA, FINRA, SOC 2) does not migrate; the customer's Salesforce admin configures field-level security and sharing rules to meet compliance requirements.

Pega stores binary attachments in its cloud blob store, which is not directly extractable. We preserve attachment metadata (filename, content type, created date, created by) in a CSV inventory delivered to the customer. The customer's admin retrieves original files from Pega Cloud directly and re-uploads them to Salesforce Files if needed. ContentDocumentLink records connect the attachment inventory to the parent Salesforce record for reference.