What does a Zoho to HubSpot migration involve?
A Zoho to HubSpot migration moves leads, contacts, accounts, deals, activities and notes into HubSpot contacts, companies, deals and activities. The records are the easy part. The real work is replacing Zoho's lead conversion with lifecycle stages, deciding what happens to custom modules, and rebuilding Blueprints, workflow rules and Deluge functions as HubSpot workflows.
This guide is for whoever owns the move from Zoho CRM to HubSpot: a sales or RevOps lead, or a founder who has already decided HubSpot is the right platform. It covers the mapping, the methods, the steps in order and what usually goes wrong.
How does Zoho CRM data map to HubSpot?
Most standard Zoho modules have a HubSpot equivalent: contacts stay contacts, accounts become companies, deals stay deals. The differences are Zoho Leads, which have no separate module in HubSpot, the ordering modules, which have no standard object, and custom modules, which need HubSpot Enterprise if they must stay separate objects.
| Zoho CRM | HubSpot | What to decide |
|---|---|---|
| Leads (not yet converted) | Contacts with a lifecycle stage or lead status, or HubSpot leads (Sales Hub Pro or Enterprise) | Whether old leads move at all; deduplicate against Contacts |
| Contacts | Contacts | Email as the unique key |
| Accounts | Companies | Domain as the matching key; parent accounts |
| Deals | Deals | Which pipeline each layout becomes; original created time; old-to-new stage map |
| Tasks, calls, meetings | Tasks, calls, meetings | How far back to bring history; reassign open tasks |
| Notes and attachments | Notes and files | Moved in a one-time transfer, not kept in sync |
| Products, quotes, invoices | Products and line items, quotes, invoices | Whether the product library is still current |
| Sales orders, purchase orders, vendors, price books | No direct standard object | Custom object, your accounting tool, or archive |
| Custom modules | Custom objects (Enterprise) or properties on an existing object | Whether you need Enterprise at all |
| Multi-select picklists | Multiple checkboxes properties | Clean the allowed values before import |
| Roles, profiles, territories | Teams, permission sets, record owners | An owner for every record, including people who have left |
Write each row into a data migration mapping sheet before anything moves.
What should happen to Zoho's lead conversion?
Replace it with lifecycle stages. In Zoho a lead converts into a contact and account, plus an optional deal, and the conversion cannot be undone. In HubSpot the same person stays one contact whose lifecycle stage moves forward. Define those stages first, then map unconverted leads to the right starting stage.
Two details matter. Zoho only creates an account on conversion when the lead has a company name, so some converted contacts arrive without a company. And the same person can exist as an unconverted lead and as a contact, which becomes a duplicate in HubSpot unless you merge them first. Our guide to HubSpot lifecycle stages covers the stage definitions.
How do you migrate Zoho CRM to HubSpot?
With one of three methods: HubSpot Smart Transfer, a migration app from the HubSpot Marketplace, or a Zoho export or backup imported with HubSpot's import tool. Smart Transfer suits standard modules. Apps and file imports give more control over custom modules, history and field mapping, at the cost of more setup.
HubSpot Smart Transfer
When we checked HubSpot's documentation in October 2026:
- Only Super Admins can use it, and it moves data one way into HubSpot. A transfer can be reverted.
- Zoho Leads and Contacts map to contacts, Accounts to companies, and Deals to deals, along with meetings, notes, products, tasks, calls, invoices, users and currencies.
- Attachments, notes and deal line items move in a one-time post-sync transfer and do not stay in sync. Custom modules are not supported.
- Custom field mappings need a Data Hub subscription.
- It creates HubSpot workflows that backfill the original created date and Zoho record IDs.
- Zoho modules you sync need a "Modified By" field.
Check the current requirements in your portal before you plan around them; HubSpot changes these often.
Marketplace migration apps
Several apps on the HubSpot Marketplace migrate from Zoho CRM. They help with custom modules and full history. Confirm Zoho is a supported source and run a sample migration on real data first.
Zoho export or backup, then HubSpot import
Export each module from Zoho, or request a full data backup, then use HubSpot's import tool, which can bring in several objects at once with their associations. Zoho's CSV export is capped at 200,000 records per module and its download links expire after seven days, so plan large exports in batches. Note that HubSpot's import cannot update notes, tasks, emails or meetings that already exist.
What are the steps, in order?
Back up Zoho, audit what is in it, design the HubSpot structure, map every field, clean duplicates, test on a sample, rebuild automation and integrations, then cut over and validate. In that order, problems show up in testing instead of in front of your reps on the first day.
- 01 Back up and auditFull backup, modules, fields, Blueprints
- 02 DesignLifecycle, pipelines, companies, permissions
- 03 Map and cleanFields, picklists, stages; duplicates merged
- 04 TestA sample in a sandbox or test portal
- 05 RebuildWorkflows and integrations
- 06 Cut over and validateFreeze, transfer, check, train
- Back up Zoho. Request a full data backup so you have a complete copy before anything changes.
- Audit Zoho. Count records per module, list custom fields and how full they are, and export the list of workflow rules, Blueprints, functions and connected apps.
- Decide what to keep. How much history the team still uses, whether old leads move, and what to archive.
- Design the HubSpot structure. Lifecycle stages, deal pipelines with exit criteria, company records and permissions. See our CRM architecture blueprint.
- Map every field, including picklist values and the old-to-new stage map.
- Clean before import. Merge duplicates across Leads and Contacts and standardize values. Our deduplication playbook covers the process.
- Test on a sample in a sandbox or test portal: associations, owners, dates and stages.
- Rebuild automation. Turn Blueprints, workflow rules and Deluge functions into HubSpot workflows, improving them where the old logic was a workaround.
- Reconnect integrations such as forms, Zoho Books or Zoho Desk, with clear field ownership.
- Cut over. Freeze edits in Zoho, run the full transfer and the one-time transfers, then import anything changed since the test.
- Validate and train. Compare record counts, spot-check deals with each owner, and train the team on the new stages.
What usually goes wrong?
Duplicates from leads that were also contacts, lost created dates, Blueprint rules that quietly disappear, Deluge functions nobody listed, picklist values that do not match, and attachments left behind. Each is cheap to prevent before cutover and expensive to discover after, when reports and workflows already depend on the data.
- Lead and contact duplicates: merge before import, not after.
- Lost dates: keep Zoho's created time in a property so reports still make sense.
- Forgotten automation: Blueprint transitions and Deluge functions stop on cutover day unless they are rebuilt and tested.
- Expired exports: Zoho download links last seven days; re-export rather than import a stale file.
Planning a move off Zoho? Bring your module list and connected apps to a free 30-minute call and we will walk through scope.
Zoho migration checklist
Key takeaway: The records move in days. What decides whether HubSpot works is the lifecycle design that replaces lead conversion, and the automation you rebuild before cutover.
Frequently asked questions
Can HubSpot import data directly from Zoho CRM?
Yes. HubSpot Smart Transfer connects to Zoho CRM and moves records one way into HubSpot, and HubSpot's import tool accepts files exported from Zoho. Custom field mappings in Smart Transfer need a Data Hub subscription, and custom modules are not supported, so check those limits before choosing a method.
What doesn't transfer from Zoho CRM to HubSpot automatically?
Automation. Zoho Blueprints, workflow rules and Deluge functions have to be rebuilt as HubSpot workflows. In Smart Transfer, custom modules are not supported, and attachments, notes and deal line items move in a one-time transfer that does not stay in sync.
What happens to Zoho Leads in HubSpot?
HubSpot has no separate leads module before conversion. Unconverted Zoho Leads usually become contacts with a lifecycle stage or lead status, or HubSpot leads on Sales Hub Professional or Enterprise. Decide first whether old, unqualified leads should move at all, and deduplicate them against your Zoho Contacts.
Do we need HubSpot Enterprise for Zoho custom modules?
Only if they need to stay separate objects. HubSpot custom objects are an Enterprise feature. Many custom modules can be modeled as properties on an existing object, or as a deal pipeline, so check that before upgrading for the migration alone.
How long does a Zoho to HubSpot migration take?
Our migrations typically take three to six weeks, depending on data volume, how many modules and integrations move across, and how much Zoho automation needs rebuilding in HubSpot.
Sources
HubSpot documentation behind the feature and tier notes above, checked October 2026. HubSpot changes features and tiers often, so check your own portal too.