Microsoft-to-Google Cloud & Workspace Migration

The technology estate was deeply connected to Microsoft Entra ID, Azure hosting, Microsoft 365, Office and OneDrive. Moving to Google required more than migrating files and mail: identity, access, applications, integrations, devices, security controls, data ownership and user working practices all had to transition without disrupting business operations.

Lead the company-wide transition across identity, productivity, storage, applications and cloud hosting while protecting continuity, security and user adoption.

• Company-wide enterprise migration
• Identity, storage, productivity and hosted services
• Applications, integrations, devices and security controls
• Phased delivery from March to August 2026

Selected technologies

• Google Workspace
• Google Cloud
• Cloud Identity
• Google Drive
• Microsoft Entra ID
• Microsoft Azure
• Microsoft 365
• OneDrive
• Cloud hosting
• Identity migration
• Data migration
• Change management

• Treat identity, data, applications and adoption as one coordinated programme rather than a file-and-mail migration.
• Use coexistence, migration waves, testing and rollback controls around business-critical transitions.
• Separate progress to date from outcomes that can only be measured after the delivery window closes.

• Assessed the Microsoft estate across Entra ID, Azure, Microsoft 365, Office, OneDrive, applications, integrations and authentication dependencies.
• Designed the target Google architecture across Workspace, Cloud Identity, Google Drive and Google Cloud hosting, including coexistence, migration waves, testing and rollback planning.
• Led the movement of users, data, access and hosted services while remediating integrations and protecting security, retention and operational continuity.
• Coordinated communications, user adoption, support readiness, cutover governance and ownership across the wider business.

The programme must consolidate the estate while preserving access, security, integration behaviour and business continuity during coexistence.

• Progress to date: target architecture and a governed transition path have been established.
• Progress to date: identity, productivity, file storage and cloud hosting are managed as one coordinated programme.
• In delivery: phased migration, coexistence and controlled cutovers are protecting business continuity and data access.
• Expected outcome: a more consolidated Google-based technology operating model after the August 2026 delivery window.

Progress is evidenced through target-state decisions, dependency assessment, migration waves, test results, cutover controls and adoption readiness. Final outcomes will be measured after delivery.