How to migrate from HubSpot to Zoho CRM without losing history
To migrate from HubSpot to Zoho CRM, you export or API-transfer HubSpot’s contacts, companies, deals, notes, tasks and logged emails into Zoho’s modules in dependency order, then rebuild the workflows, sequences, forms, reports and integrations that no tool moves. Most small and mid-sized accounts take two to six weeks, with the team working in HubSpot until a planned cutover day.
Key takeaways
- Moves: contacts, companies, deals, tickets, products, notes, tasks, meetings, calls, logged emails, attachments (with care).
- Rebuilt: workflows, sequences, forms, lists and segments, reports and dashboards, integrations, email templates.
- Biggest decision: which HubSpot lifecycle stages become Zoho Leads and which become Contacts.
- Biggest failure points: record owners, pipeline stage names, associations between records, and email history.
- Run both until a final delta import, then cut over on a quiet day and keep HubSpot read-only for a few weeks.
Before you start, make sure Zoho is the right destination. Our Zoho vs HubSpot comparison sets out where each wins; the short version is that Zoho is the better buy for sales-led teams, and HubSpot for marketing-led ones. Zoho CRM Experts has migrated businesses off HubSpot, Salesforce, Keap and Mailchimp, and only migrates into Zoho.
What moves from HubSpot to Zoho CRM?
Records move. Everything that is a row of data in HubSpot, contacts, companies, deals, tickets, products, line items and the activities attached to them, can be brought into Zoho CRM either through Zoho’s API transfer or through HubSpot CSV exports. Zoho CRM’s Data Migration tool lists HubSpot as an API-based source: you enter a HubSpot API key and the transfer runs in the background.
(checked on help.zoho.com)- Contacts become Zoho Leads or Contacts, by a lifecycle-stage rule you agree in writing first.
- Companies become Accounts, matched to contacts by HubSpot’s association IDs or by email domain.
- Deals become Deals, with each HubSpot pipeline mapped to a Zoho pipeline and every stage name mapped one to one.
- Tickets become Cases in Zoho CRM, or move to Zoho Desk if you are adopting it.
- Products and line items become Products and deal line items.
- Notes, tasks, meetings and calls become Notes, Tasks, Meetings and Calls, each linked to its parent record.
- Logged emails become email activities on the contact or deal when they come through the API transfer or an engagements export.
- Attachments move, but they are usually the largest part of the data. Zoho lets you add skipped attachments at the end of a migration without starting over.
- Property history can be exported from HubSpot for reference, but Zoho has no place to import a field’s change history; keep the export.
HubSpot’s side matters as much as Zoho’s. HubSpot record exports (CSV, XLS or XLSX) include the properties you choose and association columns with up to 1,000 associated record IDs each (all of them in CSV), and you can run 300 exports in a rolling 24 hours. Record exports leave out activities; those come through activity reports or the engagements API, which is why the API route is usually the default.
(checked on knowledge.hubspot.com)What has to be rebuilt in Zoho?
Logic, layouts and connections are rebuilt. HubSpot can export a description of most of these, but nothing on this list imports into Zoho. Migration is the right moment to list every one, keep the ones that still earn their place, and drop the rest.
(checked on knowledge.hubspot.com)| In HubSpot | What HubSpot exports | Rebuilt in Zoho CRM as |
|---|---|---|
| Workflows | A spreadsheet of workflow details and a PNG of each workflow; no history or performance data | Workflow rules, Blueprint, assignment rules, approval processes or Deluge functions |
| Sequences | Not listed as exportable; copy templates and steps by hand | Zoho CRM cadences, or Zoho Campaigns / Marketing Automation journeys |
| Forms | Form data and submissions | Zoho CRM web forms, Zoho Forms or your website's form posting to Zoho |
| Lists and segments | Segment exports | Custom views, filters and tags; Zoho Campaigns lists for marketing |
| Reports and dashboards | Report data exports | Zoho CRM reports and dashboards; Zoho Analytics for cross-module BI |
| Email templates and snippets | Copy by hand | Zoho CRM email templates and merge fields |
| Pipelines and stage settings | Visible in settings; recreate | Pipelines, stages, probability, layouts, Blueprint transitions |
| Custom properties | Part of record exports | Custom fields; picklist values created before import |
| Custom objects | Record exports | Custom modules (Standard allows 10, Professional 25, Enterprise 200) |
| Integrations | None | Native Zoho integrations, Zoho Flow, Zapier, Make, n8n or REST API v8 |
| Meeting links, quotes, payments | Quotes and payments export | Zoho Bookings, Zoho CRM Quotes, Zoho Books or Stripe via integration |
The rebuild is where the hours go, so the scope should name every workflow, sequence and integration and whether it is kept, changed or dropped. For how we rebuild automations, see Zoho CRM migration; for connections to outside tools, Zoho CRM integration.
How do HubSpot objects and properties map to Zoho modules and fields?
Standard objects map almost one to one. The decisions are in the few places where HubSpot and Zoho model things differently: lifecycle stages versus a separate Leads module, HubSpot’s flexible associations versus Zoho’s lookup fields, and HubSpot’s internal property names versus Zoho’s picklists.
| HubSpot object / property | Zoho CRM module / field | Notes |
|---|---|---|
| Contact | Lead or Contact | Rule by Lifecycle stage; e.g. subscriber, lead, MQL become Leads; SQL, opportunity, customer become Contacts |
| Contact: Lifecycle stage | Lead Status (Leads) or a custom picklist (Contacts) | Picklist values must exist in Zoho before import |
| Contact: Lead status | Lead Status | Map each HubSpot value to a Zoho value in writing |
| Contact: Contact owner | Lead Owner / Contact Owner | Zoho users created and activated first; match by email |
| Contact: Email, Phone, Mobile | Email, Phone, Mobile | Dedupe by email before import |
| Contact: Associated company | Account Name (lookup) | Resolve from HubSpot association IDs or company domain |
| Company | Account | Dedupe by domain |
| Company: Domain name, Industry, Number of employees, Annual revenue | Website, Industry, Employees, Annual Revenue | Industry picklist values created first |
| Deal | Deal | One Zoho pipeline per HubSpot pipeline |
| Deal: Pipeline, Deal stage | Pipeline, Stage | Stage names mapped one to one; stages missing in Zoho cause skipped records |
| Deal: Amount, Close date | Amount, Closing Date | Closing Date is mandatory in Zoho; fill blanks before import |
| Deal: Deal owner | Deal Owner | Match by user email |
| Deal: Associated contacts / companies | Contact Name, Account Name, Contact Roles | Primary association becomes the lookup; others become Contact Roles |
| Ticket | Case (or Zoho Desk ticket) | Status and priority picklists created first |
| Product, Line item | Product, Deal line items (Price Books) | Product codes kept as unique keys |
| Note, Task, Meeting, Call | Note, Task, Meeting, Call | Linked by the parent record's legacy ID |
| Logged email | Email activity on Contact / Deal | Via API transfer or engagements export; test first |
| Attachment | Attachment | Often the largest data; can be added at the end |
| Record ID (hs_object_id) | Custom field 'HubSpot ID' on each module | Keep it on every record for tracing and re-linking |
| Custom object | Custom module | Fields and lookups created before data arrives |
Two Zoho rules shape this map. Picklist values have to exist in Zoho before the data arrives, or the records fail. And each module has mandatory fields: Leads need a Last Name, Deals need Deal Name, Stage and Closing Date. A HubSpot deal with no close date is skipped unless you fill it first.
What are the steps, and how long does it take?
Plan, clean, build the structure, trial import, rebuild logic, test, final delta import, cut over. Two to six weeks for most accounts. The team keeps selling in HubSpot the whole time, and nobody touches Zoho for live work until cutover day.
- Week 1: scope and decisionsInventory HubSpot objects, properties, pipelines, workflows, sequences, forms, reports and integrations. Decide what moves, what is rebuilt and what is dropped. Agree the Leads-versus-Contacts rule.
- Week 1-2: clean HubSpotMerge duplicate contacts and companies, fill required fields (close dates, last names), standardize picklist values, archive dead deals. Cheaper to fix here than in Zoho.
- Week 2: build Zoho structureUsers, roles and profiles; custom fields and picklists; pipelines and stages; layouts; a HubSpot ID field on every module.
- Week 2-3: trial importAPI transfer or CSV into a Zoho sandbox or a clean account. Check counts, owners, stages, associations and a sample of emails and notes by hand.
- Week 3-5: rebuild logicWorkflow rules, Blueprint, assignment rules, cadences, web forms, email templates, reports, dashboards and integrations, each tested with a real record.
- Week 5-6: delta import and cutoverFreeze HubSpot changes, import everything changed since the trial, verify counts, switch integrations and forms to Zoho, train the team, set HubSpot read-only.
Import order matters: users first, then Accounts, then Contacts and Leads, then Deals and products, then notes, tasks, meetings, calls, emails and attachments. Each record needs its parent to exist so it can link on arrival.
Zoho’s file limits (5 GB per CSV, 200 files, 25 GB total) are rarely the constraint. HubSpot’s export behavior is: exports over a million rows split into several files, and association columns for busy companies can run long, which is why we prefer the API transfer for activities and use CSVs for a controlled, cleaned record set.
Where do HubSpot to Zoho migrations go wrong?
In four places: owners, pipelines, associations and email history. Each one looks fine in a record count and wrong when a rep opens a record. Test all four in the trial import, not on cutover day.
- Record owners. Zoho needs the user to exist and be active before a record can be owned by them. Deactivated HubSpot users, people who left, and owner emails that do not match Zoho logins all end up owned by the importing admin. Decide a reassignment rule for departed users before importing.
- Pipelines and stages. A HubSpot stage with no exact match in Zoho causes the deal to be skipped or dumped into a default stage. Map every stage of every pipeline, including closed-lost reasons, and do not rename stages in HubSpot mid-project.
- Associations. HubSpot lets a contact belong to several companies and a deal to many contacts, each with labels. Zoho has one Account lookup per Contact and Contact Roles on Deals. Decide which association is primary before import, and keep HubSpot IDs on every record so the rest can be re-linked.
- Email history. HubSpot record exports do not include emails, calls or notes. If the migration used CSVs only, years of email history simply are not there. Use the API transfer or an engagements export for activities, then open twenty contacts and confirm their emails are present and attached to the right person.
- Lifecycle stages. Importing every HubSpot contact as a Zoho Contact leaves the Leads module empty and the sales team without a qualification step. Importing them all as Leads buries customers. The written rule prevents both.
- Picklists and mandatory fields. Unknown picklist values and blank Closing Dates skip records silently in the counts you did not check. Compare per-module counts, not just totals.
- Notes and rollback. Zoho does not support upsert for Notes, and only newly inserted records can be rolled back, so a second import of notes creates duplicates rather than updating them. Import notes once, after the records are final.
- Forms and integrations left pointing at HubSpot. A website form or Zapier zap still posting to HubSpot after cutover creates a shadow CRM within a week. Switch every connection on cutover day and check the next morning.
Where does Zoho CRM Experts fit?
Zoho CRM Experts runs the whole move as a fixed-price project: scope, cleanup, mapping, structure, trial import, rebuilt automations, testing, delta import, cutover and training, with a 6-month build guarantee on everything built. Zoho’s own Data Migration tool does the transfer; our work is the decisions, the mapping, the rebuild and the testing around it.
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: record volume and custom objects, how much cleanup HubSpot needs, how many workflows and sequences have to be rebuilt, and how many integrations have to be reconnected. Every project starts with a free discovery call and a written scope with one fixed price. Access is through user invites you control in both HubSpot and Zoho, never shared passwords, and you own both accounts and all the data.
If Zoho is new to the business, the structure the data lands in (modules, pipelines, Blueprint, roles, reports) is covered on Zoho CRM implementation, and the full method for any source system is on Zoho CRM migration. If, after reading the comparison, HubSpot still looks like the right home for your business, stay; we would rather say that on a call than migrate a business that should not move.
FAQ
Can you migrate from HubSpot to Zoho CRM automatically?
Partly. Zoho CRM's Data Migration tool connects to HubSpot through an API key and transfers records in the background, and it also accepts HubSpot CSV exports. Workflows, sequences, forms, reports and integrations do not transfer and are rebuilt in Zoho.
How long does a HubSpot to Zoho migration take?
Two to six weeks for most small and mid-sized accounts. A clean account with a few thousand contacts and a handful of workflows is at the short end. Years of email history, custom objects, many pipelines and dozens of workflows push it to six weeks or more.
Does email history move from HubSpot to Zoho?
Logged emails can move as activities when they come through the API transfer or an engagements export, linked to the right contact. HubSpot's standard record exports leave activities out, so email history is the first thing to test in a trial import. Going forward, Zoho syncs the mailbox directly.
What happens to HubSpot workflows and sequences?
They are rebuilt. HubSpot workflows become Zoho workflow rules, Blueprint, assignment rules or Deluge functions depending on what they did. Sequences become Zoho CRM cadences or Zoho Campaigns journeys. HubSpot exports workflows as a spreadsheet and an image for reference, not in a form Zoho can import.
How much does a HubSpot to Zoho migration cost?
Zoho CRM Experts migrates into Zoho CRM from $1,490 as a fixed price set from the written scope. Record volume, custom objects, how much cleanup the data needs and how many workflows must be rebuilt move it up from there. Zoho license fees are separate.