Watchpoints & best practices for SharePoint

If you're migrating from OneDrive for Business, follow the instructions for SharePoint unless specified.

Before you begin to migrate content from Microsoft SharePoint, make sure you review the Google Workspace Migrate best practices. Then, familiarize yourself with the following SharePoint watchpoints and best practices. 

Watchpoint Best practices
Large single user migrations—A migration of 400,000 files or more to a single user’s Google Drive requires additional 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: 

  • One account per 400,000 files that are being migrated to Drive
  • 10 accounts per node

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 shared drive. Web parts are not migrated. 

SharePoint version metadata—Version metadata is not preserved for list items or files. Because there's no other versioned content for list items, historic versions aren't evaluated at all.

Before you migrate, tell your users about this issue.

Link sharing—If users shared SharePoint files or folders with a link, the items don't retain their link-sharing permissions following a migration.

After a migration, re-enable sharing on the target domain for the affected files and folders.

If anyone shared the files or folders with users outside your organization, you must manually re-enable sharing with these users after migrating the objects.

Large items—SharePoint items in excess of 2 GB will fail to migrate. 

Each SharePoint document, document version, file in document library, and list attachment has a migration size limit of 2 GB. Items in excess of 2 GB are skipped during a migration.

Additionally, if a document version or list attachment version is skipped, all subsequent versions are also skipped, even if they are smaller than 2 GB.

Data migrated to shared drives
  • You can’t migrate content to a user's My Drive and shared drives in one migration. You must run these migrations separately.
  • If you’re migrating to shared drives, you must use a shared drives settings template. Learn more about settings templates.
Migrating permissions to shared drives

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 environment, 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.

Make sure that the target user specified in the mapping has the appropriate access level in Drive:

  • If you're migrating data to a shared drive, the user needs to be a Content manager or Manager of the shared drive. Go to Shared drives access levels.
  • If you're migrating data to a folder in a user’s My Drive, the user must be an owner of the folder.
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 resurrects items from the trash if you run a migration again. 

Emptying the trash avoids this issue and allows you to run a fresh migration.

Migrating files and folders to multiple locations in Google Drive Google Workspace Migrate attempts to remigrate a file or folder to a new location in Drive if:
  • The item is moved on the source or target account and then remigrated.
  • The item’s target location is changed in a mapping, and the item is remigrated.

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 source 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 instead, which can create bottlenecks and slow a migration.

We recommend that you:

  • Make sure that Migrate folder permissions are turned on in the settings template. Go to Migrate SharePoint to shared drives.
  • Add additional target GUser accounts to help distribute load. We suggest that you use at least one target GUser account for each active node server.


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.

Clear search
Close search
Google apps
Main menu
Search Help Center