Many organizations are moving their server-based email and/or file sharing to the cloud and these can be done in isolation of each other with separate projects, timelines, and funding.

You are migrating a platform, not just a workload This work can be done up front or post migration, but it must be done. This means that users will only feel whole again after a lot of training and manual work to reorganize their shared workspaces. The approaches are not only different technically but also different in user experience and use cases.

In case you don't make it all the way through this article, the most important observation I have is this: Google's approach to file collaboration and portals (Google Drive, Google Sites) is vastly different from Microsoft's approach (OneDrive for Business, Teams, and SharePoint Online). If you are moving from Office 365 to Google, this article may still shed some light on things you should be thinking about. I hope this is useful reading to those contemplating a similar move or just curious about what it takes to do so.

Here are some of my observations and lessons learned covering the technical perspective of the entire project. The entire project involved a large team of partners and my role was to plan, organize, and lead a team to migrate the Google Sites and custom apps built using the Google Suite. I recently led a development team on a project to move an organization of over 75,000 users from the Google Cloud Platform to Microsoft Office 365. If your organization is already running on the Google Cloud Platform (GCP) or Microsoft Office 365, what happens when you want to switch providers?

Migrating google drive to onedrive