Zoho CRMHubSpot
Zoho CRM to HubSpot migration
Migration specialists move your accounts, contacts, deals and tasks into HubSpot, check a sample with you first, and count every record on both sides.
Free sample migration of 100 of your records, plus a fixed quote within 24 hours.
Last updated November 2026 · 10 object types mapped
- 1000+migrations
- 15 yearsof collective experience
SOC 2 Type IIGDPR compliantHIPAA compliant
Zoho CRM to HubSpot at a glance
A Zoho CRM to HubSpot migration moves your customer records into Smart CRM: contacts and accounts become contacts and companies, and deals keep their pipeline and stage. Notes, emails and files are read apart from the records and rejoined to them, and Zoho keeps running until a final delta sync.
- Objects mapped
- 10
- in this route's mapping
- Typical timeline
- About 10 business days end to end
- 3 phases
- Free sample
- 100 records
- checked by your team first
- Quote
- Fixed
- within 24 hours
- Who it is for
- Sales and revenue operations teams moving from Zoho CRM, often from a Zoho edition with small API limits, to HubSpot Smart CRM with their lead, contact and deal history in one place.
- What does not move
- Zoho workflows, blueprints, approval processes, layouts, validation rules, custom views, reports, dashboards, email templates, profiles and roles. We document each one so your admin can rebuild it in HubSpot.
- What sets the scope
- Leads, contacts, accounts and deals by module, notes, attachments and email volume, custom modules and subforms, and the Zoho edition, which decides the daily API credits and concurrency.
What moves
What moves from Zoho CRM to HubSpot
Zoho CRM contacts move to HubSpot as contacts, accounts as companies, deals as deals in matching pipelines and stages, tasks as tasks, calls as calls, events as meetings and notes as notes, with custom fields as custom properties.
- 10 included
| Zoho CRM | maps to | HubSpot | Status |
|---|---|---|---|
| Contacts | ContactsMatched on email. The Account_Name lookup becomes the contact's company association. | Included | |
| Accounts | CompaniesMatched on company domain, or on a shared ID column when no website is stored. | Included | |
| Deals | DealsDeal_Name, Stage and Pipeline, the fields Zoho requires on a deal when pipelines are on, linked to the contact and company, with the Zoho record ID in a unique property. | Included | |
| Pipelines and stages | Deal pipelines and stagesZoho's Pipeline and Stage values are built as HubSpot pipelines and stages before deals load. | Included | |
| Tasks | TasksSubject becomes the task title. HubSpot tasks need a due date, so a Zoho task without one gets a default agreed with you. | Included | |
| Calls | CallsCall type, start time and duration are kept, with the call description as HubSpot call notes. | Included | |
| Events | MeetingsTitle, start and end time, which HubSpot meetings require and Zoho events always carry, and the description. | Included | |
| Notes | NotesRead through the Zoho Notes API, since Bulk Read leaves them out, and linked to the record they belong to. | Included | |
| Custom fields | Custom propertiesPicklists, multi-select fields and lookups are created as matching properties first. | Included | |
| Users and record owners | OwnersMatched to HubSpot users by email, so each user must exist in HubSpot before records load. | Included |
- ContactsContacts
Matched on email. The Account_Name lookup becomes the contact's company association.
- AccountsCompanies
Matched on company domain, or on a shared ID column when no website is stored.
- DealsDeals
Deal_Name, Stage and Pipeline, the fields Zoho requires on a deal when pipelines are on, linked to the contact and company, with the Zoho record ID in a unique property.
- Pipelines and stagesDeal pipelines and stages
Zoho's Pipeline and Stage values are built as HubSpot pipelines and stages before deals load.
- TasksTasks
Subject becomes the task title. HubSpot tasks need a due date, so a Zoho task without one gets a default agreed with you.
- CallsCalls
Call type, start time and duration are kept, with the call description as HubSpot call notes.
- EventsMeetings
Title, start and end time, which HubSpot meetings require and Zoho events always carry, and the description.
- NotesNotes
Read through the Zoho Notes API, since Bulk Read leaves them out, and linked to the record they belong to.
- Custom fieldsCustom properties
Picklists, multi-select fields and lookups are created as matching properties first.
- Users and record ownersOwners
Matched to HubSpot users by email, so each user must exist in HubSpot before records load.
Looking for another object?Field-level mapping is reviewed with you during scoping.
What does not move
What does not move from Zoho CRM to HubSpot as-is
Workflows, blueprints, approvals, layouts, validation rules, views, reports and profiles are Zoho configuration, so they are documented for your admin to rebuild in HubSpot.
- LeadsOn request
- In HubSpot: Contacts at a lead stage, or HubSpot leadsZoho keeps Leads apart from Contacts. The target and the rule for converted leads are agreed on the scoping call.
- On request
- AttachmentsOn request
- In HubSpot: Files attached to recordsRead record by record through the Attachments API, then attached to the HubSpot record they belonged to.
- On request
- EmailsOn request
- In HubSpot: Email activitiesRead record by record, 10 to a call, and loaded with body, direction and original time.
- On request
- Custom modulesOn request
- In HubSpot: Custom objectsMoved as custom objects where your HubSpot account is on an Enterprise tier.
- On request
- Subforms and line itemsOn request
- In HubSpot: Line items and propertiesChild rows are read with their parent ID and rebuilt as line items on the deal.
- On request
- Products, Quotes, Invoices, Campaigns and CasesOn request
- In HubSpot: Products, quotes and other objectsMoved module by module, as far as your HubSpot account has an object for them.
- On request
- Workflows, blueprints and approval processesNot migrated
- In HubSpot: HubSpot workflowsZoho gives blueprint transition definitions through the API but nothing that can be loaded elsewhere. Each is documented for your admin to rebuild.
- Not migrated
- Layouts, validation rules and custom viewsNot migrated
- In HubSpot: Record layouts and saved viewsRecorded as a list of what each layout showed and required, then set up again by your admin.
- Not migrated
- Reports and dashboardsNot migrated
- Rebuilt on the migrated properties, with the Zoho record ID kept on every record for matching old figures.
- Not migrated
- Email templates, profiles and rolesNot migrated
- In HubSpot: Templates and permission setsTemplate text and the profile and role structure are documented, then recreated in HubSpot.
- Not migrated
Free sample migration of 100 of your records. Fixed quote within 24 hours.
Scope my migrationTimeline
Zoho CRM to HubSpot migration timeline
Estimated total
About 10 business days
end to end
- MigrateXwe run it
- Youyour team acts
- Bothon a call together
Preparation
Day 1-2
Scoping call
Both0.5 dayWe agree the modules in scope, the rule for leads and converted leads, whether email history, custom modules and line items come across, and your Zoho edition.
Connect both accounts
You0.5 dayYou approve API access to Zoho CRM for a user with export rights and install a HubSpot app with contact, company, deal and file scopes. Zoho users are added to HubSpot first.
Credit plan and property build
Both1 dayWe turn your record counts into a credit plan for the Zoho edition, then create the HubSpot deal pipelines, stages and properties for Zoho fields and system dates.
Migration
Day 3-7
Free sample
MigrateX1 day100 of your records, picked for a converted lead, a contact with a long email thread, a deal with line items and a note-heavy account, loaded into HubSpot with notifications off.
You review the sample
You1 dayYour sales operations lead checks the lead and contact rule, deal stages, activity times, owners and the Zoho date properties.
Full load
MigrateX2-3 daysAccounts first, then contacts and leads, deals, activities, notes, emails and files, and the associations between them, in batches of 100, paced to Zoho's credits and HubSpot's daily limit.
Delta sync
MigrateX0.5 dayZoho records modified since the full load are updated on the same Zoho record ID, and only new activities and notes are added, so nothing appears twice.
Validation
Day 8-10
Reconciliation report
MigrateX1 dayZoho against HubSpot per module, deals by stage, notes, attachments and emails against their parents, and every child row without a parent.
Sign-off
You1-2 daysYour team spot-checks a random set, HubSpot workflows replace the Zoho blueprints you chose to keep, and Zoho stays available as the fallback until you sign off.
An estimate. Record volume, API rate limits and how fast your team reviews the sample all move it.
Known risks
Every known risk on this route, with how we handle it
- 2 solved
- 7 handled
- 01HandledMost critical
Zoho CRM data leaves through four different routes
The problem
Bulk Read exports the records, but Notes, Attachments and Emails each need their own record-level calls, parent by parent. Credits and time grow with the number of records that have notes, files or email, and an export that stops at Bulk Read finishes without any of them.
How we handle it
We take record counts per module and per child type first, then read records by Bulk Read and notes, attachments and emails through their own calls, each joined to its parent record. The reconciliation report counts every type on both sides.
Source: Zoho CRM developer documentation, checked 15 Nov 2026
- 02HandledMost critical
A Free or Standard Zoho edition can stretch an extract over days
The problem
Free has 5,000 credits and 5 concurrent calls, and Standard 10 concurrent calls. A full read of notes and emails on a large database can exceed one day's pool.
How we handle it
We calculate the credit cost from your record counts before the first call, run inside the pool and the concurrency ceiling, and plan the extract over as many days as it needs. Bulk Read is used wherever it applies because it costs the fewest credits.
Source: Zoho CRM developer documentation, checked 15 Nov 2026
- 03Handled
Zoho Leads, Contacts and converted leads do not map one to one
The problem
Zoho keeps Leads apart from Contacts and has a Convert Lead action. A converted lead can appear in a Leads export beside the contact it became, and loading both as HubSpot contacts duplicates the person or loses the lead history.
How we handle it
We agree the rule on the scoping call: unconverted leads become contacts at a lead lifecycle stage, and converted leads are matched to their contact, so history lands on one record. Matching on email is checked on the free sample.
Source: Zoho CRM developer documentation, checked 15 Nov 2026
- 04Handled
Zoho created and modified details need properties of their own
The problem
Zoho returns Created_Time, Modified_Time, Created_By and Modified_By on every record, so they can be read. HubSpot makes Create date read-only on every object except deals, so a contact created in Zoho years ago would show as created on the day of the load.
How we handle it
Each record's Zoho creation time, last modified time and creator are written to dedicated properties. Deals also take the Zoho creation time in Create date, the one object HubSpot lets edit it, and Create date on contacts and companies is confirmed during your free sample.
Source: HubSpot Knowledge Base, checked 15 Nov 2026
- 05Handled
Zoho custom modules need a place to land in HubSpot
The problem
Zoho CRM accounts often hold modules built for one business, such as projects, contracts or assets. HubSpot gives those a custom object only on an Enterprise tier, so the same account on Professional has nowhere to put the records as objects.
How we handle it
We list the custom modules and their row counts on the scoping call. On Enterprise they become custom objects with their associations. On other tiers, where each module's records go is scoped with you during the free sample.
Source: HubSpot Knowledge Base, checked 15 Nov 2026
- 06Solved
Subforms and line items are child files tied to a parent key
The problem
Zoho stores subform rows, line items such as Quoted_Items and multi-select lookups as child data with a Parent_Id pointing to the parent record. If a parent key does not match, the child rows are dropped silently and the parent still looks complete.
How we handle it
Child files are read with their parent IDs and counted against the parent: line items become HubSpot line items on the deal, and other subform rows become properties or notes. Any child row without a parent is listed in the report.
Source: Zoho CRM developer documentation, checked 15 Nov 2026
- 07Handled
Zoho splits activities into Tasks, Calls and Events
The problem
Each Zoho activity module has its own required fields, and each HubSpot activity type asks for different ones: HubSpot calls need call notes, meetings a description with start and end time, and tasks a title and due date. A Zoho task needs only a subject, so many Zoho tasks have no due date at all.
How we handle it
Tasks become tasks, Calls become calls with their notes and Events become meetings, with a default agreed for any field HubSpot requires and Zoho leaves empty, such as a due date. The free sample loads one of each so you check the fields before the full load.
Source: HubSpot Knowledge Base, checked 15 Nov 2026
- 08Handled
Zoho email history is slow to read and absent from backups
The problem
The Zoho backup holds no email content, and the API returns emails 10 at a time for each record, with a call for each body. A deal with a long email thread costs many calls, and email on a record exists only as a related list.
How we handle it
Emails are read record by record, for the modules in scope, and loaded as HubSpot email activities with body, direction and original time. You choose the modules whose email history moves, which keeps credits and load time down.
Source: Zoho CRM developer documentation, checked 15 Nov 2026
- 09Solved
An extraction written for an older Zoho API can stop mid-project
The problem
Zoho's update post on the V2 API timeline says the end of life has been extended to 31 December 2026, with V2 in maintenance mode, while Zoho's V3 launch post also gives 31 December 2025, so the date is not settled. A Zoho CRM script built on V2 and run over several weeks could stop before the final delta sync.
How we handle it
MigrateX reads Zoho CRM through the current V8 API, so the full load and the delta sync keep working through cutover.
Source: Zoho Community, checked 15 Nov 2026
Technical profile
What makes this route technical
Zoho CRM sends records, notes, attachments and emails out through separate routes, each paid for in credits that depend on your edition.
- Exporting from Zoho CRM: Bulk Read takes records only
- A Zoho CRM Bulk Read job exports up to 200,000 records into one CSV inside a ZIP that stays downloadable for a day, at 10 download requests a minute. It covers every module except Notes, Attachments, Emails and related or cross modules.
Source: Zoho CRM developer documentation, checked 15 Nov 2026
- Exporting from Zoho CRM: credits follow the edition
- Zoho CRM counts API use in credits over a rolling 24 hours: 5,000 on Free, 50,000 plus 250 a user on Standard (up to 100,000), 50,000 plus 500 a user on Professional (up to 3,000,000) and 50,000 plus 1,000 a user on Enterprise (up to 5,000,000). Starting a Bulk Read job costs 50.
Source: Zoho CRM developer documentation, checked 15 Nov 2026
- Exporting from Zoho CRM: notes and emails come in small pages
- Zoho CRM returns at most 200 records, or 200 notes, in one call, and Get Records needs a page token after the first 2,000. Emails arrive 10 to a call for each record, and every body takes a further call of its own.
Source: Zoho CRM developer documentation, checked 15 Nov 2026
- Exporting from Zoho CRM: the app export is capped per module and per day
- Zoho CRM exports one module at a time, up to 50,000 records as XLSX or 200,000 as CSV, and the number of exports a day depends on the edition, from 10 on Free to 1,000 on Ultimate. The download link lasts seven days.
Source: Zoho Help, checked 15 Nov 2026
- Exporting from Zoho CRM: the backup leaves email out
- A Zoho CRM data backup holds each module as CSV plus attachments, in ZIP files of up to 1 GB, for Administrator-profile users. It excludes email content and email attachments, Documents and integration data.
Source: Zoho Help, checked 15 Nov 2026
- Importing into HubSpot: records and links in one batch call
- HubSpot's object APIs take 100 inputs per batch request and accept associations on create. Activity records also require an hs_timestamp, so every Zoho call, task and event is given its original time.
Source: HubSpot developer documentation, checked 15 Nov 2026
Facts checked 15 Nov 2026 against Zoho and HubSpot documentation. Each fact links its source.
Zoho CRM to HubSpot questions
Still unsure? Ask the engineer who would run this migration, not a sales rep.
How do I migrate from Zoho CRM to HubSpot?
Plan the Zoho read first, then load in lookup order. Users, pipelines and properties come first; then accounts and contacts, leads, deals, activities, notes, emails and files; then a delta sync at cutover. Our default plan takes about 10 business days, and the free sample shows the real pace on your own modules.
Will Zoho created dates and record creators be kept in HubSpot?
Yes, in dedicated HubSpot properties, since Zoho returns Created_Time, Modified_Time and Created_By on every record. Zoho deals also keep Created_Time in HubSpot's Create date, while Create date on contacts and companies is confirmed during your free sample.
Do Zoho notes, attachments and emails come across with the records?
Yes, each by its own route. Zoho CRM notes, attachments and emails are read through record-level calls, joined to their parent record, and loaded as HubSpot notes, email activities and files at their original times.
How do Zoho leads, contacts and converted leads map to HubSpot?
By one rule agreed with you before any record loads: unconverted Zoho leads become HubSpot contacts at a lead lifecycle stage, and each converted lead is matched to the contact it created, so the history sits on one record.
How do Zoho blueprints and workflows get rebuilt in HubSpot?
By your admin, from our documentation. Zoho exposes the transitions of a blueprint through its API, but there is nothing that loads into HubSpot, so we list each blueprint, workflow and approval with its conditions and actions. Your team rebuilds the ones still needed as HubSpot workflows and deal stages.
Will Zoho custom modules become HubSpot custom objects?
On an Enterprise tier of HubSpot, yes, with their records and associations. On other HubSpot tiers, where each Zoho custom module's records go is scoped with you during the free sample.
Does my Zoho CRM edition slow down a migration to HubSpot?
Yes, on the Zoho side. Zoho CRM credits run from 5,000 a day on Free to 50,000 plus 1,000 per user licence, up to 5,000,000, on Enterprise, and concurrent calls from 5 to 25 by edition, so a large database on a small edition takes more days to read. We cost the extract from your record counts before the first call.
What happens to Zoho owners and record ownership in HubSpot?
Each record keeps its current owner and creator. Zoho users are matched to HubSpot users by email, because HubSpot owners are created from users, so everyone who owns a record is added to HubSpot first. A change-by-change trail of past owners is not part of the default load.
Do Zoho deal pipelines and stages match after the move to HubSpot?
Yes, and the report shows it. Zoho's Pipeline and Stage values become HubSpot deal pipelines and stages before deals load, and the reconciliation report compares deal counts by stage on both sides. A Zoho stage with no HubSpot match is flagged before sign-off, not after.
What does a Zoho CRM to HubSpot migration cost?
It is priced on what moves: leads, contacts, accounts and deals, the notes, attachments and emails on them, custom modules and line items, and the Zoho edition's limits. A free sample migration of 100 of your records comes first, and your fixed quote follows within 24 hours.
How it compares
Four ways to run Zoho CRM to HubSpot
The same data, moved four different ways. This is what changes between them.
Object coverage (accounts, contacts, deals, activities, files)
MigrateX
Every object in the mapping on this page, plus the ones you ask for during scoping.
Automated migration software
Contacts and accounts are covered. Deals, activities and their links often are not.
Vendor CSV import
One object per file, and only the fields the export template exposes.
In-house scripts
Whatever you have time to build before the cutover date.
Activities and notes on each record
MigrateX
Each email, call, meeting and note is loaded on its own and linked to the records it belongs to.
Automated migration software
Activities usually arrive, but their links to contacts, deals and owners can be lost.
Vendor CSV import
Notes collapse into one field on the record, if they come across at all.
In-house scripts
Possible, but it is the part teams most often run out of time for.
Files and attachments
MigrateX
Uploaded and linked to the record they belong to. How files over the HubSpot size limit are handled is confirmed during your free sample.
Automated migration software
Supported up to the destination's file size limit. Larger files are skipped.
Vendor CSV import
Not carried by a CSV import.
In-house scripts
Needs its own download, retry and upload pipeline.
Original IDs cross-referenced
MigrateX
Every source id is stored on the destination record and handed back as a map.
Automated migration software
Often kept as a tag or a single text field.
Vendor CSV import
Lost once the file is imported.
In-house scripts
Only if you design the mapping table up front.
Delta sync before cutover
MigrateX
Included. Anything created or changed during the bulk pass is synced at cutover.
Automated migration software
Usually a paid upgrade on the top tier.
Vendor CSV import
You would re-export and re-import by hand.
In-house scripts
Requires change tracking and idempotent writes on both sides.
Rate-limit handling
MigrateX
Paced to your plan limits, honours Retry-After, and resumes from a checkpoint.
Automated migration software
Backs off, but a long run can still stall and leave partial records.
Vendor CSV import
Not applicable, and the file size limits bite instead.
In-house scripts
The most common reason a home-grown run dies overnight.
Validation report
MigrateX
Counts per object and per status on both sides, with every default and placeholder listed.
Automated migration software
A run log and an error list, rather than a reconciliation.
Vendor CSV import
Row counts in a spreadsheet.
In-house scripts
You write the reconciliation queries yourself.
Rollback plan
MigrateX
Every write is tagged, so a batch can be reversed without touching your own records.
Automated migration software
Some approaches can clear a migration, some cannot.
Vendor CSV import
Manual cleanup of everything the import created.
In-house scripts
Only if you built the tagging in from the start.
Who does the work
MigrateX
A MigrateX engineer runs it and stays on the cutover call.
Automated migration software
You run the software. The vendor's support team answers questions.
Vendor CSV import
Your admins, one file at a time.
In-house scripts
Your engineers, instead of your roadmap.
Related routes
Other routes we run
Built for your security review, from the first call.
Read how we handle your data
SOC 2 Type II
Independently audited controls over how we handle your data.
GDPR compliant
Data processing agreement available.
HIPAA compliant
Business associate agreement available.

Start your HubSpot move with 100 of your records.
Scope my migrationFree sample migration of 100 of your records, plus a fixed quote within 24 hours.
