Zoho CRM to Salesforce migration:
process and checklist
Last reviewed:
A Zoho CRM to Salesforce migration maps Zoho modules to Salesforce objects, exports the data within Zoho's export limits, and rebuilds workflows and custom functions. Attachments need the full backup, not module exports. Volumes, custom modules and connected apps decide the plan, so it starts with an audit.
When does moving make sense?
These are the situations in which a move usually pays off:
- Processes now need deeper customisation, approvals or a larger partner ecosystem.
- The business is consolidating onto Salesforce after an acquisition.
- Reporting, governance or integration needs have outgrown the current edition.
- The team plans to use Agentforce on CRM data.
What Zoho CRM lets you export
The Zoho CRM documentation sets limits that shape the plan. The points below come from the vendor's own help pages:
- Zoho module exports are CSV or XLSX in a ZIP: XLSX up to 50,000 records per export and CSV up to 200,000 records from one module; larger sets need several exports filtered by Created Time or a full backup. Source: Zoho Help
- Notes export as their own module. Attachments are not part of module exports. Source: Zoho Help
- Daily export counts depend on the edition: 10 (Free), 100 (Standard), 250 (Professional), 500 (Enterprise), 1,000 (Ultimate). Users need the Export (Module) permission. Source: Zoho Help
- An administrator can request a data backup: CSV module data plus a separate ZIP of all attachments. It excludes email content and attachments, Documents and data obtained through integrations. Download links last up to 7 days. Source: Zoho Help
- The Data Import Wizard imports up to 50,000 records at a time; Data Loader complements the web-based import wizards for larger loads. Source: Salesforce Help
How the data maps to Salesforce
Where Zoho CRM data normally lands in Salesforce. The final mapping is agreed field by field in the design phase and signed off before any data moves.
| In Zoho CRM | In Salesforce | Note |
|---|---|---|
| Leads | Lead | Keep the Zoho record ID in an external ID field; map lead status and source picklists. |
| Contacts | Contact | Load after accounts; map the account lookup. |
| Accounts | Account | Deduplicate by name and website before loading. |
| Deals | Opportunity | Map Zoho pipelines and stages to a sales process and stages. |
| Cases | Case | Map status and priority picklists. |
| Products, price books, quotes, sales orders | Product, price book, Quote, Order | Create products and price books before loading quotes and orders. |
| Tasks, events, calls | Task and Event | Map related-to and who fields. |
| Notes | Content Note or Note | Exported as their own module; relink to the parent record. |
| Attachments | Files (Content Version) | Taken from the full backup, not from module exports. |
| Campaigns | Campaign and campaign members | Map member status values. |
| Custom modules and fields | Custom objects and fields | Review multi-select, subform and lookup fields; subforms usually become related child objects. |
What does not move automatically
Some things cannot be copied across and are rebuilt, replaced or retired. These are agreed during the audit so that nothing surprises the business on go-live day:
- Workflow rules, blueprints and custom functions (rebuilt as Flow or Apex)
- Zoho web forms and portals (replaced)
- Email content and attachments held in Zoho (not in the backup)
- Reports and dashboards (rebuilt)
- Data from third-party integrations (re-collected from the source apps)
The plan, phase by phase
A migration runs in seven phases. Each phase ends with a deliverable that is reviewed before the next one starts.
1. Discover and audit
- List the Zoho CRM objects, custom fields, automations, integrations and reports in use
- Count records per object and flag duplicates and stale data
- Agree what is migrated, archived or left behind
- Request a full backup early so attachments are available
Deliverable: Scope document and data inventory
2. Design the Salesforce model and the mapping
- Choose standard and custom objects, record types and the sales or service process
- Write the field-by-field mapping with transformation rules
- Design security: profiles, permission sets, sharing
- Define record ownership and user mapping
Deliverable: Target data model and signed mapping sheet
3. Prepare Salesforce
- Configure objects, fields, page layouts, validation and automation in a sandbox
- Set up integrations that must exist on day one
- Create users and permissions
Deliverable: Configured sandbox
4. Clean and transform the data
- Deduplicate and standardise values
- Resolve relationships between records before loading
- Prepare load files in dependency order and convert subform rows into child records
Deliverable: Load-ready files and transformation scripts
5. Trial loads and reconciliation
- Load into the sandbox, compare record counts and sample values with the source
- Fix mapping errors and repeat until counts reconcile
- User acceptance testing with real scenarios
Deliverable: Reconciliation report and test sign-off
6. Cutover
- Freeze changes in the source system for the agreed window
- Run the final load into production and reconcile again
- Switch web forms, email and integrations to Salesforce
Deliverable: Production go-live and rollback plan on record
7. Hypercare and retire the old system
- Support users and fix defects after go-live
- Keep the source data read-only for an agreed period
- Cancel or downgrade the old subscription only after sign-off
Deliverable: Closure report and decommission checklist
The audit in phase 1 produces the plan with dates, effort and owners for the specific case. Techila does not quote a duration before the audit, because record volumes, automation and integrations differ for every business.
Risks and how they are handled
Every migration has the same handful of risks. This is how each one is controlled:
| Risk | How it is handled |
|---|---|
| Attachments missed | Take the full backup, which holds attachments in a separate ZIP, and plan the file load separately. |
| Export limits stall the work | Split large modules by Created Time and watch the daily export count for the edition. |
| Subform data flattened or lost | Decide a child-object design in the mapping phase and test with real records. |
| Email history not available | Confirm what email data matters; the backup excludes email content, so capture it from the mail system. |
| Custom functions and blueprints not reproduced | Inventory each one in the audit and decide whether to rebuild, replace or drop. |
| Duplicates carried across | Deduplicate before load and define matching rules in Salesforce. |
[ FAQ ]
Frequently asked questions
Can Zoho data be exported in one file?
Module exports have record limits, so large modules need several exports or the full backup.
Are attachments migrated?
Yes, from the full backup. Module exports do not include them.
Can Zoho and Salesforce run together during the move?
Yes. A phased move with a short freeze window at cutover is common. See the Zoho integration page.
How long does a migration take?
It depends on volumes, custom modules, automation and integrations. The audit produces a plan with dates for the specific case.
[ Next step ]
Talk to a Salesforce architect
Techila starts with an audit of the Zoho CRM set-up and a mapping to Salesforce. Share the objects in use, the record counts and the integrations to get started.
[ Related ]
Related
[ Evidence ]
Sources
- Zoho: export CRM data
- Zoho: data backup
- Salesforce: how many records can be imported with the Data Import Wizard
- Salesforce Data Loader guide (Winter '27)
Product names are trademarks of their owners. Zoho is a trademark of Zoho Corporation. Techila is not affiliated with Zoho. Information on this page was checked on 26 October 2026; vendor limits and prices change, so confirm on the vendor pages linked in the sources.