Salesforce to Zoho CRM migration
We migrate Accounts, Contacts, Leads, Deals, and Activity history from Salesforce Sales Cloud into Zoho CRM with the Account-Contact relationship chain resolved upfront, picklist normalization handled during transform, and every Salesforce custom field mapped to a Zoho equivalent before cutover.
FlitStack AI migrates accounts, contacts, leads, deals and campaigns from Salesforce 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: 4-8 weeks.

What moves from Salesforce to Zoho CRM?
Moving from Salesforce Sales Cloud to Zoho CRM is a schema-normalization project more than a record copy.
Read the full summary
Salesforce separates Contacts from Accounts through a many-to-many Account Contact Relation junction table; Zoho links Contacts directly to Accounts as a parent lookup. We extract the ACR records during migration and resolve each Contact's primary Account before insert, so relationship chains do not break silently. Salesforce Custom Objects, picklist values, multi-currency Opportunities, and Activity history require explicit field mapping during scoping because Zoho enforces a 300-field limit per module and only five lookup fields per module — thresholds that catch orgs with heavily customized Salesforce schemas. We do not migrate Workflow Rules, Process Builder processes, or Apex triggers as code; we deliver a written inventory of every active automation with its trigger logic and a recommended Zoho Blueprint or Deluge equivalent for the customer's admin to rebuild post-migration.
Account → Account
Salesforce Account maps to Zoho CRM Account.
How it maps
Standard fields (Account Name, Industry, Annual Revenue, Type, Phone, Website) migrate directly. Parent-Account hierarchies require sequencing: we import root Accounts first, then child Accounts with the Parent Account lookup resolved to the committed parent record ID. Salesforce Account Teams map to Zoho Account Sharing Rules configured post-migration rather than imported as team records.
Contact → Contact
Salesforce Contact maps to Zoho CRM Contact with a direct Account lookup.
How it maps
We extract the primary Account from Salesforce's Account Contact Relation (ACR) junction object during the pre-migration data audit and resolve the Contact-to-Account link before inserting Contacts into Zoho. Any additional ACR relationships beyond the primary are logged in a custom Zoho Multi-Select field for manual reassignment post-migration.
Lead → Lead
Salesforce Lead maps to Zoho CRM Lead.
How it maps
Standard fields (FirstName, LastName, Email, Phone, Company, LeadSource, Status, Rating) migrate directly. Custom Lead fields migrate as Zoho CRM custom fields of equivalent type. Unconverted Leads with an isConverted=false flag are imported as Zoho Leads; Leads already converted in Salesforce map to Account/Contact pairs in Zoho.
Opportunity → Deal
Salesforce Opportunity maps to Zoho CRM Deal.
How it maps
StageName maps to Deal Stage, Amount maps to Amount, CloseDate maps to Closing Date, Probability maps to Probability (Zoho allows decimal probability values). Multi-currency Opportunities store the CurrencyIsoCode field, which we map to Zoho's Currency field. Record Type maps to Zoho's Pipeline and Sales Process configuration.
Campaign → Campaign
Salesforce Campaign maps to Zoho CRM Campaign.
How it maps
We import Campaigns first as container records, then Campaign Members as a second pass linked to the imported Contacts and Leads. Campaign Type, Budget, Status, and Start/End Date migrate as standard fields.
Case → Cases
Salesforce Case maps to Zoho CRM Cases module.
How it maps
Status, Priority, Origin, and Contact/Account linkage migrate. Entitlement and SLAs referenced in Salesforce Case are not available in standard Zoho CRM; we flag these as gaps and document them in the pre-migration deliverable for the customer to evaluate Zoho Desk as a complementary support module.
- AccountAccount1:1
- ContactContact1:1
- LeadLead1:1
- OpportunityDeal1:1
- CampaignCampaign1:1
- CaseCases1:1
+ 6 more in the mapping below
How Salesforce 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.
| Dimension | Salesforce | Zoho CRM |
|---|---|---|
| Contact-to-Account linking | Many-to-many via Account Contact Relation junction object | One Contact per primary Account via direct lookup field |
| Deal terminology | Opportunity object with Stage, Amount, Close Date, and Probability | Deal module with Stage, Amount, Closing Date, and Probability fields |
| Custom object naming | Custom Objects with __c suffix, unlimited per org | Custom modules with _c suffix, max 20 modules with 300 fields each and 5 lookups per module |
| Automation engine | Flow (replacing retired Workflow Rules and Process Builder) | Workflow Rules, Blueprints, and Deluge scripting for advanced cases |
| Pricing model | Per-user tiers from $25 to $550/month with 8-10% annual uplift and storage overage at $125/GB | Per-user tiers from $14 to $52/month with no disclosed annual uplift or storage overage fees |
| API rate limits | 100,000 API calls/day base for Enterprise, 15,000 Bulk API batches/day | 1,000 API calls/minute per standard instance; Bulk export not available natively |
| Field limit per module | No hard field count limit; governed by org data storage | 300 fields maximum per module, with only 5 lookup fields allowed per module |
What to watch for in a Salesforce 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.
Zoho's 300-field and 5-lookup limits can block Custom Object migration
Salesforce orgs with heavy customization often exceed Zoho's 300-field module limit and 5-lookup-per-module constraint.
How we handle it
We audit every Custom Object and standard object during scoping, counting fields across all modules and flagging any that approach or exceed these thresholds. Remediation options include archiving inactive custom fields, consolidating redundant picklists, and restructuring deeply nested lookups into text or ID-reference fields. This design work must happen before any data is loaded, not during. Migrations that skip this step fail silently at insert time with field-rejected records.
Account-Contact-Relation junction records require manual primary-resolution
Salesforce's Account Contact Relation enables a many-to-many relationship where one Contact can belong to multiple Accounts with different roles.
How we handle it
Zoho CRM uses a single primary Account lookup on Contact, with no native junction equivalent. We extract the ACR records during pre-migration, compute a primary Account assignment rule (typically the Account with the highest revenue or most recent Opportunity), and map that single primary to Zoho's Account lookup. Additional Account relationships are logged to a custom Multi-Select field for manual reassignment. If a Contact has no Account relationship in Salesforce, we assign it to a Default Account or leave the lookup blank per the customer's scoping preference.
Salesforce Workflow Rules and Process Builder automations do not migrate
Salesforce Workflow Rules and Process Builder are deprecated and require migration to Salesforce Flow, but they have no Zoho equivalent that preserves the exact logic.
How we handle it
Zoho's Workflow Rules and Blueprint tools offer similar outcome-based automation but with different trigger models, condition syntax, and action types. We document every active Salesforce automation (Workflow Rule, Process Builder, Flow) with its trigger, conditions, and actions, and deliver a written rebuild guide mapping each to a Zoho Blueprint or Deluge function. This document is a pre-migration deliverable; we do not implement Zoho automations inside the migration scope.
Salesforce Bulk API batch quota limits large historical extractions
Salesforce caps Bulk API at 15,000 batches per day with up to 10,000 records per batch.
How we handle it
For orgs with millions of historical records, exhausting this quota in a single migration day blocks subsequent days until the quota resets at midnight GMT. We pace extraction across multiple days, monitor batch consumption in real time, and switch to the REST API Composite endpoint for smaller objects when the bulk quota is exhausted. This extends the data extraction phase by one to three days for large historical volumes.
Picklist value proliferation requires normalization before Zoho import
Salesforce picklists tend to accumulate free-text and duplicate values over years of admin changes (e.g., LeadSource may have 'Web', 'web', 'WEB', 'Website', 'Website Visit' across the same org).
How we handle it
Zoho enforces picklist whitelists strictly at the field level. We extract all Salesforce picklist values during scoping, deduplicate and normalize them to a canonical set, and create the Zoho picklist with the normalized values before any records are imported. Picklist values that cannot be normalized are flagged as requiring either a Zoho multi-select field or a manual categorization step post-migration.
How the migration runs
Discovery and architecture scoping
We audit the source Salesforce org across objects (standard and custom), field counts per object, picklist value sets, active Workflow Rules and Process Builder processes, Flow definitions, and engagement volume (Tasks, Events, Calls, Notes).
What this step covers
We pair this with a Zoho CRM architecture session: which Zoho edition (Standard at $14 to Ultimate at $52), which modules to activate, how to map Salesforce's object model to Zoho's modules within the field-count and lookup-count constraints, and which custom objects to carry forward versus consolidate. The discovery output is a written migration scope document and a Zoho architecture diagram with field-level mapping.
Data extraction via Salesforce Bulk API with batch pacing
We extract all Salesforce data using the Bulk API 2.0 with pacing against the 15,000-batch daily quota.
What this step covers
For orgs exceeding the daily batch limit, extraction spreads across two to three days. We extract parent objects (Users, Accounts, Leads, Products, Price Books) first, then junction and child objects (Contacts, Opportunities/Deals, Campaign Members, Activity history) in dependency order. Each extraction pass produces a row-count manifest for reconciliation against the source org's record counts.
Schema design and Zoho pre-configuration
We design the Zoho CRM schema before any data loads: modules, custom fields (respecting the 300-field limit per module), lookup relationships (capped at 5 per module), picklist value sets (normalized from Salesforce), and Pipeline/Stage configurations.
What this step covers
Custom Objects map to Zoho Custom Modules. We pre-create the entire schema via Zoho's API or bulk import before record migration begins, validating that no field or lookup limit is violated. Schema is deployed to a Zoho sandbox or staging org first for validation against the customer's data volume.
ACR extraction and primary Account resolution
We run a pre-migration pass to extract all Salesforce Account Contact Relation records.
What this step covers
For each Contact with multiple ACR entries, we apply the customer's chosen primary-Account assignment rule (highest-revenue Account, most recent Opportunity, or explicit role priority) and write the resolved primary Account ID to the Contact record before Zoho import. Additional Account relationships are exported to a reconciliation CSV for manual post-migration reassignment.
Production migration in dependency order
We run production migration in record-dependency order: Users (matched by email, missing Users held in reconciliation queue), Accounts, Leads, Contacts (with primary AccountId resolved), Deals (Opportunity mapped to Deal with Stage, Amount, Closing Date, and Record Type), Products and Price Books, Campaigns, Campaign Members, Activity history (Tasks, Events, Calls via Zoho's bulk import API), Notes and Attachments, Custom Objects (last, because they often reference standard objects via lookups).
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins. Validation rules and required-field constraints in Zoho are reviewed before each phase to prevent silent record rejection.
Cutover, validation, and automation rebuild handoff
We freeze Salesforce writes during cutover, run a final delta migration of any records modified during the migration window, then enable Zoho CRM as the system of record.
What this step covers
We deliver the Automation Inventory document (all Workflow Rules, Process Builder processes, and Flow definitions with recommended Zoho Blueprint or Deluge equivalents) and the ACR reconciliation CSV to the customer's admin team. We support a one-week hypercare window for reconciliation issues. We do not implement Zoho Workflow Rules, Blueprints, or Deluge automations inside the migration scope; that is a separate engagement or an internal admin task.
- 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 object complexity, and the scope of automation documentation. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Salesforce to Zoho CRM →Why teams move from Salesforce to Zoho CRM
- Salesforce's total cost of ownership compounds to 30-40% above sticker price when storage overages ($125/GB), annual uplift (8-10%), and add-on subscriptions (Sales Engagement, Sales Programs, Salesforce Maps, CPQ) are included. Zoho CRM's top-tier Ultimate plan at $52/user/month includes workflow automation, Blueprint, Canvas UI customization, and Zia AI without separate add-on purchases, making the five-year TCO 50-70% lower for mid-market organizations.
- Organizations with fewer than 500 users and fewer than 20 integrations find Salesforce's enterprise architecture disproportionate to their needs. Zoho's integrated suite (CRM, Finance, Desk, Projects, Campaigns, Analytics) operates under a single admin console with cross-application workflows, eliminating the middleware and point-to-point integrations that drive Salesforce implementation costs. Mid-market teams cite faster time-to-value and lower admin overhead as primary switching reasons on G2 and Gartner Peer Insights.
- Salesforce's Workflow Rules and Process Builder are officially retired, forcing all orgs still using these features to migrate to Salesforce Flow before Salesforce enforces the shutdown. This forced rework project, combined with Flow's steeper learning curve for non-developers, pushes teams toward Zoho's Workflow Rules and Blueprint visual automation builder, which offer equivalent logic without requiring Apex or Flow Builder expertise.
- Salesforce's administrative complexity requires a dedicated admin or consultant for meaningful configuration. Teams without that capacity under-configure Salesforce, losing the value of the platform while still paying the license cost. Zoho's configuration surface is shallower and more approachable for non-admin users, reducing the dependency on specialized talent and lowering ongoing admin overhead.
- Zoho's API call limits (1,000/minute per standard instance) and per-module field constraints (300 fields, 5 lookups) are known constraints that teams with simple to moderately complex schemas can architect around. Organizations that have not heavily customized Salesforce with hundreds of custom fields per object find these Zoho limits manageable with upfront schema design, making the platform a viable replacement for mid-market use cases.
Questions, answered
Salesforce to Zoho CRM migration questions
How long does a Salesforce Sales Cloud to Zoho CRM migration take?
Most migrations land between four and eight weeks for orgs under 30,000 Accounts, 30,000 Contacts, and 30,000 Leads with no custom objects. Migrations with Custom Objects, large Activity histories (over 500,000 Task and Event records), or Salesforce orgs that span multiple Business Units move to twelve to twenty weeks because of Zoho field-limit remediation, Bulk API extraction pacing, and picklist normalization work.
Do Salesforce Workflow Rules, Process Builder, and Flow automations migrate to Zoho?
No. Salesforce Workflow Rules and Process Builder are retired features with no direct Zoho equivalent that preserves the exact trigger-and-action logic. Salesforce Flow (the replacement) uses a fundamentally different model. We do not migrate automations as code. We deliver a written Automation Inventory document listing every active Workflow Rule, Process Builder process, and Flow with its trigger, conditions, actions, and a recommended Zoho Blueprint or Deluge equivalent. The customer's Zoho admin or a Zoho implementation partner rebuilds these post-migration. Apex triggers are also excluded and not migrated.
Can Zoho handle our Salesforce custom objects and custom fields?
Zoho CRM supports custom modules with up to 300 fields per module and a maximum of 20 custom modules per instance, with only 5 lookup fields allowed per module. Salesforce orgs with fewer than 300 fields per standard object and fewer than 5 custom objects can migrate directly. Orgs with heavily customized Salesforce schemas (500+ fields on Opportunities, multiple junction objects) require schema design and field consolidation before migration. We identify these constraints during scoping and propose a remediation plan before any data moves.
What happens to our Salesforce Account Contact Relation records during migration?
Salesforce's Account Contact Relation is a many-to-many junction that has no direct Zoho equivalent. We extract all ACR records during pre-migration, compute a primary Account assignment for each Contact based on the customer's chosen rule, and map that single primary to Zoho's Contact.Account lookup. Any Contact with multiple Account relationships beyond the primary is flagged in a reconciliation report for the customer's admin to review and reassign manually post-migration. This is a known limitation that requires explicit scoping.
Do historical Activity timestamps (Created Date, Last Modified Date) migrate accurately?
We migrate Salesforce's CreatedDate and LastModifiedDate as custom fields on Zoho records (e.g., sf_created_date__c and sf_modified_date__c) because Zoho's native Created Time field is set to the import timestamp and cannot be overridden through bulk import. The original Salesforce timestamps are preserved in the custom fields for audit and reporting purposes. Activity sequence ordering (call A before call B) is preserved by setting the Zoho Activity Date to the original Salesforce timestamp.
How do we handle picklist value proliferation from Salesforce?
Salesforce picklists often accumulate inconsistent values over years of admin changes. We extract all picklist values during scoping, deduplicate them against a canonical set defined by the customer, and create Zoho picklists with only the normalized values before any records are imported. Any Salesforce picklist value without a normalized counterpart is flagged as requiring either a Zoho multi-select field or a manual recategorization step post-migration. This normalization step is included in the migration scope and must be completed before the bulk import phase begins.
Can FlitStack AI also migrate our Salesforce data to Zoho Finance or Zoho Desk in parallel?
Yes. Salesforce financial data (Orders, Contracts, Invoices) can migrate to Zoho Finance Plus or Zoho Books in parallel with the CRM migration. Support Cases can migrate to Zoho Desk with Case Status, Priority, and Contact/Account linkage preserved. Each application is scoped separately with its own object mapping and validation. We do not migrate ERP integrations, Salesforce CPQ configurations, or Salesforce Revenue Cloud order management logic; these require separate Zoho implementation scoping with a Zoho specialist.
Related migrations
Zoho CRM implementation
Set up Zoho CRM and migrate into it as one engagement.
See the service → Zoho CRM to SalesforceThe same pair in reverse Act! to Zoho CRMMapping · history · rollbackHubSpot to Zoho CRMMapping · history · rollbackMailchimp to Zoho CRMMapping · history · rollbackSendCloud to Zoho CRMMapping · history · rollbackCustomer.io to Zoho CRMMapping · history · rollbackDynamics 365 Marketing to Zoho CRMMapping · history · rollback Salesforce to HubSpotMapping · history · rollbackSalesforce to Dynamics 365Mapping · history · rollbackSalesforce to Odoo CRMMapping · history · rollbackSources: official documentation
- How to Migrate from Salesforce to Zoho CRM — zoflowx
- Data Migration: An Introduction — Zoho CRM
- Standard Modules & Fields — Zoho CRM
- Custom Modules — Zoho CRM
- 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
Get a quote
Moving from Salesforce 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