OneDrive, SharePoint & Teams
Data Moving to Google Workspace

OneDrive → Google Drive

OneDrive personal files migrate to each user's My Drive in Google Drive. This is generally the most straightforward piece of the collaboration migration — file and folder structure typically carries across cleanly, with Office documents convertible to Google's native Docs, Sheets, and Slides formats where needed (or kept as Office files if your team prefers to keep working in Office format within Drive).

SharePoint → Shared Drives

SharePoint document libraries map to Google Shared Drives, generally one Shared Drive per site or major library. The bigger planning item here is permissions — SharePoint's permission model is more granular than Shared Drives' structure, so access needs to be deliberately redesigned rather than assumed to translate automatically. This is also a natural point to clean up permission sprawl that's accumulated over years, rather than replicate it exactly as-is.

SharePoint customisations — classic workflows, custom web parts, InfoPath forms — don't carry forward at all; they need to be individually assessed and either rebuilt using Google Workspace-native tools (like Apps Script or Google Forms for workflow-adjacent needs) or deliberately retired.

Microsoft Teams → Google Chat and Spaces

This is the piece with the least direct equivalent. Teams channel conversations, chat history, and file references need a specific migration path — Teams channels roughly map to Google Chat Spaces, but the underlying structure and feature set aren't identical. Meeting recordings, pinned messages, and app integrations tied to Teams typically need individual handling rather than a bulk transfer. Organisations with heavy day-to-day Teams usage should budget more planning time for this piece specifically than for OneDrive or SharePoint.

What commonly gets missed

• External sharing links from SharePoint or OneDrive often need to be regenerated post-migration rather than carrying over automatically.
• Third-party apps connected to Teams (approval workflows, scheduling bots, CRM integrations) need to be reconnected to their Google Workspace equivalent, or replaced if no direct equivalent exists.
• Large document libraries with deep folder nesting can hit path-length differences between the two platforms — worth a pre-migration scan rather than discovering mid-migration.

What we look at during discovery

Content and permissions audit. Full inventory of OneDrive, SharePoint sites and libraries, and Teams usage patterns.

Customisation assessment. SharePoint workflows, forms, and integrations catalogued and triaged individually.

Teams migration planning. A specific plan for channel conversations, files, and any critical integrations.

Migration and validation. Content and permissions verified against source before the legacy environment is decommissioned.

For the full migration picture, see our Microsoft 365 to Google Workspace migration guide, or reach out through our data migration service to discuss your specific environment.