You might encounter the following error codes when using the data migration service.
For information on error messages you might find when using the data migration service, go to Data migration service error messages.
|Error code||Details & troubleshooting|
|11001||Invalid request or response. Verify the steps in Migrating from an EWS environment.|
|11002||Invalid response from the Exchange server. Verify the steps in Migrating from an EWS environment.|
|11003||Verify the Exchange URL is valid. For details, go to Migrating from an EWS environment.|
|11004||This error might be temporary. Confirm you can connect to the Exchange server using the Microsoft Remote Connectivity Analyzer tool.|
|11007||Confirm you can connect to the Exchange server using the Microsoft Remote Connectivity Analyzer tool.|
|11008||Invalid response while reading from the Exchange server. Verify the steps in Migrating from an EWS environment.|
|11009||The data migration service is operating at a rate that exceeds the limits of the source system. To resolve this, adjust the migration speed. Make sure the source server can handle the number of connections you select.|
|11010||The Exchange mailbox is invalid or turned off. Verify the steps in Migrating from an EWS environment.|
|11011||Invalid Exchange folder or insufficient permissions to access the folder. Verify the steps in Migrating from an EWS environment.|
|11012||Error connecting to the Exchange server. Verify the steps in Migrating from an EWS environment.|
|11013||Error communicating with the Exchange server. Verify the steps in Migrating from an EWS environment.|
|11016||Check the impersonation rights of the role account. For details, go to Migrating from an EWS environment.|
|11017||Turn on the account on the Exchange server and try again.|
|11018||The Exchange server reports one of the folders in the mailbox is corrupt and cannot be migrated.
To resolve this, consult your Exchange documentation to fix the corrupted folder. Then, verify the steps in Migrating from an EWS environment.
|11019||The Exchange server reports some or all data in the mailbox is corrupt and cannot be migrated.
To resolve this, consult your Exchange documentation to fix the corrupted data. Then, verify the steps in Migrating from an EWS environment.
|11020||Verify the user exists in Microsoft Active Directory. Then, verify the steps in Migrating from an EWS environment.|
|11021||Your administrator account does not have the correct impersonation permissions. For details, go to Migrating from an EWS environment.|
|11022||Your administrator account does not have the correct impersonation permissions on the Client Access server. Check the Exchange impersonation settings. For details, go to Migrating from an EWS environment.|
|11023||There was an unexpected error when Google tried to authenticate to the Exchange server. This error indicates one of the following issues:
Try the troubleshooting steps in Migrating from an EWS environment.
|11024||Your Exchange virtual directory has not been set. Consult your Microsoft documentation for further information on creating a virtual directory.|
|11025||Verify the EWS URL you provided is accessible using the Microsoft Remote Connectivity Analyzer tool. Then, start the migration again.|
|11026||The SSL certificate is not installed or is installed incorrectly on your source server. For details, go to Set up your TLS certificate.|
|11028||Internal server error because the source server is busy. This error is temporary.
If the issue persists, it might be the data migration service is operating at a rate that exceeds the limits of the source system. To resolve this, adjust the migration speed. Make sure the source server can handle the number of connections you select.
|11029||The source server doesn't support the required TLS version. Make sure that the server supports TLS 1.2.|
|12001||The user might have been deleted from Google Workspace while the migration was running. Check the user and start the migration again.|
|13001||Internal server error. Try exiting and restarting the migration.|
|13002||Internal authentication error. Try exiting and restarting the migration.|
|13008||Internal communication error. Try exiting and restarting the migration.|
|15005||Usually a temporary error. The migration should start normally after initializing. If the issue persists, contact Google Workspace support.|
|15008||Internal server error. Try exiting and restarting the migration. If the issue persists, contact Google Workspace support.|
|15011||Internal connection error. Problem communicating with the source mail server. Verify the steps in your migration.|
|15012||Usually a temporary error. Stop the migration, wait 5 minutes, and restart.|
|15014||The number of source folders exceeds the number of labels allowed in Gmail. Reduce the number of folders and try again. For more details about Gmail labels, go to Create labels to organize Gmail.|
|15024||Draft and Sent folder not found. Check the IMAP visibility of the Draft and Sent folders on your source server and try again.|
You might have encountered this error due to a technical issue with data migration for Microsoft Exchange Online (Office 365). The data migration service for Exchange Online is temporarily unavailable. Learn more
If you're not migrating from Exchange Online, try exiting and restarting the migration.
|17009||Generating an access token with the supplied credentials was unsuccessful. The authentication might have expired. Exit and restart the migration. Complete the steps in Set up and migrate from Gmail.|
|18001||The data migration service is operating at a rate that exceeds the limits of the source system. To resolve this, adjust the migration speed. Make sure the source server can handle the number of connections you select.|
Failed to open the IMAP folder. Check Google IP address ranges for outbound mail servers and ensure that the IMAP server can accept a connection from them. If required, see the additional setup steps for migrations from HCL Domino or Gmail. Then, ensure all of the folders in the affected source user's mailbox can be accessed using IMAP. To verify this, use an IMAP mail client such as Mozilla Thunderbird or Apple Mail.
|18003||Temporary error. It might help to increase the number of parallel connections to the source server.|
|18004||Failed to connect to the IMAP mailbox. Verify the steps in Prepare your source account.|
|18005||The message format contains an invalid MIME format, and it can't be imported into Gmail. As a workaround, manually forward the message from the source mailbox to the target mailbox.|
|18006||The IMAP server is busy. Temporary error.
Can occur when migrating from Gmail or Google Workspace and a Gmail label on the source account contains unsupported Unicode characters, including Ideographic spaces and no-break spaces.
Before migrating, rename any affected labels on the source account. Post-migration, revert back to the original name in both the source and target mailboxes.
|18010||The IMAP server is busy. Usually a temporary error.|
|18011||The data migration service cannot read data from an IMAP folder. The folder might be corrupted.|
The default personal namespace of the user is set incorrectly.
To check the personal namespace:
For more information, consult the Internet Engineering Task Force documentation on IMAP4 namespace and your IMAP server documentation.
|18015||The data migration service couldn't connect to the source Gmail account. Verify you've completed the personal Gmail account setup steps and try again.|
|18016||IMAP is turned off for the source Gmail account. For details on how to turn on IMAP, go to the personal Gmail account setup steps.|
You might see this error if:
If the issue persists, choose an option, depending on where you're migrating from:
The connection to Gmail using IMAP failed.
The source account requires a more secure form of authentication because it has 2-Step Verification enabled. To migrate using more secure authentication:
If it's not possible for you to take the steps above, create an App Password in the source account. Use it instead of your regular password when adding the source account in the data migration service. See Sign in using App Passwords.
Note: The data migration service doesn't require you to turn off 2-Step Verification or allow access to less secure apps.
|19005||Verify the migration client has enough permissions to read and write the user's contacts.|
|19007||The user has exceeded their personal external contacts storage limits.|
|19008||Google Workspace user account is deleted. Verify whether the user account should be deleted and rerun the migration.|
|21004||Error uploading message. If several attempts are unsuccessful, the message will not migrate.|
|21010||Gmail service isn't turned on for the user. Turn POP and IMAP on and off for users in Google Workspace.|
|25002||Internal server error. Try exiting and restarting the migration.|
|26001||Verify the steps in Migrating from an EWS environment.|
|26003||Email with attachments larger than 25 MB (total message body exceeds 35,882,577 bytes) can't be migrated.|
|26007||Inconsistent folder listings from Exchange server. Try running the migration while the server is not in use. If the issue persists, do an IMAP migration using the steps in IMAP server.|
|27004||There is an invalid entry in your mapping of calendar event attendees. Fix the entry and restart the migration. For details, go to Use CSV files with the data migration service.|
|27005||The calendar that owns the event hasn't been migrated to Google Workspace. ContactGoogle Workspace support.|
|27006||The event might be corrupt or missing required details.|
|27007||The secondary calendar could not be created in Google Workspace.|
Events didn't migrate because the participant isn't an attendee or organizer of the event. To troubleshoot this issue:
For error codes not listed here, Contact Google Workspace support.
- Connection information for common IMAP-based webmail providers
- Troubleshoot the data migration service
- Data migration service error messages
- Data migration service FAQ
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.