// Case study
Google Workspace migration: Microsoft 365 / SharePoint → Google Workspace
Migrated a client domain from Microsoft 365 and SharePoint into Google Workspace — mail, drive content, identity, and groups cut over with continuity of access.
Tools / technologies
- Microsoft 365
- SharePoint
- Google Workspace
- Identity / domain
- Migration tooling
Problem
Delivered as a senior MSP engagement at Uptime Ontime LLC (client anonymized). The organization was running on Microsoft 365 with SharePoint as the document substrate. Day-to-day collaboration worked, but the platform mix had grown costly, complex to administer, and out of step with where the team actually worked. They wanted a unified collaboration baseline on Google Workspace.
Constraints
- Domain-wide cutover — no leaving teams behind on the legacy stack.
- Mail, files, and identity had to land intact, not re-keyed.
- Users had to be able to keep working through the transition without a multi-day blackout.
- Existing SharePoint content had to migrate into Google Workspace without losing structure.
Role
Owned the migration program on the client’s behalf: discovery, planning, communication, execution, and the post-cutover cleanup that always takes longer than the slide deck claims.
What I did
- Mapped the source environment — mail, SharePoint sites, group structures, identity, sharing rules.
- Planned the target topology in Google Workspace (organizational units, groups, sharing defaults, drive structure).
- Migrated mail and drive content from Microsoft 365 and SharePoint into Google Workspace.
- Executed domain cutover with continuity of access — users found their data where they needed it.
- Stabilized post-cutover: sharing rules, group memberships, and the small fires that show up only after real use.
Outcome
- One collaboration platform instead of two overlapping ones.
- Simpler admin surface; fewer SKUs to license and reason about.
- A clean baseline that downstream automation and AI tooling can build on.
- A client team that kept working through the transition rather than around it.
What it demonstrates
Owning a high-risk, cross-platform migration end-to-end on behalf of a client — including the unglamorous parts (sharing rules, identity mappings, communication) that decide whether a migration feels successful to the people using it.