If you plan to run a business in China or work with customers there, a well-built IT environment is essential. Technical choices impact regulatory compliance, user experience, and cost. China has unique legal and network requirements—like ICP registration, PIPL, and cross-border routing—so your plan’s order matters. This guide provides a clear, step-by-step path so your team can move from planning to production with minimal surprises.
Key Takeaways
Below let’s walk through all these steps in chronological order:
Step 1: Register the domain and decide on ICP registration
- Register your domain early and decide whether you will host your public site on mainland infrastructure.
Why?
- Domain ownership and hosting location are prerequisites for Internet Content Provider (ICP) registration and affect go-live timing.
How?
- Choose a registrar that supports China filings and can accept business documents.
- If you will host in mainland China, plan an ICP registration. ICP is the official registration required for public websites hosted on mainland infrastructure. See the official portal and a practical guide to the ICP system.
- Decide who holds the ICP license: a local subsidiary or a licensed partner. Foreign companies typically use a local entity or a service provider to hold an ICP. See how to get an ICP license in China.
- Gather documents: company registration, ID for admin contacts, and hosting details, then submit via your registrar/provider. Expect review cycles; plan weeks to months.
Flowchart of ICP application in China
Step 2: Map data flows and meet PIPL obligations
- Create a data map that shows where personal data is collected, stored, processed, and transferred.
Why?
- The Personal Information Protection Law (PIPL) requires lawful processing and imposes stricter rules on cross-border transfers. Start this before architecture selection. Read a practical guide of PIPL.
How?
- Inventory data types, customer PII logs analytics, and where each element lives.
- Decide legal bases for processing and document retention periods.
- Define cross-border safeguards, standard contractual clauses, or government-approved mechanisms and log them.
- Prepare consent capture templates and export procedures for audit evidence.
Step 3 Choose hosting cloud model and register websites
- Decide if your website should run fully inside China, partly in China and partly overseas (hybrid), or mainly overseas with China optimizations.
- Set up your hosting and website based on the option you choose.
Why?
- User experience, compliance, and costs change dramatically depending on whether user traffic is Chinese local or global.
How?
- China-only users: Prefer leading China cloud providers for latency and local ecosystem integration. Verify ICP support and provider compliance playbooks.
- Global product with China users: Use a hybrid model local data plane for user traffic plus global control plane for analytics and central governance.
- Website deployment: For mainland hosting, confirm your registrar will attach the domain to the host and include ICP filing details. For CDN, choose providers with points of presence in China. Test site rendering from multiple Chinese ISPs before public launch.
- For on-site or hybrid setups: Identify hardware requirements such as server racks, edge appliances, power backup, and cooling systems, and ensure that these can be purchased and serviced locally.
Step 4: Design network and cross-border connectivity
- Architect Content Distribution Network (CDN) placement peering and cross-border links, and decide how remote teams will access China resources.
Why?
- China’s cross-border network controls and peering arrangements affect latency reliability and third-party integrations. A poor network design kills user experience.
How?
- Measure p50 and p95 latency and packet loss from your target Chinese metros to candidate endpoints.
- Use a China POP (Point of Presence) CDN and prefer dedicated cross-border links or Express Connect (A private, high-speed link between your infrastructure and the cloud provider) equivalents for predictable latency. Our global connectivity team can help design these.
- VPN guidance: Consumer VPNs can be unreliable and legally sensitive; for enterprises, use lawful private links, SD-WAN, or MPLS, and corporate remote-access solutions that comply with local rules. Document which teams are allowed to use remote access, and specify the approved methods for doing so.
Step 5: Implement identity SSO and CRM integration.
- Implement Single Sign-On(SSO) to provision accounts and map platform IDs into your CRM.
Why?
Consistent identity reduces helpdesk load and prevents fragmented customer records, especially with WeChat integration.
How?
- Deploy Single Sign-On and sync directory services such as Azure Active Directory early and validate session lifecycles under China network conditions
- Map WeChat openID and unionID into CRM records and set deduplication rules.
- Test SSO token refresh and calendar sync for Microsoft 365 integrations.
Step 6: Integrate payments messaging and customer channels
- Connect WeChat Pay, Alipay (Official Accounts and mini-programs) to your commerce and support stack.
Why？
- Payments and messaging live inside local ecosystems and drive conversion and retention. Plan reconciliation early.
How？
- Enroll as a merchant or use a payment partner to enable domestic settlement. Test sandbox flows for refunds chargebacks and reconciliation formats.
- Hook payment events into CRM and support ticketing so finance and customer service share a single source of truth.
- Design consent and retention for customer messaging history to satisfy PIPL.
Step 7: Build security operations and audit readiness
- Centralize logs, build exportable archives, and create incident playbooks.
Why?
- Regulators expect auditable records, and you need fast, documented responses for incidents.
How?
- Implement centralized logging with timestamped export capability retention aligned with PIPL.
- Create an incident response plan with local escalation points, legal notification, and communications templates.
- Schedule periodic IT audits and tabletop drills. Our IT audits team can help prepare evidence and run readiness checks .
Step 8: Select vendors that build local operations and require exit clauses
- Choose partners for hosting connectivity payments and local support and codify exit and export rights.
Why?
- Good partners provide bilingual engineers with quick escalation and reduce operational risk; contracts without exit terms create lock-in.
How?
- Require local SLA bilingual support and references from similar foreign companies.
- Include contractual clauses for data export formats, timelines, and provider migration assistance.
- Decide to run model local operations for day-to-day with a global control plane for governance.
- Include hardware SLAs: warranty terms, spare parts, replacement timelines, and on-site maintenance responsibilities in partner contracts.
If you need local bilingual operations support and partner coordination, please contact us.
POC checklist
A short proof of concept reveals performance and compliance gaps before large investment. Execute a focused POC that validates legal architecture network identity and payment flows:
If you prefer hands-on support, we can help you run the POC and operate the environment.
Common mistakes and how to avoid them
- Treating China as another cloud region
How to avoid: Use local ISP tests early. Run p50 and p95 latency checks from target Chinese cities before committing to a provider.
- Starting architecture before legal checks
How to avoid: Do ICP and PIPL mapping first. Run a legal kickoff and produce a data map that informs hosting and design choices.
- Relying on consumer VPNs
How to avoid: Use approved enterprise links such as SD-WAN, MPLS, or dedicated cross-border circuits and document approved access methods.
- Testing only in HQ environments
How to avoid: Validate from multiple Chinese metros and ISPs, not just your headquarters or a VPN endpoint.
- Picking vendors on price alone
How to avoid: Require SLAs bilingual support and explicit data export and migration clauses in the contract.
- Not staffing local operations
How to avoid: Hire or partner for bilingual engineers and local escalation; consider a managed services partner with first-line operations.
FAQ & quick answers
Q: Do I always need an ICP filing? And how long does it take?
A: ICP (Internet Content Provider) registration is required for public websites hosted on mainland China infrastructure and for externally facing enterprise systems such as ERP and CRM that are accessible from the public internet. A local entity or licensed partner usually holds the filing. Process and timelines vary—expect weeks to a few months.
Q: What is the PIPL, and does it stop cross-border transfers?
A: PIPL (Personal Information Protection Law) is China’s main data protection law; it does not categorically ban transfers but requires legal bases, documented safeguards, and approved transfer mechanisms for cross-border data.
Q: Can I use AWS or Azure in China?
A: Yes, but AWS and Azure operate via licensed domestic partners in China—engage their local operators (for example, Sinnet, NWCD for AWS; 21Vianet for Azure) to use onshore regions.
Q: If I host my website outside China, can I avoid ICP, and what are the tradeoffs?
A: Hosting outside China avoids ICP but often results in higher latency, weaker local integrations (payments, mini-programs), and poorer user experience for Chinese users.
Q: How do I enable WeChat Pay or Alipay for my store and handle reconciliation?
A: Onboard as a domestic merchant or use a payment partner, then test sandbox flows for payments, refunds, and chargebacks; confirm settlement timing and reconciliation formats with your provider.
Q: How should I test real user performance from China?
A: Run real-user tests from your target Chinese metros and ISPs, measure p50 and p95 latency and error rates, and validate CDN cache hit ratios and DNS behavior under expected load.
Q: Can I register a domain overseas and still host in China?
A: Yes, but choose a registrar that supports China filings; you must provide company and admin documents when submitting ICP paperwork for mainland hosting.
Q: Are consumer VPNs allowed for staff to access China resources or vice versa?
A: Consumer VPNs are unreliable and legally sensitive; use enterprise solutions such as SD-WAN, MPLS, or dedicated cross-border links for lawful, predictable corporate access.
Q: Who should run day-to-day operations in China?
A: Local operations teams with bilingual staff or a trusted local managed-services partner reduce incident response time and meet local escalation requirements. You can also consider a co-managed services model between your global team and a China-based partner, but be mindful of time-zone delays and handoff gaps.
Q: How fast can a Minimum Viable Product (MVP) be ready for a China pilot?
A: A compact MVP (mini-program or public-facing site) can be ready in a few weeks with experienced teams, though integrations (payments, SSO, ICP) may extend the timeline.
Q: What are the main cost traps when operating in China?
A: Common cost drivers are cross-border egress, CDN acceleration services, peering/Express Connect fees, and local professional services for compliance and support—include these in overall operating costs.
Flowchart of the IT set-up process
About JET IT Services
JET helps businesses in China overcome IT challenges with reliable, compliant, and secure solutions. From network optimization to cybersecurity, we ensure your IT systems run smoothly so you can focus on what matters most—growing your business!