Skip to content
Get a quote

Bigin by Zoho CRM to Zoho CRM migration

We migrate Contacts, Companies, Deals, and engagement history from Bigin by Zoho CRM into Zoho CRM with the <topping_namespace>__<field_label> custom field convention resolved, pipeline stages pre-configured, and every ownership assignment mapped before any record crosses the wire.

Short answer

FlitStack AI migrates contacts, accounts, deals, sales processes + record types and products from Bigin by Zoho CRM to Zoho CRM, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 1-2 weeks.

By

Source Bigin by Zoho CRM
DestinationZoho CRM
ContactsAccountsDealsSales Processes + Record TypesProducts
Mapped field by field · sample run · one-click rollback

What moves from Bigin by Zoho CRM to Zoho CRM?

Upgrading from Bigin by Zoho CRM to Zoho CRM is an in-vendor migration that benefits from Zoho's own built-in migration tool, but that tool applies fixed module mapping and does not support Products or attachments stored inside records.

Read the full summary

We supplement the native tool with direct API extraction from Bigin to handle these exclusions, preserve the <topping_namespace>__<field_label> custom field naming, and resolve pipeline ownership assignments that the wizard cannot reconcile. We do not migrate Bigin workflows or automations as code; we deliver a written inventory of every active workflow with a recommended Zoho CRM Blueprint or function equivalent for the customer's admin to rebuild. The upgrade path spans Zoho CRM Standard ($14/user/month) through Enterprise ($52/user/month), and record-count tiers on Bigin (500 on Free, unlimited on Express, 100k on Premier) determine whether scoping requires data cleanup before migration begins.

1:1

Contacts → Contacts

Bigin Contacts map directly to Zoho CRM Contacts.

How it maps

The Bigin Developer Console custom field namespace <topping_namespace>__<field_label> convention is resolved during scoping by querying the Bigin API field metadata and creating matching custom fields in Zoho CRM before migration. Contact owner assignments migrate as Owner lookup references resolved by email match against the Zoho CRM User table.

1:1

Companies → Accounts

Bigin Companies (API name: Accounts) map to Zoho CRM Accounts.

How it maps

The Company-Contact linkage is preserved through the AccountId lookup on the migrated Contact record. Any custom Company fields created via Developer Console follow the <topping_namespace>__<field_label> naming convention and require pre-creation in Zoho CRM before data import.

1:1

Deals → Deals

Bigin Deals map to Zoho CRM Deals.

How it maps

Each Bigin Pipeline and sub-pipeline becomes a Zoho CRM Sales Process and Deal Stage configuration that we deploy before migration begins. The dealstage value from Bigin maps to the corresponding StageName in the destination Sales Process. Closed-Won and Closed-Lost reason custom fields migrate to Zoho CRM Loss Reason and Won Reason picklist fields.

configuration

Pipelines → Sales Processes + Record Types

Bigin Pipelines and sub-pipelines require pre-configuration in Zoho CRM before Deal migration because the built-in migration tool does not allow mapping modifications.

How it maps

We create Zoho CRM Sales Processes and assign them to Record Types so that deal stages land in the correct scope. Express is limited to 3 pipelines; Premier supports unlimited. We preserve pipeline ownership assignments as Zoho CRM User assignments on the Deal records.

1:1

Products → Products

Bigin Products map to Zoho CRM Products, but the Products module is excluded from the built-in Zoho migration wizard and must be handled via direct API extraction from Bigin followed by Zoho CRM API insert.

How it maps

Product name, unit price, tax, and description fields migrate directly. Custom product fields follow the Developer Console naming convention and require pre-creation.

1:1

Tasks → Tasks

Bigin Tasks linked to Contacts, Companies, or Deals migrate to Zoho CRM Tasks with Status, Priority, Due Date, and owner assignment preserved.

How it maps

The WhatId lookup resolves to the migrated Deals record ID. Tasks are available via both the built-in migration wizard and direct API; we prefer API for large task volumes to manage Bigin credit consumption.

What moves12 objects
Bigin by Zoho CRMZoho CRM
  • ContactsContacts1:1
  • CompaniesAccounts1:1
  • DealsDeals1:1
  • PipelinesSales Processestransformed
  • ProductsProducts1:1
  • TasksTasks1:1

