Integration Products | Campaign Creators

Zoho CRM HubSpot Integration | Campaign Creators

Written by Campaign Creators | Nov 17, 2026, 2:40:58 PM
Integration Assessment
Integration Assessment · CRM

Zoho CRM × HubSpot

How a business running Zoho CRM can connect it to HubSpot: what HubSpot's own Zoho CRM app already syncs, what a custom build on the Zoho CRM REST API adds, and how HubSpot becomes the place where marketing, customer data and reporting come together.

Zoho CRM REST API v8OAuth 2.0 per data centerNotification APIHubSpot's Zoho CRM appCustom modules and subformsZoho Books and Zoho Desk data
Platform ownerZoho Corporation
Integration typeHubSpot's app + custom REST build
Primary directionTwo-way, owner set per module
FeasibilityStrong fit
API accessOpen API
01 — Summary

Does Zoho CRM integrate with HubSpot?

Zoho CRM organizes data in modules: standard ones such as Leads, Contacts, Accounts and Deals, and the custom modules each business adds. Every module, standard or custom, is reachable through the same REST API.

API access
Open APIOpen with conditionsGated API

Public documentation. The client's own admin issues credentials, with no vendor approval needed.

Open API. The REST API is documented publicly. The client registers an API client in the Zoho API Console, and a Zoho admin approves the scopes.

Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.

Every Zoho CRM module is reachable by API, so HubSpot can hold the full customer picture while sales keeps working in Zoho.

Campaign Creators assessment

Zoho CRM publishes a REST API (version 8) with OAuth 2.0, a Notification API that pushes record changes to a URL CC hosts, and a Bulk Read API for large exports. HubSpot's own Zoho CRM app is the starting point: it syncs accounts, contacts, leads, deals, calls, meetings, notes, tasks, products and invoices, one-way or two-way, with custom field mappings on Data Hub. Its listing states that custom modules do not sync. The custom build adds custom modules, subforms, blueprint and stage history, layouts, more than one Zoho organization, and data from other Zoho apps in the same account, such as Zoho Books and Zoho Desk.

Scorecard
API & docsExtensive
Real-time eventsPush, renewed
App coveragePartial
Build complexityModerate

Ratings are CC judgments from Zoho's and HubSpot's public documentation. Edition, data center, custom modules and other Zoho apps in use are confirmed per account in discovery.

Strength

Push notifications for any module

The Notification API watches create, edit and delete events per module and calls a CC-hosted URL with a verification token, so changes reach HubSpot without polling.

Plan for

Data center and credit budget

Each Zoho account lives in one data center (US, EU, India, Australia, Japan, Canada, China), and the API domain follows it. Calls draw on a rolling 24-hour credit pool sized by edition and user count.

Gate

Ownership before build

HubSpot's app and the custom build must never write the same field. An ownership table assigns each module and field to one sync path before the build starts.

02 — API modules

Which Zoho CRM APIs does the integration use?

Seven building blocks shape the integration. HubSpot's app covers the standard modules; the REST API, Notification API and Bulk Read API carry everything else.

Starting point

HubSpot's Zoho CRM app

Built by HubSpot · HubSpot Marketplace

HubSpot-built sync for standard modules, one-way or two-way. The custom build extends it rather than replacing it.

  • Accounts, contacts, leads, deals, calls, meetings, notes, tasks, products, invoices
  • Listing states custom modules do not sync
  • Custom field mappings need Data Hub Starter or higher
Integration path

Zoho CRM REST API

{api-domain}/crm/v8 · JSON

Records, related lists and metadata for every module, standard or custom.

  • Read and write any module
  • Field, layout and module metadata read at run time
  • Same API for custom modules
Core

Notification API

POST /crm/v8/actions/watch

Subscribes a CC-hosted URL to events in the form Module.create, Module.edit or Module.delete.

  • Channel expiry up to one week, renewed on a schedule
  • Verification token returned on every callback
  • Covers custom modules as well as standard ones
Backfill

Bulk Read API

Asynchronous export jobs · CSV

Exports large record sets as downloadable CSV files, for the initial load and periodic reconciliation.

  • Built for large exports and backups
  • Zoho describes it as light on API limits
  • Results downloaded as a zipped CSV
Core

Custom modules & subforms

Custom module and subform API names

Custom modules become HubSpot custom objects. Subform rows become line items or associated custom object records.

  • Module and field API names read from metadata
  • Lookups become HubSpot associations
  • Subform rows keep their parent record link
Core

Blueprints & stage history

GET /{module}/{id}/actions/blueprint

The Blueprint API returns the process a record is in, its current state and the next transitions available. Deal stage history adds the path a deal took.

  • Current blueprint state on the HubSpot record
  • Stage changes as timeline events
  • Stage history fields confirmed in discovery
