CRM migration
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
Source
Nutshell
Destination
Compatibility
11 of 12
objects map 1:1 between Bigin by Zoho CRM and Nutshell.
Complexity
BStandard
Timeline
2-4 weeks
Overview
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.
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 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
Nutshell
People
1:1Bigin 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
Nutshell
Company
1:1Bigin 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
Nutshell
People.Company lookup
1:1Bigin 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
Nutshell
Deal
1:1Bigin 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
Nutshell
Pipeline stage
lossyBigin 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
Nutshell
Product
1:1Bigin 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
Nutshell
Activity
1:1Bigin 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
Nutshell
Activity
1:1Bigin 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
Nutshell
Activity (type: call)
1:1Bigin 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
Nutshell
Activity note
1:1Bigin 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
Nutshell
File attachment
1:1Bigin 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)
Nutshell
User
1:1Bigin 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.
| Bigin by Zoho CRM | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | People1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| People-Company linkage | People.Company lookup1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline and Sub-pipeline | Pipeline stagelossy | Fully supported | |
| Product | Product1:1 | Fully supported | |
| Task | Activity1:1 | Fully supported | |
| Event | Activity1:1 | Fully supported | |
| Call | Activity (type: call)1:1 | Fully supported | |
| Note | Activity note1:1 | Fully supported | |
| Attachment | File attachment1:1 | Fully supported | |
| User (Owner) | User1: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.
Bigin by Zoho CRM gotchas
Credit-based API limits vary by plan and can throttle migrations
Bulk Read API excludes Notes, Attachments, Emails, and cross-module records
Import field mapping is complicated and unintuitive for users
Undo import window is limited to 30 days
Free plan is single-user with a 500-record hard cap
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
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.
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.
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.
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.
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.
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
Bigin by Zoho CRM
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 Bigin by Zoho CRM and Nutshell.
Object compatibility
2 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
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
Bigin by 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 Bigin by Zoho CRM to Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Bigin by 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.