+ 6 more in the mapping below

How Bigin by Zoho CRM and Zoho CRM differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionBigin by Zoho CRMZoho CRM
Custom field capacity10 fields per module on Express, 25 on PremierUnlimited custom fields from Standard tier onward
Pipeline structurePipeline and sub-pipeline model with deal stagesMulti-module architecture with Leads, Contacts, Accounts, Opportunities, and separate Sales Processes
Automation10 workflows on Express, 30 on Premier, with hard capsBlueprints, functions, and macro-based workflows with per-edition limits
Custom modulesNot available; custom fields only via Developer ConsoleCustom modules (DBs) available from Standard tier onward
Marketing automationNone; requires separate Zoho product purchaseAvailable within Zoho CRM via integrated campaigns and scoring on higher tiers
EU-hosted infrastructureNot available; data centers in US and India onlyEU data center available on Enterprise and Zoho One for GDPR compliance
API rate modelCredit-based; 50,000 base plus 250 per user, max 100,000 per 24 hoursDaily API call limits per edition; Zoho One gets elevated limits across the suite

What to watch for in a Bigin by Zoho CRM to Zoho CRM migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Built-in migration wizard applies fixed module mapping and cannot be modified

Zoho's native Bigin-to-Zoho CRM migration tool (Setup > Data Administration > Import > Bigin) maps modules and fields by default and does not allow mapping changes.

How we handle it

Community posts on the Zoho Apps Facebook group document cases where data landed in the wrong modules and fields because users relied on Auto Map without manual field verification. We either use the built-in wizard for the supported subset (Accounts, Attachments in Notes, Calls, Deals, Contacts, Notes, Events, Photos, Tasks, Users) and handle Products and custom attachments via direct API, or we bypass the wizard entirely for migrations with complex custom field schemas where auto-mapping would misalign data.

high

Products module excluded from the built-in migration wizard

The Zoho-built migration tool does not support the Products module from Bigin, which means organizations with a Product catalog cannot migrate that data through the wizard.

How we handle it

We extract Products from Bigin via the REST API (GET /bigin/v1/Products) and insert into Zoho CRM via the Zoho CRM Products API (POST /crm/v2/Products) with price book entries created separately. This requires the Zoho CRM user to have API access enabled, which is available from the Standard tier onward.

high

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

Bigin's Bulk Read endpoint cannot export Notes or Attachments and returns compressed ZIP files containing CSVs that require decompression and reprocessing.

How we handle it

For large note or attachment migrations, we must fall back to individual record API calls, which consume credits at a much higher rate (1 credit per call versus bulk rates). We scope Notes volume separately, estimate credit consumption, and pace API calls to stay within Bigin's daily credit ceiling (50,000 base plus 250 per user on paid plans). Migrations that exceed the daily credit window are rescheduled for the following day.

medium

Pipeline stages must be pre-configured in Zoho CRM before Deal migration

Bigin Pipelines and sub-pipeline stages do not automatically create matching Sales Processes and Stage values in Zoho CRM during the built-in migration.

How we handle it

Zoho CRM's help documentation requires administrators to create pipelines and stages in Zoho CRM before migration begins so that Deal data lands in the correct structure. We handle this as a pre-migration configuration step, deploying Sales Processes and Stage values via Zoho CRM API or manually before any Deal records move.

medium

Workflows and automations do not migrate between Bigin and Zoho CRM

Bigin workflows (10 on Express, 30 on Premier) have no equivalent that migrates automatically to Zoho CRM Blueprints, functions, or macros.

How we handle it

The automation models differ structurally. We do not migrate workflows as code. We deliver a written inventory of every active Bigin workflow with its trigger, conditions, actions, and a recommended Zoho CRM Blueprint or function equivalent, and the customer's admin rebuilds them post-migration.

