Zoho CRM to HubSpot Migration: Steps, Field Mapping and What Breaks (2026)
By Mikhail Oskola, Founder & AI Automation Architect · · 9 min read
Checked: Zoho CRM's export and data backup help pages, HubSpot's Smart Transfer and import help pages, and the prices on our HubSpot service page on 5 November 2026.
A Zoho CRM to HubSpot migration comes down to five jobs. Take a full Zoho backup, decide where Leads, Accounts and every custom field land in HubSpot, build the HubSpot structure before any data goes in, import the records linked by their Zoho IDs, then rebuild workflow rules and Blueprints as HubSpot workflows and check a sample of records against Zoho. For a small team the data move takes one to two weeks. We're Retailbox Automation and we do these migrations, so the last sections cover our prices and the cases where you can skip us.
Decide these before you export anything
Zoho CRM is easy to customise, and after a few years most accounts carry extra modules, subforms inside records, or Blueprints that walk a deal through fixed stages. HubSpot is organised differently, so a one-to-one copy is rarely possible and usually not what you want. Work out how your team should sell in HubSpot, then decide what Zoho data serves that.
Not sure HubSpot is the right destination? Our HubSpot vs Zoho CRM comparison covers price and limits, and the 6-question CRM picker gives a quick first answer. Once you've decided, settle these:
- Leads. Zoho keeps leads in their own module, apart from contacts. Most teams bring them into HubSpot as contacts with a lifecycle stage. The same person often sits in both Zoho modules, so you need a duplicate rule before the import.
- Pipelines and stages. Which Zoho pipelines carry over, which merge, and what each HubSpot deal stage should mean.
- Custom fields and subforms. Each custom field becomes a HubSpot property, gets merged into one, or is dropped. Subforms (rows inside a record, like a list of items on a deal) need their own decision, because HubSpot has no direct equivalent.
- Users and owners. Every Zoho record owner needs a HubSpot user waiting for them, or their deals and tasks arrive unassigned.
- History. Zoho's full backup does not include emails, so decide now whether email history matters and how it will reach HubSpot.
What Zoho CRM exports, and what it leaves behind
Zoho gives you two ways to get data out, and you'll probably use both. Module export downloads one module, subform or the Notes list at a time, as CSV or XLSX. A single CSV export holds up to 200,000 records, and XLSX tops out at 50,000. You need the Export (Module) permission in your Zoho profile (https://help.zoho.com/portal/en/kb/crm/data-administration/export-data/articles/export-crm-data, read 5 November 2026).
The full data backup is the other route. An admin requests it, and Zoho delivers every module's records plus attachments and files from upload fields as CSV in a ZIP, with a download link that expires after seven days. Zoho's own page lists what it skips: "Email - Email content and attachments. Documents. Any data that is obtained through Integration." (https://help.zoho.com/portal/en/kb/crm/data-administration/data-backup/articles/requesting-data-backup, read 5 November 2026).
Workflow rules and Blueprints are the part to plan by hand. Smart Transfer, covered below, lists workflows among the data it handles, but HubSpot's help page doesn't say which Zoho rules come across or how. Write each one down as a spec for the HubSpot build and check what arrives.
How Zoho CRM maps to HubSpot
Here is the module-by-module map we use. The HubSpot side was checked against HubSpot's knowledge base on 5 November 2026.
HubSpot's Smart Transfer lists Zoho CRM as a source. It audits the Zoho account, you set up the structure in HubSpot, and it syncs the records one way into HubSpot. Only Super Admins can run it, attachments move as a separate one-time transfer after the first sync, and "You must have a Data Hub subscription to transfer custom field mappings" (https://knowledge.hubspot.com/integrations/transfer-data-from-other-apps-using-hubspot-smart-transfer, read 5 November 2026).
Without Smart Transfer, the Zoho files go through HubSpot's import tool. Files are linked to each other by a column they share, and HubSpot accepts a Record ID, a contact's email, a company's domain, or any custom property that holds unique values (https://knowledge.hubspot.com/import-and-export/import-objects, read 5 November 2026). Keeping each Zoho record ID as its own HubSpot property is what holds the relationships together.
| Zoho CRM | HubSpot | What you decide |
|---|---|---|
| Accounts | Companies | Merge duplicate accounts first; domain or Zoho ID as the match key |
| Contacts | Contacts | Duplicate rule (usually email) and owner |
| Leads | Contacts with a lifecycle stage | How to handle a person who is both a lead and a contact in Zoho |
| Deals, pipelines and stages | Deals, deal pipelines and deal stages | Which stages merge, and what each one means |
| Tasks, calls, meetings and notes | Tasks, calls, meetings and notes on the record | How far back to bring them; notes export as their own file |
| Custom fields | Custom properties | Keep, merge or drop, field by field |
| Subforms | Line items, extra properties, or left behind | Whether anyone reports on that data |
| Products | Products and line items | Only if you quote from the CRM |
| Attachments and upload fields | Files on the record | In Zoho's full backup, not in module export |
| Workflow rules and Blueprints | HubSpot workflows | Rebuilt from a written spec and tested |
Zoho CRM to HubSpot migration, step by step
Whether Smart Transfer or CSV files carry the data, we run the same seven steps in the same order.
The seven steps
- Request a full Zoho backup and keep it untouched as your reference copy. Then export the modules you're moving and clean them: merge duplicate accounts and contacts, close out dead deals, and drop fields that sit empty.
- Set up HubSpot before importing: properties, deal pipelines and stages, users, and a unique Zoho ID property on companies, contacts and deals.
- Import a small test batch made of your hardest records. Open each one and check it sits on the right company, contact and deal.
- Import everything in this order: accounts as companies, then contacts and leads, then deals, then tasks, calls, meetings and notes. Each file matches to records created by the one before it, through the Zoho ID.
- Write down what every Zoho workflow rule and Blueprint does, rebuild each as a HubSpot workflow, and run it on a real record before switching it on.
- Pick a sample of records and compare them field by field with Zoho, history included, while Zoho is still open.
- Train the team on the HubSpot screens they'll use daily. Leave Zoho readable for an agreed period, and stop new data going into it.
Time the switch-off around your Zoho renewal date, and download the backup before access ends: the link lasts seven days.
What usually breaks
Most of what goes wrong in a CRM move is the same whatever the source. The full list is in what breaks in a CRM migration. Coming from Zoho, these are the ones we look for first:
- Duplicates from the Leads module. A person who exists as a Zoho lead and a Zoho contact arrives in HubSpot twice unless one rule decides which record wins.
- Broken links between records. If the Zoho IDs aren't imported as their own property, contacts end up detached from their companies and deals from their contacts, and nobody notices until a sales rep opens an empty account.
- Blueprints that stop enforcing anything. A Blueprint might have made a rep fill in a field before a deal could move on. That rule disappears on migration day unless someone rebuilds it in HubSpot.
- Missing email history. Zoho's backup leaves out email content, and data that came in through integrations, so a team that relied on emails logged in Zoho can lose that context.
- Unowned records. Deals and tasks owned by people without a HubSpot seat come in with no owner.
How long it takes and what it costs
These prices come from our HubSpot service page, checked there on 5 November 2026. They're ranges. The fixed price for your project is agreed after a free 30-minute call.
HubSpot licenses are billed separately, by HubSpot. The HubSpot vs Zoho CRM comparison covers license costs.
| Scope | Typical time | Price (2026) |
|---|---|---|
| Migration only: clean, map, import, check | 1–2 weeks | Fixed $2,000–$5,000 |
| Full implementation: migration, automations, training | 3–8 weeks | $5,000–$25,000 |
| Keeping it running after launch | Monthly | $299–$2,000 a month, managed support |
| Doing it yourself with HubSpot's import tools | Depends on how much data you have | Your staff's time |
Can you migrate Zoho CRM to HubSpot yourself?
Yes, if the Zoho account is simple. One pipeline, few custom fields, no Blueprints, no subforms and a few thousand records is a job a careful admin can handle with Smart Transfer or CSV files. Use the steps above and don't skip the field-by-field check.
It's worth getting help when Blueprints run your sales process, when subforms or custom modules hold data people report on, or when years of activity history have to arrive linked to the right records. Those are hard to repair once Zoho is switched off.
Who does Zoho CRM to HubSpot migrations
Retailbox Automation migrates small and mid-size B2B teams to HubSpot from Zoho CRM, Pipedrive, Salesforce, monday.com and spreadsheets: data mapping, deduplication, workflow rebuilding, integrations and team training, with a field-by-field check before the old CRM is switched off.
We're a team of 2–9 people based in Orlando, FL, and we've been doing this work since 2017.
A migration on its own is a fixed price, agreed after a free 30-minute call. The scope and the checks we run are on our HubSpot migration page.
Want this built for your team? HubSpot migration — in business since 2017, 470+ jobs on Upwork.
Related services
HubSpot vs Zoho CRM
Still deciding whether to switch? How the two CRMs compare on price, limits and automation.
what breaks in a CRM migration
The full list of what goes wrong when CRM data moves, whichever system is the source.
Pipedrive to HubSpot migration
Coming from Pipedrive instead? The same steps with Pipedrive's object map.
Frequently asked questions
Who can migrate our CRM data from Zoho CRM to HubSpot?+
Look for a team that cleans and de-duplicates the Zoho data first, keeps contacts, companies and deals linked through their Zoho IDs, rebuilds workflow rules and Blueprints as HubSpot workflows, and checks records field by field before Zoho is switched off. Retailbox Automation migrates small and mid-size B2B teams to HubSpot from Zoho CRM, Pipedrive, Salesforce, monday.com and spreadsheets: data mapping, deduplication, workflow rebuilding, integrations and team training.
How long does a Zoho CRM to HubSpot migration take?+
The data move on its own usually takes one to two weeks for a small team. As part of a full HubSpot implementation with automations and training, the project runs three to eight weeks. Blueprints, subforms and custom modules add more time than record count does.
How much does a Zoho CRM to HubSpot migration cost?+
With us, a migration on its own is a fixed $2,000–$5,000. A full implementation with migration, automations and training is $5,000–$25,000, and managed support after launch is $299–$2,000 a month. Doing it yourself costs staff time, plus a Data Hub subscription if you want Smart Transfer to carry custom field mappings. HubSpot licenses are separate.
Will we lose notes, attachments and email history?+
Notes and attachments can come across. Zoho exports notes as their own file, and its full backup includes attachments and upload-field files, which then need linking back to the right HubSpot record. Email content is the gap: Zoho lists it among the things its backup does not include. Decide early whether that history matters and plan a separate route for it.
What happens to our Zoho workflow rules and Blueprints?+
Plan to rebuild them in HubSpot. Smart Transfer lists workflows among what it handles, but HubSpot doesn't say which Zoho rules it carries, so write down what each one does, rebuild or check it as a HubSpot workflow, and test it on a real record. Blueprints that forced fields or approvals at certain stages need the most care.
Should we move from Zoho to HubSpot at all?+
Only if HubSpot solves something Zoho doesn't. Moving costs money and team time either way. Our HubSpot vs Zoho CRM comparison puts prices and limits next to each other, and the 6-question CRM picker gives a quick first answer.