But Petri’s September 14 report reads more like a newly introduced capability than the record supports. Google announced this feature as a beta in May 2026, with rollout beginning April 28 for both Rapid Release and Scheduled Release domains. Google’s migration documentation was also updated on September 10. The practical news is that the guided path is now documented and visible to more administrators; it is not a surprise new replacement for enterprise migration planning.
Google Workspace Updates described the tool as aimed at “very small and small-sized businesses” and educational institutions. That qualification is important. The tool’s central limit is ten Microsoft users during Workspace setup, a ceiling that makes it useful for a five-person office or a small school department but irrelevant as a complete migration mechanism for most established Microsoft 365 tenants.
The setup wizard creates users, then hands data off to import services
Google’s setup documentation separates the user import from the data move more clearly than the simplified announcement does. During setup, an administrator connects a Microsoft account, reviews the discovered users, chooses which accounts to bring across, selects categories of data, and starts the import. The available categories are email, calendar events, contacts, files, and tasks.
The workflow copies Microsoft user information into Workspace; it does not delete or alter the Microsoft accounts. Google says imported users receive Workspace sign-in instructions by email, which the administrator must forward to a secondary address. That detail is easy to overlook in a “one-click” migration pitch: the tool can discover and create accounts, but onboarding users still requires an out-of-band communication plan.
Google also makes clear that the guided setup import is a starting point rather than a self-contained migration engine. Once users have been imported, the administrator can launch further Microsoft data transfers through the Admin console’s Data Import tool. The default Exchange Online importer handles email, calendars, contacts, and Microsoft To Do tasks; the OneDrive importer handles files, folders, and permissions.
For Windows and Microsoft 365 administrators, the important distinction is between account creation and data fidelity. Creating a Workspace user from a discovered Microsoft identity is straightforward. Moving years of mailbox history, large OneDrive libraries, external sharing relationships, resource calendars, group mailboxes, retention-sensitive content, and Teams conversations is the work that determines whether a migration succeeds.
The ten-user limit is a product boundary, not a technical maximum
Google’s ten-user limit applies to the automatic onboarding experience during Workspace setup. It does not mean Google Workspace cannot import more than ten Microsoft 365 users. Its regular default Exchange Online import supports as many as 1,000 users in a job, while the advanced importer supports batches of up to 5,000 users and up to 20 simultaneous batches. OneDrive’s advanced importer supports up to 5,000 users per batch.
Those larger methods require the administrative work the setup wizard avoids. Google’s advanced import instructions require creating an Azure application, supplying tenant and application identifiers, configuring credentials or certificates, preparing CSV mappings, and managing batches. This is where an organization moves from a simple cutover exercise into a real project with staging, validation, exception handling, and rollback planning.
Google’s own documentation recommends phased migrations for enterprise use, including moving core IT users and early adopters first, then later groups. It also supports delta imports for Exchange Online, allowing newly added or changed content to be copied after the initial pass. That is the capability a larger tenant needs to reduce the gap between a first migration run and its final cutover.
The setup tool does not offer that level of operational control. If an administrator stops the setup import, Google says the process does not roll back content already copied. It also cannot be restarted within that initial wizard. Google directs administrators to start a new import through the default Exchange Online or OneDrive tools instead. Running multiple imports over the same source data can create duplicates, according to Google’s documentation.
That makes the setup feature best treated as an acceleration tool for clean, small tenants—not a reason to skip a migration inventory. Before pressing Start Import, an administrator should still identify shared mailboxes, Microsoft 365 Groups, room calendars, OneDrive sharing structures, and data under retention or legal-hold requirements.
Microsoft 365 workloads do not all move through the same path
The guided setup feature covers the personal productivity data most visible to end users: Exchange Online email, calendars, contacts, tasks, and OneDrive files. It does not promise an equivalent one-step move for broader Microsoft 365 collaboration workloads.
Google’s own migration catalog lists Microsoft Teams and SharePoint Online separately from Exchange Online and OneDrive. Teams migrations use a separate advanced process, and Google documents material behavior changes: one-to-one and group chats become shared Google Chat spaces, while messages in a rolled-out space cannot accept later imported updates. Those are architectural conversions, not ordinary copies.
SharePoint and OneDrive should also not be treated as interchangeable. A user’s personal OneDrive is close enough to a personal Google Drive destination for a basic migration to be useful. SharePoint Online libraries, Microsoft 365 Group-connected sites, permission models, metadata, workflows, and links introduce a different class of dependency. Google’s broader migration tools can address some of those workloads, but the setup wizard itself does not make that complexity disappear.
Google’s default Exchange Online importer also carries a clear compliance warning: it is intended as a productivity feature and is not designed to meet legal-compliance requirements. Organizations subject to eDiscovery, retention, records-management, or litigation-hold obligations need to verify their obligations and destination controls before treating copied data as a compliant preservation process.
Microsoft’s documentation for moves in the opposite direction illustrates why this remains a multi-stage exercise. Microsoft’s Google Workspace-to-Microsoft 365 guidance separates tenant setup, domain verification, device security, mail and calendar transfer, Drive migration, domain cutover, and retirement of the old service. Google is collapsing some early friction for the reverse journey, but it has not eliminated the same categories of work.
Licensing and mail cutover are still prerequisites
Petri correctly highlighted licensing as a constraint, but Google’s own wording deserves more care. Google’s release announcement says the setup import applies to Flexible Plan customers and says Annual/Fixed-Term subscribers must add licenses before importing users. Its Help Center article says Flexible Plan customers can import up to ten Microsoft users during setup, while Annual/Fixed-Term customers need to add more licenses before they can import users during setup.
The official material does not present an Annual/Fixed-Term subscription as a permanent technical bar. It presents available Workspace licenses as the gating condition. An administrator on an annual commitment should therefore confirm the purchase cap and add the required seats before assuming the setup option will be unavailable.
The domain and mail prerequisites are equally significant. Google says the option appears after domain verification and activation of the organization’s email records. In other words, this is not a tool designed for a long period of unconfigured mailbox coexistence while administrators casually test the new tenant. The import can run in the background while the rest of Workspace setup continues, but the organization must already be prepared to establish Workspace as its mail destination.
For small firms, that sequencing may be acceptable: verify the domain, provision licenses, activate Google’s mail routing, create users, and import historical data. For a company with line-of-business applications, authenticated SMTP devices, third-party email gateways, Microsoft Entra ID dependencies, or Windows device-management policies tied to Microsoft 365, changing mail routing is only one item in a larger cutover plan.
Google’s retiring migration stack makes the replacement path more important
The timing of Google’s renewed emphasis on the Admin console import tools is revealing. Google’s Workspace Migrate documentation says support for its older SharePoint Online and OneDrive migration components ends on September 15, 2026, with no more updates or bug fixes. The same documentation says the Exchange Online component will no longer be available starting in October 2026, directing customers toward the advanced data import tool.
That leaves Google with a clearer two-tier story. The setup wizard is the low-friction entry point for a tenant with ten or fewer Microsoft users. The default and advanced Data Import tools are the supported path for larger or more complicated Exchange Online, OneDrive, SharePoint Online, and Teams work.
The useful takeaway for Microsoft 365 administrators is straightforward: Google has made competitive migration easier at the smallest end of the market, where an external migration specialist may be disproportionate to the job. It has not produced an enterprise “click once and leave Microsoft 365” button. Above ten users—or wherever compliance, Teams, SharePoint, shared resources, and identity dependencies enter the picture—the Azure application, mapping files, delta passes, import reports, and cutover controls are still waiting.