Troubleshoot a file migration (beta)

File migration for the new data migration service is currently in beta and subject to the Pre-General Availability Offerings Terms in the Google Workspace Service Specific Terms.

Here’s how to address common issues you may encounter when setting up file migration and migrating data.

On this page

• Can't start a migration
• Need permission to access resources error
• User account issues
• Error uploading migration scope map
• Migration completes, but there are failed items
• Missing files, folders, or permissions

Can't start a migration

You must be signed in as a super administrator for this task.

If you get the error, To start migration, you must have super admin privileges and complete all previous steps:

• Make sure that a super administrator for your Google Workspace account sets up and starts the migration.

Need permission to access resources error

If you get the error, Needs permission to access resources in your organization that only an admin can grant:

• Make sure you are connecting to the Microsoft account using a valid Global Administrator account.

For details, go to Connect to your Microsoft account.

User account issues

Before you begin a migration, you have to set up the user accounts in Google Workspace. For details on setting up user accounts, go to Requirements & setup steps for Google Workspace.

A user account that is not set up, or is set up incorrectly, can cause the following issues in the logs.

Error uploading migration scope map

When you upload the map for your migration scope, you may get one of the following errors:

• Upload sensitive CSV failed
• Validate CSV failed
• Bulk action initiation failed

To troubleshoot, confirm the items below are correct, then re-upload the CSV file:

• The CSV file has only one column with the header, Source email
• The source and destination email addresses are valid
• Each source email is only listed once

Migration completes, but there are failed items

1. Click Export Migration report

2. Identify the items that didn't migrate and the reasons for their failure. For details, go to Understand the file migration report.

3. Fix the issues and then run a delta migration.

Missing files, folders, or permissions

If you have a missing files, folders, or permissions after a migration, follow these steps:

1. Check that the migration scope file includes the emails of the users that own the missing items. Learn more about how to create a list of users to migrate.

2. Verify that your identity map contains the correct list of users. For details, go to Create & upload an identity map.

3. Make sure that at least one owner of the source file or folder has a user account in Google Workspace.

4. Export the migration report. For details, go to Understand the file migration report.

5. Search for the missing file using the file name. File names are part of the Source URI in the migration report.

6. If the message shows as failed in the report, locate the error code in Understand the file migration report. Then, follow the instructions to troubleshoot the error message.

7. Run a delta migration.