Migrate from Pega Platform to Nutshell

Pega has no standard CRM objects — everything is custom property data

Pega Platform is a BPM/case management system, not a CRM. It stores contact-like data in developer-defined properties within Data Pages and Work Object classes. There is no 'Contact' or 'Account' object — your Pega developers configured every field. Nutshell has typed People, Company, and Lead objects with standard fields. Before migration, we audit every Pega Data Page and property to determine which data maps to Nutshell standard fields versus custom fields. This discovery step can extend planning by 1–2 days on complex Pega configurations.

Pega workflows, case routing rules, and SLA definitions do not migrate

Pega's case lifecycle rules, assignment routing logic, SLA deadlines, and escalation triggers are rule-based configurations that exist only within the Pega engine. Nutshell has email sequences, basic task assignment, and lead routing — but these are not equivalent to Pega's case management. If your Pega implementation uses complex SLA definitions or conditional routing, those must be rebuilt as Nutshell workflow rules or documented as standard operating procedures. We provide a Pega workflow audit document listing every automation that needs manual reconstruction.

Pega's Data Transform mapping logic has no Nutshell equivalent

Pega Data Transforms define runtime property-to-property mappings — for example, concatenating first and last name into a display field, or deriving a value from a calculation. These are executed by the Pega engine at case creation. Nutshell has no data transform engine; field calculations must be done pre-migration or set as default values in Nutshell custom fields. We document every Data Transform that affects your target data so your Nutshell admin can configure equivalent default values before the import runs.

Pega attachment storage (file repository) requires re-upload to Nutshell

Pega stores file attachments in its document repository or external storage (S3, Azure Blob). These files are not accessible via standard Pega REST APIs — you need either a Pega-specific file retrieval mechanism or a RAP archive extraction. Nutshell accepts files via its API or direct upload. We extract attachments from Pega's storage, map them to the parent Person or Company record, and re-upload to Nutshell. Large attachments (over 25MB) require chunked upload or an alternative file-sharing reference.

Pega operator role hierarchies map imperfectly to Nutshell's flat role model

Pega access groups and operator roles define a hierarchical permission model — operators can have different roles per application, ruleset, and organizational unit. Nutshell has three base roles (Admin, Standard, Limited) with team-based access. A Pega access group with three roles, five organizational units, and rule-level permissions cannot map 1:1 to Nutshell. We map each operator to the closest Nutshell role (Admin for Pega administrators, Standard for regular users) and document role discrepancies for your review.