How the migration runs

  1. Discovery and scoping

    We audit the Bigin account across plan tier (Free/Express/Premier), record counts per module (Contacts, Companies, Deals, Products, Tasks, Events, Calls, Notes), active workflows, custom fields via Developer Console with their <topping_namespace>__<field_label> API names, pipeline and stage structure, and user count.

    What this step covers

    We cross-reference against the Zoho CRM destination edition (Standard, Professional, Enterprise) to confirm feature availability for all migrating objects. The discovery output is a written migration scope, a custom field inventory, and a Zoho CRM edition recommendation if the customer has not already selected one.

  2. Pipeline and stage pre-configuration

    We configure Zoho CRM Sales Processes, Deal Stages, and Record Types to match the Bigin Pipeline and sub-pipeline structure before any data moves.

    What this step covers

    This includes setting stage probability percentages, configuring stage picklist values, and assigning Record Types per line of business. This step is required because the built-in migration tool does not support mapping modifications and expects the destination structure to be in place. We deploy via Zoho CRM API or manually depending on complexity.

  3. Custom field schema pre-creation

    We extract all Bigin Developer Console custom field definitions (API names, types, picklist values) via the Bigin API field metadata endpoint.

    What this step covers

    We create matching custom fields in Zoho CRM with equivalent field types and picklist options before any data import. This resolves the <topping_namespace>__<field_label> naming and ensures that custom field data lands in the correct destination column rather than being rejected by validation rules.

  4. User provisioning and owner reconciliation

    We extract every distinct Bigin user referenced as an owner on Contacts, Accounts, Deals, Tasks, Events, and Calls and match by email against the Zoho CRM User table.

    What this step covers

    If Bigin and Zoho CRM share the same Zoho organization credentials, users migrate automatically via the built-in wizard. For cross-organization migrations, we match by email and flag any unmatched owners for the customer's admin to provision in Zoho CRM before record migration proceeds.

  5. Data migration in dependency order

    We run migration in record-dependency order: Users (validated), Accounts (from Bigin Companies), Contacts (with AccountId resolved), Deals (with OwnerId and stage mapping resolved via pre-configured Sales Process), Products (via direct API, excluded from built-in wizard), Tasks, Events, Calls, Notes (via individual API calls due to Bulk Read exclusions), and Attachments.

    What this step covers

    Each phase emits a row-count reconciliation report before the next phase begins. We use Bigin's REST API with OAuth 2.0 and pace calls within the credit ceiling; heavy operations (Bulk Read initialization at 50 credits) are reserved for large Accounts and Contacts batches.

  6. Cutover, validation, and workflow handoff

    We freeze Bigin writes during cutover and run a delta migration of any records modified during the migration window.

    What this step covers

    We validate record counts and spot-check 20-30 random records against the Bigin source. We deliver the active Bigin workflow inventory document with Zoho CRM Blueprint and function equivalents to the customer's admin team for rebuild. We offer a one-week hypercare window for reconciliation issues. We do not rebuild Bigin workflows as Zoho CRM automations within migration scope; that is a separate engagement.

Bigin by Zoho CRM Zoho CRM
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · Zoho CRMRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

1-2 weeksTypical, smaller accounts
3-5 weeksLarge or heavily customised accounts

Pricing reflects record volume, custom field count, and the scope of workflow inventory work. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Bigin by Zoho CRM to Zoho CRM →

Why teams move from Bigin by Zoho CRM to Zoho CRM

  • Teams outgrow Bigin's workflow and automation caps. Express limits organizations to 10 workflows and Premier to 30, which forces growing sales teams into manual workarounds that break at scale. Zoho CRM's Blueprints and functions provide enterprise-grade process automation without the artificial ceiling that pushes teams mid-adoption toward a forced upgrade anyway.
  • Custom modules are unavailable on Bigin. Organizations that need to track non-standard objects like Projects, Subscriptions, Properties, or Equipment cannot do so within Bigin and must upgrade to Zoho CRM where custom modules (called DBs) are available from the Standard tier. This is a structural blocker that reviewers on G2 consistently cite as the trigger for the upgrade.
  • Absence of EU-hosted infrastructure makes Bigin non-compliant for GDPR-sensitive companies. Bigin operates from US and India data centers only, which is a compliance gap for European customers handling EU resident data. Zoho CRM Enterprise includes EU data center availability as a standard feature, eliminating the infrastructure blocker that forces the migration.
  • Marketing automation integration requires separate Zoho product purchases with Bigin, fragmenting the customer data view. Zoho CRM's integrated Campaigns and Scoring modules on higher tiers provide marketing automation natively within the same platform, reducing tool sprawl and sync overhead that teams cite as a frustration when scaling their Zoho stack.
  • Integration ecosystem depth increases significantly on Zoho CRM. Bigin supports approximately 100 native integrations versus Zoho CRM's broader connector ecosystem including deeper ERP, HRMS, and analytics integrations that growing businesses need as their tech stack matures. Community forum posts on the Zoho Apps Facebook group consistently cite integration breadth as a driver for the upgrade.

