Google Workspace to Microsoft 365 Migration Checklist (2026)

A Google Workspace → Microsoft 365 move is very doable, but the effort lives in identity, email, files, and permissions — not the mail itself. The goal is a phased cutover with a short coexistence window so nobody loses access mid-move. Deciding between the two first? See Microsoft 365 vs Google Workspace; for budgeting, cloud migration cost.

List users, shared mailboxes, groups, shared drives, and any apps tied to Google sign-in. Decide the target M365 licence tier per user (security/compliance needs drive this). Set success criteria and a rollback point. Pick the cutover style: phased (recommended) vs big-bang.

Configure your domain in Microsoft 365, set up Microsoft Entra ID (accounts), and plan SSO/MFA. Map every Google account to an M365 identity before touching data — most cutover pain is identity that wasn't prepared. Don't change DNS/MX yet.

Run a pilot wave first (IT + a friendly team), validate mail, files, and permissions, then migrate the rest in waves. Keep both systems running during the window (coexistence) so users aren't cut off. Communicate dates and what changes for users at each wave.

Once mailboxes and files are validated, switch MX / DNS to Microsoft 365 so new mail flows there. Watch for a short propagation window. Verify mail flow, calendar free/busy, and shared-mailbox access immediately after.

Confirm every user has mail, files, and permissions; reconnect mobile devices and Outlook; deliver short user guidance (Gmail→Outlook, Drive→OneDrive). Keep Google Workspace read-only for a grace period, then decommission once you're confident. Right-size licences afterward.

We run phased Workspace→M365 migrations with identity-first planning, validated waves, and a low-downtime cutover — permissions and shared mailboxes included. Book a free consultation and we'll scope it to your environment.