CRM migration

Migrate from Nutshell to Zoho CRM

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

Nutshell logo

Nutshell

Source

Zoho CRM

Destination

Zoho CRM logo

Compatibility

60%

6 of 10

objects map 1:1 between Nutshell and Zoho CRM.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Try the reverse

Zoho CRM
Nutshell

Overview

What this migration involves

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.

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

Nutshell logo

Nutshell

What's pushing teams away

  • Reporting features are considered weak by users—many resort to exporting data and performing analysis in Excel rather than using built-in dashboards.
  • Limited customization options for workflows, fields, and pipeline configurations compared to HubSpot or Salesforce, frustrating power users.
  • Mobile app is described as stripped-down relative to desktop, lacking many features available in the full web application.
  • Jack-of-all-trades positioning means Nutshell lacks the depth in any single area—marketing, service, or advanced sales automation—that growing teams eventually require.
  • Email integration limitations documented by TrustRadius reviewers, with some teams reporting reliability issues during high-volume campaign sends.

Choosing

Zoho CRM logo

Zoho CRM

What's pulling them in

  • Free tier is genuinely usable for up to 3 users with leads, pipeline management, and email tracking — no credit card required, making it easy to evaluate before committing.
  • Pricing undercuts Salesforce by 80–90% at equivalent feature tiers, with Enterprise plans offering capabilities that cost 3–4× more on competing platforms.
  • Deep ecosystem of 45+ integrated apps (Books, Desk, Creator, Campaigns) means companies already in the Zoho suite get native integrations without third-party connectors.
  • Highly customizable: custom modules, custom fields, Canvas drag-and-drop layouts, and Blueprint workflow automation without requiring developer resources.
  • Small-business reviewers highlight real-time team visibility, daily time savings of 60–90 minutes, and the ability to mold the CRM to any industry vertical.

Object mapping

How Nutshell objects map to Zoho CRM

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

maps to

Zoho CRM

Contact (qualified) or Lead (unqualified)

1:many
Fully supported

Nutshell 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

maps to

Zoho CRM

Account

1:1
Fully supported

Nutshell 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

maps to

Zoho CRM

Lead

1:1
Fully supported

Nutshell'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

maps to

Zoho CRM

Deal

1:1
Fully supported

Nutshell 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

maps to

Zoho CRM

Stage (picklist value)

lossy
Fully supported

Nutshell 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)

maps to

Zoho CRM

Task and Event

1:1
Fully supported

Nutshell 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

maps to

Zoho CRM

Custom Fields

1:1
Fully supported

Nutshell 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

maps to

Zoho CRM

Tag

lossy
Fully supported

Nutshell 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

maps to

Zoho CRM

User

1:1
Fully supported

Nutshell 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

maps to

Zoho CRM

Attachments (manual re-attachment)

lossy
Not supported

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

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.

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

Zoho CRM logo

Zoho CRM gotchas

High

API access requires Professional tier or above

High

Subform fields do not export cleanly via CSV

Medium

API credit consumption is non-linear

Medium

Export download links expire in 7 days

Medium

Owner (User) assignments require pre-mapped user IDs

