Migrate from SalesTown CRM to Nutshell

SalesTown Contacts migrate to Nutshell People records when the contact is qualified or has an associated company. Contacts that represent unqualified prospects from auto-capture flows may map to Nutshell Leads depending on the customer's qualification criteria. We use email address as the dedupe key during Nutshell import and preserve any SalesTown custom properties as Nutshell custom fields created before the import phase.

SalesTown Leads map directly to Nutshell Leads. Lead status, source, score, and owner assignment transfer as matching fields on the Nutshell Lead object. Any SalesTown lead scoring values preserve in a custom field for ranking and prioritization after migration.

SalesTown Company records map to Nutshell Companies (the API terminology for this object is Account, but Nutshell UI uses Company). We use company name as the dedupe key and map available fields including domain, address, phone, and industry. Any unmapped company fields are flagged in the export review and carried as custom fields in Nutshell if the customer's data includes them.

SalesTown Deals map to Nutshell Opportunities. The deal amount, expected close date, owner, and associated pipeline and stage transfer to matching Nutshell Opportunity fields. We resolve the parent Company (Account) reference before Opportunity import so that the relationship is satisfied at insert time.

SalesTown Pipelines map to Nutshell Pipelines. We export pipeline names, stage order, and stage-specific flags, then configure the equivalent pipelines in Nutshell before loading any Deals. Pipeline configuration happens in the pre-migration phase via Nutshell's API or UI to ensure stage values are available when Opportunities are created.

SalesTown Stages map to Nutshell stage values within each Pipeline. Stage names, probabilities, and ordering transfer explicitly rather than by relative position to handle pipelines with different stage counts between the two systems. We map stage-to-stage by name match first, then by order if names are generic.

WhatsApp activities from SalesTown export as individual rows that lose thread parentage. We reconstruct thread relationships using timestamp ordering and sender IDs, grouping messages by thread key, and loading the reconstructed sequence as ordered Tasks in Nutshell. Each Task carries the original timestamp, sender, message content, and a custom field indicating the WhatsApp thread identifier.

Email and call activities from SalesTown map to Nutshell Tasks with TaskSubtype = Email or Call. Activity date, duration (for calls), and disposition flags transfer to matching Task fields. Activities linked to Contacts or Leads in SalesTown carry the WhoId reference to the migrated Nutshell People or Lead record.

SalesTown Users map to Nutshell Users by email address match. The customer's Nutshell admin provisions User accounts before migration; we resolve the OwnerId reference during the import phase. Any SalesTown User without a matching Nutshell User goes to a reconciliation queue for admin provisioning before record import proceeds.

SalesTown custom templates for email and communications have no documented export schema, so template bodies do not migrate as code. We export available template metadata (name, subject, field placeholders) and flag template mapping as a post-migration cleanup task. The customer rebuilds templates in Nutshell's email template builder using the exported metadata as reference.