Migrate from Pega Sales Automation to Nutshell

Pega Accounts map directly to Nutshell Organizations. The Pega account name, industry classification, website, and address fields transfer as equivalent Nutshell Organization fields. Account is the top-level parent in Pega's import sequence with no dependencies, so we import it first and use Organization as the anchor for subsequent Contact and Deal imports.

Pega Contacts map to Nutshell People. The Contact-to-Account foreign key resolves to a Nutshell Organization lookup at migration time. We preserve Pega's contact disposition codes, primary role, and any industry-specific properties as custom fields in Nutshell if the plan supports them. Pega's mandatory Account dependency means Contacts cannot load before Accounts.

Pega Leads (unqualified prospects with Pega-specific disposition codes) merge into Nutshell People rather than creating a separate record type, because Nutshell has no separate Lead object. We preserve the original Pega Lead status as a custom field or tag so the admin can segment pre-qualified prospects from converted contacts post-migration.

Pega Opportunities map to Nutshell Deals with stage name normalization across both platforms. Pega stage progression, amount, close date, and probability transfer to the corresponding Nutshell Deal fields. Pega's Opportunity-Account lookup resolves to the Nutshell Organization already migrated in Step 1.

Pega call activities map to Nutshell Tasks with the call subtype set. Call duration, disposition, and recording metadata (if available) transfer to custom Task fields in Nutshell. Parent record resolution links each Task to the migrated Person or Deal. Nutshell's task type differentiation preserves the call context without requiring a separate object.

Pega email activities map to Nutshell Tasks with the email type. We transfer email subject, body, and timestamp to the Task fields, with the email body stored as task notes linked to the Person. Parent Opportunity and Account references resolve to the migrated Deal and Organization respectively.

Pega meeting activities map to Nutshell Tasks with the meeting type. Meeting title, start time, end time, location, and attendee list transfer to equivalent Task fields. We preserve the original Pega meeting timestamp for timeline ordering against the migrated Person and Deal.

Pega standalone tasks map directly to Nutshell Tasks with status, priority, due date, and description preserved. Task ownership resolves via email match against the Nutshell user whose email corresponds to the Pega operator who owned the original task.

Pega Products attached to Opportunities via the Opportunity-Product junction transfer as line items within the corresponding Nutshell Deal. Quantity, unit price, and discount carry over on the Deal line item. We resolve the Product-to-Opportunity linkage at migration time once both Deal and Product records exist.

Pega Campaigns with linked Leads and Activities have no direct Nutshell equivalent. We migrate campaign membership as Nutshell Tags on the relevant Person and Deal records, with campaign status preserved as a tag value. A written campaign map document lists every original Pega Campaign and its Nutshell tag assignments for the admin to rebuild as Nutshell Groups or integration-driven campaign tools if needed.

Pega Work Objects (Cases) carry BPM lifecycle states, SLA timers, and assignments that do not exist as structured data in Nutshell. We extract Case title, current status, key description fields, and assignment notes as a Nutshell Note on the linked Organization or Person record, tagged with a 'Pega Case' label. The customer receives a written Case inventory documenting the original Case ID, Pega status, and migrated note for manual reconstruction in Nutshell.