Migrate from Sales Journey to Nutshell

Sales Journey Contact records map to Nutshell Person. Name, email, phone, company association, and standard address fields transfer directly. We resolve the Sales Journey company-to-contact link at migration time and re-establish it as a Person-to-Company association in Nutshell using the company record ID. Owner assignment on Contact maps to the Nutshell User via email cross-reference.

Sales Journey Company records map to Nutshell Company. Standard address, industry, and company size fields migrate directly. The relationship between Companies and their associated Contacts is preserved during migration; we export Company records first so that the link is satisfied at the moment Person records are inserted.

Sales Journey Deal records map to Nutshell Opportunity. The deal name, value (amount), close date, owner, and current stage migrate. Pipeline stage names in Sales Journey are mapped to Nutshell pipeline stage values during the scoping phase, with a stage mapping table produced before migration begins. If Sales Journey uses a single default pipeline, we create one matching Nutshell pipeline structure.

Sales Journey Lead records migrate to Nutshell Lead with status and lifecycle stage preserved as standard Nutshell Lead fields. Lead conversion history and source attribution migrate as custom fields if the customer's Sales Journey instance uses those attributes. We flag any Lead records with no corresponding Company or Person in the destination for manual review before cutover.

Sales Journey engagement records (calls, emails, notes, tasks) migrate to Nutshell Task records. Each Task is linked to the parent Person, Company, or Opportunity via Nutshell's association model. Timestamps and owner assignment preserve. We flag engagement behavioral data such as email open rates or link-click signals separately because this data may not export cleanly from Sales Journey; we audit a sample export during discovery before committing to the activity migration scope.

If Sales Journey supports custom fields on standard objects, we audit them during discovery, then pre-create matching Nutshell custom fields per Nutshell's documented types (text, long text, currency, date). Field validation rules and picklist values in Sales Journey require explicit mapping to Nutshell equivalents. Any custom field discovered during export is added to the mapping table before migration proceeds.

Sales Journey pipeline configuration (stage names, stage order, win/loss criteria) migrates as metadata. If Sales Journey uses a single pipeline, we create one matching Nutshell pipeline. If multiple pipelines are in use, we map each to a separate Nutshell pipeline. Stage-level probability and forecasting settings require reconfiguration in Nutshell after migration because stage probability is set per-pipeline in Nutshell rather than per-stage globally.

Owner assignment on Sales Journey records exports as a user email reference. We map source user emails to Nutshell User records using an email cross-reference table. Any owner without a matching Nutshell User is held in a reconciliation queue for the customer's admin to provision before the record import resumes.

Tagging taxonomy from Sales Journey exports as a flat list per record. We map tags to Nutshell Tags on the equivalent record type. Where the customer uses a more complex tagging taxonomy, we document the mapping in the scoping report and defer to the customer's preferred approach for tag equivalence in Nutshell.

File attachments stored within Sales Journey records may require a separate file-level export step if they are not included in the standard record export. We identify attachment storage location and total file size during scoping and include a file export step in the migration plan. We do not migrate attachment metadata as code; attachments transfer as raw files linked to the target record.