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 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.
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.
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.
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.
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.
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.
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.
HubSpot-built sync for standard modules, one-way or two-way. The custom build extends it rather than replacing it.
Records, related lists and metadata for every module, standard or custom.
Subscribes a CC-hosted URL to events in the form Module.create, Module.edit or Module.delete.
Exports large record sets as downloadable CSV files, for the initial load and periodic reconciliation.
Custom modules become HubSpot custom objects. Subform rows become line items or associated custom object records.
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.
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.
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.
Marketing engagement, sales activity, invoices and tickets meet on one HubSpot record, whichever Zoho app created each piece.
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.
Blueprint transitions, validation rules and invoice balances are calculated in Zoho. HubSpot stores the results and never recalculates them.
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.
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.
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.
Read modules, fields, layouts, picklists, subforms and blueprints through the metadata APIs, and estimate daily credit use.
Create properties, custom objects for custom modules, deal pipelines per layout where processes differ, and association labels, in a HubSpot sandbox.
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.
Export current records with Bulk Read jobs, load them, then let notifications keep HubSpot current.
Build lead handoff, service and reporting automations with sends paused, run two weeks in parallel, then switch on.
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 field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Leads, contacts & accounts | ||||
| Leads.Email / Contacts.Email | Contact | ↔ Both | Match key. HubSpot's app maps leads to contacts. | |
| First_Name, Last_Name | firstname, lastname | Contact | ↔ Both | Owner set per field in the ownership table. |
| Contacts.id | zoho_contact_id | Contact | Zoho → HS | Primary key. Unique. |
| Leads.Lead_Status | zoho_lead_status | Contact | Zoho → HS | Picklist values read from metadata. |
| Lead_Source | zoho_lead_source | Contact | Zoho → HS | Kept beside HubSpot's own source tracking. |
| Accounts.Account_Name | name | Company | ↔ Both | HubSpot's app handles the base sync. |
| Accounts.id | zoho_account_id | Company | Zoho → HS | Primary key. Unique. |
| Owner | hubspot_owner_id | Contact, Company | ↔ Both | Matched by user email. |
| Layout | zoho_layout | Company | Zoho → HS | Different layouts can mean different processes. |
| Deals, products & history | ||||
| Deals.Deal_Name, Amount | dealname, amount | Deal | ↔ Both | HubSpot's app handles the base sync. |
| Deals.Stage | dealstage | Deal | ↔ Both | Pipeline per layout where processes differ. |
| Deals.Closing_Date | closedate | Deal | ↔ Both | |
| Deals.id | zoho_deal_id | Deal | Zoho → HS | Primary key. Unique. |
| Deal stage history | Custom event: Stage changed | Deal | Zoho → HS | Stage path with dates. Fields confirmed in discovery. |
| Blueprint process_info (current state) | zoho_blueprint_state | Deal | Zoho → HS | From the Blueprint API. |
| Subform rows (products, quantities) | Line items | Line item | Zoho → HS | Subform API names read from metadata. |
| Products.Product_Name, Unit_Price | name, price | Product | Zoho → HS | HubSpot's app covers products. |
| Custom modules | ||||
| Custom module records | Custom object records | Custom object | ↔ Both | One HubSpot object per module in scope. |
| Lookup fields | Association labels | Custom object | Zoho → HS | Lookups become associations. |
| Subforms inside custom modules | Child custom object records | Custom object | Zoho → HS | Linked to the parent record. |
| Zoho Books & Zoho Desk | ||||
| Books invoice_number, total, balance, status | Invoice | Invoice | Zoho → HS | Read-only in HubSpot. |
| Books open balance per customer | zoho_books_balance | Company | Zoho → HS | Rolled up in the integration layer. |
| Books customer payments | zoho_books_last_payment | Company | Zoho → HS | Latest payment date. |
| Desk ticketNumber, subject, status, priority | Ticket | Ticket | Zoho → HS | Statuses map to a dedicated ticket pipeline. |
| Desk open tickets per account | zoho_desk_open_tickets | Company | Zoho → HS | Count, calculated in the integration layer. |
| Marketing context to Zoho | ||||
| Custom fields for score and last engagement | hubspotscore, last engagement | Contact | HS → Zoho | Sellers see HubSpot's marketing context in Zoho. Fields created in discovery. |
Values Zoho publishes are stated; anything account-specific is marked for confirmation.
| Topic | Zoho CRM | HubSpot |
|---|---|---|
| Access model | A 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. |
| Interfaces | Zoho CRM REST API v8 (JSON over HTTPS), with Notification, Bulk Read, Blueprint and metadata APIs. | REST APIs: CRM objects, associations, pipelines, imports. |
| Authentication | OAuth 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 detection | Notification 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 limits | Credits 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 apps | Zoho 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 setup | Each 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. |
Severity reflects impact on the SOW, not technical difficulty alone.
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.
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.
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.
Channels last up to one week. The integration layer renews them on a schedule and runs a catch-up read after any gap.
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.
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.
Score and last engagement land on the Zoho record, so sellers see what each contact has read and done before they call.
Books balances and Desk tickets sit on the HubSpot company, so renewal, collections and expansion workflows use real data.
Marketing attribution, pipeline, invoices and tickets meet in HubSpot dashboards.
A deal's blueprint state can trigger HubSpot tasks, sequences or internal alerts at the right step.
Contacts that meet agreed criteria become Zoho leads with their source and score, and the outcome comes back to HubSpot.
With history and custom modules already in HubSpot, ownership can move module by module without a second migration project.
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.
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 name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| zoho_contact_id | Zoho Contact ID | Contact | Single-line text | Contacts.id; unique |
| zoho_lead_status | Zoho Lead Status | Contact | Dropdown | Leads.Lead_Status |
| zoho_lead_source | Zoho Lead Source | Contact | Dropdown | Lead_Source |
| zoho_account_id | Zoho Account ID | Company | Single-line text | Accounts.id; unique |
| zoho_layout | Zoho Layout | Company | Dropdown | Record layout name |
| zoho_org_id | Zoho Organization | Company | Dropdown | Source organization when more than one |
| zoho_deal_id | Zoho Deal ID | Deal | Single-line text | Deals.id; unique |
| zoho_blueprint_state | Blueprint State | Deal | Single-line text | Blueprint API current state |
| zoho_books_balance | Books Open Balance | Company | Number (currency) | Sum of open invoice balances |
| zoho_books_last_payment | Books Last Payment | Company | Date picker | Latest customer payment |
| zoho_desk_open_tickets | Desk Open Tickets | Company | Number | Count of open Desk tickets |
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.
Based on public documentation from Zoho and HubSpot. Each item marked for confirmation is verified with the client's Zoho admin during discovery.
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.
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.
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.
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.
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.