This is a submission for the Google Cloud NEXT Writing Challenge
Most of the coverage from Google Cloud NEXT '26 focused on Gemini and the agentic AI push. Fair enough. But the announcement that caught my attention had nothing to do with AI models. Google launched a free, built-in migration tool that moves enterprises from Microsoft 365 to Google Workspace, and claimed it's up to five times faster than their previous migration tools.
That doesn't sound exciting until you think about what it actually means.
Microsoft's real advantage was never the product
Ask any IT leader why their company is still on Microsoft 365 and you'll rarely hear "because Word is better than Docs." The answer is almost always about switching costs. Years of SharePoint content, Teams workflows, and Exchange mailboxes wired into Active Directory and compliance systems. Moving off that stack is a six-to-twelve month project that nobody wants to own.
Microsoft knows this. Their moat has always been the pain of leaving, not Copilot or Excel. Google just went after the moat directly.
What Google actually shipped
The new tool is called Data Import. It lives inside the Workspace Admin Console, no third-party software needed. It handles email, calendar, and contact migration from Exchange Online using parallelized transfers and what Google calls "improved algorithms" for speed.
There's also a migration planning utility that estimates timelines and organizes users into speed-optimized batches. For an IT team evaluating the switch, that removes one of the first objections: "we don't even know how long this would take."
No extra GCP infrastructure costs. No licensing fees for migration tools. Google is absorbing the cost of switching entirely.
The gap nobody's mentioning
Here's what Data Import doesn't do yet: OneDrive, SharePoint, and Teams. Google says those are "coming soon."
That's a problem. Email migration is the easy part. The real lock-in for most enterprises is in shared drives and document libraries, not email. A company with 10,000 employees and years of SharePoint content isn't switching because email migration got faster. They're switching when someone solves the file and permissions migration, and that piece isn't ready.
So the "5x faster" headline is real, but it applies to the part of the migration that was already the least painful.
The $750M makes more sense now
Google also announced a $750 million partner fund at NEXT '26 for consulting firms and systems integrators. The fund is officially about accelerating agentic AI deployment, not migration specifically. But paired with the migration tool, the timing tells a story.
The people who decide which platform an enterprise adopts aren't usually the CTO. They're the Deloittes and Accentures who run the evaluation and implementation. Google is paying those firms to recommend and execute the switch. The migration tool handles the technical side, and the partner fund gets the right people in the room to say yes.
The question Google doesn't want you to ask
If Google makes it easy to move to Workspace, does that also make it easy to move away from Workspace later?
Data portability is a one-way pitch right now. Google built a tool to import from Microsoft, not a tool to export to Microsoft. Expected, but worth noticing. The easier Google makes it to arrive, the more you should ask what leaving looks like. Switching costs don't disappear when you change vendors. They just reset.
Why this matters
The AI feature race between Google and Microsoft is real, but it's converging. Gemini and Copilot will keep trading benchmarks. The actual competitive battle is happening at the infrastructure and distribution layer, where switching costs and partner incentives determine which platform enterprises land on.
Google figured out that winning the AI argument isn't enough if nobody can act on it. So they removed the friction and funded the people who make the recommendation. Whether the destination is worth it depends on how fast they ship the SharePoint and Teams migration. Until then, it's a strong pitch with an asterisk.
This article was originally published by DEV Community and written by Lewis Sawe.
Read original article on DEV Community