Migrate from Pega Platform to Pipedrive

Pega work cases map to Pipedrive deals. Each case ID becomes a Pipedrive deal, with case status mapping to deal stage. Case priority translates to a custom deal priority field. The deal name uses case subject or a formatted case ID prefix for traceability.

Pega data objects attached to cases export as property bundles. Each top-level property becomes a Pipedrive custom field on the corresponding deal or person record. Nested objects require flattening into separate fields or storing as JSON in a long-text custom field for reference.

Pega operator IDs resolve to Pipedrive users by matching the operator's email address stored in Pega. When an operator record lacks an email or no corresponding Pipedrive account exists, FlitStack flags the entry in a pre-migration report and holds the deal for team assignment. Unresolved operators receive a fallback assignment to the migrating admin user, ensuring every migrated deal has a valid owner.

Pega case assignments with a due date and assignee become Pipedrive activities of type 'task' linked to the corresponding deal. Assignment status (open, resolved) maps to Pipedrive activity status. The original Pega assignment timestamp is preserved in a custom field.

Pega workbaskets represent queues of pending assignments. Each workbasket maps to a Pipedrive pipeline stage so cases in that queue appear in the correct column. Teams with multiple workbaskets should consolidate or map each to a distinct stage in the Pipedrive pipeline.

Pipedrive records a deal's creation timestamp when the import job writes the record, which may differ from the original case creation date. FlitStack preserves the Pega case open date in a custom datetime field (Original_Created_Date__c) on the deal, enabling historical reporting, filtering, and sorting by the true case origin while keeping the native Pipedrive create date for internal timing.

Pega SLA deadlines do not have a native Pipedrive equivalent. We migrate SLA targets as a custom date field (SLA_Target__c) on the deal. Pipedrive's automation rules can reference this field to trigger follow-up tasks if the team chooses to rebuild SLA logic.

Pega case history entries (status changes, assignments, updates) export as a chronological activity log. We migrate this as Pipedrive notes attached to the deal, preserving timestamps and the operator who made each change. This maintains the full case narrative in Pipedrive.

Pega decision rules and adaptive models define next-best-action logic that has no Pipedrive equivalent. FlitStack exports the decision rule definitions as a JSON reference file that includes rule criteria, action mappings, and condition hierarchies. The Pipedrive admin can use this file to rebuild equivalent logic using Pipedrive automations or the separate Sequences add-on.

Pega BPM processes and robotic automation packages do not export in a form compatible with Pipedrive. FlitStack documents the process flow structure as a reference artifact. The Pipedrive team rebuilds these as automations or sequences based on the documented logic.

Pega case attachments are uploaded to Pipedrive as deal files, respecting Pipedrive's per-file size limits. For attachments exceeding the limit, FlitStack splits the file or flags it for manual upload. Inline images embedded in Pega case notes are extracted and attached as separate image files to the corresponding deal, preserving visual content with descriptive file names derived from the original case context.

Pega supports parent‑child case relationships that reflect hierarchical business context. Where Pipedrive's native deal‑linking feature applies, FlitStack creates linked deal associations. For cases with deeper hierarchies or unsupported link types, the related case ID is stored in a custom field (Related_Pega_Case__c) on the target deal, allowing your team to manually establish connections in Pipedrive's UI after migration.

Pega stores customer data as part of the case context. We split this into Pipedrive Person (contact details) and Organization (company). The primary customer name and contact info land on the Person; company details route to the Organization. Both link to the migrated deal.

Pega's operational reports and BPM analytics dashboards—such as SLA compliance, case cycle‑time, and throughput metrics—have no direct Pipedrive equivalent. Pipedrive's Insights provide deal pipeline and activity metrics, but they do not replicate Pega's case‑level performance analytics. FlitStack documents the structure of each Pega report, including field references and filter criteria, to guide your team in manually rebuilding comparable dashboards within Pipedrive's Insights or via third‑party reporting tools.

Pega's internal case object instance key (pxRefObjectInsKey) is a unique identifier that FlitStack stores in a custom Pipedrive field (Source_Case_ID__c) on each deal. This field supports delta‑run reconciliation, allowing the migration to capture any Pega changes after the initial export, and provides a direct link back to the original Pega record for audit trails, compliance checks, and integration with downstream systems.