Scope decision

Other Zoho apps

Zoho Books · Zoho Desk

Zoho Books (invoices, payments) and Zoho Desk (tickets) have their own APIs, scopes and organization IDs. Decide per app whether its data comes into HubSpot directly.

  • Books: invoice totals, balances, payments
  • Desk: tickets, status, priority
  • Each app is its own sync module in the SOW
03 — Framework

How does the Zoho CRM HubSpot integration work?

HubSpot's app handles the standard modules. A CC-built integration layer sits beside it for everything else: it receives Zoho notifications, reads the changed records, applies the ownership rules, matches records and writes to HubSpot in batches. HubSpot-owned data travels back to Zoho through the same REST API.

Zoho
Zoho CRM standard modulesleads, contacts, accounts, deals
Custom modules & subformsclient-specific data
Blueprints & stage historyprocess state, transitions
Zoho Books / Zoho Deskinvoices, payments, tickets
CC integration layer
OAuth client per data centerrefresh token, regional API domain
Notification receivertoken check, de-dup, channel renewal
Ownership rulesone sync path per module and field
Identity resolverZoho record ID · email · account
HubSpot writerbatch upserts, credit-aware pacing
HubSpot
Contacts & Companiesleads, contacts, accounts
Deals & Line itemsdeals, subform rows, products
Custom objectsone per custom module in scope
Tickets & InvoicesDesk tickets, Books invoices
Lists, workflows & reportsjourney, pipeline and service views
Zoho → HubSpot (records, history, Books and Desk data)HubSpot → Zoho (leads, score, engagement, HubSpot-owned fields)
Principle

HubSpot brings the customer view together

Marketing engagement, sales activity, invoices and tickets meet on one HubSpot record, whichever Zoho app created each piece.

Principle

Extend the app, don't duplicate it

Standard modules stay on HubSpot's Zoho CRM app. The custom layer handles only what the app does not, so two syncs never write the same field.

Principle

Zoho keeps its own rules

Blueprint transitions, validation rules and invoice balances are calculated in Zoho. HubSpot stores the results and never recalculates them.

04 — Process

What does Zoho CRM HubSpot integration setup involve?

Each phase ends on a gate the client signs off before the next begins. HubSpot's app is set up first, so the custom build only adds what the app does not cover.

1

Discovery & ownership

List the Zoho edition, data center, organizations, layouts, custom modules and other Zoho apps in use. Agree the use case (side by side, by organization, or a phased move) and which system owns each module and field.

Gate to next phaseSigned module and field ownership table
2

Access & app setup

Register the client in the Zoho API Console in the account's data center, agree scopes with the Zoho admin, add the Modified By field HubSpot's app needs, and install HubSpot's app for the modules it covers.

Gate to next phaseToken works against a Zoho sandbox; app syncing default modules
3

Metadata audit

Read modules, fields, layouts, picklists, subforms and blueprints through the metadata APIs, and estimate daily credit use.

Gate to next phaseSigned data dictionary and credit budget
4

HubSpot data model

Create properties, custom objects for custom modules, deal pipelines per layout where processes differ, and association labels, in a HubSpot sandbox.

Gate to next phaseSchema approved and created in sandbox
5

Build

Build the notification receiver, channel renewal, custom module and subform sync, blueprint and stage history events, and the Books and Desk sync modules in scope.

Gate to next phaseEvery in-scope module syncing in sandbox
6

Backfill

Export current records with Bulk Read jobs, load them, then let notifications keep HubSpot current.

Gate to next phaseHubSpot counts reconcile to Zoho views within an agreed tolerance
7

Workflows, parallel run & launch

Build lead handoff, service and reporting automations with sends paused, run two weeks in parallel, then switch on.

Gate to next phaseFive consecutive days with no unresolved sync errors
05 — Data mapping

What does the Zoho CRM HubSpot integration sync?

Zoho field names are API names as Zoho CRM's REST API returns them. Custom module and custom field API names differ per account and are read from metadata during discovery. Rows the HubSpot app covers are noted.

