CRM migration

Migrate from SalesNexus to Nutshell

Field-level mapping, validation, and rollback between SalesNexus and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

SalesNexus logo

SalesNexus

Source

Nutshell

Destination

Nutshell logo

Compatibility

88%

7 of 8

objects map 1:1 between SalesNexus and Nutshell.

Complexity

BStandard

Timeline

1-3 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

SalesNexus logo

SalesNexus

What's pushing teams away

  • The legacy version and the 2026 Nexi-powered version are distinct products requiring an explicit migration path, creating confusion and data duplication for long-time users.
  • Automation and enrichment limits on lower tiers are restrictive, pushing growing teams toward platforms like HubSpot or Salesforce with higher per-seat quotas.
  • The learning curve is steeper than expected; some actions lack intuitiveness and require consulting the training library, per multiple Capterra and G2 reviews.
  • Contact tier caps (1000 on free, 5000 on Starter) force mid-sized teams into paid upgrades or migration, with no transparent path to unlimited contacts.
  • Exporting drip automation sequences and Nexi AI configurations is not supported by the public API, requiring manual rebuilding in the destination system.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How SalesNexus objects map to Nutshell

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

maps to

Nutshell

Person

1:1
Fully supported

SalesNexus 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

maps to

Nutshell

Company

1:1
Fully supported

SalesNexus 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

maps to

Nutshell

Pipeline

1:1
Fully supported

SalesNexus 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

maps to

Nutshell

Pipeline Stage

lossy
Fully supported

SalesNexus 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

maps to

Nutshell

Activity

1:1
Fully supported

SalesNexus 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

maps to

Nutshell

Email Template

1:1
Fully supported

SalesNexus 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

maps to

Nutshell

Custom Field (People or Company)

1:1
Fully supported

SalesNexus 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

maps to

Nutshell

User

1:1
Fully supported

SalesNexus 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.

Gotchas + challenges

What specifically takes care here

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 logo

SalesNexus gotchas

High

Dual-platform account confusion blocks clean exports

High

Contact tier limits are enforced at migration time

Medium

Drip automation sequences are not exportable via API

Medium

API rate limits restrict export throughput on Free and Starter plans

Low

Nexi AI suggestions and automations produce no exportable artifact

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • SalesNexus dual-platform account confusion blocks clean exports

    SalesNexus now operates two distinct platforms: the current 2026 version (app.salesnex.us) and a Legacy version (salesnexus.com/login.html). Long-time customers sometimes hold active data in both environments simultaneously. We detect which platform each account instance uses during scoping and confirm with the customer whether legacy system data is in scope. Failing to identify the active platform before export results in exporting stale or incomplete data into Nutshell, causing downstream reconciliation failures.

  • Contact tier limits enforced at migration time

    The SalesNexus Free plan caps contacts at 1,000 and Starter at 5,000. When we export from a paying tier, the raw export may contain more contacts than the destination Nutshell plan accommodates on day one. Nutshell Foundation (the entry-level paid plan) includes unlimited contacts, but if the customer uses the Free trial tier (500-contact limit), we validate the contact count before committing the import and flag any overflow for plan upgrade or deferred migration before proceeding.

  • Drip automation sequences are not exportable via API

    SalesNexus does not expose drip workflow definitions over its public API. We can export the list of contacts enrolled in each sequence, the sequence name, and enrollment dates, but the trigger logic, delay rules, and conditional branches must be manually rebuilt in Nutshell's workflow builder. We provide a sequence audit report listing all active automations, their enrollments, and a recommended Nutshell workflow equivalent so the customer's admin can reconstruct them.

  • API rate limits restrict export throughput on lower tiers

    The SalesNexus Free plan limits API calls to 50 per month and Starter scales to 500, with no publicly documented rate-limit table. For large datasets on lower tiers, we implement exponential backoff and pagination chunking to stay within limits, but this extends export time significantly. As an alternative, we advise using SalesNexus's manual CSV export option for bulk record extraction before triggering an API-based migration, then using Import2 for the Nutshell import.

  • Nexi AI suggestions and Smart Recommendations have no exportable artifact

    Nexi AI features (AI Email Assistant, AI Meeting Notes, Smart Recommendations) generate outputs stored ephemerally in the SalesNexus AI inference layer. Any suggestions stored as contact notes export as plain-text note content, but the AI model state and real-time recommendations cannot migrate. We document which Nexi features are active in the source account so customers understand what will be lost before committing to migration. Nutshell's Power AI tier includes its own AI features, which the customer can configure independently post-migration.

Migration approach

Six steps for a successful SalesNexus to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

SalesNexus logo

SalesNexus

Source

Strengths

  • Bundles CRM, email marketing, and automation in a single subscription without per-feature add-ons.
  • Weekly live training and responsive support are consistently praised on G2 and Capterra.
  • Contact enrichment, drip emails, and call transcription are included on all paid plans.
  • Unlimited email archival on all tiers preserves full customer communication history.
  • API access is available across all plans, though rate limits scale with the plan tier.

Weaknesses

  • The 2026 Nexi platform and legacy version are two distinct products, complicating in-platform upgrades.
  • Drip automation workflow logic is not exposed via API and must be rebuilt manually at the destination.
  • Contact tier caps on free and Starter plans create artificial ceilings that force upgrades or migration.
  • Nexi AI features produce outputs that cannot be exported, only referenced in notes.
  • No publicly documented bulk API; data export relies on paginated REST calls, which is slow for large datasets.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across SalesNexus and Nutshell.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    SalesNexus: Not publicly documented in a rate-limit table; Free plan limits are 50 API calls/month, Starter increases to 500+.

  • Data volume sensitivity

    B

    SalesNexus doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your SalesNexus to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about SalesNexus to Nutshell data migrations

Answers to the questions buyers ask most during SalesNexus to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your SalesNexus to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most migrations land between one and three weeks for accounts under 5,000 Contacts with no complex drip automation rebuild. Accounts with large engagement histories, multiple active drip sequences, or Nexi AI feature documentation scope move to three to six weeks. The SalesNexus 2026 versus Legacy platform split adds a scoping step that typically adds two to four days to the discovery phase.

Adjacent paths

Related migrations to explore

Ready when you are

Move from SalesNexus.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day