Mon–Sat 10:00–18:00 London · UK
Remote & on-site ☎ 0207 096 0936
← Guides
Cloud & Email

Moving From Google Workspace to Microsoft 365: What Migrates, and in What Order

Microsoft's built-in tools move Gmail mail, calendars and contacts, and copy Drive into OneDrive and SharePoint. Groups, aliases, shared calendars, signatures and sharing links are rebuilt by hand, and the DNS cutover has an order that keeps mail flowing.

Microsoft’s own tools will move most of a Google Workspace tenant. The Google Workspace migration in the Exchange admin centre carries each person’s mail, calendar and contacts, and brings Gmail filters across as Outlook rules. Migration Manager copies My Drive and shared drives into OneDrive and SharePoint. Neither touches Google Groups, aliases, shared calendars, room bookings, signatures, out-of-office replies or sharing links, so those are rebuilt by hand. And the order you work in decides whether anyone loses a day’s email.

This assumes the decision is made. If it isn’t, our Microsoft 365 vs Google Workspace comparison covers the choice, and the cloud migration checklist covers planning any move.

Two mail routes, and only one moves calendars

In the Exchange admin centre, Migration > Add migration batch offers two ways out of Gmail.

Google Workspace (Gmail) migration is the one to use. It connects through a Google service account, which the wizard can set up for you, and migrates mail, calendar, contacts and rules. Each is a separate tick box on the Move configuration page.

IMAP migration is the older route, and Microsoft is explicit that it moves mail folders only: no contacts, calendar items or tasks. Those become a manual export and import for each person, which is how a migration “finishes” on Friday and someone’s diary is empty on Monday.

Even on the right route, treat calendars and contacts as their own job; their speed depends on separate quotas on Google’s side. Before cutover, compare a few migrated calendars and address books with Google rather than trusting a batch marked Synced.

Microsoft also documents what the Google route leaves behind:

  • out-of-office and vacation settings;
  • shared calendars and event colours;
  • meeting room bookings;
  • any email addresses beyond the third on a contact, plus contact labels and URLs;
  • any single message over your tenant’s size limit, which is 35 MB by default.

Filters arrive as rules switched off, so each person should check theirs before turning them on. And Microsoft recommends disabling retention and archive policies on the new mailboxes until migration ends, or items those policies move get reported as missing.

Labels become folders, sometimes more than once

Microsoft’s Exchange team has described the translation: most Gmail labels become folders, and mail with no other label goes to the Archive folder. Because one message can carry several labels, it can appear in several folders. Warn people beforehand, or the first support call will be “my email’s been duplicated”. The PowerShell route’s -ExcludeFolder parameter can leave out labels you don’t need.

The cutover order

Microsoft’s documented route is staged, with mail routed between the two systems through temporary subdomains until the end.

  1. Add and verify your domain in the Microsoft 365 admin centre under Settings > Domains > Add domain, using the TXT record. Don’t let the wizard set up email records yet. If your registrar supports Domain Connect, it may offer to delete Google’s MX record, so add records manually.
  2. Create the routing subdomains. Microsoft’s example uses one pointing at Microsoft 365 and one pointing at Google, both added in the Google admin console as user alias domains.
  3. Create everyone as a mail user, not a licensed mailbox. Starting the batch converts mail users into mailboxes, and Microsoft says to assign the Exchange licence only after that point, within 30 days. Licensing everyone on day one is the usual instinct, and the wrong order here.
  4. Fix SPF and DKIM before anyone sends from Microsoft 365. Add include:spf.protection.outlook.com to your existing SPF record alongside Google’s, keeping a single record. Then publish Microsoft’s two DKIM CNAME records and switch signing on in the Defender portal under Email & collaboration > Policies & rules > Threat policies > Email authentication settings. Microsoft doesn’t DKIM-sign mail from your own domain until you do. Our SPF, DKIM and DMARC guide explains each record.
  5. Lower the TTL on your MX record to an hour or less, well before the switch.
  6. Run the batch and wait for Synced.
  7. Complete the batch. This runs a last incremental sync and sets forwarding in Google, so anything still arriving there goes on to Microsoft 365. If your Google settings stop users adding a forwarding address, the tool can’t add one either.
  8. Switch the MX record to the value shown in the Microsoft 365 admin centre, and remove Google’s.
  9. Tidy SPF once nothing sends from Google, and check DMARC reports to confirm Microsoft mail is passing.

