Microsoft 365 tenants are now the target of a fresh data-migration tool aimed at organizations weighing a move away from Google Workspace. According to Neowin, the background tool copies emails, OneDrive files, calendars, and tasks during initial setup, though it currently caps imports at just 10 users. It is one of a growing set of Google Workspace migration tools designed to lower the barrier between the two productivity giants.
The announcement is a small but telling detail in the ongoing competition for enterprise productivity suites. For teams that have spent years on Gmail, Google Drive, and Google Calendar, leaving that ecosystem for Microsoft 365 has traditionally meant hiring consultants and juggling third-party migration software. This new tool appears designed to simplify exactly that first step.
What the migration tool actually does
At its core, the tool is a background data mover. It runs while an organization is still in its initial setup phase, pulling content over and dropping it into the Microsoft 365 tenant being provisioned.
The four categories it handles are emails, OneDrive files, calendars, and tasks. That is a deliberately practical set: email and calendar are the two things that make or break a switch, OneDrive covers shared files, and tasks round out the everyday workflow most users rely on.
Because it operates in the background, the expectation is that IT staff can kick off the migration during onboarding without sitting and watching a progress bar. The content lands in the destination accounts, and users can start working in their new environment.
Why the 10-user limit matters
The most notable constraint right now is the import cap. The tool currently limits imports to 10 users, which is small enough to suggest this is aimed at pilots, test environments, or very small teams rather than full-scale fleet migrations.
A 10-user ceiling is a common shape for early-stage or free-tier tooling. It lets an organization validate the process on a handful of accounts before committing to a larger rollout. It also keeps server load and support burden down for whoever is hosting the tool.
For a mid-size or large enterprise, that limit means the tool is unlikely to be the end-to-end solution on its own. It is more of a starting point — a way to prove the concept with a small group before planning a broader migration.
What this means for you
If you run a small business or lead a team considering a switch from Google Workspace to Microsoft 365, this is worth a look. The biggest fear with any productivity migration is lost email and calendar history, and a tool that automates those transfers during setup directly addresses that concern.
The 10-user cap means it is best suited for a pilot. You could onboard a small group first, confirm the emails, files, and calendars arrived intact, and then plan the rest of the organization from a position of experience rather than guesswork.
For larger organizations, the practical takeaway is that this tool is a complement, not a complete migration platform. You would likely use it to de-risk the initial move and then layer in additional tooling for the full fleet.
How to get it
As reported, the tool is available now, but with the 10-user import limit in place. Anyone interested should plan to test it on a small set of accounts first and confirm the four data types — email, OneDrive files, calendars, and tasks — transfer cleanly before scaling up.
Because it runs during initial setup, the timing matters: you will want to schedule the migration as part of your provisioning workflow rather than as an afterthought. Getting the data over before users fully transition reduces the chance of duplicate or lost messages.
The bigger picture for a Google Workspace migration
Google Workspace and Microsoft 365 have been the two dominant enterprise productivity suites for over a decade, and the switching costs on both sides have historically kept most organizations locked into whichever they started with.
Tools like this one nudge at that inertia. Even a small, free, 10-user migration helper lowers the barrier for teams that have long assumed moving meant a costly, risky project. It also signals how competitive the market has become, with vendors investing in exactly the friction points that keep customers from leaving.
Whether this tool grows beyond its current limit remains to be seen, but for now it offers a low-risk way to test the waters when considering a Google Workspace migration to Microsoft 365.
Source: Neowin
Over to you: If your team were switching from Google Workspace to Microsoft 365, would you start with a 10-user pilot like this, or migrate everyone at once?



