Migrate from Salesforce Sales Cloud to Nutshell

Discovery and data audit

We audit the source Salesforce org across objects in scope (Accounts, Contacts, Leads, Opportunities, Activities, Campaigns), record counts per object, and custom field inventory. We identify Account hierarchies (depth, parent-child relationships), Account Contact Relation junction records, multi-currency Opportunities, and any Custom Objects. The discovery output is a written migration scope with object counts, a deduplication strategy by email for People, and a flag list of records that require transformation before import.

Schema design and pipeline configuration

We design the Nutshell destination schema before migration begins. This includes configuring pipeline stages to match the Salesforce Opportunity stages (with probability notes), setting up custom fields on People, Companies, and Deals to receive transformed data, and creating the tagging taxonomy for Leads, converted Leads, and Campaign Members. Nutshell's pipeline and stages are configured in the application by the customer's admin before we begin data import; we provide a stage mapping spreadsheet as the configuration reference.

Deduplication and hierarchy flattening

We run deduplication logic on the extracted Salesforce data using email address as the primary key for People and Company name plus domain as the dedupe key for Companies. Duplicate records are flagged in a reconciliation report for the customer to resolve before import. We flatten Account hierarchies by identifying top-level parent Accounts and flagging child Account names on the parent Company record. Account Contact Relation records are processed and the secondary Account links are stored in a custom text field.

Multi-currency normalization and activity timestamp mapping

We normalize all Opportunity amounts to the destination org's default currency using exchange rates from the Salesforce org, storing the original currency code and original amount in custom fields on the Nutshell Deal. Activity records (Tasks and Events) are mapped with their original timestamps preserved, and parent WhoId and WhatId references are resolved to their corresponding Nutshell People and Deal IDs before import.

Production migration in dependency order

We run production migration in record-dependency order: Team Members (manual provisioning validated first), Companies (from Accounts), People (from Contacts and Leads with Company references resolved), Deals (from Opportunities with Team Member and Company references resolved), Activities (from Tasks and Events via Bulk API with parent-record lookup resolution), and Campaign Member tags (final pass). Each phase emits a row-count reconciliation report before the next phase begins.

Cutover, validation, and automation rebuild handoff

We freeze Salesforce writes during the cutover window, run a final delta migration of any records modified during migration, then mark Nutshell as the system of record. We validate record counts against the source extraction totals and spot-check 20-30 records per object for field-level accuracy. We deliver the automation inventory document listing every Workflow Rule, Process Builder, and Flow with a Nutshell automation rebuild recommendation. We do not rebuild Salesforce automations as Nutshell automations inside the migration scope.