Who this is for
This service fits organizations leaving Google Workspace for Microsoft 365, from small offices to multi-site groups. Common signs it is time:
- Clients and partners send Word and Excel files and expect Teams meetings and co-authoring.
- You need desktop Office apps and tighter identity and device control than you have today.
- Shared drives have no clear owners and offboarding is inconsistent.
- You run Google and Microsoft side by side and pay for both.
- Business apps sign in with Google, and you want one identity provider.
What is in scope, and what is not
Usually in scope
- Inventory of users, groups, aliases, shared and delegated mailboxes, resource calendars, shared drives, data volume and Google-dependent apps
- Microsoft 365 identities, licensing by role and MFA set up before anyone moves
- Gmail, Calendar and contacts migrated in batches
- My Drive to OneDrive and shared drives to SharePoint or Teams sites, from a written mapping plan
- Apps that use Sign in with Google re-pointed to Microsoft Entra ID
- MX, SPF, DKIM and DMARC cutover with a final sync
- Role-based quick-start guides and support after cutover
Handled separately or agreed during discovery
- Rebuilding Google Sites, Forms, Apps Script automations and Keep notes. We list them and agree what to rebuild, replace or retire.
- Comments, suggestions and full version history on Docs, Sheets and Slides, which do not always carry over.
- Moving phones and laptops from Google endpoint management to Intune, usually its own workstream.
- Ending the Google Workspace subscription. You decide when; we plan the timing so nothing needed is lost.
How the project runs
- Inventory and mapping. Gmail, Calendar, Drive and shared drives are mapped before any bulk job runs, including label-to-folder decisions.
- Target tenant built properly. MFA and licensing by role, not defaults, and sign-in tested before users move.
- File destinations decided. Which content belongs in Teams channels, SharePoint libraries or OneDrive, with an owner for each shared space.
- Tools chosen per workload. Exchange Online's built-in Google Workspace migration handles Gmail, calendar and contacts, and Microsoft's Migration Manager can move Google Drive. Third-party tools are used where volume or reporting needs them.
- Pilot with heavy file users. Include people who live in client folders all day, not only IT. In our case study, finance and operations went first.
- Batches with coexistence. Mail routing and calendar coexistence keep internal mail and invites working while batches move.
- Cutover. MX change, final delta sync, mobile reprofiling and a clear rollback point.
- Training and support. Short role-based onboarding for Outlook, OneDrive and Teams, then a support window after cutover.
Project risks and how we handle them
| Risk | What goes wrong | How we handle it |
|---|---|---|
| Shared drive sprawl moves too | Years of unowned folders land in SharePoint unchanged | Owners named and stale content cleaned before mapping |
| "Where is this file?" | Help desk tickets spike in the first week | Pilot feedback, a clear file-location guide and a second training pass |
| Apps lose sign-in | SaaS apps that used Google sign-in fail when accounts close | Apps re-pointed to Entra ID before Google is switched off |
| Files that will not upload | Invalid characters, long paths or very large files fail in SharePoint | Pre-scan of Drive content and a fix list before the bulk run |
| Mail gap at cutover | Recent mail or invites are left behind | Coexistence routing, MX change in a quiet window and a final delta sync |
What we need from you
- Google Workspace super admin access, or a named admin who can grant it
- Microsoft 365 admin access, or approval to create the tenant
- DNS registrar access for your mail domains
- A list of apps that use Sign in with Google, if you have one
- An owner for each shared drive
- Pilot users from teams that work in files all day
- Your preferred cutover window
How long it takes
Our Google Workspace package lists a typical duration of 4 to 8 weeks, set after discovery. The firm in our case study, about 180 users, went from pilot to post-cutover support in about 5 weeks.
Proof from similar projects
- Leaving Google Workspace without losing working files: about 180 users, 5 weeks, two pilot groups first, and Teams-ready landing zones from day one.
- Multi-location roll-up: about 200 source environments, many on Google Workspace, consolidated into one Microsoft 365 tenant.