Get a Free Quote
Article

Google Workspace to Microsoft 365 Migration: Moving Gmail to Exchange Online

A Google Workspace to Microsoft 365 migration moves Gmail, Google Calendar and Google Contacts into Exchange Online, and usually Google Drive files into OneDrive and SharePoint. Microsoft’s built-in Google Workspace migration moves mail with rules, calendars and contacts in batches, while coexistence through routing subdomains lets Gmail and Outlook users keep exchanging mail until everyone has moved.

This guide explains how a Google Workspace to Office 365 migration works and how to plan it. It is part of our email migration services; see also the Office 365 migration guide and checklist.

Google Workspace Migration vs IMAP Migration

FactorGoogle Workspace migrationIMAP migration
MailYes, including mail rules (disabled until users review them)Mail folders only
CalendarYesNo
ContactsYes, up to three email addresses per contactNo
Best forGoogle Workspace business tenantsConsumer Gmail and other IMAP systems
BatchesYes, through the Exchange admin center or PowerShellYes

What Moves and What Does Not

ItemMoves?Notes
Email and labelsYesLabels become folders; folders or labels can be excluded
Mail rulesYesMigrated turned off; users confirm them in Outlook
Calendars and contactsYesShared calendars and event colors do not move
Vacation and auto-repliesNoUsers set these again in Outlook
Room bookingsNoRebuild rooms and resources in Exchange Online
Google Drive filesSeparate migrationMoved to OneDrive and SharePoint with a content migration tool

Messages larger than the tenant’s maximum message size, 35 MB by default, need the limit raised before migration.

How a Google Workspace to Microsoft 365 Migration Works

  1. Assess. Count users, mailbox and Drive sizes, shared calendars, groups and devices.
  2. Prepare Microsoft 365. Verify domains, create users as mail-enabled users and license them.
  3. Prepare Google Workspace. Set up the Google project and service account access the migration uses.
  4. Set up coexistence. Create routing subdomains so mail flows between Google Workspace and Microsoft 365 while users move.
  5. Pilot. Migrate a small group and confirm mail, calendars, rules and mobile devices.
  6. Migrate in batches. Pre-stage mail, calendars and contacts, then run a final sync at cutover.
  7. Cut over. Switch MX records to Microsoft 365, move Drive content, reconnect devices and retire Google licenses after retention needs are met.

Planning Tips

  • Pause retention and archive policies in Microsoft 365 during migration so moved items are not flagged as missing.
  • Plan the user experience change: Gmail labels become folders and the Outlook interface is new to many users.
  • Move Drive and shared drives as a coordinated phase, with permissions mapped.
  • Check government clouds: the built-in Google Workspace migration is not available in GCC High or DoD tenants.

Moving from Google Workspace to Microsoft 365?

RockTeam plans and delivers Gmail, calendar, contact and Drive migrations to Microsoft 365 with coexistence, so users keep working throughout. RockTeam is an official HCL Business Partner and a long time Microsoft collaboration specialist. Start with a no cost assessment.

See Email Migration Services

Related Articles

Google Workspace to Microsoft 365 Migration FAQs

Yes. Microsoft’s Google Workspace migration moves Gmail with rules, Google Calendar and Google Contacts into Exchange Online, and Google Drive content can be moved to OneDrive and SharePoint.

Yes, with the Google Workspace migration method. IMAP migration moves mail folders only.

Yes. Routing subdomains provide mail coexistence between Google Workspace and Microsoft 365 until all users have moved.

Vacation and auto-reply settings, room bookings, shared calendars, event colors and some contact fields. Users and admins recreate these in Microsoft 365.

Small organizations can move in days to weeks. Larger organizations migrate in batches, with mail pre-staged and a short final sync at cutover.