Migrate from Sales Snap to Nutshell

Sales Snap Contact records map to Nutshell People. We extract name, email, phone, address, company name, and lifecycle stage from the CSV export. Sales Snap inline company data is mapped to a Nutshell Account lookup where the company name dedupes against existing Nutshell Accounts during import. Any custom fields visible in the Sales Snap export are mapped 1:1 to Nutshell custom fields on the People record.

Sales Snap exports company data per contact, which can duplicate across multiple contact rows. We deduplicate on company name during transformation and map to Nutshell Account. The Account is created before the linked People record is imported so that the People-Account relationship is satisfied at the moment of insert. Website, industry, phone, and address fields map to the corresponding Nutshell Account fields where available.

Sales Snap Sequences are the core workflow object defining email cadence, step order, and timing rules. We map email template content, step sequence, and timing delays to a written Sequence structure document that the customer's Nutshell admin uses to rebuild Sequences in Nutshell's built-in sequence editor. Personalization tokens require manual reconfiguration in the destination because they reference field names that may differ after import. Nutshell Sequences are available on Pro tier ($42/user/month) and above.

Sales Snap follow-up tasks generated by sequences map to Nutshell Activities. Task type, due date, completion status, and notes migrate as Activity records linked to the corresponding People record. Orphaned tasks (no linked contact) are flagged in a separate reconciliation report for the customer to resolve manually.

Sales Snap email engagement metrics (opens, clicks, replies) are aggregated and mapped to Nutshell Activity records on the People record. We preserve the engagement timestamp and engagement type as activity metadata. Because Nutshell's native activity timeline does not store granular engagement metrics in the same structure as Sales Snap, we create custom fields on the Activity record to capture open count, click count, and reply status from the source data.

Sales Snap does not expose a configurable pipeline object in CSV exports. Pipeline state is inferred from Contact lifecycle stage values in the export. We map the inferred Sales Snap lifecycle stages to Nutshell pipeline stage values that the customer configures before migration. The customer defines the stage names and probabilities in Nutshell during setup, and we map source values to the destination stage names in the import mapping document.

Sales Snap custom fields visible in the UI export are mapped 1:1 to Nutshell custom fields on the People record. We flag any fields requiring type conversion (for example, a date field in Sales Snap that maps to a datetime field in Nutshell) and document the conversion logic in the field mapping spreadsheet. Fields that are hidden or programmatically gated in Sales Snap and not included in the export are listed as unmapped with a note that manual entry or post-migration data entry is required.

Sales Snap Owners (sales reps assigned to contacts) are matched by email to Nutshell User accounts. If a Sales Snap Owner has no corresponding Nutshell User, the contact is imported with the Owner field blank and flagged in the reconciliation report for the customer to assign manually after provisioning the User in Nutshell.