Does Fivetran Work in China? Data Residency, ICP & Cross-Border Rules
Fivetran is a managed ELT service that extracts from your sources and loads into a cloud warehouse, so moving China-origin data (often personal information) offshore is itself a PIPL cross-border transfer, not a speed test. Fivetran's managed cloud has no mainland-China region, but its Hybrid Deployment keeps the pipeline and data on infrastructure you control, in-country.
Does Fivetran work in China?
It can — but what decides it is where the pipeline runs and where it lands your data, because with Fivetran that is a data-residency question, not a "can we reach it" one. Fivetran is a managed ELT service whose whole job is to carry data from your sources into a destination, so when a pipeline moves China-origin data (routinely including personal information) to an offshore warehouse, the sync itself is the cross-border transfer.
Fivetran's managed cloud has no mainland-China processing region, so the default pipeline lands your data offshore — a cross-border transfer (数据出境) under PIPL Articles 38–40, with in-country storage duties under the Cybersecurity Law's Article 39 (formerly Article 37) for a critical information infrastructure operator or high-volume handler. The residency lever is real, though: Fivetran's Hybrid Deployment runs the processing agent on infrastructure you control, so the pipeline and data can stay in-country — while the control plane, metadata and logs still reach Fivetran's offshore cloud, a smaller flow to assess.
21YunBox maps what your pipelines carry, helps you run the engine in-country and land China-origin data in a China-resident destination, secures a lawful transfer basis only where data must truly leave, and delivers your China-facing stack on ICP-filed infrastructure — no rebuild, and never any form of circumvention. Confirm the specifics with counsel.
What Fivetran's own documentation says about China
| Fact | Primary source |
|---|---|
| Fivetran's Hybrid Deployment keeps the data in your own network. Fivetran's documentation states that its Hybrid Deployment model “processes data within your infrastructure, keeping your actual data within the secure boundaries of your network,” that “You host this agent on your infrastructure,” and that “Only metadata (including MAR information) and logs are sent to Fivetran” — so running the agent on in-country infrastructure keeps the pipeline and data resident, while the control plane stays in Fivetran's cloud. | Fivetran Docs, “Hybrid Deployment” (fivetran.com/docs), retrieved 2026-10-12 |
| Fivetran's managed cloud lists no mainland-China region. Fivetran's region/privacy documentation lists data-processing locations across the US, UK, EU, Canada, Australia, Singapore, India, Japan, South Korea, Indonesia, the Middle East and Switzerland, and states that “All connections configured in a destination run in the destination's designated location” — no mainland-China location appears, so a managed pipeline processing China-origin data lands it offshore. | Fivetran Docs, “Data Processing / Privacy” region list (fivetran.com/docs/security-and-privacy/privacy), retrieved 2026-10-12 |
| Moving China-origin personal information offshore is a regulated cross-border transfer. Under PIPL Articles 38–40, sending personal information collected in mainland China to an offshore destination requires a lawful transfer mechanism — a CAC security assessment, the CAC standard contract, or certification — plus notice and, for sensitive personal information, separate consent. | China cross-border data transfer rules (PIPL Articles 38–40), 21YunBox compliance reference, retrieved 2026-10-12 |
| CIIOs and high-volume handlers owe in-country storage. The Cybersecurity Law's Article 39 (formerly Article 37) requires personal information generated in mainland China to be stored in the mainland for a critical information infrastructure operator or high-volume handler — a duty an offshore managed pipeline cannot meet, but an in-country Hybrid deployment landing data in a China-resident destination can. | China Cybersecurity Law, Article 39 (formerly Article 37), 21YunBox compliance reference, retrieved 2026-10-12 |
Sources verified by the 21YunBox compliance team on 2026-10-12.
For a data team running Fivetran into a mainland-China-facing product, the question that matters is not whether the Fivetran dashboard paints quickly from Shanghai. Fivetran is a managed ELT service whose entire job is to move data: it extracts from your sources — operational databases, SaaS applications, event streams — and loads it into a destination, usually a cloud data warehouse. The moment one of those pipelines carries data collected in mainland China to a destination that sits offshore, the pipeline run is itself a cross-border transfer, and the rows in flight routinely include personal information — customer and user tables, contact records, behavioral events. The compliance axis here is residency and cross-border transfer, not latency. What decides the China answer is not reachability but where the pipeline engine runs and where it lands the data — and here the lever genuinely exists, because Fivetran’s Hybrid Deployment runs the processing agent on infrastructure you control. Three prongs decide it: the residency and cross-border exposure of the data the pipeline carries, including the personal information in it; the distinctive second half a reachability check never sees — that the pipeline operation is the border crossing, not merely access to a tool; and the self-managed engine that lets you keep the compute and the data in-country.
Fivetran in China at a glance
| What decides it | In Fivetran's own terms — and China's law |
|---|---|
| What it moves | Fivetran's job is to carry data across systems: it extracts from your sources — databases, SaaS apps, event streams — and loads into a destination warehouse. The rows in flight routinely include customer and user tables, contact records and behavioral events. Wherever those name or describe a person they are personal information under China's law. |
| No mainland-China region (managed cloud) | Fivetran's managed SaaS lists data-processing regions in the US, UK, EU, Canada, Australia, Singapore, India, Japan, South Korea, Indonesia, the Middle East and Switzerland — and no mainland-China region (Fivetran privacy/regions documentation, retrieved 2026-10-12). Run the default managed pipeline and your China-origin data is processed and lands offshore. |
| The pipeline IS the transfer — the distinctive second half | The half a reachability check never sees. It is not whether your data team can open the Fivetran dashboard from Shanghai — it is that Fivetran exists to carry your data across systems, so a pipeline moving China-origin data to an offshore destination is itself the cross-border transfer, on every sync. A page-load test watches the dashboard paint; it cannot see which rows are moving, whether they contain personal information, or that they are leaving the country. |
| Hybrid Deployment — the self-managed lever (the premise) | Fivetran's own documentation states that its Hybrid Deployment model “processes data within your infrastructure, keeping your actual data within the secure boundaries of your network,” that “You host this agent on your infrastructure,” and that “Only metadata (including MAR information) and logs are sent to Fivetran.” Run that agent in-country and the pipeline and the data stay resident — while the control plane, orchestration and logs still live in Fivetran's offshore cloud, a smaller flow to assess. (Fivetran also lists a separate Self-Hosted, HVR-based model.) |
| Residency & cross-border | Landing China-origin personal information in an offshore destination is a cross-border transfer (数据出境) under PIPL Articles 38–40 — notice, a transfer mechanism (a CAC security assessment, the CAC standard contract, or certification), and separate consent for sensitive personal information. For a critical information infrastructure operator or a high-volume handler, Cybersecurity Law Article 39 (formerly Article 37) requires China-collected personal information to be stored in the mainland — which the offshore pipeline cannot satisfy but an in-country Hybrid deployment can. |
| Reachability is not the axis | Whether the dashboard loads quickly from the mainland is operational, not the compliance question. What decides it is where the pipeline runs, where the data lands, and under what consent and transfer basis. 21YunBox helps you run the engine in-country, keep regulated data resident, ICP-file any China-facing surface, and deliver compliantly — the 21YunBox Optimizer — in front of the warehouse and tools you already run. Never circumvention of any kind. |
What Fivetran actually moves — your source data, and the people in it
Fivetran is not a website; it is data plumbing, and the whole point of it is that your data does not sit still. Every connector reaches into a source — a production database, a CRM or support tool, an ad platform, a stream of product events — and copies rows into a destination warehouse on a schedule. That cargo is rarely anonymous. Customer and user tables, order and contact records, support tickets, and behavioral event streams all travel through the pipeline, and wherever those rows name or describe a person they are personal information under China’s Personal Information Protection Law. Some of it is sensitive personal information, which carries heavier duties again. So the question “does Fivetran work in China” is really a question about a flow of regulated data: what the pipeline carries, where it starts, and where it ends up — because a managed ELT service is, by definition, in the business of moving that cargo from one place to another.
The doors: residency, cross-border, and the ICP surface
Point a Fivetran pipeline at a destination that lives offshore — which, on the managed cloud, is the only option, since Fivetran lists processing regions across the US, UK, EU, Canada, Australia, Singapore, India, Japan, South Korea, Indonesia, the Middle East and Switzerland, but none in mainland China — and the first door opens. Moving personal information collected in mainland China to that offshore destination is a cross-border transfer (数据出境). The duty lands on you, the handler, not on Fivetran: PIPL Articles 13 and 23 require notice and a basis to collect the data, and Articles 38–40 require a transfer mechanism to send it offshore — a CAC security assessment, the CAC standard contract, or certification — with separate consent for sensitive personal information. Depending on the data, its volume, and whether you are a critical information infrastructure operator, that transfer may be subject to China’s data-export security assessment.
For a critical information infrastructure operator or a high-volume handler, the Cybersecurity Law’s Article 39 (formerly Article 37 — the 2025 Cybersecurity Law amendment, in force January 1, 2026, renumbered the data-localization article from 37 to 39, its substance unchanged) requires personal information generated in China to be stored in the mainland. The offshore managed pipeline has no China region and cannot satisfy that duty; a Hybrid Deployment that runs the engine in-country and lands the data in a China-resident destination can, which is exactly why the China answer here is warn, not no.
The ICP door is narrower for a pipeline than for a website. A Fivetran pipeline is mostly internal plumbing, so it does not, on its own, usually trigger an ICP filing. But the moment you serve a China-facing surface built on that data — a customer-facing app, a dashboard or reporting portal served to mainland users — that surface is an internet information service and carries an ICP filing (备案) duty bound to a mainland hosting resource.
The self-managed engine is the residency lever
It is tempting to think the China question is answered by making the Fivetran dashboard reachable from the mainland, or by choosing the nearest offshore region. It is not. A nearer offshore region is still offshore; reachability moves nothing in-country. The lever that actually answers the residency question is where the pipeline engine runs. Fivetran’s Hybrid Deployment is built for exactly this: you host the processing agent on your own infrastructure, the agent manages the data pipeline processing within your network, and — in Fivetran’s own words — it “processes data within your infrastructure, keeping your actual data within the secure boundaries of your network,” with “Only metadata (including MAR information) and logs” sent to Fivetran. Run that agent on in-country infrastructure and the pipeline compute and the data stay resident in the mainland.
Be precise about what that does and does not cover. The data stays in your network; the orchestration and control plane remain in Fivetran’s offshore cloud, and the agent keeps in contact with that control plane and sends it metadata and logs. So the lever closes the big door — the bulk movement of personal information across the border — while leaving a smaller flow (pipeline metadata and logs) to inventory and assess with counsel. That is still a decisively better residency posture than a managed pipeline that carries the whole payload offshore, and it is why a self-managed engine, not reachability, is the real answer.
Why a reachability check misses this
A probe from inside China can load the Fivetran dashboard, watch a connector’s status turn green, and conclude “it works.” That answer is beside the point. The compliance exposure is not on the screen — it is in the data the pipeline moves and where it lands: customer and user tables, contact records and event streams, flowing on a schedule from a mainland source into a destination that, by default, sits abroad. A page-load test measures none of that. It cannot see which rows are moving, whether they contain personal or sensitive information, whether separate consent was taken, whether a transfer mechanism is in place, or that the destination is offshore. That is the competitor-proof second half of the question — and it is exactly why making the Fivetran console merely reachable from the mainland is not the answer. Running the engine in-country, and landing China-origin data in a China-resident destination, is.
The lawful path — map, localize, deliver
There is a compliant way to run Fivetran for a mainland-China operation, and it sits in front of the warehouse and tools you already run — no rebuild, no migration, and never a route that ships data offshore by stealth.
First, map: our China compliance team inventories what each pipeline carries — which sources and destinations, and whether personal or sensitive personal information is in flight — establishes where the pipeline engine and control plane run, where the data lands, and on what lawful-transfer basis. We build the technical picture; the legal conclusions are settled with counsel.
Then localize: because Fivetran offers a self-managed engine, localizing is a genuine option — run the Hybrid Deployment agent on in-country infrastructure so the pipeline compute and the data stay on the mainland, land China-origin data in a China-resident destination, minimize the personal data the pipeline carries, and use a lawful cross-border mechanism (a CAC security assessment, the CAC standard contract, or certification) plus separate consent for sensitive personal information only where a transfer is truly needed. Localize means keeping the data on an in-country path — never a route, of any kind, that ships it offshore or reaches back across the border to retrieve it.
Then deliver: any China-facing surface built on that data is an internet information service, so it carries an ICP filing duty and needs compliant, in-country delivery, and your data team needs fast, reliable access to the tools from the mainland. 21YunBox delivers that in-country — the 21YunBox Optimizer — in front of the stack you already run, so your China-facing app, dashboards and tool access run legally and compliantly for your users in China. 21YunBox never uses or suggests circumvention of any kind — we keep in-country what the law says must stay, deliver the rest compliantly from inside the mainland, and never move personal information across the border by stealth. 21YunBox is a compliance overlay and partner to the platform you already run, not a competitor to it.
None of this is a verdict that Fivetran is “blocked” or “illegal” in China; it is a risk-and-residency map. Which duties bite your case turns on your entity, your role under Chinese law, your data volumes, and what your pipelines actually carry — worth settling the specifics with counsel before your China-facing data flow depends on it.
Related reading:
- How to get an ICP filing for China
- Cross-border data transfers under PIPL
- China’s Personal Information Protection Law (PIPL)
- China’s Cybersecurity Law (data localization, Article 39)
