Migrate from Pega Sales Automation to Twenty CRM

Pega Accounts (economic decision-making units in B2B selling mode) map directly to Twenty CRM Company records. The Pega Account.pxCompanyName field maps to Company.name, Account.pxStreetAddress1 to Company.address_street, and Account.pxCity to Company.address_city. Account is the top-level entity in Pega's dependency graph and must be migrated first; we import all Companies before any Contacts to satisfy foreign-key resolution in Twenty.

Pega Contacts map to Twenty CRM Contacts with AccountId resolved to the migrated Company record by email domain match. Pega's Contact.pxFirstName and Contact.pxLastName map to Contact.name (Twenty uses a composite name field). Phone, email, and job title migrate to standard Contact fields. Contacts must import after Companies per Pega's dependency graph; we use a batch-chunked import with parent-record lookup to resolve the Company relationship before inserting each Contact batch.

Pega Leads represent unconverted prospects and may carry Pega-specific disposition codes and lead scoring values from the Customer Decision Hub. We map Lead to Twenty CRM Lead preserving disposition status in a custom field, lead score in a numeric field, and source attribution in the standard source field. If the customer's Pega instance uses a lead-to-opportunity conversion workflow, we map the converted opportunity to a Twenty CRM Opportunity and mark the original Lead as converted.

Pega Opportunities link to Accounts (and optionally Contacts) and include stage progression, amount, close date, and probability. We map Opportunity.stageName to Twenty CRM Opportunity.stage, Opportunity.amount to Opportunity.amount, and Opportunity.closeDate to Opportunity.closeDate. Probability migrates as a custom numeric field since Twenty CRM does not enforce stage-to-probability mapping. Stage history from Pega's progress tracking becomes a JSON-formatted notes field for audit.

Pega Activities (calls, emails, meetings, tasks) are tied to parent entities via the Work Object relationship. Pega's import documentation mandates loading Activities after their parent records. We map Pega Activity types to Twenty CRM Activity records: Calls as type=CALL with duration, emails as type=EMAIL with body, meetings as type=MEETING with date range, and tasks as type=TASK with status and due date. The parent-reference relationship resolves to the migrated Contact, Company, or Opportunity record.

Pega Products (sellable items in the CDM) map to Twenty CRM Products. Product.name, Product.pxProductCode (SKU), and pricing fields migrate to Twenty Product.name, Product.description, and Product.price fields. Opportunity-Product junction records from Pega (defining which products attach to which opportunities) map to Twenty CRM OpportunityLineItems with resolved product and opportunity references.

Pega Territories segment Accounts and users by geography or business unit using territory assignment rules that trigger on record creation. Twenty CRM does not have a native Territory object. We map territory assignments to a custom text field on Company and Contact records, preserving the territory name so the customer's admin can use it for segmentation and reporting. If the customer requires a full territory hierarchy, we document the structure for admin-level configuration in Twenty.

Pega Sales Teams define which users have access to a given Account or Opportunity. Pega stores team membership as a separate assignment entity. Twenty CRM uses a Workspace-based sharing model where records are assigned to workspaces. We map Pega team membership to Workspace assignments on the migrated Company and Opportunity records, resolving Pega operator IDs to Twenty CRM user accounts by email match.

Pega Campaigns group Leads and Activities for coordinated outreach. Twenty CRM does not have a dedicated Campaign object. We migrate campaign membership records as linked Opportunities with a campaign_name custom field, and preserve campaign status and linked Opportunity associations in a campaign tracking object. The customer's admin rebuilds campaign automation sequences in Twenty's workflow builder post-migration.

Pega Sales Automation wraps many entities as Cases (Work Objects) under its BPM engine. Cases carry lifecycle states, assignments, and SLA timers that have no direct Twenty CRM equivalent. During scoping, we identify all Case Work Object types in the customer's Pega instance and determine whether they map to a custom Twenty CRM object (requiring schema pre-creation) or to an Opportunity with extended notes capturing the case context. SLA timers and assignment data migrate as custom fields on the target object.

Pega allows unlimited custom properties on any base entity through App Studio or Rule configuration. There is no automated discovery endpoint that lists 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, then hand-map each to a Twenty CRM custom field, matching Pega data types (Text, Integer, DateTime, Boolean, Decimal) to Twenty's type system. Custom field mapping is the highest-effort step in this migration and is scoped separately during discovery.