Migrate from Pega Platform to Freshsales

Work Object maps to Freshsales Account. Pega Case ID stored as Account custom field Source_Case_ID__c for traceability. Case Type maps to a custom text field. Freshsales' flat account model requires flattening any Pega parent-child case hierarchy. We also map the Pega CreatedDateTime and UpdatedDateTime to custom datetime fields on the Account to preserve audit history. The parent Case ID is stored in Parent_Case_ID__c for reference.

When Pega Work Object represents a sales opportunity, it maps to Freshsales Deal (Opportunity). Case Type becomes Deal name. Pega Case Status maps to Freshsales Deal Stage via a value-mapping table built during scoping. We also preserve the original Pega Case ID in a custom field (Source_Case_ID__c) on the Opportunity for traceability, and store any parent Case reference in Parent_Case_ID__c if needed.

Work Party (person associated with a case) maps to Freshsales Contact. Work Party Name becomes Contact Name. Email maps directly. Phone maps to Phone or Mobile Phone. Work Party Type stored as custom contact field. If the Work Party includes a role such as Manager or Stakeholder, we store that in a custom pick-list field (Pega_Work_Party_Role__c) on the Contact for segmentation.

Pega Assignment maps to Freshsales Task. Assignment description becomes Task subject. Due Date maps to Freshsales due_date field. Assignee resolved by email match to Freshsales users. Pega datetime values truncated to date when importing to Freshsales date field. If the original Pega datetime includes time-of-day, we store it in a custom datetime field (pega_assignment_datetime__c) for precision.

Pega Data Pages (structured data collections) map to Freshsales Custom Objects. Each Data Page property becomes a custom field on the Custom Object. Nested structures require flattening or JSON serialization into a text field. We also create a lookup field on the Custom Object to link it to the parent Account or Contact, ensuring you can navigate from the primary CRM record to its related data pages.

Custom fields on Pega Work Objects are recreated as Freshsales Custom Fields on Account or Opportunity. Numeric types migrate directly. Pick-list fields require value-by-value mapping in Freshsales Custom Fields before migration. We also validate that any default values set in Pega are replicated as default values in Freshsales, and we log a mapping report for each custom field to confirm translation accuracy.

Pega CreatedDateTime and UpdatedDateTime preserved as custom datetime fields on Freshsales Account. Freshsales sets its own CreatedDate on import — original Pega timestamp stored in Pega_Created_Date__c for audit continuity. We also capture ResolvedDateTime and ClosedDateTime in additional custom fields (Pega_Resolved_Date__c and Pega_Closed_Date__c) to preserve the full case lifecycle. These fields are populated during migration and validated in the test run.

Pega Work Party Type (Customer, Manager, Stakeholder) stored as Pega_Work_Party_Role__c on Freshsales Contact. Freshsales has no native equivalent for party-role labeling on contacts. We configure the custom field as a pick-list in Freshsales, populating it with the same values from Pega. During migration, we map each Work Party Type to the corresponding pick-list value, and we verify the mapping in the test phase to ensure accurate segmentation.

Pega file attachments on Work Objects are downloaded and re-uploaded to Freshsales Files, linked to the corresponding Account or Contact record. File size limits (Freshsales default 25MB per file) are checked before upload. We also preserve the original file name and creation date as metadata in Freshsales, and we log each file transfer for audit. If a file exceeds the limit, we flag it for manual handling.

Pega Group records (non-person entities in a case context) map to Freshsales Account. Group Name becomes Account Name. Group Description maps to Account Details. Group Type stored as custom field. We also capture the Pega Group ID in a custom field (Source_Group_ID__c) for traceability, and we map any associated Work Parties to Contact roles linked to the Account.