#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.