#Perform Google Drive Migrations

Google Drive Migration allows you to migrate folders or files from Google Drive to SharePoint Online/OneDrive.

To understand the supported and unsupported elements in the migration, you can refer to the Support Lists for Google Drive Migration. Note that Fly only supports Google Drive migrations of Google Workspace, G Suite Business, and G Suite Basic accounts.

#Prepare for Migrations

Before performing Google Drive migrations in Fly, follow the instructions below to prepare the source and destination environments for the migration.

1. Build the inventory on your source Google Drive environment.

   • Number of user accounts

   • Size and structure

   • Other file storage locations

2. Set up Microsoft 365 services and configure your Microsoft 365 subscription.

3. Add and verify the domain

4. Configure application settings

   Refer to Microsoft 365 for enterprise overview for details.

5. Fly does not automatically provision new users in Microsoft 365. Make sure the destination users already exist before the migration.

   There are different ways to add new Microsoft 365 users:

   • Adding users individually. See instructions here.

   • Adding users in bulk. See instructions here.

   • Adding users via PowerShell. See instructions here.

   • Synchronizing users from local Active Directory to Microsoft 365 via Microsoft Entra Sync or Microsoft Entra connect. See instructions here.

6. If you want to migrate content to site collections of the Microsoft 365 Multi-Geo tenant, make sure the corresponding site collections have been created in the destination and the custom script is allowed on the destination site collections.

7. (Optional) Pre-provision OneDrive for users

   If you want to migrate content to OneDrive, make sure the corresponding OneDrive has been created. Refer to Pre-provision OneDrive for users in your organization for details.

8. (Optional) External User migration

   External users cannot be migrated in the migration. Make sure the external users have been created or imported in the destination tenant before the migration. Then you can map the source external users to the destination users in the migration.