Migrate from Pega Platform to Microsoft Dynamics 365 Sales

Each Pega Case Work Item migrates as a Dynamics 365 Sales Case record. The case pxRefObjectInsName (internal ID) is stored as SourceSystemID__c for traceability. Open cases migrate with status Open; resolved cases migrate with status Resolved. Case metadata (pxClass, pyWorkStatus) is preserved in custom fields on the Case record.

If a Pega case type tracks revenue or deal-like work, it can also map to a Dynamics 365 Sales Opportunity. FlitStack surveys your case types to identify revenue-carrying ones and maps those to Opportunities with AccountId and Amount fields populated from Pega data page properties.

Pega Data Objects representing organizations or customers map to Dynamics 365 Sales Account records. The Data Object's pxInsKey (internal ID) is stored on the Account as SourceSystemID__c. Account name, address, and industry fields map directly; custom Data Object properties map to custom fields on the Account.

Pega Data Objects representing people or operators map to Dynamics 365 Sales Contact records. Email, name, phone, and job title map directly. The Data Object pxInsKey is stored as SourceSystemID__c. Operator records can be split — contacts that are also Pega users get the SourceSystemID populated for owner resolution.

Pega Data Pages holding property lists or custom data structures have no direct Dynamics 365 Sales equivalent. FlitStack creates a custom Dataverse table for each Data Page, preserving all properties as columns. The table name reflects the Pega Data Page name and a SourceSystemID column links each row back to the originating Pega record.

Pega Assignments (individual operator tasks within a case) map to Dynamics 365 Sales Task records. The assignment title becomes the Task Subject. Operator name and operator group are stored as custom fields (AssignedOperator__c, OperatorGroup__c) since Dynamics 365 Sales does not have a native operator assignment model for Tasks.

Pega file attachments are downloaded from Pega Cloud storage or extracted from the Pega API and re-uploaded to the corresponding Dynamics 365 Sales Case or Opportunity. Files attach to the record's SharePoint location if the Dynamics 365 Sales instance is configured for SharePoint integration.

Pega Pulse comments and free-text Notes attached to cases migrate as Dynamics 365 Sales Note records linked to the Case. Original author and timestamp are preserved. Rich-text formatting is converted to plain text to match Dynamics 365 Sales Note field constraints.

Pega Operator records map to Dynamics 365 Sales User records by email match. Operators without a Dynamics 365 Sales license are flagged as unmatched and can be assigned to a fallback owner. Operator group membership is preserved as a custom field on the User record for reporting.

Pega SLA rules and timer definitions have no Dynamics 365 Sales equivalent. FlitStack preserves SLA name and target duration as custom fields on the Case record. The actual SLA enforcement logic must be rebuilt in Dynamics 365 Sales using Power Automate or a third-party SLA app post-migration.

Pega business rules (validation rules, routing rules, escalation rules) are automation constructs with no Dynamics 365 Sales counterpart. FlitStack exports Pega rule definitions as a reference document for your Dynamics 365 Sales admin to use when rebuilding automation logic in Power Automate.

Pega captures full case history including status transitions, assignment events, and SLA events. This history migrates to a custom Dataverse table (CaseHistory__c) with columns for event type, from-status, to-status, timestamp, and operator. The parent Case record links via SourceSystemID__c for traceability and audit reporting in Dynamics 365 Sales.