CRM migration

Migrate from Bigin by Zoho CRM to Nutshell

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

Bigin by Zoho CRM logo

Bigin by Zoho CRM

Source

Nutshell

Destination

Nutshell logo

Compatibility

92%

11 of 12

objects map 1:1 between Bigin by Zoho CRM and Nutshell.

Complexity

BStandard

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Bigin by Zoho CRM to Nutshell is a simplification migration for teams that have outgrown Zoho's upgrade pressure and complexity overhead. Bigin organizes data around Pipelines containing sub-pipelines of Deals, with Contacts and Companies linked through lookups; Nutshell uses a flat People-Companies-Deals model with a single pipeline hierarchy and activity logging. We extract from Bigin via OAuth 2.0 REST API with credit-rate pacing (5,000 to 100,000 credits per 24 hours depending on plan), fall back to individual record API calls for Notes and Attachments which are excluded from Bigin's Bulk Read endpoint, and load into Nutshell via its REST API with standard rate-limit handling. Bigin Pipelines and sub-pipelines collapse into Nutshell pipeline stages, custom fields created via Bigin's Developer Console use the <namespace>__<field_label> convention and require explicit mapping against Nutshell's custom field schema, and user owners match by email address with unresolved owners held for admin provisioning. Workflows, automation rules, and telephony integrations do not migrate; we deliver a written inventory of every active workflow for the customer's admin to rebuild in Nutshell.

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

Bigin by Zoho CRM logo

Bigin by Zoho CRM

What's pushing teams away

  • Integration ecosystem is limited to roughly 100 connectors, forcing teams with complex tool stacks to build and maintain custom API workarounds that break frequently.
  • Teams that grow beyond five users quickly hit workflow caps and missing advanced CRM features, making Zoho CRM a necessary but costly upgrade mid-adoption.
  • Field mapping during data import is complicated and unintuitive, causing frustration during initial setup and blocking clean migrations from tools like Zoho Books.
  • Absence of EU-hosted infrastructure makes Bigin non-compliant for GDPR-sensitive companies in Europe, forcing an unwilling migration.
  • No built-in marketing automation means growing companies must purchase separate Zoho products or third-party tools, fragmenting the customer data view.

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 Bigin by Zoho CRM objects map to Nutshell

Each row shows how a Bigin by 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.

Bigin by Zoho CRM

Contact

maps to

Nutshell

People

1:1
Fully supported

Bigin Contacts map directly to Nutshell People. Standard fields (name, email, phone, address) migrate with type matching. Bigin's lifecycle fields (Created Time, Last Modified Time) preserve as People creation and update timestamps. Owner assignment maps from Bigin Owner (by email) to Nutshell user. We validate email uniqueness for dedupe before insert.

Bigin by Zoho CRM

Company

maps to

Nutshell

Company

1:1
Fully supported

Bigin Companies (API name: Accounts) map to Nutshell Companies with a direct name-to-name field mapping. Website, industry, phone, and address fields map directly. Company is created before any linked People import to satisfy the People.Company lookup. Any custom Company fields from Bigin map to Nutshell custom fields created during scoping.

Bigin by Zoho CRM

People-Company linkage

maps to

Nutshell

People.Company lookup

1:1
Fully supported

Bigin stores Contact-Company linkage via the Companies field on Contact. We resolve this at migration time by querying the Companies module first, then matching the Company ID or name on each Contact record before inserting People. Unmatched Companies are held in a reconciliation queue.

Bigin by Zoho CRM

Deal

maps to

Nutshell

Deal

1:1
Fully supported

Bigin Deals map to Nutshell Deals with the pipeline stage flattened from the sub-pipeline structure. Each sub-pipeline in Bigin becomes a Nutshell pipeline or a stage within the default pipeline depending on scoping. Deal amount, closing date, owner, and stage status map directly. Bigin's deal closing reason (custom field) migrates to a Nutshell custom field.

Bigin by Zoho CRM

Pipeline and Sub-pipeline

maps to

Nutshell

Pipeline stage

lossy
Fully supported

Bigin Pipelines contain sub-pipelines containing deal stages. Nutshell has a flat pipeline model with stage columns. We map each Bigin sub-pipeline to a named stage group in Nutshell, or create multiple Nutshell pipelines if the customer uses separate Pipelines for different business lines. Stage names and probabilities are preserved from Bigin.

Bigin by Zoho CRM

Product

maps to

Nutshell

Product

1:1
Fully supported

Bigin Products (name, unit price, tax, description) map to Nutshell products. Standard price fields migrate directly. Products are imported before Deals so that line items can reference them at migration time. Any custom product fields map to Nutshell custom product fields.

Bigin by Zoho CRM

Task

maps to

Nutshell

Activity

1:1
Fully supported

