Migrate your Pega Platform data

Cases are Pega's core work object. We export them via Data Set APIs or Export wizard, preserving all standard properties, status, and assignment history. The case ID, creation timestamp, and parent-child hierarchy map cleanly to most destination schemas.

Data Sets hold structured data (list, decision, and Cassandra-backed). We export them as CSV or JSON depending on the destination API. Cassandra-backed Data Sets require chunked reads to avoid memory pressure during export.

Data Objects represent business entities in the logical data layer. We map them to destination object types, preserving property names and relationships where field-level mapping is defined.

Custom Fields attach metadata to Rules or Cases. Since they are defined per application and can reference external tables, we require a custom field inventory from the customer before mapping to the destination schema.

Rules are Pega's executable configuration units. Exporting them via the Product Rule wizard bundles rules into an archive, but portability depends on whether destination Pega environment has compatible versions. We extract rule metadata and flag version incompatibilities.

Work Parties represent stakeholders attached to a Case (e.g., customer, guarantor, manager). We map these to destination contact or account associations, but role naming conventions vary widely between Pega applications.

Decision Rules (Decision Trees, Tables, MATRIX) encode business logic. We preserve them as structured records, but translating their conditional logic requires manual review since the destination may not support the same decisioning syntax.

Assignments represent queued work items and Worklists are the operator's queue. These depend heavily on Operator ID (user) resolution between systems, which we handle via an explicit user mapping table.

Pega Operator IDs carry role, organization, and access group data. We extract them but cannot import directly into a destination without explicit user mapping, as role and access group semantics differ across platforms.

An Application bundles rulesets, data model, and UI into a deployable unit. Migration requires extracting the application via Export wizard, then decomposing it into its constituent objects for import into the destination.

Pega Robotics (now part of Pega Platform) uses separate licensing and automation packaging. These packages are not accessible via standard Pega REST APIs and require manual export via Robotic Automation Importer. We do not migrate Robotics automations as part of standard Pega data migration.