Drive and shared drives

Files go through Migration Manager, which Microsoft names as its tool for Google content. It’s in the Microsoft 365 admin centre under Setup > Migration resources > Explore migration & imports tools > Google Workspace.

My Drive lands in OneDrive and shared drives in SharePoint. Docs, Sheets and Slides convert to Word, Excel and PowerPoint, and Drawings become PNG images. Google Sites and Maps don’t move, shortcuts are skipped, and orphaned files in no folder aren’t even scanned. Running Migrate again copies only new and changed files, so copy early and top up at cutover.

Three defaults catch people out:

  • only the latest version of each file is copied unless you change the File versions setting;
  • file-level permissions are off, so files take their destination folder’s permissions;
  • external sharing links aren’t recreated.

A task can also show Completed while unsupported files inside it failed, so read the report, not just the status.

Groups, aliases and second domains

Google Groups aren’t on either tool’s list, so recreate each one by what it does. A mailing list becomes a distribution list, a collaborative inbox usually works better as a shared mailbox, and a group that owns a shared drive becomes a Microsoft 365 group. Create that last kind before migrating its shared drive, because Microsoft’s permission mapping expects it. Our guide to shared mailboxes, distribution lists and Microsoft 365 groups covers which fits where.

Aliases go back on by hand under Users > Active users > Manage username and email, up to 400 per person. That option only appears once the user is licensed, so it comes after step 3 and before the MX switch. A Google user alias domain, which gives every user an address at a second domain automatically, has no direct equivalent: in Exchange Online, email address policies apply only to Microsoft 365 groups. Each person’s second-domain address is added individually or by script.

Pay for both for a month

Don’t cancel Google on cutover day. Its forwarding catches mail from senders still using the old MX record, and Microsoft allows up to 72 hours for other mail systems to notice the change. Drive top-ups need the source accounts too. Budget for both subscriptions for about a month. On Google’s Annual/Fixed-Term Plan, unused licences only come off at renewal, so check that date before choosing a cutover weekend.

Monday morning

  • Outlook needs the new account adding. In classic Outlook, a fresh profile stops the Google account lingering, and the autodiscover DNS record lets Outlook find the mailbox from an address and password.
  • Phones need the Google account removed from mail and calendar sync and the Outlook app signed in, or people see two calendars, one going stale.
  • Calendar sharing is set up again, since shared calendars don’t migrate.
  • Out-of-office replies and signatures are set again. Neither is on the list of what moves.
  • Meeting rooms need room mailboxes, and recurring room bookings made again.

None of these steps is difficult alone. The problems come from doing them out of order. If you’d rather someone else held the checklist, the whole sequence is part of our cloud migration work.

Frequently asked questions

What happens to Starred and Important mail from Gmail?

Starred messages arrive flagged in Outlook, so a starred backlog becomes a list of flagged items. Important doesn't survive as a label. Microsoft's Exchange team says it feeds into whether a message lands in Focused or Other instead. If anyone has been using Important as a to-do list, ask them to star or file those messages before the move so nothing drops out of sight.

Will links to Google Docs in old emails and documents still work?

Only while the Google account exists. Migration Manager creates new Office files in OneDrive and SharePoint with new addresses, and it doesn't recreate external sharing links. A link to a Google Doc in an old email, a proposal template or your website keeps opening the Google original until that tenant closes, and then it stops working. Search your website, templates and standard replies for docs.google.com and drive.google.com links before you cancel, and re-share the new copies with clients on purpose.

Should everyone move at once, or in batches?

The Google route supports batches, and mail between staff who have moved and staff who haven't keeps flowing through the routing subdomains. For a small team, one batch over a weekend is usually simpler, because nobody spends a week working across two systems. If you do split it, move people who share calendars and inboxes together, since shared calendars don't migrate and have to be rebuilt between people who are already on the same platform.

What should we do with the Google tenant once everyone has moved?

Keep it until the overlap is over, then take a final export before cancelling. A super administrator can run Google's Data Export tool from the Admin console under Data > Data import & export. A full export can take days, so start it in good time and store the archive somewhere safe. After that, cancel the subscription, remove any Google entries left in your MX and SPF records, and delete the routing subdomains, which have done their job.

Related services

Free · no obligation

Want a hand with any of this?

Tell us what you're trying to sort out and we'll come back with a clear, no-obligation plan and price.