Bigin Tasks linked to Contacts, Companies, or Deals map to Nutshell Activities logged on the corresponding People, Company, or Deal record. Due date, status (open, completed), priority, and owner assignment preserve. Task description migrates as activity notes.

Bigin by Zoho CRM

Event

maps to

Nutshell

Activity

1:1
Fully supported

Bigin Events (calendar meetings) map to Nutshell Activities with type set to Meeting. Start time, end time, location, and description migrate. Recurring events from Bigin (which Bulk Read collapses into a single entity) are expanded back to individual Nutshell Activity records per occurrence if the recurrence pattern is parseable; otherwise a single summary record is created.

Bigin by Zoho CRM

Call

maps to

Nutshell

Activity (type: call)

1:1
Fully supported

Bigin Call logs (duration, subject, outcome) map to Nutshell Activities with type set to Call. Duration in seconds, call outcome, and notes migrate. Call recordings stored as attachments in Bigin migrate as Nutshell file attachments linked to the Activity.

Bigin by Zoho CRM

Note

maps to

Nutshell

Activity note

1:1
Fully supported

Bigin Notes are excluded from Bulk Read API and must be retrieved via individual record API calls. We query each Contact, Company, and Deal record individually to fetch its Notes module, then log them as Nutshell Activity notes on the parent record. This step consumes credits at a higher rate than bulk export and is budgeted separately during scoping.

Bigin by Zoho CRM

Attachment

maps to

Nutshell

File attachment

1:1
Fully supported

Bigin file attachments (excluded from Bulk Read) are retrieved via individual API calls and uploaded to Nutshell as file attachments linked to the parent People, Company, or Deal record. We flag any file exceeding Nutshell's attachment size limit during scoping and discuss handling options (chunking, URL reference, or exclusion).

Bigin by Zoho CRM

User (Owner)

maps to

Nutshell

User

1:1
Fully supported

Bigin Owner records (user name, email, role) are matched by email against Nutshell users. Owners without a matching Nutshell user are held in a reconciliation queue for the customer admin to provision. Active status in Bigin maps to active status in Nutshell unless the admin specifies otherwise.

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.

Bigin by Zoho CRM logo

Bigin by Zoho CRM gotchas

High

Credit-based API limits vary by plan and can throttle migrations

High

Bulk Read API excludes Notes, Attachments, Emails, and cross-module records

Medium

Import field mapping is complicated and unintuitive for users

Medium

Undo import window is limited to 30 days

Low

Free plan is single-user with a 500-record hard cap

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

  • Bigin Bulk Read excludes Notes, Attachments, Emails, and cross-module records

    Bigin's Bulk Read endpoint returns only Contacts, Companies, Deals, Products, Tasks, Events, and Calls in compressed CSV format. Notes and Attachments require individual record API calls, which consume 1 credit per call versus 1 credit for bulk operations, and can exhaust daily credit budgets on Free and Express plans during large migrations. We scope Note and Attachment counts before extraction, budget individual API calls against the account's credit limit, and pace calls to avoid hitting the 24-hour credit window mid-migration. If the account is on the Free plan (5,000 credits) and has more than 5,000 Notes, we flag the overage and schedule the migration in two or more credit windows.

  • Bigin custom fields use namespace-prefixed API names requiring explicit mapping

    Custom fields created via Bigin's Developer Console follow the <topping_namespace>__<field_label> naming convention (double underscore separator). These do not have direct equivalents in Nutshell, which creates custom fields inline without namespace prefixes. We enumerate every Bigin custom field during scoping, validate their types (text, picklist, number, date, currency), create matching Nutshell custom fields, and map them explicitly in the transform layer. Unmapped custom fields are listed in the handoff document for the customer admin to review.

  • Sub-pipeline hierarchy in Bigin does not map directly to Nutshell's flat pipeline

    Bigin Pipelines contain sub-pipelines which contain stages. A single Bigin account can have up to 3 pipelines on Express and unlimited on Premier, each with multiple sub-pipelines. Nutshell uses a flat pipeline with stage columns grouped by status (open, won, lost). We flatten the sub-pipeline stages to Nutshell stages during transformation, preserving stage names and probability percentages. If the customer uses separate Bigin Pipelines for distinct business lines, we create separate Nutshell pipelines. Stage ordering is preserved from Bigin left-to-right.

  • Bigin API credit consumption varies by operation type and plan tier

    Bigin's credit system charges 1 credit per standard API call, 3 credits per Get Records with custom view ID, and 50 credits per Bulk Read initialization. The Free plan caps at 5,000 credits per 24 hours; paid plans get 50,000 plus 250 per user license up to 100,000. We monitor credit consumption during extraction and pace the migration to stay within daily limits. If a 24-hour window closes mid-migration, we resume from the last successful checkpoint rather than re-extracting completed modules.

Migration approach

