CRM migration
Field-level mapping, validation, and rollback between Nutshell and Zoho CRM. We move data and schema; workflows are rebuilt natively in Zoho CRM.
Nutshell
Source
Zoho CRM
Destination
Compatibility
6 of 10
objects map 1:1 between Nutshell and Zoho CRM.
Complexity
BStandard
Timeline
3-5 weeks
Try the reverse
Overview
Moving from Nutshell to Zoho CRM is a structural migration that resolves fundamental schema differences. Nutshell uses a flat People-attached-to-Companies hierarchy with Leads as separate records; Zoho CRM splits unqualified prospects into Leads and qualified contacts into Contacts attached to Accounts. We handle that mapping at scoping, preserving Nutshell's People records as Zoho Contacts (or Leads for unqualified records) and converting Companies to Accounts. Pipeline stages migrate as Zoho picklist values, and the full activity timeline (calls, emails, meetings, tasks) transfers into Zoho Tasks and Events. Nutshell's JSON-RPC API requires paginated extraction with rate-limit handling that adds extraction time on large datasets. We do not migrate email sequences, Nutshell IQ enrichment data, or attachments (binary blobs not accessible via API). We deliver a written automation inventory for Zoho Blueprint rebuild post-migration.
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.
Source platform
Nutshell platform overview
Scorecard, SWOT, gotchas, and pricing for Nutshell.
Destination platform
Zoho CRM platform overview
Scorecard, SWOT, gotchas, and pricing for Zoho CRM.
Data migration guide
The complete Zoho CRM migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Source platform guide
Nutshell migration guide
Understand the data you're exporting from Nutshell before mapping it.
Destination checklist
Zoho CRM migration checklist
Pre- and post-cutover tasks for moving onto Zoho CRM.
Source checklist
Nutshell migration checklist
Exit checklist for unwinding your Nutshell setup cleanly.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Nutshell object lands in Zoho CRM, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Nutshell
People
Zoho CRM
Contact (qualified) or Lead (unqualified)
1:manyNutshell People records map to Zoho CRM Contacts if the record is sales-qualified or has an associated Company. Unqualified Nutshell People with no company association and no deal history map to Zoho Leads. We compute the split at migration time using Nutshell's person_type property and any associated pipeline activity. The original Nutshell person_type and any owner assignment preserve in Zoho custom fields for audit. Phone, email, address, and social media fields map directly to Zoho's standard Contact fields.
Nutshell
Company
Zoho CRM
Account
1:1Nutshell Companies map directly to Zoho CRM Accounts. The company name becomes Account Name, and domain information maps to the Website field. We use company name as the dedupe key during import. Account is created before any Contact import so that the Account-Contact lookup relationship is satisfied at Contact insert time. Multi-address Company records preserve the primary address in the Account and additional addresses in Account custom fields.
Nutshell
Lead
Zoho CRM
Lead
1:1Nutshell's separate Lead records map directly to Zoho CRM Leads. Nutshell Lead custom fields migrate to Zoho Lead custom fields. Lead status values (New, Contacted, Qualified, Disqualified) map to Zoho Lead Status picklist values. We preserve the original Nutshell lead score in a Zoho custom field for sales prioritization after migration.
Nutshell
Deal
Zoho CRM
Deal
1:1Nutshell Deals map to Zoho CRM Deals. The deal name, amount, expected close date, and owner migrate directly. We map Nutshell pipeline and stage names to Zoho Stage picklist values, creating new stage values in Zoho if the Nutshell stage names do not already exist. The deal's associated Company resolves to the Zoho Account lookup; the associated Person resolves to the Contact lookup.
Nutshell
Pipeline Stage
Zoho CRM
Stage (picklist value)
lossyNutshell pipeline stages migrate as Zoho CRM Stage picklist values on the Deal module. Stage probability percentages migrate to Zoho Probability fields. Each Nutshell pipeline becomes a separate set of Stage values. If Nutshell stages include win/loss statuses, we map those to Zoho Stage values with the Closed Won and Closed Lost indicators set per Zoho's stage configuration.
Nutshell
Activity (calls, emails, meetings, tasks)
Zoho CRM
Task and Event
1:1Nutshell Activities map to Zoho Tasks (for calls and tasks) and Events (for meetings). Email activities transfer as Zoho Tasks with the email body preserved. The activity timestamp, duration, and outcome map to Zoho Task fields. Each Activity's associated Person and Company resolve to Zoho Contact and Account lookups. Activity history ordering preserves by setting the Zoho Activity Date to the original Nutshell timestamp.
Nutshell
Custom Fields
Zoho CRM
Custom Fields
1:1Nutshell custom fields on People, Companies, and Leads enumerate and recreate as Zoho CRM custom fields before data import. Text fields map to Zoho Text, numeric fields to Zoho Number or Decimal, date fields to Zoho Date, and picklist fields to Zoho Picklist. Custom fields are created per module in Zoho before migration begins. Note that Zoho Standard tier does not include Lookup and Formula custom field types; we flag this and recommend Professional tier if the customer requires cross-module lookup fields.
Nutshell
Tag
Zoho CRM
Tag
lossyNutshell tags on People and Companies migrate to Zoho CRM Tags. Tags used for record categorization map to Zoho's native tagging feature. We flatten any tag hierarchy during transfer since Nutshell does not expose hierarchical tag structures via API. Tags that represent industry, segment, or lifecycle stage may alternatively map to Zoho custom picklist fields based on the customer's preference during scoping.
Nutshell
Owner/User
Zoho CRM
User
1:1Nutshell Users referenced as record owners map to Zoho CRM Users by email match. We extract all distinct Nutshell owners from People, Companies, Deals, and Activities and match by email against the Zoho destination User table. Owners without a matching Zoho User go to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Nutshell owners map to inactive Zoho users with the OwnerId preserved in a custom field for audit.
Nutshell
Attachments
Zoho CRM
Attachments (manual re-attachment)
lossyThe Nutshell API exposes attachment metadata (filenames, URLs, sizes) but does not return binary file blobs. We export attachment filenames, URLs, and record associations and deliver this as a structured re-attachment checklist. The customer's admin downloads files from Nutshell (via manual export or Nutshell's full backup tool) and re-uploads them to Zoho CRM after migration. This is a known limitation of Nutshell's JSON-RPC API and cannot be resolved programmatically.
| Nutshell | Zoho CRM | Compatibility | |
|---|---|---|---|
| People | Contact (qualified) or Lead (unqualified)1:many | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline Stage | Stage (picklist value)lossy | Fully supported | |
| Activity (calls, emails, meetings, tasks) | Task and Event1:1 | Fully supported | |
| Custom Fields | Custom Fields1:1 | Fully supported | |
| Tag | Taglossy | Fully supported | |
| Owner/User | User1:1 | Fully supported | |
| Attachments | Attachments (manual re-attachment)lossy | Not 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.
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
Zoho CRM gotchas
API access requires Professional tier or above
Subform fields do not export cleanly via CSV
API credit consumption is non-linear
Export download links expire in 7 days
Owner (User) assignments require pre-mapped user IDs
Pair-specific challenges
Migration approach
Discovery and Zoho edition assessment
We audit the source Nutshell account across tiers (Foundation/Pro/Business/Enterprise), API endpoint connectivity, custom field definitions per object, active pipeline count and stage definitions, engagement volume (calls, emails, meetings, tasks), and any active email sequences on Pro and Business plans. We pair this with a Zoho CRM edition assessment: Standard ($14/user) covers basic migrations without custom field lookups; Professional ($23/user) adds advanced analytics, workflow rules, and Blueprint support; Enterprise ($47/user) adds AI (Zia), custom data types, and unlimited workflows. The discovery output is a written scope document with Nutshell record counts, Zoho edition recommendation, and a custom field audit listing every field requiring recreation in Zoho.
Zoho schema provisioning and custom field creation
We provision the destination Zoho CRM schema before any data moves. This includes creating every Nutshell custom field in Zoho with the appropriate field type (Text, Number, Decimal, Date, Picklist, Multi-select), configuring the Lead-Contact split rule for unqualified versus qualified Nutshell People records, creating Deal Stage picklist values from Nutshell pipeline stages (including probability percentages), and setting up Account-Contact lookup relationships. Schema provisioning occurs in a Zoho sandbox or the live account depending on customer preference. Custom field types are validated against Zoho's field type constraints before migration begins.
Sandbox migration and reconciliation
We run a full migration into a Zoho sandbox environment using production-equivalent record volume. The customer's RevOps lead reconciles record counts (People in, Companies in, Deals in, Activities in), spot-checks 20-30 records against the Nutshell source for field-level accuracy, and validates the Lead-Contact split behavior. Any field mapping corrections, custom field type adjustments, or stage value additions happen in sandbox before production migration begins. This step prevents mid-migration schema changes that would require re-extraction from Nutshell.
Owner reconciliation and User provisioning
We extract every distinct Nutshell User referenced as an owner on People, Companies, Deals, and Activities and match by email against the Zoho destination Users table. Owners without a matching Zoho User go to a reconciliation queue. The customer's Zoho admin provisions any missing Users in Zoho (active for current team members, inactive for departed Nutshell users whose records should be preserved). Owner resolution must complete before record import because OwnerId is a required field on most Zoho standard objects.
Production migration in dependency order
We run production migration in record-dependency order: Accounts (from Nutshell Companies), Contacts (with AccountId resolved from Company mapping), Leads (applying the split rule for unqualified People), Deals (with AccountId, ContactId, and OwnerId resolved), Activities (Tasks and Events via Zoho REST API with batch chunking), Custom field values (per-object mapping validated in sandbox), and Tags (applied post-import to avoid import-order dependency). Each phase emits a row-count reconciliation report. We use Zoho's bulk import API for large record sets (5,000+ records per module) with exponential backoff on rate-limit responses.
Cutover, validation, and automation rebuild handoff
We freeze Nutshell writes during the cutover window, run a final delta migration of any records created or modified during migration, then enable Zoho CRM as the system of record. We deliver the automation inventory document listing every Nutshell email sequence and workflow rule with its trigger, conditions, and recommended Zoho Blueprint or Workflow Rule equivalent. We support a 72-hour hypercare window to resolve reconciliation issues reported by the customer's sales team. We do not rebuild Nutshell sequences as Zoho Workflow Rules inside the migration scope; that is a separate engagement or an internal admin task.
Platform deep dives
Nutshell
Source
Strengths
Weaknesses
Zoho CRM
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 Nutshell and Zoho CRM.
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
Nutshell: Not publicly documented in summary form..
Data volume sensitivity
Nutshell exposes a bulk API — large-volume migrations stream efficiently.
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 Nutshell to Zoho CRM migration scoping. Not seeing yours? Book a call.
Walk through your Nutshell to Zoho CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Nutshell
Other ways to arrive at Zoho CRM
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.