Microsoft 365 migration in Nanjing
A Microsoft 365 migration project in Nanjing looks simple on a spreadsheet and rarely stays that way. The first question is the one nobody asks outside China: the global Microsoft tenant, or the local 21Vianet service? From there it becomes a design exercise — keeping mail flowing, Teams history intact, and an audit trail your head office can actually read.
For foreign-owned companies in Nanjing we take the whole journey: audit, then tenant and licence design, then cutover, then the settling-in weeks when the odd fault surfaces. The aim is a migration nobody has to talk about afterwards.
What makes Microsoft 365 migration in Nanjing a different project
Treat the two clouds as different products, because that is what they are. Licences differ, some features behave differently, and performance comes down to how traffic leaves your office and where it joins Microsoft’s network. Then there is the compliance angle: where personal data may legally sit, and what you can hand to a regulator or a head office when they ask.
Nobody touches a mailbox until the audit is done: what you are licensed for, how Domains and DNS are set, which mail rules exist, how Teams and SharePoint are genuinely used, how identity is configured, and where the devices are enrolled. Most migrations take two to four weeks end to end.
The scope we move
- User and shared mailboxes, plus the mail-flow rules around them
- Teams and channels, carrying chat history across where the move supports it
- SharePoint and OneDrive content, with permissions checked before and after
- Entra ID, groups, sign-in policy and conditional access
- Devices and policy, including Intune enrolment
- DNS records, domains, and the licence position on the new tenant
User mailboxes move first, then the collaboration content, so people keep working while the rest follows.
How the project runs, step by step
- Audit the current tenant and the actual business requirements
- Design the destination — tenant choice, licensing, routing
- Run a pilot group and record what actually changes for users
- Cut over in a planned window; we schedule it outside business hours
- Hypercare — we stay on for the fortnight after cutover, while the small faults surface
- Hand over documentation, and support what we left behind
Where we work
We are not a single-city provider. NETK5 dispatches engineers across mainland China: our own team is based in Shanghai, Beijing, Guangzhou and Hong Kong, and we staff projects elsewhere in the country as clients need them — Xi’an, Chengdu, Taixing and beyond. Outside China we have delivered rack-and-stack work and WiFi surveys in Japan, Korea, Singapore and Taiwan, usually for international companies coordinating several sites from a head office that has never been on site.
For Microsoft 365 migration in Nanjing that matters in a practical way: work can be planned around a visit rather than a relocation, and the same team that surveys or installs can hand over documentation the head office can actually use.
Our experienceOur China practice dates back to 2002 and Microsoft 365 work sits at its centre. We ran a pilot migration from the global tenant to 21Vianet for a client here, and we run cloud estates day to day — one of them more than thirty Azure virtual machines alongside Microsoft 365. Siemens, Nestlé, McKinsey and JLL are among the names we work with, generally alongside the international IT firms whose client sites we support.
The questions that come up every time
Do we have to move to 21Vianet if we are in China?
No. Plenty of foreign-owned companies run on the global tenant and it works. The trade-offs are performance, routing, and how comfortably you can evidence data handling. Some migrations go the other way — from 21Vianet back to global — when a company restructures or leaves. The right answer depends on your users, your regulator and your head office, which is why the audit comes first.
How long are users without email?
Very little, if the cutover is planned properly: mail flow flips inside a window, users sign in again, work resumes. The time goes into the days afterwards — profiles, devices, shared mailboxes, and the odd Teams channel that behaves differently.
Can you support us after the migration?
Yes, and a good share of our migration work becomes ongoing support — helpdesk in English and Chinese, monitoring, and someone who already knows how your tenant was built.
Talk to us about Microsoft 365 migration in Nanjing
Tell us what you have now and what you need to end up with — tenant, users, sites, and any deadline driving it. We will tell you what the move involves and what it costs before anyone starts.
English 
Chinese