5users
Two to three working days
A founder, a few staff and a shared inbox. Cutover on an evening, everyone signed in the next morning.
Google Workspace to Microsoft 365
From Google Workspace to Microsoft 365, with nothing left behind by surprise.
Acquired by a Microsoft 365 company, a parent that standardises on one platform, a compliance requirement. Whatever the reason, we move Gmail, calendars, contacts, Drive and shared drives into Exchange Online, OneDrive and SharePoint, switch mail over in a window you choose, and close only when the counts match.
From Google Workspace
To Microsoft 365What moves, and where it goes
Every Google service, mapped to its Microsoft home.
We plan and run the move with Microsoft's own tools. Mail, calendars and contacts go through Microsoft's Google Workspace migration in the Exchange admin center, in batches. Drive and shared drives go through Microsoft's Migration Manager, run from the Microsoft 365 admin center with Microsoft's migration app installed from the Workspace Marketplace.
| In Google Workspace | In Microsoft 365 | What to know |
|---|---|---|
| Gmail | Exchange Online mailbox; labels become folders | Largest message follows your tenant's transport settings, 35 MB by default |
| Gmail filters | Outlook rules | Imported turned off; we switch on the ones still in use |
| Calendars | Outlook calendars with events | Room bookings, shared calendars and event colours are not migrated |
| Contacts | Outlook contacts | Up to three email addresses per contact |
| Google Groups | Distribution lists or Microsoft 365 groups | Rebuilt by us from the group inventory, members and owners included |
| My Drive | Each user's OneDrive | Docs, Sheets and Slides converted to .docx, .xlsx and .pptx; Drawings to PNG; Forms migrated |
| Shared drives | SharePoint sites or Teams | Shared drive permissions migrated with group mapping |
| File sharing | Permissions on the migrated files | File-level permissions off by default; external sharing links not recreated |
| File history | Current version | Latest version by default; files up to 250 GB; delta runs pick up later changes |
Based on Microsoft's own migration documentation, checked October 2026. Limits change; we confirm them for your tenant during discovery.
What does not survive
The gaps on this route, listed before we start.
Microsoft's tools are good at moving data. A few things stay behind, and each one becomes a line on your plan with an owner.
- Vacation and auto-reply settingsNot migrated. We note who has one active and set it again in Outlook on cutover day.
- Room bookings and shared calendarsNot migrated. Rooms are recreated as Microsoft 365 resources and shared calendars re-shared, before people need them.
- Event colours and extra contact addressesColours are dropped, and contacts keep up to three email addresses. We flag contacts that carry more.
- Google Sites, Maps and orphaned filesNot migrated by Migration Manager. We export what matters and find owners for orphaned files first.
- Shortcuts and very long pathsShortcuts are skipped and paths over 400 characters fail. We shorten the folder tree before the first pass.
- External sharing links and old versionsLinks shared outside the company are not recreated, and only the latest version moves by default. We list both per drive.
How this route runs, step by step.
Microsoft's prerequisites decide the first half of the plan. Our cutover order decides the second.
Inventory
Every user, alias, group, shared drive, calendar resource and integration that sends mail, with sizes, plus the Sites, long paths and orphaned files that need a decision.
Identity on Microsoft 365
Mail users pre-provisioned in the destination, as Microsoft requires, and Google Groups rebuilt as distribution lists or Microsoft 365 groups.
Connect the two sides
A Google Cloud project and service account with the Gmail, Calendar and Contacts APIs enabled, the right Microsoft admin roles, and routing subdomains on both sides with their own MX so mail flows between platforms during the move.
Authentication before the switch
Microsoft 365 DKIM and SPF published while Google is still authorized, so receivers trust the new platform from its first message.
Seed in batches
Mailboxes moved in batches and Drive copied with Migration Manager in the background, a pilot group first, while everyone keeps working in Google Workspace.
Cutover in your window
MX changed at the hour you choose, a final delta pass for mail and files, and the Outlook rules people still need switched on.
Reconcile and hand off
Message and file counts compared per user on both sides, Google Workspace kept for a period you set, and a one-page runbook for your next admin.
Timeline and pricing
How long it takes, and how the price is set.
Typical calendar time from kickoff to reconciled hand-off for mail, calendars and contacts. Large file libraries add seeding time in the background, not downtime.
25users
About one week
Groups, shared mailboxes and a file library come into play. One seeding pass, one evening or weekend cutover.
100users
Two to three weeks
Seeded in waves by department with a pilot group first. The MX change still happens once, in one window.
- One fixed price per migration. Set after the discovery call from the number of users, the sources and the file volume. It changes only if the scope does.
- Licences are yours. You buy Microsoft 365 directly on the plan that fits. We advise on the tier; we do not resell it.
- Included. Planning, data migration, DNS and email authentication, the cutover window, reconciliation, a sign-in session for your team and thirty days of questions afterwards.
How we scope, quote and invoice is on how we work.
Before you decide
Straight answers.
Why do companies move this way?
Usually for reasons outside the tools: an acquisition by a Microsoft 365 company, a parent that standardises on one platform, or a compliance requirement. Both platforms are solid; our job is a clean move.
Do labels and filters come across?
Labels arrive as Outlook folders. Filters arrive as Outlook rules turned off, and we switch on the ones you still use. Auto-replies are set again by hand.
What happens to Docs, Sheets and Slides?
They become Word, Excel and PowerPoint files. Drawings become PNG and Forms are migrated. Sites, Maps and orphaned files are not, and we list them first.
Does file sharing survive?
Shared drive permissions move with group mapping. File-level permissions are off by default and turned on when you need them. External links are listed for re-sharing.
What about government clouds?
Microsoft's Google migration in the Exchange admin center is not available in GCC High or DoD. We confirm another route during discovery before quoting.
Going the other way?
The reverse move has its own page: Microsoft 365 or Exchange to Google Workspace. Dropbox or Box in the mix? See file migration.
Product names and logos belong to their respective owners.
Tell us the date Microsoft 365 needs to be live.
Thirty minutes, free. Bring the user count, roughly how much is in Drive and shared drives, and your deadline, and you leave with a plan, the known losses and a fixed price.