Questions, answered

Bigin by Zoho CRM to Zoho CRM migration questions

How long does a Bigin to Zoho CRM migration take?

Small migrations under 5,000 records with no complex custom field schemas land between one and two weeks. Mid-size migrations with 10,000-50,000 records, multiple pipelines, and attachment history move to three to five weeks because of Bigin Bulk Read exclusions (Notes and Attachments require individual API calls), pre-configuration scope, and the workflow handoff documentation. The built-in Zoho migration wizard reduces timeline for the supported module subset but does not handle Products or attachments, which require direct API work.

Does the built-in Zoho migration tool handle everything, or why would I need FlitStack AI?

The built-in Zoho migration tool covers Accounts, Attachments in Notes, Calls, Deals, Contacts, Notes, Events, Photos, Tasks, and Users with fixed module mapping that cannot be modified. It excludes Products entirely and does not migrate attachments inside CRM records. Organizations with complex custom field schemas (created via Developer Console with the <topping_namespace>__<field_label> convention) may find the auto-mapping incorrect. We handle the Products gap, custom field resolution, and any migration where the built-in wizard's fixed mapping would misalign data.

Do Bigin workflows and automations migrate to Zoho CRM?

No. Bigin workflows (10 on Express, 30 on Premier) are not compatible with Zoho CRM Blueprints, functions, or macros and cannot be migrated as code. The automation models differ structurally. We deliver a written inventory of every active Bigin workflow with its trigger conditions, actions, and a recommended Zoho CRM Blueprint or function equivalent. The customer's admin rebuilds the automations post-migration. This is standard scope for all FlitStack AI migrations and is not included as a rebuild service.

Can we migrate Products from Bigin to Zoho CRM?

Yes, but not through the built-in migration wizard, which excludes the Products module. We extract Products from Bigin via the REST API (GET /bigin/v1/Products) and insert into Zoho CRM via the Products API (POST /crm/v2/Products), including Standard Price Book entries. This requires the Zoho CRM user to have API access enabled, which is available from the Standard tier onward. We scope the Product catalog size during discovery to confirm API feasibility within Bigin's credit ceiling.

What happens to our Bigin notes and attachments during migration?

Notes are available through the built-in migration wizard but are excluded from Bigin's Bulk Read API, which means large note migrations consume credits at a higher rate. Attachments embedded in Notes migrate via the wizard, but attachments stored directly inside CRM records do not. We handle the attachments-inside-records gap via direct API extraction and Zoho CRM attachment insert, subject to the 25 MB per-file API limit. We scope attachment volume and file size distribution during discovery to budget API call consumption.

How do we handle GDPR compliance if we are migrating from EU-based Bigin to Zoho CRM?

Bigin operates from US and India data centers only, which is a documented compliance gap for EU-resident data. Zoho CRM Enterprise includes EU-hosted infrastructure as a standard feature, which resolves this gap for the destination. We do not provide legal GDPR compliance advisory. We confirm the destination data center selection with the customer's legal team before migration begins and ensure that data extraction from Bigin follows the customer's data handling policy.

What customizations survive the migration?

Custom fields created in Bigin Developer Console migrate as custom fields in Zoho CRM, provided we pre-create the destination schema with matching types and picklists. Pipeline ownership assignments migrate as User assignments on Deal records. Tag counts per module migrate to Zoho CRM tags. The Bigin workflow rules, automation sequences, and pipeline configuration (as structure, not data) do not migrate. Reports and dashboards in Bigin do not migrate and must be rebuilt in Zoho CRM as part of the post-migration adoption work.

Get a quote

Moving from Bigin by Zoho CRM to Zoho CRM?

Tell us roughly how many records and objects you have. We scope the mapping and the Zoho CRM setup with you, then send a quote.

Get a quote