Zoho CRM fieldHubSpot propertyObjectDirectionNotes
Leads, contacts & accounts
Leads.Email / Contacts.EmailemailContact↔ BothMatch key. HubSpot's app maps leads to contacts.
First_Name, Last_Namefirstname, lastnameContact↔ BothOwner set per field in the ownership table.
Contacts.idzoho_contact_idContactZoho → HSPrimary key. Unique.
Leads.Lead_Statuszoho_lead_statusContactZoho → HSPicklist values read from metadata.
Lead_Sourcezoho_lead_sourceContactZoho → HSKept beside HubSpot's own source tracking.
Accounts.Account_NamenameCompany↔ BothHubSpot's app handles the base sync.
Accounts.idzoho_account_idCompanyZoho → HSPrimary key. Unique.
Ownerhubspot_owner_idContact, Company↔ BothMatched by user email.
Layoutzoho_layoutCompanyZoho → HSDifferent layouts can mean different processes.
Deals, products & history
Deals.Deal_Name, Amountdealname, amountDeal↔ BothHubSpot's app handles the base sync.
Deals.StagedealstageDeal↔ BothPipeline per layout where processes differ.
Deals.Closing_DateclosedateDeal↔ Both
Deals.idzoho_deal_idDealZoho → HSPrimary key. Unique.
Deal stage historyCustom event: Stage changedDealZoho → HSStage path with dates. Fields confirmed in discovery.
Blueprint process_info (current state)zoho_blueprint_stateDealZoho → HSFrom the Blueprint API.
Subform rows (products, quantities)Line itemsLine itemZoho → HSSubform API names read from metadata.
Products.Product_Name, Unit_Pricename, priceProductZoho → HSHubSpot's app covers products.
Custom modules
Custom module recordsCustom object recordsCustom object↔ BothOne HubSpot object per module in scope.
Lookup fieldsAssociation labelsCustom objectZoho → HSLookups become associations.
Subforms inside custom modulesChild custom object recordsCustom objectZoho → HSLinked to the parent record.
Zoho Books & Zoho Desk
Books invoice_number, total, balance, statusInvoiceInvoiceZoho → HSRead-only in HubSpot.
Books open balance per customerzoho_books_balanceCompanyZoho → HSRolled up in the integration layer.
Books customer paymentszoho_books_last_paymentCompanyZoho → HSLatest payment date.
Desk ticketNumber, subject, status, priorityTicketTicketZoho → HSStatuses map to a dedicated ticket pipeline.
Desk open tickets per accountzoho_desk_open_ticketsCompanyZoho → HSCount, calculated in the integration layer.
Marketing context to Zoho
Custom fields for score and last engagementhubspotscore, last engagementContactHS → ZohoSellers see HubSpot's marketing context in Zoho. Fields created in discovery.
06 — Auth & API

How are authentication and API limits handled?

Values Zoho publishes are stated; anything account-specific is marked for confirmation.

TopicZoho CRMHubSpot
Access modelA client registered in the Zoho API Console in the account's data center; a Zoho admin approves the scopes.Private app access token or OAuth public app, scoped per object. Custom objects need an Enterprise subscription.
InterfacesZoho CRM REST API v8 (JSON over HTTPS), with Notification, Bulk Read, Blueprint and metadata APIs.REST APIs: CRM objects, associations, pipelines, imports.
AuthenticationOAuth 2.0. Access tokens last one hour; refresh tokens stay valid until revoked. The accounts URL and API domain differ per data center (for example accounts.zoho.eu and www.zohoapis.eu).Bearer token on every call.
Change detectionNotification API channels per module event. Expiry can be set up to one week; without it, channels expire after one hour.Webhooks for HubSpot-side changes.
Rate limitsCredits per rolling 24 hours: 50,000 plus a per-user allowance by edition (250 Standard, 500 Professional, 1,000 Enterprise, 2,000 Ultimate). Concurrency from 50 to 300 calls by edition.Per-10-second burst and daily limits by subscription tier.
Other Zoho appsZoho Books and Zoho Desk have their own APIs, scopes and organization IDs; Desk calls carry an orgId header.Invoices and Tickets objects receive their data.
HubSpot's app setupEach Zoho CRM module that syncs needs the Modified By field.Installed by a Super Admin or a user with App Marketplace permissions. Custom field mappings need Data Hub Starter or higher.
07 — Issues & opportunities

What should you plan for, and what does the integration unlock?

Severity reflects impact on the SOW, not technical difficulty alone.

Challenges to plan for

Two sync paths on one moduleHigh

If HubSpot's app and the custom layer both map a field, they overwrite each other. The ownership table assigns every field to exactly one sync, and the app mapping is switched off where the custom build takes over.

Custom modules sit outside the appHigh

HubSpot's listing states custom modules do not sync. Every custom module in scope is a custom object plus a sync module in the SOW.

Credit budgetMedium

Every call spends credits from a rolling 24-hour pool. The integration batches reads, uses Bulk Read for exports and alerts before the pool runs low.

Notification channels expireMedium

Channels last up to one week. The integration layer renews them on a schedule and runs a catch-up read after any gap.

Picklists and layouts differMedium

Stages, statuses and layouts are set per account. The mapping is built from the account's metadata, and each layout with its own process gets its own HubSpot pipeline.

