Zoho CRM + ERPNext Integration: Keep the CRM, Add the ERP

I lead ERPNext and Frappe programmes at MithTech, a small senior AI-assisted team of Frappe specialists in Bengaluru. We connect ERPNext to the CRMs teams already use, Zoho CRM among them. An integration is a contract between two systems about who owns what. Write that down first and the code is the easy part.

Who keeps Zoho CRM and adds ERPNext?

Businesses whose sales process lives happily in Zoho CRM, but whose operations need more than an accounting app: stock across several warehouses, bills of materials, job work, several companies, or approvals before purchases. They keep the CRM the sales team knows and add ERPNext behind it, instead of retraining everyone.

Zoho has its own answer for the accounts side: the Zoho CRM and Zoho Books integration. Per Zoho's help, CRM accounts and contacts become customers in Books, products become items, and new records sync every two hours after the first sync. Quotes, sales orders and invoices sync only when they are created in CRM's Zoho Finance module. When Books covers your accounting and stock, that pairing works well and you need nothing else.

ERPNext comes in when the back office needs a full ERP. If you are also weighing a full move, ERPNext vs Zoho has the side-by-side.

What syncs, and which system owns it?

Customers and contacts flow from Zoho CRM to ERPNext. Items and prices flow from ERPNext to Zoho CRM. A won deal creates a quotation or sales order in ERPNext. Invoice and payment status flow back to the deal. Each field has exactly one owner, and both systems store each other's record id.

Two-way sync of the same field is where integrations go wrong. If sales can edit a customer's billing address in Zoho CRM and accounts can edit it in ERPNext, one of them will overwrite the other. Pick the owner, make the other side read-only for that field, and move on.

What do you need to know about Zoho CRM's API?

Zoho CRM's current API is V8. It uses OAuth 2.0: an access token is valid for one hour and a refresh token gets new ones until it is revoked. Zoho runs separate data centres, India among them, so the integration must call the right domain for your account. Every call spends API credits.

The credit rules, per Zoho's API limits page:

• Credits are counted in a rolling 24-hour window, not reset at midnight.
• Your allowance depends on your edition and your number of user licences.
• Most calls cost 1 credit; heavy ones cost more, and bulk writes cost 1 credit per 10 records.
• There is also a limit on how many calls can run at the same time, from 5 on the Free edition to 25 on the top edition.

For a daily flow of deals and orders, the credits are rarely the issue. They bite on the first load: pushing thousands of products or customers in one go. Use bulk APIs, spread the load and watch the remaining-credits header Zoho returns once half the allowance is used. Module availability also depends on edition; check Zoho's edition comparison before you design around a module.

How do you get changes out of Zoho CRM?

Two ways. A workflow rule can call a webhook when a deal changes stage, which is simple and immediate. Or the Notification API can watch modules and post every change to your endpoint. Both can miss events, so add a scheduled sweep that asks Zoho for records modified since the last run.

The channel expiry catches people out. Zoho's developer community has a long thread of people asking whether they must recreate channels daily; Zoho's own FAQ answers that from V4 the maximum is one week and you must re-subscribe before it lapses. Put the renewal in a scheduled job, and alert when it fails.

What does the ERPNext side need?

ERPNext exposes every document through its REST API (/api/resource/<DocType>), with token authentication for an API user you create for the integration. Its Webhook feature posts document events to a URL and can sign each request with a secret. Server Scripts can add small logic, but since version 15 they are off by default.

Practical points:

• API user. Create a dedicated user with only the roles the integration needs, and an API key and secret for it.
• Webhooks out. ERPNext's Webhook doctype posts on document events. With a webhook secret set, Frappe adds an X-Frappe-Webhook-Signature header (an HMAC-SHA256 of the payload), so the receiver can check the call came from your ERPNext.
• Custom fields. Add a "Zoho CRM ID" field on Customer, Contact and Sales Order, and store ERPNext's names in Zoho. This is how the two sides find each other.
• Server Scripts. Off by default since version 15 and not allowed on Frappe Cloud's shared benches; a private bench is needed. A small custom app is the cleaner place for logic anyway.

Three ways to build it

n8n, a paid connector, or a small custom service. n8n has a Zoho CRM node and an ERPNext node, so a team can build the flows visually. Webkul sells an ERPNext Zoho CRM connector as one ready option. A custom service on both REST APIs gives the most control. Choose by who will look after it in a year.

Zoho Flow, Zoho's own integration tool, did not list an ERPNext app when we checked its app directory. For the n8n route, our ERPNext and n8n guide covers credentials and patterns; the same patterns power our Shopify integration.

A first flow worth building:

1. A Zoho workflow rule fires a webhook when a deal moves to Closed Won.
2. The integration fetches the deal, its account, contacts and products from Zoho CRM.
3. It finds or creates the customer in ERPNext, matching on the stored Zoho id, then GSTIN, then email.
4. It creates a draft sales order with the deal's products mapped to item codes, and writes ERPNext's order number back to the deal.
5. When the invoice is submitted and paid in ERPNext, a webhook updates the deal's invoice and payment fields.

What goes wrong, and how do you prevent it?

Duplicates, expired tokens and channels, credit caps on big loads, and mismatched products or prices. All are preventable: match before you create, refresh tokens automatically, renew channels on a schedule, load in bulk, and keep a queue of rejected records that a person reviews each day.

• Duplicate customers. Match on the stored id first, then GSTIN, then email. Never create on a name match alone.
• Token expiry. Refresh the one-hour access token before it lapses, and alert if a refresh fails; a revoked refresh token stops everything.
• Missed events. Webhooks retry once; channels expire. A nightly sweep of records modified since the last run fills the gaps.
• Credit caps. First loads use bulk APIs and run off-peak.
• Item mismatch. A deal line with a product that has no item code in ERPNext goes to the rejected queue, not into a guessed item.
• Currency and price lists. Decide which price list a CRM deal uses in ERPNext, and keep currencies consistent on both sides.

The rejected-records queue matters more than any of the above. Integrations fail quietly; a short daily list that someone owns is how you find out.

When should you bring CRM into ERPNext instead?

When the CRM is used lightly: a pipeline, a few follow-ups, quotations. Then ERPNext's own CRM or Frappe CRM can do the job and you drop the integration entirely. When the sales team lives in Zoho CRM's automation, reports and apps every day, keep Zoho CRM and integrate.

A rough test: if you would miss Zoho CRM's features within a week of switching it off, keep it. If you would mostly miss the habit, consider moving it. Our ERPNext CRM guide shows what the built-in CRM covers. If the whole Zoho estate is the question, the Zoho to ERPNext migration guide and Zoho to ERPNext cover the move.

Skimmable summary: integrate when sales live in Zoho CRM; bring CRM into ERPNext when it is used lightly and the link would cost more than it saves.

Frequently asked questions