Migrate from Nutshell to Salesforce Sales Cloud

Nutshell People with a lifecycle status indicating an unqualified prospect map to Salesforce Lead. People attached to an existing customer organization or with an assigned owner matching an active sales rep map to Salesforce Contact tied to an Account. We determine the split using Nutshell's people_type field and the presence or absence of a linked deal. The original Nutshell person_id migrates as a custom field nutshel_person_id__c on both Lead and Contact for audit trail and cross-reference.

Nutshell Company records map directly to Salesforce Account. Company name is the dedupe key during import. Nutshell's flat hierarchy means a Company exists without a mandatory parent, which maps cleanly to Salesforce's Account model where top-level Accounts have no parent unless a hierarchy is explicitly configured. We create Account records before People import so that the AccountId Lookup is satisfied at Contact insert time.

Nutshell Leads are distinct records separate from People, with their own custom fields and lifecycle. They map directly to Salesforce Lead without requiring conversion. Any custom fields on the Nutshell Lead object are enumerated during discovery, and matching custom fields are created in Salesforce before the Lead import phase begins.

Nutshell Pipelines map to Salesforce Opportunity Record Types with a corresponding Sales Process that whitelists the stage values. We extract the pipeline definitions during discovery and configure Salesforce Record Types in the sandbox before production migration. Each Record Type gets its own Opportunity Page Layout so stage values remain scoped per line of business.

Nutshell stage-level data (probability, order, win/loss status) maps to Salesforce Opportunity Stage definitions. Stage probability percentages transfer to Salesforce StageProbability, rounded to the nearest allowed integer. Win and loss stage flags map to IsWon and IsClosed checkboxes on the Opportunity.

Nutshell Activities are extracted per Person and Company as a flat timeline. Calls migrate as Salesforce Task with TaskSubtype=Call. Meetings migrate as Event records with StartDateTime, EndDateTime, and Location preserved. Emails migrate as EmailMessage records linked to Task records on the activity timeline. Activity timestamps are preserved as ActivityDate for timeline ordering. We use the Bulk API 2.0 for activity ingest because the volume typically exceeds what CSV-based Data Loader can handle without timeout errors.

Nutshell custom field definitions are enumerated per object during discovery. We create matching custom fields in Salesforce using the same field label and a sanitized API name (spaces removed, special characters stripped, __c suffix appended). Field types are mapped: Nutshell text to Salesforce Text, Nutshell number to Number, Nutshell date to Date, Nutshell dropdown to Picklist, Nutshell multi-select to Multi-Select Picklist. Picklist values are migrated verbatim if the field is a standard picklist; if values exceed 500, we recommend a text field to avoid Salesforce picklist limits.

Nutshell tags on People and Companies are extracted and mapped to Salesforce Multi-Select Picklist fields on the Contact or Account. If the customer uses more than 150 unique tags, we recommend a Salesforce Custom Metadata configuration or a junction object to handle the tag taxonomy rather than a multi-select picklist field (Salesforce caps multi-select picklist values at 500). The customer selects the strategy during scoping.

Nutshell Users are mapped to Salesforce User records by email address. We run an owner reconciliation step before migration: any Nutshell User without a matching Salesforce User is held in a queue and the customer provisions the missing User account before record import resumes. This step is required because OwnerId is a required reference on Opportunity and Activity records.

If Nutshell Products are in scope (available on Pro and Business plans), they map to Salesforce Product2 records with Standard Price Book entries created during import. The Nutshell SKU field maps to ProductCode on Product2.

Nutshell's API exposes attachment metadata (filename, content type, URL reference) but does not return binary file blobs. We export attachment filenames, content types, and original upload dates as a structured CSV inventory. The customer manually re-attaches files in Salesforce after migration using the inventory as a checklist. We cannot automatically migrate attachments and flag this explicitly in the migration scope document.

Nutshell Email Sequences are server-side automation configurations on Pro and Business plans that are not accessible via the public API. We do not migrate sequences. During discovery we capture sequence names, step counts, step types (email, task, delay), and trigger conditions in a written inventory document that the customer's Salesforce admin uses as a rebuild checklist. Sequences do not map to any standard Salesforce object; they are rebuilt as Salesforce Flow or a Sales Engagement tool (Sales Engagement is a separate Salesforce license).