Zoho CRM migration without losing data or history
A Zoho CRM migration moves your records, history and processes from another system into Zoho CRM, then rebuilds the automations that data tools cannot move. Zoho CRM Experts migrates businesses into Zoho CRM from Salesforce, HubSpot, Keap, Mailchimp and spreadsheets, with a field-by-field mapping, deduplication and a planned cutover.
Key takeaways
- Zoho’s own Data Migration tool moves records well. It does not move workflows, reports or integrations.
- Decide what to leave behind before you map anything. Old junk is cheaper to delete than to migrate.
- Import in dependency order: users, accounts, contacts, deals, then activities and notes.
- Dedupe before import, not after.
- Run both systems in parallel until a final delta import, then cut over on a set date.
What migration tools does Zoho offer?
Zoho CRM has a built-in Data Migration tool that imports from CSV or ZIP exports and, for some CRMs, pulls data directly through an API key. Zoho also has a form to request free migration help from its product experts. Both are worth using. Neither rebuilds your automations, reports or integrations.
Here is what Zoho documents for its Data Migration tool (as of November 2026):
- File-based migration from exports of Salesforce, Pipedrive, Highrise, Insightly, Microsoft Dynamics, Maximizer and other Zoho CRM accounts, with other sources handled through a custom setup.
- API-based migration for HubSpot, Pipedrive, Capsule, Insightly, Highrise, Bitrix and Bigin: you enter an API key and the transfer runs in the background.
- Limits of 5 GB per file, 200 files at a time and 25 GB in total.
- Rules to know: picklist values must already exist in Zoho, records missing mandatory fields are skipped, upsert isn’t supported for users, roles, profiles or notes, and only newly inserted data can be rolled back.
Zoho’s free migration request form lists HubSpot, Salesforce, Pipedrive, Microsoft Dynamics 365 and others as sources. Zoho doesn’t publish exactly what that free help includes, so ask before you rely on it.
Where a team like ours adds value is everything around the tool: deciding what to migrate, cleaning and mapping it, rebuilding the processes, testing, and getting your team working in the new system.
How do fields map from Salesforce or HubSpot to Zoho CRM?
Most standard objects map one-to-one: Salesforce and HubSpot companies become Zoho Accounts, contacts become Contacts, and opportunities or deals become Deals. Custom objects, lead statuses, lifecycle stages and owner fields need decisions, because each CRM models them differently. The HubSpot side has its own full field map and cutover plan in our HubSpot to Zoho migration guide.
| Source | Salesforce | HubSpot | Zoho CRM |
|---|---|---|---|
| Companies | Accounts | Companies | Accounts |
| People | Contacts and Leads | Contacts (with lifecycle stage) | Contacts and Leads |
| Revenue | Opportunities | Deals | Deals |
| Stages | Opportunity stages, sales processes | Deal pipelines and stages | Deal stages, layouts and Blueprint |
| Activities | Tasks, Events, Activity history | Tasks, meetings, calls, emails | Tasks, Meetings, Calls |
| Notes and files | Notes, Files, Attachments | Notes, attachments | Notes and Attachments |
| Products | Products, Price Books | Products, line items | Products, Price Books |
| Custom data | Custom objects | Custom objects | Custom modules |
| Ownership | Owner (User) | Contact/Deal owner | Record owner (users created first) |
| Automation | Flows, approval processes | Workflows, sequences | Rebuilt as workflow rules, Blueprint, Deluge or Zoho Flow |
HubSpot lifecycle stages are the field that causes the most debate. Zoho splits Leads and Contacts into separate modules, so you need a rule for which HubSpot records arrive as Leads and which as Contacts. Agree that rule in writing before any import.
In what order should modules be migrated?
Import in dependency order, so every record can link to its parent when it arrives. Users first, then Accounts, then Contacts and Leads, then Deals, then Products and line items, then activities, notes and attachments. Getting the order wrong leaves orphaned records that must be re-linked by hand.
- Users, roles and profilesCreate users first so record owners map correctly.
- Picklists and custom fieldsEvery picklist value and custom field exists in Zoho before data arrives.
- AccountsCompanies, deduplicated by domain or a unique ID.
- Contacts and LeadsLinked to Accounts by the old system's ID, kept in a legacy ID field.
- Deals and productsLinked to Accounts and Contacts, with stages mapped to the new pipeline.
- Activities, notes, attachmentsHistory last, linked to the records above.
- Delta import and cutoverChanges since the first import, then everyone switches on an agreed date.
How do you handle duplicates and dirty data?
Clean data before it reaches Zoho. Export everything, dedupe by email, phone and company domain, merge or delete stale records, standardize picklist values, and fill required fields. Zoho can flag duplicates on import, but fixing thousands of duplicates after go-live is slower and riskier than fixing them in a spreadsheet first.
Decisions we ask clients to make before mapping:
- How far back? Contacts with no activity in several years are often better archived than migrated.
- Which record wins? When two duplicates disagree, which source, date or owner takes priority.
- Legacy IDs. We keep the old system’s record ID in a field, so every record can be traced and re-linked.
- What stays behind. Old reports, dead pipelines and unused custom fields usually do.
How are automations rebuilt in Zoho CRM?
Automations are rebuilt, not migrated. Each Salesforce Flow, HubSpot workflow, Keap campaign or Mailchimp journey is listed, kept or dropped, then rebuilt with the right Zoho tool. Migration is a good time to drop the automations nobody remembers building.
| What it did in the old CRM | How it is rebuilt in Zoho |
|---|---|
| Field updates, alerts, task creation on a trigger | Workflow rules |
| Stage-by-stage process with required steps | Blueprint |
| Lead routing by territory or round robin | Assignment rules |
| Approvals for discounts or contracts | Approval processes |
| Logic across related records, outside API calls | Deluge custom functions |
| Email nurture sequences | Zoho Campaigns, Zoho Marketing Automation or cadences, depending on edition |
| App-to-app syncs | Native integrations, Zoho Flow or the REST API |
Integrations are rebuilt the same way; see Zoho CRM integration. If Zoho is new to you, the structure the data lands in is covered on Zoho CRM implementation.
How does cutover work?
Cutover is the day your team stops using the old CRM and starts using Zoho. Pick a quiet day, freeze changes in the old system, run a final delta import of everything changed since the main import, check record counts, then switch. Keep the old system read-only for a few weeks as a reference.
A cutover checklist:
- Record counts in Zoho match the source for each module.
- A sample of records checked by hand, including owners, stages and linked activities.
- Every rebuilt automation tested with a real record.
- Integrations switched to point at Zoho.
- Users trained and logged in before day one.
- The old CRM set to read-only, not cancelled, until the team is confident.
Salesforce to Zoho migration: what is different?
A Salesforce to Zoho migration is mostly a mapping exercise: Salesforce objects map cleanly to Zoho modules, but Flows, Apex code, validation rules and reports have to be rebuilt by hand. Export from Salesforce with the Data Export service or Data Loader, then import the files with Zoho’s Data Migration tool.
Before you switch, be sure Zoho fits; our Zoho vs Salesforce comparison covers where each one wins. We only migrate into Zoho CRM; if the comparison points you toward Salesforce, you will need a Salesforce team for that move, and we will tell you so on the discovery call.
Who does the migration?
Zoho CRM Experts has migrated businesses off HubSpot, Salesforce, Keap and Mailchimp, and has set up, audited or migrated about 200 CRM accounts in total. Migrations start at $1,490, and every one begins with a free discovery call and a written scope with one fixed price before work starts. Access is through user invites you control, never shared passwords, and you own both systems and all data.
Migration into Zoho CRM
From $1,490
per project · 2–6 weeks
- Field-by-field mapping from your old CRM
- Dedupe and cleanup before import
- Pipelines and automations rebuilt in Zoho
- Parallel run, delta import and planned cutover
- 6-month build guarantee
What moves the price above the starting point: the number of records and modules, the source system and what it can export, how much deduplication the data needs, and how many workflows have to be rebuilt in Zoho. All of it is listed in the scope, and the full menu is on the Zoho CRM implementation cost and pricing page.
Every project ends with a live training call, a recorded walkthrough video, a PDF manual of the build and a 6-month build guarantee.
When are we the wrong choice for a Zoho migration?
We are the wrong choice for very large data programs with millions of records across many systems and strict compliance sign-offs, which need a dedicated data engineering team. We are also overkill for a single spreadsheet of a few hundred contacts; Zoho’s import tool handles that well on its own.
Already on Zoho CRM and not sure whether to rebuild, fix or leave? A Zoho CRM audit shows whether fixing the current account is cheaper than starting over.
CRM projects our team has delivered
Each case study describes the client's problem, the system the team built and the result. Ask on the call which platform and integrations each project used.
FAQ
Does Zoho offer free migration to Zoho CRM?
Zoho has a built-in Data Migration tool in Zoho CRM and a request form for free migration assistance from its product experts. Zoho does not publish the exact scope of that free help, so ask what it covers. Automations, reports and integrations still need to be rebuilt by someone.
How long does a Zoho CRM migration take?
A small account moving from spreadsheets or one CRM usually takes two to four weeks including cleanup and testing. A larger Salesforce or HubSpot account with custom objects, years of activity and many automations takes six weeks or more.
Do workflows and automations move over to Zoho automatically?
No. Data migration tools move records, not logic. Salesforce Flows, HubSpot workflows and Keap campaigns have to be rebuilt as Zoho workflow rules, Blueprint processes, Deluge functions or Zoho Flow.
Can we keep using the old CRM during the migration?
Yes. The team keeps working in the old system while Zoho is built and tested. A final delta import of recent changes happens just before cutover, so nothing is lost.
How much does a Zoho CRM migration cost?
Migrations into Zoho CRM start at $1,490 as a fixed price, set from the written scope. The number of records, the source system, how much cleanup the data needs and how many automations have to be rebuilt move it up from there. Zoho license fees are separate.
What happens to email history and attachments?
Notes, emails and attachments can usually be migrated, but how depends on the source system and the export it allows. We confirm what each source can export during scoping, so nothing is promised that the source cannot provide.