Google Workspace Migrate known issues

Bridges are automatically deleted if a connection is deleted

If you delete a connection, all bridges using that connection are also deleted.

Connection page stalls

The connections page stalls and needs to be refreshed in order to display connections. If your connections page takes longer than 10 seconds to load, refresh the page. 

MySQL & CouchDB admin passwords change after database upgrade

If the database admin passwords change, Google Workspace Migrate can’t connect to the databases and it won't function.

Workaround: During the database upgrade, you will get a new password. When the upgrade is complete, update the Google Workspace Migrate database settings with the new password. For details, go to Configure database settings.

Migration is not currently available for Exchange Online for US government environments.

Some calendar settings don't migrate for Exchange 2019

You encounter the issue when migrating calendars from Exchange 2019. Settings that aren't migrated: 

• Decline and cancel my meetings during this period
• Allow forwarding

  If you turn off Allow forwarding in the source account, the corresponding setting in Google Calendar (Invite others) is not turned off after a migration.

Hyperlinked image doesn’t migrate correctly

You encounter the issue when an Exchange 2010 calendar event description contains a hyperlinked image. The link URL is migrated incorrectly.

Inline image in a calendar event description is migrated as a attachment

You encounter the issue when an Exchange Online or Exchange 2016 calendar event description contains an inline image. The image is migrated as an attachment and the description contains a string like [cid:0ce85575-4cf9-46d0-9c6c-c7c98b600b00].

Migrations show zero bytes in data migrated column

After migrating email data from an Exchange Online (Microsoft 365) user mailbox to a Google Workspace group, the partition logs show zero bytes in the data migrated column, even though data was migrated.

The Add inbox label to subfolders setting not working as expected

You encounter the issue when migrating email data from Exchange Online (Microsoft 365) when the Add inbox label to subfolders setting is turned on. After a migration, messages in subfolders have the Inbox label applied but not the name of the subfolder, as expected. 

Spam messages aren’t migrated

You encounter the issue following a migration from Exchange Online (Microsoft 365). Spam email messages are not migrated to the target domain.

Spam & trash messages aren’t labeled correctly

You encounter the issue when migrating from Exchange 2010. Spam and trash items aren’t labeled correctly in the target account. They are shown in All Mail but don't have the Spam or Trash label.

After an Outlook folder change, emails are duplicated on a delta migration

You encounter the issue if you migrate Exchange email and then a user renames a folder in Outlook. When you run a delta migration, email messages from the renamed folder are duplicated.

Email with an incorrect number of From headers are not migrated

Email messages that contain more or less than one From header fail to migrate to Gmail. This normally occurs if email messages are added directly to an inbox through automated processes or have been previously migrated from another system without following RFC 2822 requirements. If email acceleration is enabled, these messages are migrated but are missing From information in Gmail.

Email read state isn't migrated

You encounter the issue following a migration from Exchange 2010. The read or unread state of email messages isn't migrated. Messages appear as read in the target Gmail account.

Files not migrated in a shared drive to shared drive migration

You encounter this issue when you migrate files from a shared drive on the source account to a shared drive on the target account and use the Default settings template. Google Workspace Migrate creates the new shared drive but doesn't migrate any content.

Workaround: Use the Migrate My Drive to shared drives settings template. For details, go to Set up or select a settings template.

A user is not removed from a shared drive after a delta migration

You encounter the issue when a user is removed from a shared drive folder and a delta migration is run. The user is not removed from the shared drive folder, and you see a "no object found" warning.

Incorrect user shown in Drive's "Last modified" column and "Details" section

If you're copying files from any source to Drive, and the modifying user of a file doesn't have access to the file in Drive, the file modifier in Drive shows incorrectly. The admin who set up the Google connection displays as the file's modifier. If the user looks at the file's versions, the correct user appears as the modifier in the history. However, the values shown in Drive's Last modified column and Details section are incorrect.

Additional transactions shown when migrating with subpaths

If you're copying files from Google to Drive using the subpath feature, an additional transaction is recorded. The migration summary log shows a transaction for the destination account in addition to the source account.

