#SharePoint Online to Google Drive Migration Process

The sections below contain the general migration process for SharePoint Online to Google Drive Migration. The details outlined in this document can serve as general guidelines with some minor adjustments.

• Preparation
• Migration Execution

More steps may be needed, and some steps included in the process may be optional according to your migration requirements.

#Preparation

Before the migration, you need to identify what object types you want to migrate. See the Supported and Unsupported List.

#1. Create a service account or app profile with required permissions for SharePoint Online

To connect Fly to your SharePoint Online, create a service account or an app profile with required permissions in AvePoint Online Services. Refer to the latest Required Permissions to check the required permissions for SharePoint Online to Google Drive Migration.

#2. Create an app profile with required permissions for Google Drive

To connect Fly to your Google Drive, create an app profile with the required permissions in AvePoint Online Services. Refer to Permissions for Destination Google Drive to check the required permissions. 

#3. Filter site collections (optional)

If there are many site collections in your tenant and you only want to migrate some of them, you need to prepare a custom app profile with different set of permissions and apply the app to the desired site collections. Refer to Permissions for Source SharePoint Online for details.

#4. Run the source tenant discovery (optional)

Before you migrate from SharePoint Online, you can run a tenant discovery for SharePoint Online to scan and report the object count, object type, object size, and other details. According to the discovery reports, you can better understand your source environment and plan for your migrations. Refer to the user guide for Tenant Discovery for details.

#5. Provision all necessary users/groups in the destination tenant

Fly does not automatically create new users in Google Drive. Make sure the destination users already exist before the migration.

#6. Throttling limits in migration

Google has throttling restrictions. The more mappings you run at a time, the greater effect of throttling restrictions on the migration speed. You can contact Google Support for help.

#7. Migration throughput

For SharePoint Online to Google Drive migrations, generally, a reasonable migration speed is 5-20 GB/hour/mapping. For the number of mappings that can be run in each project, it is automatically allocated based on the subscription you purchased. The more user seats you purchase, the more mappings you can run in a project.

There are many factors which may affect migration performance:

• The above throughput number is for full migration. Generally, it may be lower for incremental migration since Fly needs to spend quite some time in checking the migrated item status for incremental migration. 

• Throttling: There may be throttling in the source or destination, which will reduce the migration performance.

#8. Create source and destination connections

Refer to Create a Connection to connect to your source SharePoint Online and destination Google Drive. The connection including both the app profile and service account or app profile and delegate app is recommended.

#9. Design the migration policy

A SharePoint migration policy allows you to configure the conflict resolution, filter policy, user mapping and other options for SharePoint Online to Google Drive Migration. Refer to  Configure a Migration Policy for details. 

To ensure the maximum preservation of source data, we recommend you use Merge as the container level conflict resolution and use Overwrite by last modified time as the content level conflict resolution.

#10. Plan a pilot run

We recommend that you do a pilot run for the following purposes:

• Get familiar with Fly interface and understand the whole migration process.

• Discover any potential issues early and resolve them before production migration.

• Understand the throttling situation in case content size is large, and then try to resolve it with the destination.

A pilot migration should be as close to the wave migration as possible and involve all steps that any wave will involve.

Refer to Run Migrations to Migrate Objects for details.

#Migration Execution

Based on your source tenant discovery report, you need to prepare a final mapping file to list the mappings of source data and destination location. As you may have a heavy load of content to migrate, we recommend you separate your mappings into multiple waves according to your departments for easy management. Keep communicating with users about the migration status.

#1. Configure projects and mappings in Fly

To configure projects and mappings, refer to Create a Project and Create Migration Mappings for details. Use the mapping file of data to be migrated to configure the migration project.

#2. Perform regular full migrations

Before running the job, we recommend you verify the mappings to ensure that the mappings are available for migration. Refer to Pre-analyze Mappings for details.

Then you can run a full migration job to migrate the objects based on your configured migration policy. Refer to Run Migrations to Migrate Objects for details.

#3. Perform regular incremental migrations

Handle new, updated, and failed data. Refer to Run Migrations to Migrate Objects about how to perform regular incremental migrations.

#4. Validate migration results

• Check the mapping report. If the mapping fails or finishes with exceptions, you can check the error code and comment for the mapping in the Migration error section. You can click the error code to view the details and recommendations of the code in the Troubleshooting Guide, which can assist you in resolving or avoiding the error.

• Check the item count and permissions in the destination. If permissions are failed to be migrated, you can run a Migrate permissions only migration job.

• Check Google Drive sheet in the destination.

• New data can be created in destination.

#5. Set the source site to read only

Before executing the final delta/incremental migration, make sure that no data will be changed or created in the source during the migration to enforce the data consistency.

• To set a site collection as read only, run the following script using PowerShell:

  #Set Parameters
  
  $AdminCenterURL="https://contoso-admin.sharepoint.com"
  
  $SiteURL = "https://contoso.sharepoint.com/sites/marketing"
  
  #Connect to SharePoint Online
  
  Connect-SPOService -Url $AdminCenterURL -Credential (Get-Credential)
  
  #PowerShell to set onedrive for business site to read only
  
  Set-SPOSite -Identity $SiteURL -LockState ReadOnly

• To unlock a site collection, run the following script using PowerShell:

  #Unlock site from read only mode
  
  Set-SPOSite -Identity $SiteURL -LockState Unlock

#6. Perform the final incremental migration for current wave

At the end of the migration project, we recommend you run a final incremental job to ensure all source data are migrated to the destination.

#7. Run migrations for all other waves (optional)

This step is only needed if you have separated the migration plans into multiple waves.