Step 4: Review destination paths for Google migrations

On the Drive migrations tab, review the destination paths of the tasks that you moved to the migrations list, making sure they're correct. A task can't be migrated without a destination indicated. Once you start migrating content to a destination, the destination can't be modified.

Single destination edits

If a destination is missing on a migration task (equals a Drive in Google), highlight the row and update the value.

  1. Highlight the row to display its details panel. Under Destination, select Edit to open the Edit destination panel.
  2. Select a OneDrive, SharePoint, or Teams path as the destination. Depending on your selection:
    • For OneDrive, enter the OneDrive URL or email address and the location or folder name.
    • For SharePoint, enter the site URL and location.
    • For Teams, select the team and channel.
  3. Select Save path.

Note

  • If the task contains Google Forms, the Edit destination panel prompts you to enter a Forms destination. Enter the email address of the Microsoft 365 destination user where you want to store the Forms files.
  • Destinations might not appear in the UI because of admin access limitations, multi-geo tenant issues, recent site creation delays, or special characters in the destination path. If you can't locate a destination in the Edit destination panel, upload the destination using a CSV file as described in the next section.

Upload destinations using a CSV file

If there are many destinations to edit, you can choose to upload a bulk destinations CSV file.

upload destinations for Google accounts bulk.

  1. Select Upload destinations from the menu bar to activate the upload destinations panel.
  2. Download the CSV template to your computer. The template lists all migration tasks that haven't run.
  3. Enter your destinations in the correct destination path format by adding to or modifying the Destination path (to be added/modified) column. Save the file as a .csv file.
  4. Select Browse to upload the file. Migration Manager validates the destinations and generates a report if it finds issues. Validation might take some time. We strongly recommend you complete the validation.
  5. Ensure all destinations pass validation, and then select Save.

Note

  • The Forms destination column is required to migrate Google Forms. If a row contains Google Forms, the column displays Forms destination required, please input an email as the Forms destination. Replace this message with the email address of the Microsoft 365 destination user where you want to store the Forms files.
  • Rows with vacant destination paths are skipped in the validation process.

Destination path format

Type Format Example
SharePoint URL https://<tenant>.sharepoint.com/sites/<site name>/<library name>/<optional folder name> https://contoso.sharepoint.com/sites/sitecollection/Shared Documents
https://contoso.sharepoint.com/sites/sitecollection/Shared Documents/SubFolder
OneDrive UPN name@example.com user@contoso.onmicrosoft.com
OneDrive URL https://<tenant name>-my.sharepoint.com/personal/<user principal name>/Documents/<optional folder name> https://contoso-my.sharepoint.com/personal/user_contoso_onmicrosoft_com/Documents
https://contoso-my.sharepoint.com/personal/user_contoso_onmicrosoft_com/Documents/SubFolder

Important

If you select a SharePoint document library root as the destination, the sourceroot-folder permissions aren't migrated. To migrate those permissions, create a folder in the library and use that folder as the destination. Review permission settings.

Pre-provision OneDrive

If you choose OneDrive as the destination, make sure each user's OneDrive exists before migration. If it doesn't, pre-provision OneDrive for users in your organization. Destinations without a provisioned OneDrive fail validation, causing migrations to fail.

[NOTE] For eligible Migration Manager Lite projects, Migration Manager can automatically provision OneDrive on behalf of administrators. If automatic provisioning isn't available or fails, pre-provision OneDrive before starting migration.

Go to Step 5: Map identities