Migrate your Pega Sales Automation data

Accounts are the top-level company records and the primary import anchor. They have no parent dependencies, so we import them first and preserve all standard fields including industry classification, address, and owner assignment.

Contacts are linked to Accounts via a foreign key. The import documentation mandates loading Contacts after Accounts to satisfy the referential integrity requirement. We map the Contact-to-Account association at import time using the Account's external identifier.

Leads represent unconverted prospects and may carry Pega-specific disposition codes. When migrating to a CRM that does not have a separate Lead object, we merge Leads into Contacts and preserve the Lead_Status as a custom Contact property.

Opportunities link to Accounts and optionally to Contacts. They include stage progression, amount, close date, and probability. We preserve stage history and forecast category as extended properties on the Opportunity record.

Activities (calls, emails, tasks, meetings) are tied to parent entities (Opportunity, Contact, Account). The import sequence requires Activities to load after their parent records. We flatten the activity hierarchy into a normalized activity log to avoid circular dependency issues during import.

Products are the sellable items attached to Opportunities via an Opportunity-Product junction. We preserve the quantity, unit price, and discount fields on the junction record during migration.

Sales Teams define which users have access to a given Account or Opportunity. Pega stores team membership as a separate assignment entity. When the destination does not have an equivalent team-sharing model, we convert team assignments into owner or territory fields.

Territories segment Accounts and users by geography or business unit. Pega assigns territory rules that trigger on record creation. We map territory assignments to equivalent segmentation fields in the destination or recreate the rule logic as a post-import data transform.

Campaigns group Leads and Activities for coordinated outreach. We preserve campaign membership records and campaign status, including linked Opportunities that originated from campaign response.

Pega supports custom fields at the property level on any base entity. Custom fields require manual mapping against the destination schema, as naming conventions and data type representations vary. We generate a field-mapping manifest before import and validate type compatibility for each custom property.

Pega Sales Automation wraps many entities as Cases (Work Objects) under its BPM engine. Cases carry their own lifecycle states, assignments, and SLA timers. Migrating Cases to a non-Pega CRM requires decomposing the case state machine into a flat record or a series of milestone timestamps.

Pega stores binary attachments in a separate content repository tied to the Pega Cloud blob store. We do not extract or reimport binary blobs directly. We preserve attachment metadata (filename, content type, linked entity, upload timestamp) and provide a URL reference file for post-migration manual reattachment.

Pega's AI decisioning generates Next-Best-Action recommendations stored in the Customer Decision Hub. These are runtime inference records, not source-of-truth data. They are not exported as part of standard data migration and are regenerated by the AI engine on the destination platform.