SharePoint Online and OneDrive for Business migrations each have two endpoint types:
- SharePoint Online v2
- OneDrive for Business
- OneDrive Pro for Business v2
SharePoint and OneDrive for Business endpoints use the legacy CSOM API. SharePoint Online v2 and OneDrive Pro for Business v2 use the new SharePoint Online Azure Migration API, which does not throttle or block migrations, as CSOM API does when exceeding throttling limits, and is definitely faster. Since Microsoft plans to begin throttling CSOM calls more and more, migrations that use CSOM endpoints will become slower than they are today.
The new SharePoint Online Azure Migration API has completely changed the way migrations are done, which directly impacts the migration speed (with a performance increase ranging from 2 to 10 times faster) and the number of concurrent migrations (migrations won't be throttled or blocked anymore). An important difference of the new API is that it leverages Azure Storage as a temporary holding place for the data being migrated. Therefore, when creating the endpoints in MSPComplete or in MigrationWiz, you have to provide an Azure Storage account and its primary access key. If you don’t already have an Azure Storage account, you can register and purchase it, or use a free trial by clicking on this link. The location of your Azure Storage should be the same location as your tenant, to reduce the processing time of data ingestion into SharePoint Online.
During the migration process, the v2 connectors now create two unique Blob Containers. The first is the one into which the Source files will be migrated, while the second is used for a package containing the migration instructions that Microsoft is to follow during the import.
- The v1 endpoints support Delta migrations; the v2 endpoints do not. If you need Delta migrations, you would need subsequent migrations to use a v1 connector. A v2 connector can only be used for the first migration pass (i.e. the v2 connector can never be used for delta migration passes).
- The v1 connectors support the closest approximation for the Shared with Me feature when migrating from Google Drive. The v2 connectors do not support the Shared with Me feature. If you care primarily about the Shared with Me feature, use the v1 connectors. KB005034 explains how to use MigrationWiz with the moderate mode Advanced Option to support the Shared With Me feature. Watch the how-to video in the article here, to learn how to migrate from Google Drive to OneDrive for Business.
- When migrating from Google Drive, using the v2 connector, all permissions are mapped as SharePoint permissions versus Sharing Roles (which are specific to Google Drive). As such, the Google Drive "Shared with Me" sharing role view will not be populated, as many users expect. This is because specifying the Sharing Roles is not directly supported in the Microsoft migration package definition at this time. If you want the closest approximation for the Destination Shared with Me view as you would find in the Source, you will need to use the v1 endpoint to migrate the data.
- The Blob containers that are created during migration should be deleted post-migration. The reason for is to ensure that no extra Azure costs can be incurred if any automated tasks are repeatedly trying to remigrate items due to failed migrations.
- If you experience any failed migrations when using v2 endpoints:
- Reset watermarks. KB005101
- Remove all items from Azure blob containers that were created by the migration.
- Remove any items from the Destination (e.g., in OneDrive for Business accounts).
- Begin the entire process again (including the upload to Azure, followed by migration). For exact steps, refer to the migration guide that matches your migration scenario.