Migrate Google Workspace to Microsoft 365
What people are actually asking: A recurring question on r/sysadmin and IT forums like Spiceworks sums up the whole problem: “What’s the best way to migrate emails from Google Workspace to Microsoft 365 without losing folder structure, read/unread status, or breaking Shared Drive permissions along the way?”
That question comes up so often because there isn’t a single clean answer. It depends on how much history your mailboxes carry, how much you rely on Shared Drives, and honestly, how much patience your team has for a rough week. Google Workspace to Microsoft 365 migration is one of the more common IT projects going right now — usually triggered by licensing costs, a merger, or just wanting tighter Teams and Windows integration. Deciding to switch is the easy part. Doing it without breaking email threads or locking someone out of a shared spreadsheet mid-project is where things get interesting.
Below is what actually needs to move, how far Microsoft’s own tools get you, and when it’s worth paying for something built specifically for this job.
What Actually Needs to Move
Map this out before you touch a single setting. Most Google Workspace to Office 365 migrations involve four buckets of stuff, and each one has its own headaches.
- Email and mailboxes: Every message, folder, label (which becomes a folder in Outlook, more or less), and read/unread flag, across every account in the domain.
- Calendars and contacts: Meetings, recurring events, shared calendars, personal and domain-shared contact lists. A lot of migrations quietly fail here — recurring meetings sometimes lose their series structure if the path isn’t handled carefully, and nobody notices until three weeks later when the standup invite duplicates itself.
- Google Drive and Shared Drives: My Drive files are the easy part. The part people underestimate is the sharing permissions attached to everything. A folder shared with twelve people in Google Drive needs those same twelve people mapped correctly once it lands in SharePoint or OneDrive — otherwise you’re rebuilding access lists by hand.
- Groups and Sites: Group addresses and membership need to be recreated as Microsoft 365 Groups or distribution lists. Google Sites content usually just has to be rebuilt from scratch; there’s no real equivalent to migrate it into.
Once the scope is clear, the actual decision is simple: do it yourself with what Microsoft provides, or bring in dedicated software.
Before You Start: A Few Things Worth Getting Right
Domain verification comes first — you can’t route mail to Microsoft 365 until the domain is added and verified there. Every mailbox you’re migrating also needs to already exist as a licensed user on the Microsoft side; the migration tools move data into accounts, they don’t create them.
On the Google side, you’ll need either 2-step verification with an app password, or an OAuth service account with domain-wide delegation, depending on which path you take.
Run a test batch. Five or ten accounts, including at least one person who’s been at the company for years and has the mailbox size to prove it. Skipping this step is probably the most common mistake mentioned in IT forums, and it’s an easy one to make when you’re under a deadline. The instinct is to just do a weekend cutover and deal with problems as they come up — and then Monday morning, half of sales can’t find last quarter’s client emails, and now it’s your problem before coffee.
Don’t touch MX records until mail migration is confirmed complete. Switch too early and mail starts landing in two places at once, which is its own special kind of mess to untangle.
Manual Method: Microsoft’s Native Migration Tools
Microsoft does have a built-in path, it’s just tucked away in two spots: IMAP migration in the Exchange admin center, or a Workspace migration batch via PowerShell if you’d rather script it.
Rough steps:
- Verify your domain in the Microsoft 365 admin center first — nothing else works until this is done.
- Create and license mailboxes for everyone moving over.
- On the Google side, either set up a service account with domain-wide delegation, or just enable IMAP per user if you want less setup.
- In Exchange admin center, create a migration endpoint pointed at imap.gmail.com.
- Start the migration batch — pick your accounts, map old addresses to new ones.
- Wait it out. Small mailboxes finish in hours; anything with years of attachments can stretch into days. Don’t schedule the cutover tightly around this.
- Flip the MX records, update Outlook profiles, done.
Heads up though — IMAP migration only moves mail. Calendar, contacts, tasks don’t come along for the ride. If your users need those too, you’ll want Google’s Data Migration Service or a third-party tool instead, this method alone won’t cut it.
Limitations of the manual method:
- Email only, mostly — IMAP migration moves mail, full stop. Calendars, contacts, Drive files don’t come along; you’re doing those separately, by hand.
- Drive permissions don’t survive the move — nothing native carries sharing permissions over to SharePoint or OneDrive. Someone ends up re-sharing files manually, and on a team with a lot of shared folders that’s real hours, not a quick cleanup.
- Labels get messy — Gmail labels don’t map cleanly onto Outlook folders, especially once a message has two or three labels stacked on it.
- Throttling slows things down — Google caps API calls, so a big mailbox or several migrations running together will crawl.
- No rollback — if a batch fails partway through, there’s no clean way to undo it. You’re troubleshooting live.
- Needs a babysitter — past a handful of users this stops being “run a script” and becomes someone’s part-time job for a week: checking reports, re-running stragglers, chasing edge cases.
Fine for a five-person startup with light mailboxes. Riskier fast for a 50-person company sitting on years of email, Shared Drives, and calendar dependencies.
Automated Method: A Dedicated Migration Tool
This is where paying for a dedicated tool starts to make sense. Built-for-purpose migration software handles mail, calendars, contacts, and sometimes Drive data in one pass — permission mapping and progress tracking included, which is exactly what the manual method leaves you without. SysInfo Google Workspace to Office 365 Migration tool is one example built around that gap.Â
Steps typically look like:
- Install it and sign into both the Google Workspace and Microsoft 365 admin accounts.
- Add source and destination users — manually, or via CSV if you’re dealing with a big list.
- Choose what gets migrated (mailboxes, calendars, contacts, Drive/Shared Drives) in a single job instead of separate ones for each.
- Filter by date if there’s old data you don’t need dragged over.
- Test it on a small group first — confirm the mapping’s right before running the whole thing.
- Run the full migration, keep an eye on the live dashboard as it tracks per-user progress and errors.
- Once it’s done, check the report and re-run anything that failed.
A few things worth checking for, whichever tool you land on:
- Mail, calendar, contacts, and Drive migrating together, not as separate jobs
- Date filtering
- Delta/re-run support for anything added after the first pass
- Logs specific enough to actually tell you what moved and what didn’t
- CSV bulk mapping, if you’ve got more than a handful of users
You’re paying for it either way — either in software cost, or in admin hours and support tickets from doing it tool-by-tool yourself. Past 20-30 users, the math tips toward just paying for the software.
Wrapping Up
None of this is conceptually hard — verify the domain, move the data, fix the logins, cut over. The difficulty lives in the details: calendar recurrence, Drive permissions, labels that don’t translate cleanly, and how much time it takes to babysit a manual process across dozens of accounts. A small team with light mailboxes and nothing fancy in Drive can get there with Microsoft’s native tools plus some manual cleanup, but Shared Drives, years of mail, and more than a handful of users is where a dedicated tool starts saving more time than it costs. Either way, test a batch first, run both platforms in parallel until you’ve confirmed everything landed, and leave MX records alone until mail migration is actually done — and if you’re staring down a bigger or messier migration than the manual path can comfortably handle, it’s worth looking at the Google Workspace to Microsoft 365 migration tool from SysInfoTools before you lock in a cutover date.Â
Frequently Asked Questions
Q1. Can I migrate from Google Workspace to Office 365 without downtime?
Ans. Yes — run both platforms in parallel and hold off switching MX records until mail migration is fully verified. Users keep working in Gmail while their Microsoft 365 mailbox fills in behind the scenes.
Q2. Does Microsoft’s native tool migrate Google Drive files?
Ans. No. IMAP migration only moves mail. Drive and Shared Drive content needs a separate tool or a manual transfer through OneDrive/SharePoint’s import options.
Q3. How long does the migration actually take?
Ans. Depends entirely on size — a handful of light mailboxes might finish in a few hours, while a larger org with years of stored mail and heavy Shared Drives can take several days.
Q4. Will my Gmail labels show up correctly as Outlook folders?
Ans. Mostly, yes. Nested or multi-label messages are the exception — they don’t always map one-to-one, so it’s worth spot-checking a few accounts after the fact.
Q5. Do I need Microsoft 365 licenses set up before migrating?
Ans. Yes. Every destination mailbox has to already exist and be licensed before a migration batch can run against it.
Q6. Is third-party migration software actually necessary?
Ans. If it’s just mail for a small team, probably not. Once calendars, contacts, Shared Drive permissions, and dozens of users enter the picture, dedicated software saves considerably more manual cleanup than it costs. more
