CRM migration
Field-level mapping, validation, and rollback between Salesmate and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Salesmate
Source
Nutshell
Destination
Compatibility
7 of 8
objects map 1:1 between Salesmate and Nutshell.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Moving from Salesmate to Nutshell is a lateral-feature migration between two SMB-focused CRMs with different object models. Salesmate separates Contacts from Companies and uses Deals for pipeline tracking; Nutshell refers to these as People, Companies, and Opportunities respectively, with a unified Activity timeline for tasks, calls, and emails. We map Salesmate's module IDs (Contacts module ID 1, Companies module ID 5, Deals module ID 4, Tasks module ID 2, Products module ID 6) to Nutshell's People, Companies, Opportunities, Tasks, and Products API objects using the REST API on the Salesmate side and the JSON-RPC API on the Nutshell side. The most significant migration difference is Smart Flow automations: Salesmate's automation definitions are not fully exposed via the public API, so we export sequence membership (which contacts are enrolled in which campaigns) and deliver it as a written rebuild guide rather than migrating the logic itself. Team Inbox conversations are preserved as custom fields because Nutshell does not have an equivalent shared-inbox object. Pricing on the destination side is predictable: Nutshell Foundation starts at $16/user/month billed annually and includes unlimited contacts with no per-contact billing surprises, removing the credit-consumption anxiety that drives teams away from Salesmate's Basic tier.
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 Salesmate 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.
Salesmate
Contact
Nutshell
People
1:1Salesmate Contacts (module ID 1) map to Nutshell People. Standard fields (name, email, phone, address) map directly. Custom fields migrate to Nutshell custom People fields. The Salesmate contact's associated Company ID (module 5) resolves to a Nutshell Company via a lookup at migration time, satisfying the People-Company relationship before the People record is committed.
Salesmate
Company
Nutshell
Company
1:1Salesmate Companies (module ID 5) map to Nutshell Companies with a direct 1:1 correspondence. Company name, domain, address, and industry fields map to equivalent Nutshell Company fields. Custom Company fields migrate as Nutshell custom Company fields. Companies are imported before People so that the People-Company lookup reference is valid at the moment of People insert.
Salesmate
Deal
Nutshell
Opportunity
1:1Salesmate Deals (module ID 4) map to Nutshell Opportunities. Deal name, value, stage, expected close date, and owner assignment migrate directly. The Salesmate pipeline maps to a Nutshell pipeline configuration we create in the destination account before migration. Deal custom fields migrate as Nutshell custom Opportunity fields. Owner resolution uses email matching against Nutshell Users.
Salesmate
Task
Nutshell
Task
1:1Salesmate Tasks (module ID 2) map to Nutshell Tasks with Status, Priority, and ActivityDate preserved. Task assignment migrates by resolving the Salesmate owner ID to a Nutshell User ID via the owner email mapping. Open and completed task status carries over. Tasks associated with Deals map to the corresponding Nutshell Opportunity via the WhatId reference resolved at migration time.
Salesmate
Product
Nutshell
Product
1:1Salesmate Products (module ID 6) map to Nutshell Products with name, description, and pricing fields. Salesmate's product code maps to Nutshell's SKU field. If Salesmate products have multiple price variants, we create corresponding Nutshell products and note the pricing structure in the migration documentation for the customer's admin to finalize in the Nutshell UI.
Salesmate
Tag
Nutshell
Tag
1:1Salesmate tags on Contacts and Companies migrate to Nutshell tags on People and Companies respectively. Tags export from Salesmate as string arrays and import as Nutshell tag strings. The tag vocabulary is preserved without transformation, and tags that do not yet exist in Nutshell are created during the import phase.
Salesmate
Smart Flow Sequence Membership
Nutshell
Engagement Sequence Inventory
lossySmart Flow automation definitions are not fully accessible via the Salesmate public API, so the automation logic itself does not migrate. We export sequence membership: which contacts are enrolled in which Smart Flow campaigns, the enrollment date, and the campaign step each contact is on. This membership data is delivered as a written inventory document with recommended Nutshell Engagement Suite equivalents so the customer's admin can rebuild sequences post-migration.
Salesmate
Team Inbox
Nutshell
Custom People Fields
1:1Salesmate Team Inbox conversations have a threading model with per-message authorship and team assignment that has no native Nutshell equivalent. We preserve thread metadata (message body, sender, recipient, timestamp, thread ID) as custom fields on the related People record, and we store a thread summary in a notes field. The conversation body migrates as structured text, and the customer receives a thread-index document mapping each Salesmate thread to its corresponding People custom fields in Nutshell.
| Salesmate | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | People1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Deal | Opportunity1:1 | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Product | Product1:1 | Fully supported | |
| Tag | Tag1:1 | Fully supported | |
| Smart Flow Sequence Membership | Engagement Sequence Inventorylossy | Fully supported | |
| Team Inbox | Custom People Fields1: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.
Salesmate gotchas
API uses per-user access keys, not OAuth 2.0
v1 and v3 API versions are deprecated
Smart Flow credits consume based on unique contacts per campaign
All users must be on the same pricing plan
Team Inbox storage and permission model differs from standard CRM activity
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
Discovery and API credential provisioning
We audit the source Salesmate account: Contacts, Companies, Deals, Tasks, Products, Tags, and Team Inbox volume by module. We confirm the Salesmate plan tier and request a full-access admin Access Key for API operations. On the Nutshell side, we create a dedicated migration API key with impersonation permissions so that activity records are attributed to the correct owner User rather than the migration service account. We identify any Salesmate custom fields by module and generate the corresponding custom field definitions in Nutshell before data begins moving.
Schema pre-creation and custom field mapping
We create all Nutshell custom fields (People, Company, Opportunity, Task) to match the Salesmate custom field set before any data import. This ensures field IDs are available for mapping during the import phase and prevents records from being rejected due to unmapped required fields. We map Salesmate Tags to Nutshell Tags and create any missing tag values in the destination account. We configure the Nutshell pipeline stages to match the Salesmate deal pipeline stages, mapping stage names and probabilities.
Owner and User reconciliation
We extract every distinct Salesmate owner ID referenced on Contacts, Companies, Deals, and Tasks and match by email against the Nutshell Users table. Owners without a matching Nutshell User are held in a reconciliation queue. The customer provisions any missing Users in Nutshell before record import begins. This step is required before Deals and Tasks can be imported because owner assignment is a required field on Opportunity and Task in Nutshell.
Import in dependency order with reconciliation
We import in record-dependency order: Companies first (standalone), then People (with Company lookup resolved), then Opportunities (with Owner and Account lookups resolved), then Tasks (with Owner and Opportunity lookups resolved), then Products. Each phase produces a row-count reconciliation report comparing Salesmate source counts to Nutshell destination counts. Team Inbox data migrates as structured custom fields on the related People records with a thread-index document delivered alongside.
Smart Flow inventory delivery
We export Smart Flow sequence membership from Salesmate: for each active Smart Flow campaign, we list the enrolled contacts and their step position in the cadence. We deliver this as a written inventory document that maps each Salesmate Smart Flow to a recommended Nutshell Engagement Suite sequence configuration, including step type, delay, and action. This document is the handoff artifact for the customer's admin to rebuild sequences in Nutshell.
Cutover, validation, and post-migration support
We freeze Salesmate write access during cutover and run a delta migration to capture any records modified during the migration window. We validate a random sample of migrated records against the Salesmate source and deliver a final reconciliation report. We provide a one-week hypercare window to resolve any record-level issues raised by the customer's team. We do not rebuild Smart Flow automations or configure Nutshell workflows inside the migration scope; those are delivered as written specifications for the customer's admin to configure.
Platform deep dives
Salesmate
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 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 Salesmate and Nutshell.
Object compatibility
1 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
Salesmate: Not publicly documented in the API docs.
Data volume sensitivity
Salesmate 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 Salesmate to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Salesmate 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 Salesmate
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.