Pair-specific challenges

  • Nutshell's JSON-RPC API requires paginated extraction

    Nutshell provides no bulk export endpoint. Extracting large datasets (15,000+ records) requires cursor-based pagination across JSON-RPC requests with careful rate-limit handling. We implement exponential backoff between requests and chunk records into batches of 200. Extraction time scales linearly with record count and must be accounted for in migration timeline planning. Accounts with 50,000+ total records across People, Companies, Deals, and Activities may require an additional one to two weeks for extraction alone. We validate the extraction rate during discovery to provide an accurate timeline projection.

  • Zoho CRM Free and Standard tier restrictions block custom fields

    Zoho CRM Free edition does not support custom fields at all. Standard tier supports custom fields but excludes Lookup fields (for cross-module references) and Formula fields. If the Nutshell migration includes custom fields that require lookups to other modules, the customer must upgrade to Zoho Professional or higher before migration begins. We pre-scan Nutshell custom fields during discovery and confirm the required Zoho edition tier before initiating migration to avoid mid-migration tier upgrades.

  • Lead-to-Contact conversion in Zoho has no automated Nutshell equivalent

    Nutshell uses a flat People model where every contact lives at the same level regardless of qualification. Zoho requires an explicit Lead record for unqualified prospects and a Contact record (attached to an Account) for qualified contacts. We design the split rule during scoping based on the customer's Nutshell record data (company association, deal association, person_type field). Records without a Company association and no pipeline activity default to Zoho Lead; records with active deals or a Company association default to Zoho Contact.

  • Email sequences, Nutshell IQ, and automation configs do not migrate

    Nutshell email sequences (Pro+ feature) and Nutshell IQ enrichment data are server-side configurations and API-inaccessible data that we cannot migrate. We document every active Nutshell sequence, its trigger conditions, step cadence, and body templates during discovery and deliver a written rebuild checklist mapped to Zoho CRM Workflow Rules and Blueprint sequences. The customer's admin rebuilds sequences in Zoho post-migration using the documented parameters.

  • Attachment binary blobs require manual re-attachment

    The Nutshell API does not surface binary file attachment data. We export attachment metadata (filename, URL, associated record ID) and deliver it as a re-attachment checklist. The customer downloads the actual files from Nutshell via the full data backup tool and uploads them to Zoho CRM manually or via Zoho's file upload API after migration. We flag this in the pre-migration scope document and provide a structured CSV mapping Nutshell attachment URLs to the target Zoho record IDs for efficient manual re-attachment.

Migration approach

Six steps for a successful Nutshell to Zoho CRM data migration

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

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

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

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

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

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

Context on both ends of the pair

Nutshell logo

Nutshell

Source

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
Zoho CRM logo

Zoho CRM

Destination

Strengths

  • Generous free tier (3 users) with real CRM functionality — no artificial feature restrictions that prevent valid use cases.
  • Per-seat pricing is transparent and predictable; no contact-based billing surprises that inflate monthly invoices.
  • Blueprint visual workflow builder lets sales ops teams automate stage progressions without developer involvement.
  • Canvas drag-and-drop layout editor lets non-technical users customize module views and forms per role.
  • Active development cadence: API v8 is well-documented, supports bulk endpoints, and COQL queries handle complex filtering.

Weaknesses

  • Poor support quality and inconsistent SLA — Enterprise tier requires 50+ user minimum for Priority Phone support.
  • Daily export limits in the UI vary by plan tier, making large dataset extraction slow and planning-dependent.
  • Zia AI features are gated behind $40+/user Enterprise tier, not available to most SMB customers who chose Zoho for cost savings.
  • User-reported occasional UI inconsistencies and performance slowdowns on large datasets with many custom fields.
  • No EU-hosted option limits appeal for GDPR-sensitive companies; some competitors offer data residency guarantees Zoho does not.

Complexity grading

How hard is this migration?

Standard CRM migration. 1 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 Nutshell and Zoho CRM.

  • Object compatibility

    B

    1 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

    Nutshell: Not publicly documented in summary form..

  • Data volume sensitivity

    A

    Nutshell exposes a bulk API — large-volume migrations stream efficiently.

Estimator

Estimate your Nutshell to Zoho CRM 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 Nutshell to Zoho CRM data migrations

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

Can't find your answer?

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 consultation

Most migrations land between three and five weeks for accounts under 15,000 People and 3,000 Deals with no complex custom field dependencies. Migrations with large engagement histories (over 200,000 activity records), multi-pipeline Nutshell setups, or extensive custom field configurations move to eight to twelve weeks. Nutshell's JSON-RPC paginated API adds extraction time proportional to record volume; we validate the extraction rate during discovery to provide an accurate projection before the project begins.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Nutshell.
Land in Zoho CRM, 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