International companies operating in China face email migration challenges that extend beyond a standard cloud cutover, including very large mailboxes, device disk limits for PST (Personal Storage Table) staging, data residency requirements under the Personal Information Protection Law, and the decision regarding tenancy between Microsoft 365 operated by 21Vianet and global Microsoft 365. This article shows a complete case study we delivered, explains the practical decisions it forced, and gives an actionable POC and migration checklist you can follow.
Key Takeaways
- Archive first for very large mailboxes and migrate later to avoid device and export bottlenecks.
- Decide China tenancy early because Microsoft 365 operated by 21Vianet and global Microsoft 365 have different compliance and feature tradeoffs.
- Use HDD staging and small PST packages to prevent SSD exhaustion during the export period.
- Validate PIPL export needs with legal before any cross-border transfer.
Case Study: Email Migration for a Company
Background
One of our clients planned to have an email migration from Alibaba Cloud to Microsoft 365 as part of an ISO27001 readiness program, and our team supported the project end to end. The mailboxes were large, endpoints had limited SSD capacity, there was no centralized Active Directory, and the project required compliance evidence for PIPL and audit trails.
Challenges
- Mailboxes ranged from 100GB to 250GB each.
- User devices had roughly 110GB of SSD space, with a 2TB HDD available for staging.
- No unified Active Directory or single sign-on (SSO) was in place.
- The project required 100% historical data preservation and auditability for ISO27001.
Solution Approach
Our team followed a Prepare, Archive, Migrate, Validate pattern:
- Prepare: Readiness audit, network and endpoint remediation, and tenancy assessment.
- Archive: Export mailboxes in batches to PST files stored on HDD staging; validate each batch with checksums and manifests. Microsoft export guidance informed batch sizing and export procedures.
- Migrate: Run pilot groups, perform migrations during off-hours, and execute MX/DNS cutovers with reduced TTL and rollback plans.
- Validate: Confirm folder structure, permissions, retention settings, and eDiscovery readiness. Plan around Purview limits.
Results and Conclusion
- Upgraded network and endpoints in both offices to support export tooling.
- Migrated all user mailboxes to Microsoft 365 with 100% of historical data preserved.
- Delivered the compliance evidence needed for ISO27001 readiness and reduced long-term operational risk.
This case shows how operational constraints and compliance obligations shape tenancy, archiving, and connectivity choices. The next section explains how to turn those lessons into a practical tenancy and migration strategy for your organization. If your team needs help designing or running a Microsoft 365 migration in China, our IT projects team can support you from POC to production, including PST archiving and tenancy workshops.
Key Considerations for Tenancy and Migration Approach
If your email migration also involves large mailboxes, China-based operations, and strict compliance requirements, use the criteria below to choose the right tenancy and plan a practical migration approach:
- Data residency and PIPL risk: If personal data must remain in China, prefer China-local tenancy such as Microsoft 365 operated by 21Vianet.
- Mailbox profile and archive capacity: If many mailboxes exceed 100GB, plan an archive-first strategy and server-side or staged PST export; see Microsoft’s export procedures.
- Feature parity needs: If you must keep global integrations and full feature parity with Microsoft services, weigh the technical and legal tradeoffs for a global tenancy.
- Network performance: If cross-border sync or reporting needs low latency, design China POPs and dedicated links; consider involving our global connectivity team.
- Operational model: Decide between local, co-managed, or centralized operations — this project succeeded with local endpoint standardization combined with a limited co-managed operations handover.
POC and Migration Checklist
Once you set tenancy and the high-level approach, the next practical step is a short POC that exercises archive, export, and cutover steps—this reduces surprises during full migration.
Post-Migration Actions and Ongoing Operations
With a successful POC, scale the approach to full migration and then tighten long-term operations and backup patterns.
- Implement Exchange Online retention and purge policies to control mailbox growth.
• Design ongoing backup and recovery for mail and archives; consider managed backup in your operating model. Our managed IT services can provide secure backups and operations.
• Monitor sync latency and client health; establish runbooks and bilingual support flows for Chinese and international users. For connectivity optimization, consider the China POP design and dedicated links.
FAQ
- Do I have to use Microsoft 365 operated by 21Vianet in China?
Not always. Choose Microsoft 365 operated by 21Vianet when you must keep data in China or want a local operations partner. If you need full global feature parity and can document lawful cross-border transfers, a global Microsoft 365 tenancy can be appropriate. - How important is PIPL for an email migration in China?
Very important. The Personal Information Protection Law (PIPL) governs personal data processing and cross-border transfers. Document legal basis, collect consent where required, and complete any internal sign-offs before exporting personal data out of China. - How should I handle very large mailboxes (100GB+) during migration?
Archive-first. Export in controlled batches, stage PSTs on HDD, validate checksums and manifests, then migrate smaller increments. This project used HDD staging and batch exports to avoid filling SSDs and to protect export integrity. - Which migration method should I pick — cutover, staged, or IMAP?
It depends on the source system, mailbox counts, and service compatibility. Use a pilot to validate the chosen method and test incremental sync behavior. For technical guidance, see Microsoft cutover and staged migration docs. - How do we avoid losing mail during MX/DNS cutover?
Run a final incremental sync, lower DNS TTL in advance, perform MX change in an off-hours window, monitor queues, and keep a rollback plan. Test mailflow and delivery receipts immediately after cutover. - Can Alibaba Cloud tools help with the migration?
Alibaba Cloud publishes migration guidance and tools. Test compatibility in a pilot and confirm the export formats meet your import pathway. - What post-migration operational model works best?
Local bilingual operations or a co-managed model generally works well for China-based setups, especially for fast troubleshooting and regulatory liaison. A common approach used in this project is local endpoint standardization with a small co-managed handover. - What backup and retention strategy should we use after migration?
Keep independent backups for mail and archives, apply retention and litigation hold policies in Exchange Online, and align retention with regulatory needs. Consider managed backup if you prefer to outsource operations. - Are there export or eDiscovery limits I should watch for?
Yes. Purview/eDiscovery and export tools have limits on package size and request throughput. Plan exports and manifests accordingly. - What network design improves Microsoft 365 performance in China?
For cross-border sync or reporting, use China POPs and dedicated cross-border links to reduce latency and increase reliability. Our global connectivity team can help design this. - How long does a migration like this usually take?
Duration varies with mailbox size, compliance work, and the number of pilot phases. Large, compliance-driven projects require several weeks of preparation plus phased migration windows; plan your schedule around archives and pilot feedback. This project included substantial archive and validation phases. - How do I measure migration success?
Validate data integrity, confirm user access and application performance, monitor user support tickets, and confirm audit logs and compliance proofs. Keep migration manifests and a small set of restore tests as evidence.
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!