A Google Workspace to Microsoft 365 migration moves Gmail, Google Calendar, Contacts and Google Drive into Exchange Online, Outlook, OneDrive, SharePoint and Teams. The technical move is well understood; projects succeed or fail on preparation: mapping shared drives to the right SharePoint sites, translating sharing permissions, planning the DNS cutover and helping users adapt to Outlook and Teams. Use this checklist to plan each phase.
Key Takeaways
- Microsoft provides native tooling for Gmail mailbox migration into Exchange Online; Drive content needs a planned approach for files, shared drives and permissions.
- Google Docs, Sheets and Slides are converted to Word, Excel and PowerPoint formats, so test complex files first.
- Map each shared drive to a SharePoint site or Teams team before moving any data.
- Run a pilot group, then migrate in batches with a final delta sync before switching MX records.
- Adoption training is part of the migration, not an optional extra.
Why Organizations Move from Google Workspace to Microsoft 365
Common drivers include standardizing on Microsoft Office desktop apps, consolidating security with Microsoft Entra ID, Intune and Defender, meeting compliance needs with Microsoft Purview, adopting Microsoft 365 Copilot, and aligning with a parent company or acquirer that already runs Microsoft 365.
Phase 1: Discovery and Planning
- Export a list of all users, groups, aliases, shared mailboxes (delegated Gmail accounts) and resources (rooms, equipment).
- Measure mailbox and Drive sizes per user from the Google Admin console reports.
- List all shared drives, their owners and member counts.
- Identify third-party apps using “Sign in with Google” or Google APIs that will need re-pointing.
- Document DNS records: MX, SPF, DKIM, DMARC and any verification TXT records.
- Decide the identity model: cloud-only Microsoft Entra ID accounts or synchronization from on-premises Active Directory.
Phase 2: Prepare the Microsoft 365 Tenant
- Verify your domains in the Microsoft 365 admin center without switching MX yet.
- Create users and assign licenses; set UPNs to match current email addresses.
- Enable multifactor authentication and baseline Conditional Access policies before data lands.
- Build the SharePoint and Teams structure that shared drives will map into.
- Configure retention, sensitivity labels and audit logging if you have compliance needs.
Phase 3: Map Google Drive to OneDrive, SharePoint and Teams
| Google Workspace | Microsoft 365 destination | Notes |
|---|---|---|
| Gmail | Exchange Online / Outlook | Labels become folders; messages in several labels may appear in several folders. |
| Google Calendar | Outlook Calendar | Recurring meetings and room bookings need testing. |
| My Drive | OneDrive | Personal files and files shared directly with colleagues. |
| Shared drives | SharePoint sites or Teams | One shared drive usually maps to one site or channel library. |
| Google Groups | Microsoft 365 Groups or distribution lists | Choose based on whether the group needs files and chat. |
| Google Chat / Meet | Microsoft Teams | Chat history is not usually migrated; plan communication. |
Our SharePoint and OneDrive migration team designs this mapping so permissions translate cleanly.
Phase 4: Pilot Migration
Move 5–20 users from different departments. Validate mail folder structure, calendar invites, file conversions, sharing links, mobile setup and Outlook profile creation. Collect feedback and update user guides before the bulk migration.
Phase 5: Bulk Migration and Delta Sync
- Pre-stage historical mail and files in batches while users keep working in Google.
- Run delta passes to pick up changes.
- Lower DNS TTL values a few days before cutover.
- On cutover day, switch MX records to Microsoft 365 and update SPF, DKIM and DMARC.
- Run a final delta sync and freeze editing in Google Drive.
Phase 6: Cutover, Hypercare and Decommissioning
- Provide a quick-start guide for Outlook, OneDrive sync and Teams.
- Offer drop-in help sessions for the first week.
- Re-point third-party apps to Microsoft Entra ID single sign-on.
- Keep Google Workspace in read-only mode for an agreed period, then export and cancel licenses.
Common Pitfalls to Avoid
- Ignoring sharing permissions: links shared externally from Drive do not automatically recreate as SharePoint sharing links.
- Underestimating file conversion: complex Sheets formulas and Apps Script automation need review.
- Skipping email authentication: missing DKIM or DMARC updates hurt deliverability after cutover.
- No training plan: users switching from Gmail to Outlook need simple guidance on search, folders and calendar sharing.
Budgeting? Read our guide on Microsoft 365 migration cost.
How Skytech Enterprise Helps
Skytech Enterprise runs Google Workspace to Microsoft 365 migrations for organizations across the USA and UAE, including tenant hardening, Teams deployment and user adoption. Talk to our team about a migration assessment.
Frequently Asked Questions
Can I migrate Gmail to Microsoft 365 without losing emails?
Yes. Using a staged approach with delta syncs, all mail, including labels converted to folders, moves to Exchange Online. Validate a pilot group first to confirm completeness.
What happens to Google Docs and Sheets after migration?
They are converted into Word, Excel and PowerPoint files. Most convert cleanly, but files with complex formulas, add-ons or Apps Script should be tested and may need rework.
Do users need to do anything during the migration?
Very little until cutover. Users then sign in to Outlook, OneDrive and Teams with their new credentials, register for MFA and reconfigure mobile devices.
Is Google Chat history migrated to Teams?
Chat history is not usually migrated in standard projects. Most organizations export what they need for records and start fresh in Teams.
How long does a Google Workspace to Microsoft 365 migration take?
Timelines depend on data volume and user count. Smaller organizations can often complete it in a few weeks; larger ones plan for several months with staged batches.
Should we keep Google Workspace after the move?
Keep it in read-only mode for a short, agreed period to resolve any missed items, then export required data for retention and cancel subscriptions.