Six steps for a successful Bigin by Zoho CRM to Nutshell data migration

  1. Scoping and credit budget estimation

    We audit the Bigin account across plan tier, record counts per module, custom field inventory (with namespace-prefixed names), pipeline and sub-pipeline structure, and owner list. We estimate the API credit cost of the full extraction including the individual Note and Attachment calls required for each module, then compare against the account's daily credit allowance to determine whether migration requires single or multi-day extraction windows. The scoping output is a written migration scope document with object counts, custom field list, pipeline mapping plan, and credit budget.

  2. Nutshell schema preparation and custom field creation

    We create the Nutshell custom fields required for any Bigin custom field mappings before any data extraction begins. We configure pipeline stages in Nutshell to match the flattened sub-pipeline structure, set stage probabilities, and configure any custom deal fields. Custom field types are matched (text to text, picklist to single-select, multi-select to multi-select, currency to currency) before extraction so the transform layer can write typed data.

  3. Bulk extraction with credit-pacing and checkpointing

    We extract Bigin data in dependency order: Companies first (no dependencies), then Products, then Contacts (with Company linkage resolved), then Deals (with Contact and Company lookups resolved), then Tasks, Events, and Calls. Notes and Attachments are extracted via individual record API calls after bulk extraction completes, paced to stay within credit limits. If the 24-hour credit window closes mid-extraction, we record a checkpoint and resume from the next unprocessed record ID in the next window.

  4. Owner reconciliation and user provisioning

    We extract every distinct Bigin Owner referenced on Contacts, Companies, Deals, Tasks, Events, and Calls and match by email against Nutshell's user list. Owners without a matching Nutshell user are held in a reconciliation queue. The customer admin provisions any missing Nutshell users (active or inactive status per their choice) before record import begins. Migration does not proceed past owner reconciliation because owner lookups are required on most record types.

  5. Production import in dependency order

    We import data into Nutshell in record-dependency order: Companies first, then People (with Company lookup resolved), then Products, then Deals (with People and Company lookups resolved), then Activities (Tasks, Events, Calls, Notes, Attachments) linked to their parent records. Each phase emits a row-count reconciliation report showing records extracted, records loaded, and any records skipped or held for reconciliation. We handle Nutshell API rate limits with exponential backoff and batch chunking.

  6. Cutover, validation, and workflow handoff

    We freeze Bigin writes during cutover, run a final delta migration of any records created or modified during the migration window, then enable Nutshell as the system of record. We deliver a written inventory of every Bigin workflow and automation rule (name, trigger, conditions, actions) for the customer's admin to rebuild in Nutshell. We support a five-day hypercare window for reconciliation issues raised by the customer's team. We do not rebuild Bigin workflows, automation rules, or telephony integrations in Nutshell; these are separate configuration engagements.

Platform deep dives

Context on both ends of the pair

Bigin by Zoho CRM logo

Bigin by Zoho CRM

Source

Strengths

  • Lowest entry cost of any serious CRM at $7 per user per month with a genuine free tier for solo operators.
  • Pipeline-centric design that mirrors how small sales teams actually think about their work.
  • Ready-made templates for common business types require no customization to get started.
  • Native two-way sync with full Zoho CRM lets organizations mix lightweight Bigin users with power Zoho CRM users.
  • Built-in undo import capability allows rollback of bad imports within 30 days.

Weaknesses

  • Limited third-party integrations forces reliance on custom API workarounds that require ongoing maintenance.
  • Workflow and automation caps on lower tiers create artificial barriers that push teams toward Zoho CRM upgrades.
  • No EU-hosted infrastructure makes Bigin non-compliant for GDPR-regulated businesses in Europe.
  • No marketing automation features require separate tool purchases that fragment customer data.
  • Import complexity from other Zoho products like Zoho Books requires manual field mapping work.
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 Bigin by Zoho CRM 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

    C

    Bigin by Zoho CRM: Credit-based system: 5,000 credits/24h on Free; 50,000 + (user licenses × 250) capped at 100,000/24h on Express, Premier, and Zoho One. Concurrency cap of 5 simultaneous API calls per user on Free, 10 on paid editions, with a sub-cap of 10 across resource-intensive operations..

  • Data volume sensitivity

    A

    Bigin by Zoho CRM exposes a bulk API — large-volume migrations stream efficiently.

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Migrations under 5,000 Contacts, 2,000 Deals, and moderate Note and Attachment volumes land in two to four weeks. Migrations with Premier-tier Bigin accounts (up to 100,000 records, multiple sub-pipelines, large attachment volumes requiring individual API calls) extend to five to eight weeks because of credit-budget pacing during extraction, sub-pipeline-to-stage mapping complexity, and the individual Note retrieval calls that Bulk Read excludes.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Bigin by Zoho CRM.
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