Created date of Google Drive files is incorrect

You encounter the issue when you migrate Drive files (Google Docs, Sheets, Slides, Forms, Drawings, or Jamboard) in a Google Workspace to Google Workspace migration. The Created date metadata associated with the files on the target domain reflects the time and date of the migration, rather than the creation of the original file.

Duplicate files created when migrating from Drive

You encounter the issue when migrating files from a source Drive account to a target Drive account and manually stop the bridge during the migration. Google Workspace Migrate creates files called AppBridgeStagedFileFileID on the source account.

Workaround: In the source Drive account, locate and manually delete the AppBridge temp folder.

Entry in the mapping file doesn't validate

You encounter the issue when the email address of the Google Group contains uppercase letters, and you enter the address in the GGroup column of the comma-separated values (CSV) mapping file.

Workaround: In the mapping file, use lowercase for entries in the GGroup column.

Mapping validations don't complete

You encounter the issue if you're using Google Workspace Migrate versions 2.3.6.0 or 2.3.8.0 and the system time is ahead of Coordinated Universal Time (UTC). If you try to validate a mapping, the validation doesn't complete.

Workaround: Upgrade to version 2.3.10.0 or later. If you are using an older version, set the system time to a timezone behind UTC. For example, if the system time is UTC+3, change it to UTC-8.

Bridge generation fails if its mappings are deleted

It is possible to delete mappings that are used by bridges without getting a warning. This causes bridge generation to fail.

Workaround: Before you delete a mapping, check to see if the mapping is currently used by a bridge.

Final permissions on an object after a migration can be unpredictable

You encounter the issue if you use an identity mapping to map multiple source accounts to the same target account, and the source accounts have different access or sharing levels on a source-side object. The final permissions on the target object depend on the order the users are processed, which can be unpredictable.

For example, users Source1 and Source2 are both mapped to Target1 in an identity mapping. Google Workspace Migrate processes an object that is shared with Source1 but inaccessible to Source2. Whether the object is shared with Target1 after the migration depends on what order the permissions are processed. It can cause the bridge to have transactions waiting indefinitely to complete.

Platform services get stuck in "Starting" status

You encounter the issue when the platform is configured and the database information is not set up correctly. When you try to sign in to Google Workspace Migrate using a browser, you’re not able to sign in, and you don’t see an error message or any feedback.

Workaround: Use the management app to configure your database settings correctly.

Exchange public folder object totals scan report is blank

You encounter the issue following a scan. The Exchange public folder object totals report is blank.

Public folder depth scan report is blank

You encounter the issue following an Exchange scan. The Public folder depth report is blank.

Workaround: Run a scan without using a scoped view.

Settings templates can get lost when software is updated or reinstalled

This error leads to apparent regression. For example, after an update, file permissions aren’t migrated.

Workaround: You can't export or import settings templates. You have to manually reapply them following an update.

SharePoint 2010 connections fail to migrate certain files

Files with the following extensions are not migrated: .aspx, .asmx, .ascx, .exe, .htc, .jar, .master, .swf, .xap, and .xsf.

SharePoint location lists can cause errors

SharePoint location lists with URLs that end in forward slashes (/) can cause errors with mapping import validation.

Workaround: Ensure URLs in location lists do not end with a forward slash.

File metadata is not created when the "Map Content Only" flag is active

When the "Map Content Only" flag is active on a SharePoint to Drive mapping, the Google Sheet containing file metadata is not created. The transaction log shows failed GSheetRow entries for all files that were unable to write their metadata.

Deleted users show as unidentified in SharePoint 2010, 2013, and 2016

Users that have had their username (not display name) deleted are logged as unidentified following a migration. The issue affects all files in versioned document libraries that are created or modified by these users. 

After a migration, you can also see a transaction log message, "The users in the following fields could not be identified." Postmigration, the owner of the Drive folder is shown as the user. If the data is migrated to a shared drive, the user specified in the data's mapping appears in these fields. 

SharePoint lists renamed

Following a migration, SharePoint Online lists that have non-ASCII characters in their name are renamed as List, List1, List2, and so on.