Understand email migration reports

When migrating email data with the new data migration service, you can access reports to get detail on migrated items. The 2 types of reports are a migration report and a user report.

On this page

Export the reports

After you run a migration, you can download the 2 reports in the Google Admin console of your target account.

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

  1. Sign in to your Google Admin console.

    Sign in using an account with super administrator privileges (does not end in @gmail.com).

  2. In the Admin console, go to Menu and then Dataand thenData import & exportand thenData migration.
  3. To export the reports to Google Sheets, click Export migration report or Export user report (not available for consumer Gmail migrations).

    If the amount of data in the report exceeds the limit allowed in Sheets, the report is downloaded as a comma-separated values (CSV) file.

  4. If the Tasks list doesn't open automatically, click Tasks .
  5. For Your Tasks, click the link to open the file in Sheets.

Understand the user report

This report isn't available if you're running a migration from a consumer Gmail account.

The user report provides a count for each user of the success or failure of their email migration.

User summary report field Description
Source user Email address of the user on the source account
Target user Email address of the user on the target account
Status Status of the user's migration:
  • Running—Migration is in progress.
  • Failed—Migration didn't complete because of discovery issues. To troubleshoot, check the migration report for the specified error.
  • Completed—Migration completed successfully. Any messages or labels that didn’t migrate are listed in the migration report.
Emails migrated successfully Number of messages migrated successfully for the user (including messages that were skipped in an earlier migration)
Emails failed Number of messages that failed to migrate for the user

Discovery failures

(IMAP migrations only)

Number of folders that failed to be crawled for messages

Interpret the migration report

The migration report provides detail about issues encountered during the migration process. You can use the report to identify items that didn't migrate and the reasons for the failure. If all items in the migration were successfully migrated or skipped, a detailed log isn't generated.

Error report field Description
Status

The migration status of the item:

  • Success–The item successfully migrated.
  • Warning–The item migrated, but failed to complete as expected.
  • Error–The item didn't migrate, due to an error.
  • Skipped–The item was skipped. Items can be skipped for the following reasons:
    • The item was migrated in a previous migration and wasn't updated in the source account before a delta migration.
    • The item was migrated to one user, then later migrated to a different user in the same migration wave (the migration wasn't exited and re-established).
Error/warning code & description The code and message associated with the error or warning status.

For help with frequently seen error messages, go to Common error messages (later on this page).

Processing start time
Processing end time
The start and end time of the migration of the item
Source type & source identifier (for Google Workspace and consumer Gmail migrations)
  • Gmail message—users/user_email/messages/message_id
  • Gmail message crawler—users/user_email
  • Gmail label—users/user_email/labels/label_id
  • Gmail label crawler—users/user_email
  • Source URI—Full header (message-ID) of a message or label name from the source account
Source type & source identifier (for IMAP server migrations)
  • IMAP folder crawler–users/user_email
  • IMAP folder–users/user_email/folders/folder_id
  • IMAP message crawler–users/user_email/folders/folder_id
  • IMAP message–users/user_email/messages/message_id
Target type & target identifier
  • Gmail message—users/user_email/messages/message_id
  • Gmail label—users/user_email/labels/label_id

Resolve common error messages

If you get an error that is not mentioned in this table, try running a delta migration.

Error message Description & troubleshooting help
Temporary error occurred A transient error. Run a delta migration.
User not found A user in the migration map wasn't found. Either the domain or the username is incorrect.

Remove the current migration map, correct the map, and upload again. For details, go to create & upload a migration map for a Google Workspace or IMAP account. If you are migrating from a consumer Gmail account, make sure that you have entered the source and target user correctly. For details, go to steps 1 and 2 of Migrate email from a Gmail account.

User does not exist
User is deleted
The user has been deleted from the source account. Add the user to the source account, and run a delta migration.
Virus or other attachment problem Gmail blocks messages that might spread viruses, such as messages that include executable files or certain links.

For more information, go to File types blocked in Gmail.

Connection not in usable state Your connection contains errors and is no longer in a usable state.

Disconnect the current connection and create a new connection making sure you complete the authorization steps. For details, go to run a migration for Google WorkspaceIMAP, or Gmail account.

All required OAuth scopes have not been granted access Some or all of the required OAuth scopes haven't been granted domain-wide delegation.

Disconnect the current connection, and create a new connection making sure you complete the authorization steps. For details, go to run a migration for Google WorkspaceIMAP, or Gmail account.

Error occurred while generating user credential Domain-wide delegation hasn't been granted. In most cases, the domain-wide delegation process completes within a few hours, but you should allow up to 24 hours.

When the process is complete, run a delta migration to retry the failed tasks. For details, go to Run a delta migration.

Error occurred while calling source system An error occurred when the system was generating the consumer Gmail user's credentials. The user on the source account might have revoked OAuth access.
Invalid user provided in migration mapping A user email ID in the migration map is invalid or is not a Google email ID.

Remove the current migration map, correct the map, and upload again. For details, go to create & upload a migration map  for a Google Workspace or IMAP account. If you are migrating from a consumer Gmail account, make sure that you have entered the source and target user correctly. For details, go to steps 1 and 2 of Migrate email from a Gmail account.

User provided in migration mapping does not belong to a Workspace customer A user email ID in the migration map is not a Google Workspace email ID.

Remove the current migration map, correct the map, and upload again. For details, go to create & upload a migration map for a Google WorkspaceIMAP, or Gmail account migration.

User provided in migration mapping does not belong to the source Workspace customer A user email ID in the migration map doesn't belong to the source account.

Remove the current migration map, correct the map, and upload again. For details, go to create & upload a migration map  for a Google Workspace or IMAP account. If you are migrating from a consumer Gmail account, make sure that you have entered the source and target user correctly. For details, go to steps 1 and 2 of Migrate email from a Gmail account.

Invalid label A label was deleted from the source account during the migration. Add the label again and run a delta migration.

You can also get this error if the target account is new. Wait for a few hours before trying the migration again.

Label name exists or conflicts with label This error can occur if a label on the source account already exists on the target account. Remove the label from the target account and run a delta migration.
Mail service not enabled

Turn on the Gmail service for your users. For details, go to Control Gmail access for your organization’s users.

If the error persists, wait for a few hours before trying the migration again.

Related topics

Was this helpful?

How can we improve it?
Search
Clear search
Close search
Main menu
8769156340168927996
true
Search Help Center
true
true
true
true
true
73010
false
false