Workspace migration: Microsoft checklist

A Workspace migration from Microsoft needs a plan for the business services people use, not just a successful import. Confirm which accounts and records can move through the chosen path, what needs separate treatment and how staff will know the new environment is ready.

Google's setup import may be relevant to a small team. Assess its scope before assuming it covers your whole organisation or every Microsoft service.

What the new setup import covers

Google's announcement dated 11 September 2026 describes a generally available setup path that can automatically import up to ten Microsoft users and their data. The listed categories are email, OneDrive files, calendar events, contacts and tasks. Larger organisations need other options. Google's Microsoft-to-Workspace setup announcement.

Google describes an admin-only process running in the background during setup. It requires Microsoft global administrator credentials and completed domain verification and MX activation. The announcement describes a Flexible Plan path; Annual or Fixed-Term plans require licences to be added before importing users. Confirm current eligibility and instructions before making changes. Setup requirements and supported scope.

Those facts do not establish that Teams, SharePoint or every shared resource is covered. The planning sequence below is practical guidance, not a guarantee of complete migration or uninterrupted service.

Decide whether migration addresses the real problem

Write down why the business is considering a move and which workflows it expects to improve. Include the work people already complete successfully so it is not lost in a discussion focused only on new features.

Ask the team to demonstrate a representative working day: receiving a request, finding a document, arranging a meeting and handing work to a colleague. List the accounts, shared resources and connected applications involved.

For an illustrative small consultancy, a shared calendar and a document approval process may matter as much as individual inboxes. Treat each as something to investigate, not as automatically included because an import supports calendar events or files.

Separate import scope from the full move

Divide the inventory into three groups: covered by the chosen import path, requiring another method, and unresolved. Assign an owner to every unresolved item.

Check identity and access arrangements, shared addresses, permissions, retained records and business-critical integrations. Ask who owns each configuration and what evidence would show it works in the destination. Keep administrator access secure and agree who is authorised to perform each step.

Review subscription and licence assumptions alongside the technical plan. A tool being available does not settle the cost or commitment of the complete migration.

Agree acceptance before cutover

Write a small set of acceptance examples with the people who perform the work. These might include finding an agreed sample of records, using expected calendar information and confirming appropriate access to selected files. Establish a reconciliation method for scope and completeness rather than treating a handful of successful examples as proof that everything transferred.

Test the relevant business integrations separately. Record failures and missing items with an owner and a decision date. Use appropriate test arrangements that avoid accidentally contacting customers or changing live business records.

Do not make the cutover decision solely from a progress percentage. The business owner should understand what has been checked and what remains uncertain.

Coordinate the change and support period

Have the responsible administrator plan domain and mail-routing changes in the correct sequence, taking account of the import path's prerequisites. Agree the communication plan, escalation route and response to an unsuccessful change before execution.

Tell staff where to find the authoritative service after cutover and how to report missing information. Keep the original environment and records under a documented retention and access decision; do not remove them simply because a setup task says it finished.

For help assessing a migration and coordinating suppliers, explore IT management consulting. Bring the reason for moving, your account inventory and the workflows the business cannot afford to overlook.