CRM migration
Field-level mapping, validation, and rollback between SalesNexus and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
SalesNexus
Source
Nutshell
Destination
Compatibility
7 of 8
objects map 1:1 between SalesNexus and Nutshell.
Complexity
BStandard
Timeline
1-3 weeks
Overview
Moving from SalesNexus to Nutshell is a structural migration for small teams leaving a bundled CRM-and-email-marketing platform that enforces contact tier caps. SalesNexus limits contacts to 1,000 on Free and 5,000 on Starter, which creates artificial ceilings for growing teams. Nutshell offers unlimited CRM contacts on all paid plans, removing that ceiling entirely. We resolve which SalesNexus platform version (2026 or Legacy) holds your active data during scoping, export via paginated REST calls with exponential backoff, and import through Nutshell's Import2 tool with white-glove validation. Drip automation sequences and Nexi AI features are not exportable via API; we deliver a sequence audit report listing all active automations for your admin to rebuild in Nutshell's workflow builder. Email templates require merge-field syntax conversion from SalesNexus double-brace patterns to Nutshell's format.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a SalesNexus object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
SalesNexus
Contact
Nutshell
Person
1:1SalesNexus Contacts map directly to Nutshell People records with all standard fields (name, email, phone, address, company) and custom fields preserved. We retrieve the full field schema via the get-all-fields endpoint, export each field with its integer field ID and current value, then map each field to the equivalent Nutshell field or create a custom People field for non-standard fields. Contact enrichment data (Nexi scores, tags, drip enrollment status) migrates as text fields. The Nexi AI suggestions stored in contact notes transfer as plain-text note content; the AI model state cannot migrate.
SalesNexus
Company
Nutshell
Company
1:1SalesNexus Company records map directly to Nutshell Company records. The company name, domain, address, phone, and industry fields transfer 1:1. We export companies first, then import them before contacts so that the company lookup is satisfied at the moment of contact import. Companies without contacts in SalesNexus migrate as standalone Nutshell companies with no further transformation required.
SalesNexus
Pipeline
Nutshell
Pipeline
1:1SalesNexus Pipelines (up to 3 on Free, 10 on Starter) map to Nutshell Pipelines. The pipeline name and stage count transfer 1:1. Nutshell supports unlimited pipelines on all paid plans, so there is no tier constraint on the destination side. We create pipelines in Nutshell before any deal or contact migration begins so that stage references are valid on import.
SalesNexus
Pipeline Stage
Nutshell
Pipeline Stage
lossySalesNexus pipeline stages are ordered integer values within a pipeline. We export stage names, order, and probability percentages and recreate them as Nutshell pipeline stages with corresponding probability defaults. If the destination pipeline uses a different stage model, we map them by probability range during configuration. Stage names with special characters are preserved as-is.
SalesNexus
Task
Nutshell
Activity
1:1SalesNexus Tasks map to Nutshell Activities. Due date, subject, completion status, and priority transfer directly. Owner assignment resolves by matching the SalesNexus user email to a Nutshell user; any unresolved owner goes to a reconciliation queue for the admin to assign. Open and completed tasks both migrate; task body migrates as activity notes.
SalesNexus
Email Template
Nutshell
Email Template
1:1SalesNexus email templates with HTML body and merge fields export in full. We convert common merge field patterns from SalesNexus double-brace syntax (e.g., {{contact.first_name}}) to Nutshell's format (e.g., [[contact.first_name]]). Templates with non-standard field references are flagged for manual review after import. The template subject line, sender name, and HTML body all transfer.
SalesNexus
Custom Field
Nutshell
Custom Field (People or Company)
1:1SalesNexus custom fields on Contacts and Companies identified by integer field IDs export with their labels, types, and values. We pre-create matching custom fields in Nutshell People or Company before the migration phase. Field types map from SalesNexus types (text, number, date, picklist, checkbox) to Nutshell equivalents (text, number, date, single-select, checkbox). Multi-select picklists in SalesNexus map to Nutshell multi-select fields.
SalesNexus
User
Nutshell
User
1:1SalesNexus user records (name, email, role) export for owner assignment resolution. We match by email to existing Nutshell users. Users without a matching Nutshell account go to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive or archived SalesNexus users are flagged separately so the admin can decide whether to import their historical assignments.
| SalesNexus | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Pipeline | Pipeline1:1 | Fully supported | |
| Pipeline Stage | Pipeline Stagelossy | Fully supported | |
| Task | Activity1:1 | Fully supported | |
| Email Template | Email Template1:1 | Fully supported | |
| Custom Field | Custom Field (People or Company)1:1 | Fully supported | |
| User | User1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
SalesNexus gotchas
Dual-platform account confusion blocks clean exports
Contact tier limits are enforced at migration time
Drip automation sequences are not exportable via API
API rate limits restrict export throughput on Free and Starter plans
Nexi AI suggestions and automations produce no exportable artifact
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Scoping and platform version confirmation
We audit the source SalesNexus account to confirm whether the active data lives on the 2026 platform (app.salesnex.us) or the Legacy version (salesnexus.com). We catalog record counts (Contacts, Companies, Pipelines, Tasks), identify active drip sequences, and assess custom field schemas. We validate the contact count against the target Nutshell plan tier and flag any overflow before committing to the migration scope. The scoping output is a written migration plan with record counts, object list, and a drip-automation inventory.
Schema extraction and destination field mapping
We export the full SalesNexus field schema using the get-all-fields endpoint, capturing field IDs, labels, types, and any picklist values. We design the Nutshell People and Company custom field schema based on the export, creating custom fields before any data import. We configure Nutshell Pipelines and Stages to match the SalesNexus pipeline names and stage order with corresponding probability defaults.
Test migration into Nutshell sandbox
We run a sample migration using a subset of records (typically 50-100 contacts with their companies, pipeline stages, and activities) into the customer's Nutshell account via Import2. The customer reviews the mapped fields, validates that custom field data landed correctly, and confirms the pipeline configuration. We correct any field mapping errors in this phase before proceeding to production migration.
Production data migration in dependency order
We run production migration in dependency order: Nutshell Users resolved by email match (any unresolved users held in a reconciliation queue), Companies (standalone records), People (with company lookups resolved), Pipeline Stages (configured during schema design), and Activities (Tasks linked to the correct People records). Email templates are imported separately with merge-field syntax converted. Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, delta validation, and drip-automation handoff
We run a final delta migration of any records modified during the migration window, then deliver the drip-automation audit report. The customer's admin rebuilds drip sequences in Nutshell's workflow builder using the audit report as a guide. We support a three-day hypercare window where we resolve any data reconciliation issues raised during the first business days in Nutshell. We do not rebuild drip automations as Nutshell workflows inside the migration scope.
Platform deep dives
SalesNexus
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across SalesNexus and Nutshell.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
SalesNexus: Not publicly documented in a rate-limit table; Free plan limits are 50 API calls/month, Starter increases to 500+.
Data volume sensitivity
SalesNexus doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during SalesNexus to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your SalesNexus to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave SalesNexus
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.