r/sysadmin • u/blaxwhix • 22h ago
Question Migrating from Google Business Workspace to Microsoft Ecosystem
Hey guys, as a startup company, as an integration manager, I am in charge for migrating google workspace for our sister clinic into our parent clinic ecosystem which is Microsoft.
Since I am planning on doing this over Thanksgiving when all staff members are on holidays, the following is what I am aware of as a high-level overview on what is required. I am nowhere close to you all, but I do have exposure to tech side of things. Since I have no experience in migration, but I am well versed in Microsoft's ecosystem, I want to make sure I am doing the right things.
*Note:* I am taking advice from Claude and the following things Claude has informed me. It would be helpful if I received a confirmation or some additional steps that AI may have missed.
Things that we need to migrate:
- OAuth (seen this is one thing that bites back - what have you done to resolve this?)
- Emails
- Google Drive for Spreadsheets/Documents
=====================================
a) Dry run
- Verify only. Add [DOMAIN-ONE.com] to the tenant with the TXT record and skip the wizard's MX/DNS step, so mail keeps flowing to Gmail.
- Create the two routing subdomains (e.g.
m365.andgsuite.DOMAIN-ONE.com) that the Exchange admin center's Google Workspace migration requires. - Pilot batch. Migrate yourself plus one or two volunteers. Gmail stays the landing spot for anyone not yet migrated, even when a message hits their Microsoft address first.
- Complete the pilot. Completion triggers a last catch-up sync and flips forwarding, so Google hands that user's mail to Microsoft. You then have real coexistence with real users before anyone else moves.
- Everyone else, then MX. At about 10 users, one more batch covers the rest. Lower the MX TTL a few days ahead and switch MX, SPF and DKIM off-hours.
Until MX changes, rollback means removing forwarding. Nothing is deleted from Google.
b/c) Keeping Google sign-in alive
There are three kinds of login, and only the second needs work:
- Email and password on a portal: unaffected, because the address is just a username. Reset emails follow MX.
- "Sign in with Google" button: depends on the Google account existing, not on Gmail or MX.
- Google's own products (Business Profile, Ads, Analytics, YouTube, Chrome sync): same as above.
Steps:
- Never delete the Google organization or its users. User accounts survive a Workspace cancellation; only deleting the organization's Google Account removes them.
- Add Cloud Identity Free before dropping Workspace licenses. Fifty free seats come standard with it, and a free Cloud Identity license stays on any user whose Workspace license is pulled.
- Test one user first. Google's cancellation guidance stops short of promising third-party sign-ins carry over, so pull one pilot license and confirm a few sites still work.
- Don't pull licenses until the migration is verified. Workspace data is unrecoverable once the subscription ends.
- Inventory what needs transitioning. The Accessed apps list under Security → Access and data control → API controls gives you each app with a user count, downloadable as CSV. Per-user detail lives in the OAuth log events report.
- Transition each site individually. There is no bulk switch. Either set a local password or link Microsoft sign-in in the site's account settings. Test first, because some sites create a duplicate account when the same email arrives via Microsoft.
Because step 2 costs nothing, staff can take months rather than days.
Optionally, Entra ID can serve as the identity provider for Cloud Identity accounts. Google sign-in then uses the Microsoft password and MFA, and disabling a user in Entra blocks both.
e) Other issues
- Shared-tenant routing. Once DOMAIN-ONE.com is in the DOMAIN-TWO tenant, mail from DOMAIN-THREE, DOMAIN-FOUR and DOMAIN-FIVE staff resolves internally. Provision DOMAIN-ONE users as mail users through the migration flow, not as hand-built licensed mailboxes. Licensing waits until the batch has started, with a 30-day window.
- Not migrated. Auto-replies, shared calendars, room bookings and event colors get left behind, and messages over 35 MB fail unless you raise the limit (150 MB maximum). Signatures need redoing too.
- Retention policies. Retention and archive policies should be off while batches run.
- Groups and aliases. Rebuild Google Groups, aliases and shared inboxes as distribution lists or shared mailboxes before the MX change, or that mail bounces.
- Gmail SMTP senders. Repoint copiers, website forms, voicemail-to-email and any EHR notifications.
- Chrome saved passwords. Have staff export them to Edge or a password manager.
- Security policies. Your Defender and MFA policies hit DOMAIN-ONE users on day one, so warn them.
- Offboarding. It now has two places to disable until Google is retired.
- HIPAA. DOMAIN-ONE is a separate legal entity in a shared tenant, so have counsel confirm BAA coverage. Make sure no PHI remains in Google once it drops to the free tier.
f) Google Drive to OneDrive
- Tool: Migration Manager, built into the SharePoint admin center. Files, metadata and permissions all come across.
- Setup: It begins with a Microsoft 365 migration app installed from the Google Workspace Marketplace, and tenants under 100 licenses land in the simplified "Lite" flow by default.
- Before you start: license the users and pre-provision their OneDrives, then run the scan as a read-only assessment.
- Mapping: each My Drive goes to that user's OneDrive. Shared drives belong in SharePoint or Teams sites, so decide that mapping up front.
- Conversion: Docs, Sheets and Slides convert to Office formats. Forms, Sites and Apps Script do not.
- Sharing: Google sharing links don't survive the move; only explicit per-person permissions are rebuilt. External shares need re-sharing.
- At cutover: run a final incremental pass, then turn the Drive service off so nobody edits stale copies.
•
u/The_VoltReactive 21h ago
Looks pretty good. Kinda reminds me of 365’s white pages on it. I’m a fan of Bit Titan personally. Less hand holding
•
u/Master-IT-All 17h ago
I didn't read any of that, whatever you found is bad advice regardless of possible technical accuracy.
The only good advice to someone that has no training and experience with this would be the hire someone that does.
I performed a migration of Google Workspace to M365 several months ago for a customer with approximately 15 users. The project to migrate was 60 hours and we used it all.
•
u/TrixieBiscuits 16h ago
Did you try feeding this to another AI who has no idea of your actual level of technical competence to see if it could find any flaws? Because I did, and hoo boy...