Migration error report

  1. Migration launch errors
  2. Common migration errors

The number of errors and their description are displayed on the Migration tab.

To view a detailed report, click Details.

The report contains the following fields:

  • Login: The username of the employee who had a migration error.
  • Status: Migration status.
  • Error reason: Error text.

Migration launch errors

  1. Errors loading Google secret
  2. Errors loading Microsoft secret
  3. Common errors

Errors loading Google secret

Error text Solution
Client is unauthorized to retrieve access tokens using this method, or client not authorized for any of the scopes requested
  1. Make sure you enabled API access to the project in Admin SDK API, Google Drive API, and Gmail API.
  2. Start migration again (click New migration).
If access to the project is enabled but the error persists, contact Google Support.
Access Not Configured. Drive API has not been used in project ... before or it is disabled
  1. Make sure you prepared the secret file correctly.
  2. If the file is correct, try creating a new service account and secret key.
  3. Start migration again (click New migration).
The domain administrators have disabled Drive apps
  1. Make sure you prepared the secret file correctly.
  2. Check access to Google Drive.
  3. Start migration again (click New migration).
Invalid credentials
  1. Make sure you prepared the secret file correctly.
  2. Check the Google Drive access token.
  3. Start migration again (click New migration).
Disabled_client: The OAuth client was disabled...
  1. Enable the service account.
  2. Start migration again (click New migration).
Invalid_request: Account disabled
Invalid_grant: No valid verifier for issuer ... The problem is on the side of the server from which you're migrating data. To resolve it, contact Google Support.
Invalid_request: Invalid impersonation "sub" field: @domain.com...
Error text Solution
Client is unauthorized to retrieve access tokens using this method, or client not authorized for any of the scopes requested
  1. Make sure you enabled API access to the project in Admin SDK API, Google Drive API, and Gmail API.
  2. Start migration again (click New migration).
If access to the project is enabled but the error persists, contact Google Support.
Access Not Configured. Drive API has not been used in project ... before or it is disabled
  1. Make sure you prepared the secret file correctly.
  2. If the file is correct, try creating a new service account and secret key.
  3. Start migration again (click New migration).
The domain administrators have disabled Drive apps
  1. Make sure you prepared the secret file correctly.
  2. Check access to Google Drive.
  3. Start migration again (click New migration).
Invalid credentials
  1. Make sure you prepared the secret file correctly.
  2. Check the Google Drive access token.
  3. Start migration again (click New migration).
Disabled_client: The OAuth client was disabled...
  1. Enable the service account.
  2. Start migration again (click New migration).
Invalid_request: Account disabled
Invalid_grant: No valid verifier for issuer ... The problem is on the side of the server from which you're migrating data. To resolve it, contact Google Support.
Invalid_request: Invalid impersonation "sub" field: @domain.com...

Errors loading Microsoft secret

Error text Solution
Application with identifier '...' was not found in the directory '...' This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant.
  1. Make sure you entered the domain and application ID in the secret file correctly, or prepare a new secret.
  2. Start migration again (click New migration).
AADSTS7000215: Invalid client secret provided. Ensure the secret being sent in the request is the client secret value...
AADSTS90013: Invalid input received from the user These errors most often occur if you entered an invalid secret identifier or value.
  1. Create a new secret file.
  2. Start migration (click New migration) with the new secret file.
Either scp or roles claim need to be present in the token
AADSTS7000222: The provided client secret keys for app '73e871c4-2970-4aef-a0ff-7b0797cc46d1' are expired...
  1. Create a new secret file.
  2. Start migration (click New migration) with the new secret file.
Unable to get authority configuration for https://login.microsoftonline.com/your_tenant. Authority would typically be in a format of https://login.microsoftonline.com/your_tenant. Also please double check that your tenant name or GUID is correct The problem is on the side of the server from which you're migrating data. To resolve it, contact Microsoft Support.
Error text Solution
Application with identifier '...' was not found in the directory '...' This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant.
  1. Make sure you entered the domain and application ID in the secret file correctly, or prepare a new secret.
  2. Start migration again (click New migration).
AADSTS7000215: Invalid client secret provided. Ensure the secret being sent in the request is the client secret value...
AADSTS90013: Invalid input received from the user These errors most often occur if you entered an invalid secret identifier or value.
  1. Create a new secret file.
  2. Start migration (click New migration) with the new secret file.
Either scp or roles claim need to be present in the token
AADSTS7000222: The provided client secret keys for app '73e871c4-2970-4aef-a0ff-7b0797cc46d1' are expired...
  1. Create a new secret file.
  2. Start migration (click New migration) with the new secret file.
Unable to get authority configuration for https://login.microsoftonline.com/your_tenant. Authority would typically be in a format of https://login.microsoftonline.com/your_tenant. Also please double check that your tenant name or GUID is correct The problem is on the side of the server from which you're migrating data. To resolve it, contact Microsoft Support.

Common errors

