CRM migration
Field-level mapping, validation, and rollback between Zoho CRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Zoho CRM
Source
Nutshell
Destination
Compatibility
9 of 10
objects map 1:1 between Zoho CRM and Nutshell.
Complexity
BStandard
Timeline
2-4 weeks
Try the reverse
Overview
Moving from Zoho CRM to Nutshell is a consolidation migration: Zoho maintains separate Leads and Contacts as distinct objects with a Convert action that links the Contact to an Account, while Nutshell uses a single People record type for both prospects and customers. We split the migration design at scoping by establishing a Zoho Lifecycle Stage or Lead Status rule to determine which Zoho Leads become Nutshell People records and which require Account attachment on import. Zoho subform data (line items within Quotes, Sales Orders, and Invoices) is stored as separate related records and requires a separate API pass; we reconstruct the parent-child hierarchy and upsert both layers into Nutshell's equivalent structure. Nutshell's native Import2 tool handles straightforward CSV-based Contacts, Companies, and Deals but has limited support for custom fields, multi-select picklists, attachments, and custom modules. We use Zoho's REST API v8 for extraction when Professional tier or above is available, falling back to manual CSV export for Free and Standard plans which do not include API access. Blueprints, workflow rules, and multi-pipeline configurations do not migrate as code; we deliver a written inventory of each for the customer's admin to rebuild in Nutshell or via a third-party automation layer.
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
Zoho CRM platform overview
Scorecard, SWOT, gotchas, and pricing for Zoho CRM.
Destination platform
Nutshell platform overview
Scorecard, SWOT, gotchas, and pricing for Nutshell.
Data migration guide
The complete Nutshell migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Source platform guide
Zoho CRM migration guide
Understand the data you're exporting from Zoho CRM before mapping it.
Destination checklist
Nutshell migration checklist
Pre- and post-cutover tasks for moving onto Nutshell.
Source checklist
Zoho CRM migration checklist
Exit checklist for unwinding your Zoho CRM 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 Zoho CRM 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.
Zoho CRM
Lead
Nutshell
Person (People)
1:1Zoho Leads map to Nutshell People records. We apply a scoping-stage rule based on Zoho Lead Status or Lifecycle Stage to determine whether the migrated Lead should be treated as a prospect (unqualified) or customer (qualified). Zoho's Lead fields including Phone, Email, Company, Last_Name, and any custom fields map to equivalent Nutshell People fields. Zoho Lead Source maps to Nutshell's Source field or a custom picklist. The original Lead creation date migrates as a custom field rather than overwriting Nutshell's native created_at timestamp.
Zoho CRM
Contact
Nutshell
Person (People)
1:1Zoho Contacts map to Nutshell People records. The key mapping decision is whether a Zoho Contact that was converted from a Lead should inherit the same People record or create a new one. We use Zoho's CONTACT_ID as an external ID to upsert rather than re-create, avoiding duplicates when both a Lead and a Contact exist for the same person. Account lookup on the Zoho Contact maps to a Nutshell Company record via the Account ID resolution. Email, phone, address, and custom fields map directly; multi-select picklists map to Nutshell tag values.
Zoho CRM
Account (Company)
Nutshell
Company
1:1Zoho Accounts map to Nutshell Companies. We extract Account_Name as the Company name, Website as the domain field, and Industry as a custom field or category. Account-to-Contact relationships are preserved by sequencing Account import before Contact import so that the Company lookup is available at Contact insert time. Multiple address records on Zoho Accounts are consolidated into a single Nutshell Company address with the primary address prioritized.
Zoho CRM
Deal
Nutshell
Deal
1:1Zoho Deals map to Nutshell Deals with Stage, Amount, Closing Date, and Owner preserved. Zoho's pipeline and stage names map to Nutshell's stage values. If Zoho multi-pipeline is in use (Professional tier or above), we consolidate all pipelines into Nutshell's single pipeline structure and document which stages belong to which original pipeline in a custom field for reporting continuity. Closed-Won and Closed-Lost statuses migrate with the original reason if captured as custom fields.
Zoho CRM
Product
Nutshell
Product
1:1Zoho Products map to Nutshell Products. Product_Code maps to the Nutshell Product Code field; Product_Name maps to the Name field; Unit_Price maps to Price. We migrate Products before any Quote or Sales Order subform data so that product references resolve at migration time. Nutshell Products are linked to Deals via Product Line Items.
Zoho CRM
Tasks, Events, Calls
Nutshell
Activities
1:1Zoho activity records (Tasks, Events, Calls) map to Nutshell Activity records. We preserve the parent linkage by resolving the Zoho CONTACT_ID or ACCOUNT_ID to the corresponding Nutshell People or Company external ID at migration time. Task Status, Priority, Due Date, and Subject map directly; Call duration and disposition migrate to custom Activity fields if present in Zoho. Activity timestamps preserve the original Zoho created_at date to maintain timeline continuity.
Zoho CRM
Notes
Nutshell
Notes
1:1Zoho Notes map to Nutshell Notes attached to the parent People or Company record via the external ID lookup. Rich text formatting in Zoho Notes is preserved as plain text in Nutshell Notes. Notes linked to Deals migrate with the Deal association maintained where Nutshell's activity model supports Deal-linked notes.
Zoho CRM
Attachments
Nutshell
Files
1:1Zoho Attachments stored via the Attachments API endpoint do not appear in standard CSV exports and require a separate API pass. We extract each attachment file and its parent record lookup ID, then upload to Nutshell as a File linked to the corresponding People, Company, or Deal record. If the source Zoho plan lacks API access, we flag attachment extraction as requiring manual download or a Zoho partner-assisted export; Nutshell's Import2 tool does not handle attachment migration natively.
Zoho CRM
Users
Nutshell
Users
1:1Zoho User records carry email, name, and role assignments that map to Nutshell User accounts. We resolve Zoho Owner IDs to Nutshell Users by email match at migration time. Any Zoho Owner without a matching Nutshell User goes to a reconciliation queue for the customer to provision before record import resumes, preventing Owner assignment errors on Deals and Activities.
Zoho CRM
Tags
Nutshell
Tags
lossyZoho Tags stored as multi-checkbox or multi-select properties on Leads, Contacts, Accounts, or Deals map to Nutshell Tags. We parse tag arrays during extraction and create matching tag values in Nutshell, then attach them to the corresponding People, Company, or Deal record. Zoho's per-module tagging translates to Nutshell's cross-record tagging model where the same tag can apply to People, Companies, and Deals.
| Zoho CRM | Nutshell | Compatibility | |
|---|---|---|---|
| Lead | Person (People)1:1 | Fully supported | |
| Contact | Person (People)1:1 | Fully supported | |
| Account (Company) | Company1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Product | Product1:1 | Fully supported | |
| Tasks, Events, Calls | Activities1:1 | Mapping required | |
| Notes | Notes1:1 | Fully supported | |
| Attachments | Files1:1 | Mapping required | |
| Users | Users1:1 | Mapping required | |
| Tags | Tagslossy | Mapping required |
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.
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
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 Zoho plan verification
We audit the source Zoho CRM across plan tier, active modules, custom fields, pipeline count, active Blueprints, and engagement volume. We confirm API entitlement by checking the plan tier: Professional or above allows REST API v8 extraction; Standard and Free require CSV export with the subform and attachment limitations documented. The discovery output is a written scope document listing all Zoho modules in use, custom field inventory, pipeline and stage mappings, and the estimated record counts per object. We also identify any Zoho custom modules requiring schema introspection via GET /settings/fields.
Split rule definition and Nutshell schema setup
We define the Lead-to-People split rule based on Zoho Lead Status values and document it as a migration transform. We set up the Nutshell target schema including custom fields (matched to Zoho custom field names and types), stage values (mapped from Zoho pipeline stages), and Company records that will receive Contact-linked People. Nutshell's single pipeline structure means any Zoho multi-pipeline configuration requires a documented consolidation plan. We configure tags in Nutshell to receive Zoho multi-select picklist values.
Data extraction from Zoho
For Zoho Professional and above, we use the REST API v8 with COQL queries and paginated record fetches, implementing exponential backoff on 429 responses and credit-aware query batching to stay within the rolling 24-hour API credit window. For Zoho Standard and Free plans, we run CSV exports immediately upon session start (to avoid the seven-day link expiry) and supplement with manual subform exports for line items. We extract Users first to build the Owner email-to-Nutshell-User mapping, then proceed to Accounts, Leads, Contacts, Deals, Products, Activities, Notes, and Attachments in dependency order.
Sandbox migration and reconciliation
We run a test migration into a Nutshell trial or sandbox environment using a representative data subset. The customer reconciles record counts (People in, Companies in, Deals in, Activities in), spot-checks 20-30 records against the Zoho source for field-level accuracy, and validates that multi-select values and tags appear correctly. Any mapping corrections and custom field type adjustments happen at this stage before production migration begins.
Production migration in dependency order
We run production migration in record-dependency sequence: Nutshell Users are validated (manual provisioning if needed), Companies are imported first (as the lookup target for Contacts), People are imported using the Lead-Contact split rule with Account lookups resolved, Deals are imported with Owner assignments and stage mapping, Products are imported before any line item data, Activities and Notes are imported with parent record lookups resolved via external IDs, and Attachments are uploaded last. Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, delta sync, and Blueprint handoff
We freeze Zoho writes during a cutover window, run a final delta migration of any records modified during the migration window, then enable Nutshell as the system of record. We deliver the Blueprint and workflow inventory document to the customer's admin with a recommendation for Nutshell native automation or Zapier/Make rebuild. We support a one-week post-migration window to resolve reconciliation issues. We do not rebuild Zoho Blueprints as Nutshell rules or Zapier workflows as part of the migration scope; that is a separate engagement.
Platform deep dives
Zoho CRM
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 Zoho CRM 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
Zoho CRM: Starter: 500 req/min | Professional: 2,500 req/min | Enterprise: 10,000 req/min, plus a credit-based system for complex queries (1–3 credits per COQL fetch).
Data volume sensitivity
Zoho CRM 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 Zoho CRM to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Zoho CRM 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 Zoho CRM
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.