Bigin by Zoho CRM to Salesforce migration
We migrate Contacts, Companies, Deals, Pipelines, and Activity history from Bigin by Zoho CRM into Salesforce Sales Cloud, resolving Bigin's pipeline-centric model against Salesforce's Account-Contact-Opportunity structure, managing credit-throttled API exports, and mapping every Bigin field to a typed Salesforce field before cutover.
FlitStack AI migrates lead or contacts, accounts, opportunities, record type + sales process and product2s from Bigin by Zoho CRM to Salesforce, 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: 3-5 weeks.

What moves from Bigin by Zoho CRM to Salesforce?
Moving from Bigin by Zoho CRM to Salesforce Sales Cloud is a schema translation migration.
Read the full summary
Bigin organizes data around Pipelines containing Deals tied directly to Contacts and Companies, with no separate Lead object and no built-in marketing automation. Salesforce uses a Lead-to-Contact-to-Account hierarchy with separate Opportunity records, which means we must decide whether to create Salesforce Leads or Contacts for Bigin's contact-level data during scoping. We handle Bigin's credit-based API limits, which throttle bulk exports, and we fall back to individual API calls for Notes and Attachments that Bigin's Bulk Read endpoint cannot return. Pipeline configurations in Bigin become Salesforce Record Types and Sales Processes, which we configure before any record data moves. Workflows, automation rules, and any Zoho-specific integrations do not migrate as code; we deliver a written inventory for the customer's admin to rebuild in Salesforce Flow. Custom fields created in Bigin's Developer Console use the <topping_namespace>__<field_label> convention and map to Salesforce custom fields with the __c suffix, requiring explicit field-type validation during scoping.
Contact → Lead or Contact (split required)
Bigin Contacts have no built-in lead-to-contact lifecycle, so we design the split rule during scoping.
How it maps
Bigin Contacts that represent unqualified prospects (no associated Deal, no purchase history) map to Salesforce Lead. Bigin Contacts attached to Deals or with activity history suggesting a qualified sales relationship map to Salesforce Contact tied to an Account. We preserve any Bigin custom lifecycle or status fields in a custom Salesforce field for audit and segmentation.
Company → Account
Bigin Companies (API name: Accounts) map directly to Salesforce Account.
How it maps
Company name becomes Account Name; website becomes Website; industry and phone migrate to equivalent fields. Account is created before Contact import so that AccountId lookup is satisfied at the moment of Contact insert. Bigin's Company-Contact linkage is preserved as Salesforce Account-Contact relationships.
Deal → Opportunity
Bigin Deals map to Salesforce Opportunity.
How it maps
The Bigin deal stage maps to Salesforce StageName via the corresponding Sales Process. Closed-Lost and Closed-Won dates migrate as CloseDate and StageName. Deal amount migrates to Amount. We resolve the Contact (WhoId) and Account (WhatId) references before Opportunity insert.
Pipeline → Record Type + Sales Process
Bigin Pipelines (up to 3 on Express, unlimited on Premier) become Salesforce Opportunity Record Types.
How it maps
Each Record Type gets a corresponding Sales Process that whitelists the exact stage values from Bigin. Stage probability percentages migrate from Bigin to Salesforce StageProbability, rounded to the nearest integer. This configuration happens in the destination org Sandbox before any record data is migrated.
Product → Product2
Bigin Products map to Salesforce Product2 records with Standard Price Book entries created during import.
How it maps
ProductCode migrates from Bigin's SKU field. Price book entries are activated during migration so that OpportunityLineItems can reference them.
Task → Task
Bigin Tasks linked to Contacts, Companies, or Deals migrate to Salesforce Task with Status, Priority, ActivityDate, and subject preserved.
How it maps
Task assignment resolves Bigin owner email to Salesforce User ID via the User mapping. The WhatId on Task points to the migrated Account or Opportunity.
- ContactLead or Contactsplit
- CompanyAccount1:1
- DealOpportunity1:1
- PipelineRecord Typetransformed
- ProductProduct21:1
- TaskTask1:1
+ 6 more in the mapping below
How Bigin by Zoho CRM and Salesforce 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.
| Dimension | Bigin by Zoho CRM | Salesforce |
|---|---|---|
| Contact vs Lead model | Single Contact object; no Lead concept in Bigin | Separate Lead and Contact objects; unqualified prospects as Leads, qualified buyers as Contacts on Accounts |
| Account model | Companies module; Contacts attach directly to Deals without mandatory Account linkage | Accounts required as parent of Contacts; Opportunities attach to Accounts |
| Pipeline structure | Named Pipelines with sub-pipelines and stages; up to unlimited on Premier | Record Types and Sales Processes that whitelist stage values per line of business |
| Custom objects | Custom fields per module via Developer Console; no custom module/table support | Full custom objects (__c) with lookup relationships from Professional tier ($80/user/mo) |
| Marketing automation | None; requires separate Zoho product or third-party tool | Available via Salesforce Marketing Cloud Account Engagement (Pardot) or Marketing Cloud integrations |
| EU data residency | No EU-hosted infrastructure; GDPR non-compliant for European companies | Salesforce EU data residency available in EU regions; GDPR-compliant by design |
| Integration ecosystem | Approximately 100 native connectors; custom API workarounds for complex stacks | AppExchange with over 9,000 listings including ERP, CPQ, and revenue intelligence |
What to watch for in a Bigin by Zoho CRM to Salesforce migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Bigin Bulk Read API excludes Notes and Attachments
Bigin's Bulk Read endpoint cannot export Notes or Attachments and returns only compressed ZIP files containing CSVs.
How we handle it
For migrations with significant note or attachment volume, we must fall back to individual record API calls, which consume 1 credit per call versus 1 credit for bulk operations. We scope note and attachment counts during discovery, estimate credit budgets accordingly, and pace API calls to avoid exhausting the daily credit window (5,000 credits per 24 hours on Free, up to 100,000 on paid plans). Skipping this step mid-migration causes incomplete activity history at the destination.
Credit-based API throttling requires pacing strategy
Bigin's API uses a credit system where standard GET calls consume 1 credit, heavy operations (Get Records with cvid) consume 3 credits, and Bulk Read initialization consumes 50 credits.
How we handle it
Free plans cap at 5,000 credits per 24 hours; paid plans get 50,000 plus 250 per user (max 100,000). We monitor credit consumption continuously, pace API calls within limits, and reschedule if the daily credit window resets mid-migration. Large migrations without credit budgeting risk partial exports that omit records processed after the credit window closes.
Bigin has no Lead object; Salesforce Lead-Contact split requires design decision
Bigin has no equivalent to Salesforce's Lead object.
How we handle it
All contacts live in a single Contacts module. When migrating to Salesforce, we must decide whether each Bigin Contact becomes a Salesforce Lead or a Contact attached to an Account. We design this split rule during scoping based on whether the contact has associated Deals, activity history, or pipeline ownership. Without explicit design, all Bigin Contacts defaulting to Salesforce Leads creates a backlog of unconverted leads on day one, while defaulting to Contacts without Accounts creates orphaned records.
Bigin Pipelines do not automatically map to Salesforce Record Types
Bigin Pipelines (top-level containers with sub-pipelines and stages) have no automatic equivalent in Salesforce.
How we handle it
Salesforce requires manual configuration of Record Types and Sales Processes before Deal data can import. We pre-configure these in the destination Sandbox before migration, but any changes to Bigin pipeline structure after scoping require corresponding Salesforce schema updates. Pipeline stages also have different naming constraints in Salesforce (40-character limit on stage values) which may require truncation.
Bigin Workflows and automations do not migrate to Salesforce Flow
Bigin Workflows (email alerts, field updates, task creation) are Zoho-specific automation rules that have no direct Salesforce Flow equivalent.
How we handle it
We do not migrate them as code. We deliver a written inventory of every active Bigin Workflow with its trigger, conditions, and actions, mapped to a recommended Salesforce Flow equivalent. The customer's admin or a Salesforce partner rebuilds these post-migration. Any Bigin-specific field-update logic embedded in workflows requires explicit documentation to prevent business-rule gaps at cutover.
How the migration runs
Discovery and scoping
We audit the source Bigin account across plan tier (Free, Express, Premier), record counts per module, custom field definitions via Developer Console, pipeline count and stage names, owner assignments, and engagement volume for Notes and Attachments.
What this step covers
We also extract Bigin's API credit allocation and estimate the pacing budget. This audit produces a written migration scope including the Lead-Contact split design, custom field mapping table, pipeline-to-Record-Type configuration plan, and a credit-consumption schedule for large note and attachment volumes.
Destination schema design
We design the Salesforce destination schema in a Sandbox org.
What this step covers
This includes creating custom fields (with __c API names matched to Bigin custom field names), configuring Record Types and Sales Processes for each Bigin pipeline, mapping Bigin stage values to Salesforce StageName entries, and designing the Lead-Contact split logic as a transform rule in our migration engine. We also configure the necessary Salesforce profiles and permission sets for the migration user. Schema is validated in Sandbox before production migration begins.
Sandbox migration and reconciliation
We run a full migration into a Salesforce Sandbox using production-like data volume.
What this step covers
The customer's admin reviews record counts (Accounts, Contacts, Leads, Opportunities, Tasks, Events, Notes), spot-checks mapped fields against Bigin source records, and validates that pipeline-to-Record-Type assignments are correct. Any mapping corrections, schema adjustments, or stage-value truncations happen in Sandbox before production cutover. This step typically takes one to two weeks depending on the complexity of the object mapping.
Owner reconciliation and User provisioning
We extract every distinct Bigin user referenced as an owner on Deals, Contacts, Companies, Tasks, Events, and Calls and match by email against the Salesforce destination org's User table.
What this step covers
Owners without a matching Salesforce User are held in a reconciliation queue for the customer's admin to provision. This step gates all subsequent record imports because OwnerId references must resolve at insert time in Salesforce.
Production migration in dependency order
We run production migration in record-dependency sequence: Accounts (from Bigin Companies), then Leads and Contacts (with the Lead-Contact split applied), then Opportunities (with AccountId, OwnerId, and RecordTypeId resolved), then Products and Pricebook entries, then Tasks and Events, then Notes and Attachments (using individual API calls paced to Bigin credit limits).
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins. We monitor Bigin credit consumption throughout and pause if the daily limit approaches to preserve data integrity.
Cutover, validation, and automation rebuild handoff
We freeze writes to Bigin during cutover, run a final delta migration of any records modified during the migration window, then enable Salesforce as the system of record.
What this step covers
We validate record counts and spot-check 30-50 records for field-level accuracy. We deliver the Workflow and Automation inventory document mapping each Bigin Workflow to a recommended Salesforce Flow equivalent. We support a one-week hypercare window for reconciliation issues. We do not rebuild Bigin Workflows as Salesforce Flow within the migration scope; that is a separate engagement.
Bigin by Zoho CRM - Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, custom field count, and pipeline complexity. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Bigin by Zoho CRM to Salesforce →Why teams move from Bigin by Zoho CRM to Salesforce
- Teams hitting workflow and feature caps migrate when they outgrow Bigin's pipeline limits. The Express plan allows only 10 workflows and 3 pipelines; Premier allows 30 workflows and unlimited pipelines but still lacks the advanced automation depth that growing teams need. Salesforce Sales Cloud at Professional ($80/user/mo) supports unlimited Record Types, Sales Processes, and Salesforce Flow automation, removing the ceiling that forces Zoho CRM upgrades mid-adoption.
- Bigin has no EU-hosted infrastructure, making it non-compliant for GDPR-regulated businesses in Europe. Companies in Germany, France, or the UK that store EU customer data in Bigin must move to a platform with verifiable EU data residency. Salesforce offers dedicated EU region deployments (Frankfurt, Dublin, Paris) with GDPR controls, which is the most common compliance-driven migration trigger from Bigin.
- Integration limitations push teams with complex tool stacks to Salesforce. Bigin supports roughly 100 native connectors, which forces teams with ERP systems, contract lifecycle management, CPQ, or revenue intelligence tools into custom API workarounds that break during Zoho updates. Salesforce AppExchange has over 9,000 listings including native ERP connectors (NetSuite, SAP, Workday) and certified CPQ tools that eliminate custom integration maintenance.
- Zoho's platform complexity and user experience frustrations are documented across Reddit and G2 reviews. Small business owners report spending 10-15 hours per month fighting Zoho CRM performance issues including report crashes, custom field glitches on pipeline stages, email thread drops, and mobile app lag during client calls. Salesforce's UX learning curve is steeper but consistent once implemented, and performance issues at scale are addressed through dedicated infrastructure rather than workaround maintenance.
- No marketing automation in Bigin fragments the customer data view. Growing companies must purchase separate Zoho products or third-party tools to handle email campaigns and lead nurturing, which splits customer engagement data across platforms. Salesforce offers Marketing Cloud and Marketing Cloud Account Engagement (Pardot) as native options, keeping all customer data within a single platform and eliminating sync gaps between marketing and sales.
Questions, answered
Bigin by Zoho CRM to Salesforce migration questions
How long does a Bigin by Zoho CRM to Salesforce migration take?
Most migrations land between three and five weeks for accounts under 15,000 Contacts, 3,000 Deals, and no custom objects. Migrations with large note and attachment volumes (exceeding Bigin's daily credit budget), multiple Bigin pipelines requiring Salesforce Record Type and Sales Process configuration, or extensive custom field mapping move to eight to twelve weeks. The Sandbox validation step alone typically takes one to two weeks for complex object mappings.
Do Bigin Workflows, Pipelines, and automations migrate to Salesforce?
No. Bigin Workflows are Zoho-specific automation rules with triggers, conditions, and actions that do not map to Salesforce Flow. We do not migrate them as code. We deliver a written inventory of every active Bigin Workflow with its trigger conditions, actions, and a recommended Salesforce Flow equivalent. The customer's admin or a Salesforce partner rebuilds them post-migration. Pipelines in Bigin become Salesforce Record Types and Sales Processes, which we do configure as part of the schema migration.
Why do we need to decide between Lead and Contact for Bigin Contacts?
Bigin has a single Contacts module with no Lead concept. Salesforce separates unqualified prospects (Lead) from qualified buyers (Contact on an Account). We design the split rule during scoping based on whether each Bigin Contact has associated Deals, pipeline stage history, or activity records. Without this design, all Bigin Contacts defaulting to Salesforce Leads creates a day-one backlog of unconverted leads, while defaulting to Contacts without Accounts creates orphaned records with no Account parent.
Do we lose Note and Attachment history during the migration?
No. We migrate Notes and Attachments, but they require individual Bigin API calls rather than bulk export, which consumes more credits per record. We scope the note and attachment count during discovery, estimate the credit budget, and pace the API calls to stay within Bigin's daily credit limit. Large note volumes (over 10,000) may require multiple migration sessions across credit-reset windows, which extends the timeline. We flag this during scoping so there are no surprises at cutover.
Can we keep our Zoho integrations while moving to Salesforce?
Bigin integrations are Zoho-specific and do not carry over to Salesforce. Any Zoho Desk tickets, Zoho Books invoices, or Zoho Analytics dashboards connected to Bigin require replacement integrations in Salesforce (Service Cloud for support, Salesforce Billing or a third-party for invoicing, Salesforce CRM Analytics for reporting). We identify all active integrations during scoping and flag which ones require replacement before or shortly after cutover.
How does Bigin's API credit system affect our migration timeline?
Bigin's API credits reset every 24 hours: Free plans get 5,000 credits, paid plans get 50,000 plus 250 per user (capped at 100,000). Bulk Read initialization consumes 50 credits per operation, which limits how many concurrent bulk exports we can run. For large migrations, we schedule exports across multiple days, resume when the credit window resets, and monitor consumption continuously. This pacing extends the migration window for data-heavy accounts but ensures no records are missed due to credit exhaustion mid-export.
What happens to Bigin's import undo window during migration?
Bigin allows rollback of imported data within 30 days of the import date. We complete migrations and validate data promptly within this window so that customers retain the ability to request corrections through Bigin's native undo feature if post-migration review identifies issues. However, once the 30-day window closes, imported records in Bigin become permanent. We coordinate the migration timeline to stay well within this window to preserve customer flexibility.
Related migrations
Salesforce implementation
Set up Salesforce and migrate into it as one engagement.
See the service → Sage CRM to SalesforceMapping · history · rollbackCision to SalesforceMapping · history · rollbackSharpspring to SalesforceMapping · history · rollbackSysteme IO to SalesforceMapping · history · rollbackJobnimbus to SalesforceMapping · history · rollbackMoEngage to SalesforceMapping · history · rollback Bigin by Zoho CRM to Zoho CRMMapping · history · rollbackBigin by Zoho CRM to HubSpotMapping · history · rollbackSources: official documentation
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Uploading Activity data to Salesforce — Salesforce Stack Exchange
- Sandboxes — Staging Environments for Customizing and Testing
- Case Comment STRING_TOO_LONG — Salesforce Stack Exchange
- Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV
- Salesforce Duplicate Management — Salesforce Stack Exchange
Get a quote
Moving from Bigin by Zoho CRM to Salesforce?
Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.
Get a quote