Migrate from Pega Customer Engagement Suite to Microsoft Dynamics 365 Sales

Pega Customer Profiles map to Dynamics 365 Contact records linked to Account records. Standard fields (name, email, phone, address) map directly. Any custom properties on the Customer Profile become Dynamics custom fields on Contact. Account is created first and the AccountId lookup is resolved before Contact insert. The Pega Customer Profile identifier is preserved in a custom field pega_profile_id__c for reconciliation. If Pega's customer entity has company associations, those map to Account records with AccountId resolved at import time.

Pega Cases map to Dynamics 365 Case if the destination org includes Service Cloud licensing. Case Type from Pega becomes Case Origin or a custom Case Type field in Dynamics. pyStatusWork maps to Case Status. If the case represents a sales pipeline item rather than a service request, we map it to Opportunity with the Pega case ID preserved in a custom field pega_case_id__c. The split rule is defined during scoping based on the customer's Pega Case Type definitions. Historical case records migrate with their original creation and resolution timestamps preserved.

Pega Work Objects are case instances created from Case Type templates. pyStatusWork and pyAssignment fields are extracted and mapped to Dynamics Case Status and Owner (User) respectively. Stage and SLA metadata map to custom fields on Case. Work Object history and audit records migrate as Notes or EmailMessage records attached to the parent Case. Stage transitions are preserved as custom timeline fields if the customer requires the full case lifecycle audit trail.

Pega Entities are core data model objects that map to database tables, often with organization-specific custom Entities beyond Pega's standard set. Each Pega Entity maps to a Dynamics custom entity (table) with equivalent columns. We pre-create the destination schema via the Dataverse API, including all attribute types (string, integer, lookup, picklist), before data import. Custom Entity relationships are recreated as Dataverse lookup columns with referential integrity enforced at migration time. Pega Entities with no Dynamics equivalent become custom tables.

Pega Data Pages are cached data structures used to retrieve and display information within Pega applications. We extract the cached data values and map them to equivalent custom fields on the relevant Dynamics entity or as configuration records in a custom Dataverse table. The Data Page structure (source, mode, parameters) is documented separately so that the customer's Dynamics admin can recreate equivalent lookup behavior using Power Apps or custom plug-ins if needed.

Pega custom fields extend standard objects and are associated with Rules. We extract field names, data types, and all populated values. Field-level mapping to Dynamics custom fields is required because Pega field types (text, integer, decimal, date, attachment) map to specific Dynamics attribute types. Custom fields that reference Pega-specific picklist values are mapped to Dynamics picklist or option set fields with equivalent value labels. Fields that reference deprecated Pega Rules are flagged in the mapping documentation.

Pega Decision Manager and Next-Best-Action rules are AI-driven logic trees specific to Pega's decisioning engine. These cannot be extracted and translated to other platforms. We deliver a written specification of every active Decision rule, including the input conditions, output actions, and the business logic it encodes, so that the customer's Dynamics admin or implementation partner can rebuild equivalent logic using Power Automate, Power Apps, or the Dynamics 365 Business Rules framework. Organizations using Pega's real-time personalization for customer-facing offers should evaluate Dynamics 365 Customer Insights as a replacement.

Pega workflows (cases, processes, and service levels) and Case Type routing rules use Pega's low-code BPMN-adjacent syntax that does not export in a standard format compatible with Dynamics 365. We deliver a written inventory of every active Pega Case Type, including stages, steps, assignments, routing rules, SLA configurations, and escalation logic. Microsoft Dynamics 365 Sales automation capabilities are more limited on the base tier; organizations requiring complex routing may need Service Cloud with its Case SLAs and Entitlements, or Power Automate for workflow-style automation. The rebuild scope is significant and should be budgeted as a separate phase.