Error text Solution
Domain validity check failed When migrating from Google Workspace or Microsoft 365:
  1. Make sure that the source and target domain names match.
  2. Start migration again (click New migration).
After migration is completed, you can link a new domain, set it as primary, and delete the old domain.
Login error (when migrating from other servers)
  1. Make sure that you entered the correct username and password in the CSV file and enabled IMAP or POP3 access in the mailbox settings.
  2. Start migration (click New migration) after at least one hour so that the hacking protection isn't triggered.
Connection error
  1. Make sure that you entered the correct server address, username, and password when logging in (if you're migrating from another server).
  2. Try logging in with this data in an email client such as Mozilla Thunderbird.
  3. If all fields are filled in correctly but the issue persists, contact the support service of the server from which you're migrating data.
SSL handshake error
  1. Check whether SSL encryption is used in the source server.

  2. If SSL encryption is used, enable the Use SSL encryption option in the Other servers block on the Migration tab.

    If SSL encryption isn't used, disable this option.

  3. Start migration again (click New migration).
Forbidden
  1. Check API permissions in Google Workspace or Microsoft Azure. If there are not enough permissions, add them.
  2. Start migration again (click New migration).
Not Found
  1. Make sure you entered the source mailbox address correctly.
  2. Start migration again (click New migration).

If the address of the source mailbox is a mailing list, you won't be able to migrate data from it.
Session expired, login again
  1. Wait until migration is completed for all accounts.
  2. Start a new migration only for accounts that received this error.
Login error (when migrating from Google or Microsoft servers) Change service account permissions. To do this, contact the support service of the server from which you're migrating data.
ExternalUserNotFound
  1. Make sure you entered the original username correctly.
  2. Start migration again (click New migration).
DiskTemporaryError

If there are multiple accounts with this error in the report, start migration again (click New migration).

If only some of the accounts received this error:
  1. Wait until migration is completed for all accounts.
  2. Click New migration and start migration only for the accounts that received this error.
Failed to get bb info You won't be able to fix this error yourself. Contact support via the form at the bottom of the page.
Error text Solution
Domain validity check failed When migrating from Google Workspace or Microsoft 365:
  1. Make sure that the source and target domain names match.
  2. Start migration again (click New migration).
After migration is completed, you can link a new domain, set it as primary, and delete the old domain.
Login error (when migrating from other servers)
  1. Make sure that you entered the correct username and password in the CSV file and enabled IMAP or POP3 access in the mailbox settings.
  2. Start migration (click New migration) after at least one hour so that the hacking protection isn't triggered.
Connection error
  1. Make sure that you entered the correct server address, username, and password when logging in (if you're migrating from another server).
  2. Try logging in with this data in an email client such as Mozilla Thunderbird.
  3. If all fields are filled in correctly but the issue persists, contact the support service of the server from which you're migrating data.
SSL handshake error
  1. Check whether SSL encryption is used in the source server.

  2. If SSL encryption is used, enable the Use SSL encryption option in the Other servers block on the Migration tab.

    If SSL encryption isn't used, disable this option.

  3. Start migration again (click New migration).
Forbidden
  1. Check API permissions in Google Workspace or Microsoft Azure. If there are not enough permissions, add them.
  2. Start migration again (click New migration).
Not Found
  1. Make sure you entered the source mailbox address correctly.
  2. Start migration again (click New migration).

If the address of the source mailbox is a mailing list, you won't be able to migrate data from it.
Session expired, login again
  1. Wait until migration is completed for all accounts.
  2. Start a new migration only for accounts that received this error.
Login error (when migrating from Google or Microsoft servers) Change service account permissions. To do this, contact the support service of the server from which you're migrating data.
ExternalUserNotFound
  1. Make sure you entered the original username correctly.
  2. Start migration again (click New migration).
DiskTemporaryError

If there are multiple accounts with this error in the report, start migration again (click New migration).

If only some of the accounts received this error:
  1. Wait until migration is completed for all accounts.
  2. Click New migration and start migration only for the accounts that received this error.
Failed to get bb info You won't be able to fix this error yourself. Contact support via the form at the bottom of the page.

Common migration errors

Error text Solution
Contains the phrase HTTPSConnectionPool
Example
HTTPSConnectionPool(host='login.microsoftonline.com', port=443): Read timed out. (read timeout=None)

If there are multiple accounts with this error in the report, start migration again (click New migration).

If only some of the accounts received this error:
  1. Wait until migration is completed for all accounts.
  2. Click New migration and start migration only for the accounts that received this error.
Error text Solution
Contains the phrase HTTPSConnectionPool
Example
HTTPSConnectionPool(host='login.microsoftonline.com', port=443): Read timed out. (read timeout=None)

If there are multiple accounts with this error in the report, start migration again (click New migration).

If only some of the accounts received this error:
  1. Wait until migration is completed for all accounts.
  2. Click New migration and start migration only for the accounts that received this error.

If the error persists or isn't described in the article, contact support.