Data center routingLow

Tokens and API calls must go to the account's data center. Confirm it in discovery; a second organization in another data center needs its own client.

Opportunities in HubSpot

Marketing context for Zoho sellersHigh value

Score and last engagement land on the Zoho record, so sellers see what each contact has read and done before they call.

Finance and service on one recordHigh value

Books balances and Desk tickets sit on the HubSpot company, so renewal, collections and expansion workflows use real data.

One reporting layerHigh value

Marketing attribution, pipeline, invoices and tickets meet in HubSpot dashboards.

Blueprint-aware automationMedium value

A deal's blueprint state can trigger HubSpot tasks, sequences or internal alerts at the right step.

Clear lead handoffMedium value

Contacts that meet agreed criteria become Zoho leads with their source and score, and the outcome comes back to HubSpot.

A phased move when the client is readyMedium value

With history and custom modules already in HubSpot, ownership can move module by module without a second migration project.

Coexistence plan

Decide what each system owns, then set the pace.

Most clients run both systems side by side for a period. The integration is the same whether that period is permanent or the first step of a move to HubSpot; only the ownership table changes.

  1. Side by side: sales works in Zoho CRM, marketing works in HubSpot, and HubSpot reports on the full journey.
  2. By organization: each Zoho organization keeps its own records and meets the others in one HubSpot portal.
  3. Finance and service: add Zoho Books and Zoho Desk data so the HubSpot record shows invoices and tickets.
  4. Phased move: history and custom modules are loaded into HubSpot first, then ownership moves module by module.
08 — Property schema

Which HubSpot properties does the integration create?

All custom properties use the zoho_ prefix in a Zoho property group. Records synced by HubSpot's Zoho CRM app keep that app's own properties; these extend them.

Internal nameLabelObjectTypeSource / logic
zoho_contact_idZoho Contact IDContactSingle-line textContacts.id; unique
zoho_lead_statusZoho Lead StatusContactDropdownLeads.Lead_Status
zoho_lead_sourceZoho Lead SourceContactDropdownLead_Source
zoho_account_idZoho Account IDCompanySingle-line textAccounts.id; unique
zoho_layoutZoho LayoutCompanyDropdownRecord layout name
zoho_org_idZoho OrganizationCompanyDropdownSource organization when more than one
zoho_deal_idZoho Deal IDDealSingle-line textDeals.id; unique
zoho_blueprint_stateBlueprint StateDealSingle-line textBlueprint API current state
zoho_books_balanceBooks Open BalanceCompanyNumber (currency)Sum of open invoice balances
zoho_books_last_paymentBooks Last PaymentCompanyDate pickerLatest customer payment
zoho_desk_open_ticketsDesk Open TicketsCompanyNumberCount of open Desk tickets
09 — Scope builder

Interactive scope builder

Choose the modules and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.

Scope summary

0Fields
0Inbound
0Write-back
Zoho CRM × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

Zoho CRM HubSpot integration FAQ

Does Zoho CRM integrate with HubSpot?

Yes. HubSpot’s Zoho CRM app syncs accounts, contacts, leads, deals, calls, meetings, notes, tasks, products and invoices, one-way or two-way, but its listing states that custom modules do not sync. Campaign Creators extends it with a custom build on the Zoho CRM REST API (v8) for custom modules, subforms, blueprint and stage history, more than one Zoho organization, and Zoho Books and Zoho Desk data.

What data syncs between Zoho CRM and HubSpot?

Leads, contacts and accounts sync to HubSpot contacts and companies; deals, stages and subform rows sync to HubSpot deals and line items; and each custom module in scope becomes a HubSpot custom object. Zoho Books invoices, balances and payments and Zoho Desk tickets are written to HubSpot, and HubSpot score and last engagement are written back to Zoho so sellers see the marketing context.

Which system owns which data?

Each module and field has one owner and one sync path, set in an ownership table the client signs before the build. HubSpot’s app keeps the standard modules and the custom layer handles only what the app does not cover, so two syncs never write the same field. Blueprint transitions, validation rules and invoice balances are calculated in Zoho; HubSpot stores the results and never recalculates them.

What does setting up the Zoho CRM HubSpot integration involve?

Seven phases, each closed by a client sign-off: discovery and ownership, access and app setup (an API client registered in the Zoho API Console in the account’s data center and HubSpot’s Zoho CRM app installed), a metadata audit with a daily credit budget, the HubSpot data model, the build, a Bulk Read backfill, and workflows with a two-week parallel run before launch.

How long does the integration take and what does it cost?

Timeline and cost depend on the modules, custom modules, fields and other Zoho apps in scope (for example Zoho Books, Zoho Desk or more than one Zoho organization). Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.