7 min read · Intermediate · Related: Microsoft 365

Updated October 2026 · Tampa Bay–tested steps

Switching From Google to Microsoft 365

Licenses, mail flow, Drive files, calendars — the order that avoids lost email for teams of 5–50.

  1. 1. Pick the right licenses before touching mail

    Map each person to Business Basic, Standard, or Premium based on whether they need desktop Office apps and advanced security. Buying everyone Premium wastes hundreds per year; buying Basic for people who live in Excel costs more in frustration. List shared mailboxes and ex-employees first — those often don't need paid licenses at all.

  2. 2. Verify the domain and stage the mailboxes

    Add your domain to Microsoft 365 and verify with a TXT record (no mail impact yet). Create all users, assign licenses, and run a pre-migration sync so mailboxes exist before cutover. Export a Google Takeout backup of Drive and mail for at least owners and finance before anything moves.

  3. 3. Move files before the mail cutover weekend

    Migrate shared Drive folders to SharePoint/Teams and personal files to OneDrive during the week using the SharePoint Migration Tool. Fix sharing permissions as you go — 'anyone with the link' Drive folders should become proper Teams memberships, not public links.

  4. 4. Cut over MX records on Friday evening

    Lower your DNS TTL to 300 seconds a day ahead, then switch MX records to Microsoft after hours. Migrate the final delta of mail, verify send/receive, and update SPF/DKIM/DMARC. Keep Google active (not deleted) for 30 days as a safety net while stragglers and forwards drain out.

  5. 5. Lock it down on Monday

    Enforce MFA, set up Conditional Access, turn off legacy auth, and review external sharing defaults. Walk every user through Teams, OneDrive sync, and Outlook mobile setup — the migration fails if Monday feels broken, even when the data is perfect.

Switching From Google to Microsoft 365 — When to Call a Pro

  • You have 5+ mailboxes, shared drives, or compliance needs — a botched cutover loses mail silently.
  • SPF/DKIM/DMARC, archiving, or retention policies need to survive the move.
  • You want someone on call through the cutover weekend, not a support ticket queue.
Get help with this(813) 702-3155

Guide FAQ

Not with a staged migration. Both systems run in parallel, the final delta syncs at cutover, and Google stays active for 30 days. Downtime is typically zero — users just restart Outlook on Monday.
They map to SharePoint (shared) and OneDrive (personal). Permissions need remapping since Google and Microsoft sharing models differ — that's the step most DIY migrations get wrong.
Remote migrations start at $75/hr; most teams of 5–25 land in the 3–6 hour range plus licenses. Weekend cutover coverage and Monday hypercare are included in our fixed quotes.
Was this guide helpful?

Keep going on Microsoft 365

Turn On MFA in Microsoft 365 First5 min readOneDrive Says Storage Full? Fix It Without Paying4 min read"File Is Locked for Editing" in Excel? Unlock It Properly3 min read

Related service: Microsoft 365 →