Moving files is easy. Preserving access, ownership, and daily workflows is harder. This guide explains how to plan a Google Workspace to Microsoft 365 migration, prepare accounts, choose tools, transfer personal and shared content, and verify the result before retiring Google Workspace.
At Bridgeall we are a Microsoft 365 partner that helps business migrate to Microsoft 365 from Google workspace. In this article we discuss our step-by-step guide.
Google Workspace to Microsoft 365 migration overview
A migration is not a one-click copy. It includes discovery, destination design, account setup, transfer, testing, cutover, and user support.
Google Workspace content usually moves to:
- My Drive → OneDrive: Personal files owned by a user.
- Shared Drives → SharePoint Online: Team-owned files that need group access.
- Collaboration spaces → Teams and SharePoint: Department or project files accessed through Microsoft Teams.
Start with an inventory and pilot. Then move users and Shared Drives in batches. After a final sync, verify access and restrict the old system.
Success means more than matching file counts. Users must be able to find, open, edit, and share files without gaining improper access.
Why move from Google Workspace to Microsoft 365?
Microsoft 365 is not right for every business. Google Workspace may suit teams built around browser-based, Google-native work. Migration makes sense when Microsoft’s model better fits the organisation.
Common reasons include:
- Office integration: Teams that use Word, Excel, PowerPoint, and Outlook may prefer Microsoft’s desktop and web apps.
- Identity and security: Microsoft Entra ID, conditional access, and device management can support a shared access strategy.
- Collaboration: Teams, SharePoint, and OneDrive provide separate spaces for meetings, team files, intranets, and personal work.
- Compliance: Some plans include retention, auditing, eDiscovery, sensitivity labels, and records tools.
- License consolidation: Subscription-based licensing may reduce overlap when a business already buys Microsoft productivity, security, identity, or device services.
Compare plans, training, integrations, administration, data location, and current Google processes, not price alone. The value of subscription-based licensing depends on which services the business will use.
Both suites offer cloud-based productivity tools, but they organise content in different ways.
The key driver for Microsoft is when you start to look at cyber security, the ability to jump to Business Premium o E3 licenses and have access to entra ID, Defender, endpoint manager and more is a big bonus and offers great value, whereas Google is just the productivity suite.
Storage, ownership, and sharing
My Drive often uses individual ownership, while Shared Drives use organisational ownership.
Microsoft separates storage as follows:
- OneDrive is linked to one user.
- SharePoint Online stores team and organisational content.
- Teams uses SharePoint for channel files and OneDrive for some personal sharing.
Permission models also differ. Google uses users, groups, domains, and sharing links. Microsoft uses users, Microsoft 365 groups, SharePoint groups, site membership, and links. Similar labels may not create equal access.
Google Docs, Sheets, and Slides can be converted to Word, Excel, and PowerPoint. Complex formatting, formulas, scripts, comments, or embedded items may change. Test representative files before migration.
Plan the migration and prepare accounts
Inventory users, My Drives, Shared Drives, data volumes, owners, permissions, external guests, stale accounts, and sensitive files. Flag former employees and content without clear owners.
Check for common risks:
- Unsupported, oversized, or zero-byte files
- Long paths or unsupported characters
- Broken shortcuts, links, and bookmarks
- External users without Microsoft identities
- Permissions that do not map well
- Missing or reduced version history
- Google Apps Script, Forms, Sites, or add-ons that need rebuilding
- API throttling during large batches
Decide whether to migrate, convert, archive, rebuild, exclude, or manually move each affected item.
Prepare Microsoft 365:
- Create or sync users and groups.
- Assign suitable licenses.
- Provision OneDrive accounts and SharePoint sites.
- Map Google accounts to Microsoft identities.
- Map each Shared Drive to a SharePoint site or library.
- Confirm administrator access and source authorisation.
- Tell users the schedule, expected effects, and required actions.
Choose a migration method
Migration Manager is Microsoft’s built-in tool for scanning and moving supported Google Workspace content. Other options include:
- Manual download and upload: Best for small, simple datasets.
- Microsoft workload tools: Used for services such as Exchange Online rather than Drive files.
- Third-party platforms: May offer added reporting, transformations, support, or coexistence features.
Choose based on data volume, permissions, reporting, schedule, support, and budget. Organisations may also use a Microsoft partner for destination design and migration support.
Migration limitations and considerations
Not every Google feature has a direct Microsoft equivalent. Native files may need conversion. Sharing models can change, while shortcuts and embedded links may still point to Google. Version history, metadata, comments, external access, and permissions may not transfer exactly.
Tools also have service limits and supported-item rules. Review current Microsoft guidance before scanning and keep a process for files that need manual work. Plan separate fixes for Sites, Forms, Apps Script, add-ons, and other Google-specific workflows.
Step-by-step migration process
Here is a step-by-step guide for migrating Google Workspace to Microsoft 365:
- Connect Google Workspace and grant the required access.
- Scan My Drives and Shared Drives for volumes, owners, and issues.
- Review reports for invalid paths, unsupported items, permission errors, and unmapped users.
- Map My Drives to OneDrive.
- Map Shared Drives to SharePoint sites and libraries.
- Set filters and migration tasks.
- Run a representative pilot.
- Validate the pilot before production.
- Migrate in controlled batches.
- Fix errors and rerun failed items.
Avoid moving every department at once. Smaller batches make errors and support needs easier to manage.
File transfer is only one workstream. Gmail, calendars, and contacts need an Exchange Online plan, identity mapping, mail-flow preparation, and a coordinated cutover. Test Gmail migration with pilot mailboxes before changing production mail routing.
Cutover, verification, and post-migration steps
Limit source changes before the final sync. If email is included, coordinate DNS and mail routing with the file cutover. Old Google links may not open the new SharePoint files. Give users destination maps and link-replacement guidance.
Where policy allows, keep Google read-only for an agreed period. Fix urgent issues, finish manual rebuilds and meet retention or legal needs. Then remove access, revoke migration permissions, export required audit records and decommission Google securely.
Lessons and final migration checklist
Use this checklist:
- Inventory users, files, permissions, owners, and guests.
- Map My Drives to OneDrive and Shared Drives to SharePoint.
- Prepare accounts, groups, licenses, sites, and administrator access.
- Scan data and resolve risks and limitations.
- Pilot representative users, formats, and permissions.
- Move data in controlled batches.
- Coordinate email, calendar, contacts, and DNS changes.
- Run the final sync and restrict source edits.
- Verify files, permissions, links, versions, and ownership.
- Support users and resolve logged issues.
- Retain Google as required, then decommission it securely.
A Microsoft 365 Migration Partner
At Bridgeall we are a Microsoft 365 Migration Partner. We have a proven methodology and regularly help businesses migrate to Microsoft 365 from Google Workspace. We ensure you have a smooth migration, and your new Microsoft 365 tenant is fully optimised and secure.



