When using G Suite Migration for Microsoft Outlook® (GSMMO), you may run into error codes. See the explanations and links below to help resolve your issues.
If you run into a number of issues migrating from Outlook, or are migrating a large number of users, consider using G Suite Migration for Microsoft Exchange as an alternative migration tool.
|Error Code / Error Message||Explanation||Relevant Links|
|Can't determine recipient email||Senders/recipients/address book entries are in a non-SMTP address format. The application can't read these, so this header information won't migrate for the message. Reformat the addresses so that they're in email@example.com format. An alternative is to do a server-side migration using G Suite Migration for Microsoft Exchange.|
|User has not agreed to the Gmail Terms of Service||The user hasn't agreed to the G Suite Terms of Service in the web interface. Make sure the user is able to sign in and use G Suite Mail without issue.|
|This problem typically occurs when the PST file exceeds the maximum size supported by Outlook.||Configure PST File Size in Outlook (Microsoft support site)|
|This issue can occur when the user conducting the migration has insufficient privileges to access the PST, or when the tool is unable to find or access the PST file. Note that GSMMO requires both read and write access to the PST.|
|0x80040109||Another process is accessing the PST file or Outlook profile at the same time as GSMMO. Ensure that no other MAPI applications are running at the time of the migration which might be accessing the profile, and that any anti-virus, back-up, or desktop search software is excluding the Outlook PST files from scans.|
|0x80070036||This issue can occur when the user conducting the migration has insufficient privileges to access the PST or the tool is unable to find what it's searching for. Make sure that GSMMO has both read and write access to the PST files.|
|0x80072ee2||The sync tool is experiencing temporary errors, please try the migration again with Migrate new data enabled. This error may also be due to network timeouts. Changing the registry keys in the next column may resolve this.||Migrating large messages can time out over a slow connection|
|0x8007065e||This issue can occur if the network timeout registry entries have been created using the wrong registry data type (for example REG_SZ instead of REG_DWORD). Use the Registry Editor (regedit), to make sure that all entries under HKEY_CURRENT_USER\Software\Google\Google Apps Migration\Other are of type REG_DWORD and not any other type.|