If you haven’t yet, review the Google Workspace Migrate best practices first.
Before you migrate content from Microsoft SharePoint or OneDrive for Business, review the following points.
| Migrating from OneDrive for Business |
|---|
| If you're migrating from OneDrive for Business, follow the instructions for SharePoint unless specified. |
| Large single-user migrations |
| A migration of 400,000 files or more to one user's Google Drive account requires extra planning. Use a sharding users list to spread the migration load among many user accounts.
To determine the number of user accounts to add to the list, use the larger value of:
We recommend you set up temporary Google Workspace users for your sharding users list. Then, delete the users after you complete the migration. For details, see Create a sharding users list. |
| SharePoint sites |
| When you set up a migration, map the library content to Drive. Google Workspace Migrate transfers file content to a user's My Drive or a shared drive. Web parts are not migrated. |
| SharePoint version metadata |
| Version metadata is not preserved for list items or files. |
| Link sharing |
|
| Items over 2 GB |
| Each SharePoint document, document version, file in a document library, list attachment, and list attachment version has a migration size limit of 2 GB. Items in excess of 2 GB are skipped during a migration.
If a document version or list attachment version is skipped, all subsequent versions are also skipped, even if they are smaller than 2 GB. |
| Migrating to shared drives |
|
| Restricted permissions |
| Restricted permissions (where a child file or folder has fewer permissions than its parent) are not supported by shared drives. If the file or folder has restricted permissions on the source account, the restricted permissions are not migrated. |
| Access level in Drive |
If you're migrating content to Drive, the target user must have the correct access level before you start the migration:
|
| Running test migrations to Drive |
|
If you delete items in the target Drive account following a test migration, make sure to empty the trash before rerunning the migration. Google Workspace Migrate tracks items by ID and will restore items from the target account's trash if you run the migration again. Emptying the trash avoids this issue and allows you to run a fresh migration. |
| Migrating files & folders to multiple locations in Drive |
Google Workspace Migrate attempts to remigrate a file or folder to a new location in Drive if:
The outcome of the remigration depends on the item’s existing and new locations. If both locations are in My Drive or in the same shared drive, the item is moved to the new location. Otherwise, the item is not moved and the transaction fails with error code 1081344. |
| Naming migrated items |
| The names of migrated items correspond to their URL address in SharePoint, not their display name.
If you update the display name of the item in SharePoint, the URL (and the item's name on the target account) doesn’t change. |
| Access to shared drives on target account |
| If the original content authors don’t have access to the shared drives on the target account, files are transferred using the target GUser account specified in the mapping. This type of transfer can create bottlenecks and slow a migration.
We recommend that you:
|
Next step
Now it's time to set up a SharePoint connection. To get started, see Create a location list.
Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.