Does Zoho CRM Work in China? Data Residency, PIPL & the Two Data Centers
Zoho CRM runs a mainland-China data center (CN, zoho.com.cn) — but each data center holds only the data of users who registered there, so a global Zoho org keeps its China contacts, leads and deals offshore, a cross-border transfer under PIPL. A compliance-first look at the two data centers.
Does Zoho CRM work in China?
Whether you can use Zoho CRM in China is first a data-residency question, not a speed one. Zoho CRM holds the contacts, leads, deals and conversation history your sales team runs on, and China's law responds to where that personal data is stored.
Here the answer is genuinely two-sided, and Zoho states both halves in its own Multi DC documentation. It runs a data center inside mainland China (CN, at accounts.zoho.com.cn), yet it also rules that "Each DC exclusively holds the data of users who have registered at that domain." So if your organization signed up on global Zoho (zoho.com, .eu, .in, .com.au, .jp, zohocloud.ca), your China users' records sit offshore — a cross-border transfer of personal information PIPL governs, needing notice, separate consent, a transfer mechanism, and for a CIIO or large-volume handler, in-country storage. If instead your org is on the China data center, that data can stay in the mainland — but it is a separate, siloed account you register into, not a toggle on your existing global org. The facts below are Zoho's own wording and the rules they trigger.
This is a risk picture, not a verdict — your obligations turn on which data center you are on, your data volumes and your role. Our China team can map your Zoho CRM exposure with you →
What Zoho CRM's own documentation says about China
| Fact | Primary source |
|---|---|
In Zoho's own words: its Multi DC documentation lists seven data centers — US, AU, EU, IN, CN, JP and CA — including a mainland-China region reached at accounts.zoho.com.cn, and states that "Each DC exclusively holds the data of users who have registered at that domain." Where your organization signed up therefore decides where your CRM's personal data lives, and the data centers are siloed. | Zoho CRM — Multi DC Support (developer documentation), retrieved 2026-10-07 |
| If your org is on a global Zoho data center, the contacts, leads and deals you hold for people in China are stored outside the mainland. PIPL governs that cross-border transfer: the personal-information handler (you, Zoho's customer — not Zoho) must give notice, obtain separate consent, and satisfy one transfer mechanism — a CAC security assessment, the CAC standard contract, or certification. | PIPL Chapter III, Articles 38–43 |
| The exposure scales with volume and role, not merely with using the tool: under the CAC's March 2024 cross-border rules, a non-CIIO transferring fewer than 100,000 individuals' non-sensitive personal information in a calendar year is exempt from the security assessment, standard contract and certification. | CAC — Regulations on Promoting and Regulating Cross-border Data Flows, March 2024 |
| For a CIIO or large-volume handler, personal information collected in China must be stored inside mainland China (PIPL Article 40; CSL Article 37). Because Zoho's data centers are siloed, the only Zoho path that meets this is being registered on the China data center — and a China-facing site that collects this data through embedded Zoho forms is itself an internet information service that brings an ICP filing into the picture. | PIPL Article 40; CSL Article 37; Zoho — Multi DC Support (data-center regions), retrieved 2026-10-07 |
Sources verified by the 21YunBox compliance team on 2026-10-07.
For a mainland-China audience, the first question about Zoho CRM is not how quickly it loads — it is where the customer records it holds are allowed to live. Zoho CRM stores the contacts, leads, deals and conversation history your sales team runs on, and China’s law responds to where that personal data sits. Here the answer is genuinely two-sided, and Zoho states both halves in its own documentation: it runs a data center inside mainland China, and it keeps each customer’s data only in the region where that customer signed up. So whether Zoho CRM is compliant for your China users turns on a single fact — which of Zoho’s data centers your organization is on.
accounts.zoho.com.cn alongside its US, Australian, European, Indian, Japanese and Canadian regions, and states that “Each DC exclusively holds the data of users who have registered at that domain.” Source: zoho.com/crm/developer/docs/api/v8/multi-dcZoho CRM in China at a glance
| What decides it | In Zoho's own terms |
|---|---|
| Where it runs | Seven data centers — US (zoho.com), AU (zoho.com.au), EU (zoho.eu), IN (zoho.in), CN (zoho.com.cn), JP (zoho.jp) and CA (zohocloud.ca). One of them, CN, is inside mainland China. |
| How your data location is set | “Each DC exclusively holds the data of users who have registered at that domain.” Where you signed up decides where your CRM data lives, and the data centers are siloed from one another. |
| On global Zoho | Your China contacts, leads and deals are stored offshore (US, EU, India, Australia, Japan or Canada) — a cross-border transfer of personal information PIPL governs. |
| On the China data center | Records created on zoho.com.cn stay in the mainland — but it is a separate account and domain, not a region you can switch your existing global org into with a setting. |
| Serving the public | A China-facing site that embeds Zoho web-to-lead forms is itself an internet information service that needs an ICP filing, and each submission carries a visitor's details to whichever data center your org uses. |
Door one — Zoho does run a mainland-China data center
Zoho CRM is one of the few global SaaS CRMs that operates a data center inside mainland China. Its Multi DC documentation lists a CN data center reached at “accounts.zoho.com.cn” alongside its US, Australian, European, Indian, Japanese and Canadian regions. That matters, because it means in-country storage of your CRM’s personal data is at least possible without leaving Zoho — the thing a vendor with no mainland presence cannot offer at all.
But two conditions sit on that door. First, Zoho’s own rule: “Each DC exclusively holds the data of users who have registered at that domain.” The data centers are siloed; your data lives where your organization signed up, and an account created on zoho.com is not served from the China region. Second, moving an existing global org onto the China data center is a migration between separate data centers, not a toggle in settings — and the two accounts do not share data. So “we already use Zoho CRM” does not, by itself, put your China data in China; that depends entirely on which domain your org was created under.
Door two — on global Zoho, your China CRM data stays offshore
If your organization registered on zoho.com (or .eu, .in, .com.au, .jp, zohocloud.ca), that is where your records stay — including every contact, lead and deal belonging to a person in China. Under China’s Personal Information Protection Law, holding that personal information outside the mainland is a cross-border transfer, and the personal-information handler — you, Zoho’s customer, not Zoho — has to give notice, obtain separate consent, and clear one transfer mechanism: a CAC security assessment, the CAC standard contract, or certification.
The weight of that duty scales with volume and role. Under the CAC’s March 2024 cross-border rules, a non-CIIO moving fewer than 100,000 individuals’ non-sensitive personal information in a calendar year is exempt from all three mechanisms; a critical information infrastructure operator or large-volume handler, by contrast, must keep personal information collected in China inside the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)). For that second group, Zoho’s China data center stops being a convenience and becomes the only Zoho path that meets the residency duty at all.
The public-facing edge — lead forms and an ICP filing
There is a second compliance surface the moment you collect from China. A Zoho web-to-lead or contact form embedded on a China-facing website makes that website an internet information service, which turns on an ICP filing tied to a mainland hosting resource under State Council Order No. 292 and MIIT Order No. 33 — and each submission carries a person’s details to whichever Zoho data center your org uses. So a single form can raise both doors at once: the ICP filing for the public collection point, and the cross-border transfer for where the data finally lands.
This is a risk map, not a verdict: which door you are standing in, and whether you face a localization duty at all, depends on your entity, your data volumes and who your users are — worth settling with counsel before you build.
Where 21YunBox fits — a compliant overlay, not a migration
Your team keeps working in Zoho CRM exactly as it does today. What we add is the piece Zoho leaves to you: compliant, ICP-filed delivery from inside the mainland for the China-facing properties that feed and surface your CRM — lead forms, customer portals and marketing pages — set in front of your existing origin, with no rebuild and no second codebase. Our China team maps which Zoho data center you are on, assesses your PIPL cross-border and data-residency exposure for your entity and data volumes, and, where the law requires your China users’ data to stay on the mainland, stands up the in-country delivery and storage a compliant presence needs.
Related reading:
