Google Workspace Migrate release notes

These release notes reflect improvements and new features in each version of Google Workspace Migrate. As we add enhancements and fixes to Google Workspace Migrate, we'll regularly update these release notes. 

For details about the current list of known issues, go to Google Workspace Migrate known issues.

Upgrade software to avoid conflicts with deprecated features

Important: To ensure you are not affected by deprecated features or security issues, upgrade to the latest version of Google Workspace Migrate. Go to Upgrade the software.

  • Deprecation of Contacts API–From version 2.4.2.0, Google Workspace Migrate uses the People API instead of the Contacts API. If you're using version 2.4.2.0 or later, you must turn on the People API. For details, go to Use Google Cloud to turn on APIs.
  • Sign-in deprecation–From version 2.4.0.0, Google Workspace Migrate uses Google Identity Services for authorization support instead of the Google Sign-In JavaScript Platform Library. Note the following points:
    • After March 31, 2023, you won't be able to sign into Google Workspace Migrate versions earlier than 2.4.0.0 and you must upgrade your version of Google Workspace Migrate to continue.
    • You won't be able to access the platform using less secure URLs. If you want to continue to use servername:port to access the platform, you must configure a port with a TLS certificate and add https://servername:port to the authorized URIs in Google Cloud.
  • Drive orphaned content—Google Workspace Migrate no longer creates orphaned Google Drive items on the target account  during a Google Workspace to Google Workspace migration. For details, go to Orphaned content.
  • Drive items in multiple locations—From October 15, 2021, all versions of Google Workspace Migrate no longer add Drive files and folders to multiple locations during a migration. If you use a version earlier than 2.2.0.0, you will get unresolvable failures if Google Workspace Migrate attempts to add files and folders to multiple locations in Drive.

Expand section  |  Collapse all & go to top

Release notes for 2.4.14.0

May 8, 2024

What's fixed
  • Fixed an issue where Google Workspace Migrate did not delete the temporary AppBridgeStagedFileFileID files that it created on the source account when migrating files from a source Google Drive account to a target Drive account.

Release notes for 2.4.12.0

March 4, 2024

What's new
  • Upgraded MySQL & CouchDB software to the latest versions:
    • MySQL–Version 8.0.36
    • CouchDB–Version 3.2.3

    For details on how to upgrade the databases, go to Upgrade the software.

  • Added support for Microsoft Exchange 2019 connections.

    For details, go to Add or edit an Exchange connection.

Release notes for 2.4.10.0

January 10, 2024

What's fixed
  • Fixed an issue where Sharepoint list item attachments in Japanese didn't migrate.
  • Fixed an issue where an Exchange email migration fails if the original email is deleted.

Release notes for 2.4.8.0

September 12, 2023

What's new
  • Optimized MySQLQuery to view and download transaction logs.
What's fixed
  • Fixed an issue where a contact migration failed for contacts that have multiple organizations.

Release notes for 2.4.6.0

August 3, 2023

What's new
  • Upgraded MySQL to version 8.0.33.
  • Upgraded CouchDB to version 3.3.2.
  • You now see the name of the associated bridge when deleting an identity mapping.
What's fixed
  • Fixed a Gmail API quota issue that occurred during the migration or scan of messages.
  • Fixed the issue that occurred when migrating Google Tasks between 2 Google Workspace accounts. Some tasks displayed a 404 error and some other task migrations were skipped.

Release notes for 2.4.4.0

July 4, 2023

What's new
  • Upgraded MySQL and CouchDB to the latest versions.
What's fixed
  • Fixed an issue where some transaction error codes didn't appear in the migration summary.
  • Fixed an issue where large transactions logs were failing to download.
  • Fixed an issue where a Google Workspace to Google Workspace migration failed to correctly migrate contacts.
  • Fixed an issue where Google Workspace Migrate didn't migrate more than 100 memberships to a shared drive.

Release notes for 2.4.2.0

February 27, 2023

What's fixed
  • Fixed an issue where RunBridgePartition actions weren't visible in the actions list for platform users if they didn't initiate the action themselves.
  • Fixed the MySQL data directory issue.
  • Fixed the issue where execution logs were not displayed after the page is reloaded.

Release notes for 2.4.0.0

January 4, 2023

What's new
  • Upgraded from the Google Sign-In JavaScript Platform Library to the more secure and enriched Google Identity Services. After March 31, 2023, you won't be able to sign into Google Workspace Migrate versions earlier than 2.4.0.0 and you must upgrade your version of Google Workspace Migrate to continue. For details, go to Upgrade the software.
  • Upgraded MySQL & CouchDB software to the latest versions:
    • MySQL–Version 8.0.30
    • CouchDB–Version 3.2.2

    For details on how to upgrade the databases, go to Upgrade the software.

  • You now can't delete a mapping if you're running a bridge that is using the same mapping.

Release notes for 2.3.10.0

September 20, 2022

What's fixed
  • Fixed an issue where validations keep running and don't complete when the system time is ahead of UTC.

Release notes for 2.3.8.0

August 29, 2022

What's new
  • Upgraded MySQL to version 8.0.29.
What's fixed
  • Fixed an issue where Google Workspace Migrate didn't send email notification to users outside the organization who have assigned permissions for Drive data.

Release notes for 2.3.6.0

June 22, 2022

What's fixed
  • Fixed calendar permission migration.

Release notes for 2.3.4.0

May 11, 2022

What's new
  • Google Workspace Migrate database installers skip install-time settings when upgrading.
What's fixed
  • Fixed issue with downloading bridge reports.
  • Google Workspace Migrate can now run with Federal Information Processing Standards (FIPS) mode enabled.

Release notes for 2.3.2.0

March 31, 2022

What's new
  • Added system requirement checks to installers.
  • Updated the CouchDB installer with Microsoft .NET Framework 3.5.
  • Upgraded the MySQL and CouchDB versions.
What's fixed
  • Fixed issue where permission roles were not mapped correctly when migrating from Box, SharePoint, or a file share to shared drive subfolder.
  • Fixed an issue where a scan didn't fail if the associated scoped view was invalid.
  • Updated error message to clarify that trailing commas should be removed in the uploaded CSV file.
  • Fixed an issue where some email messages used the Exchange folder ID as a Google label ID and caused the migration to fail.

Release notes for 2.3.0.0

February 14, 2022

What's new
  • Google Workspace Migrate is now in General Availability (GA). Learn more
  • New icon for Google Workspace Migrate.
  • Users with the Manage Google Workspace Migrate Deployments admin role can view and manage all actions across the platform.
  • Users with the Access Google Workspace Migrate Deployments admin role can view and manage actions for all projects that they belong to.

Release notes for 2.2.10 & earlier

Earlier version release notes (English & Japanese only)

Expand section  |  Collapse all & go to top

Release notes for 2.2.10.0

January 31, 2022

What's new
  • During a Google Workspace to Google Workspace migration, Google Workspace Migrate no longer creates orphaned Google Drive items on the target account. From March 30, 2022, this change will apply to all versions of Google Workspace Migrate. For details, go to Orphaned content.
  • Added partition name to the Execution log UI.
  • Add new error messages to indicate the reason when a SharePoint migration fails.
What's fixed
  • Fix a bug that caused some Exchange mail messages to not migrate because of an error with their parent folder.
  • Fixed an issue where reminders for a calendar event were set to default when the source event didn't have any reminders. Now, calendar event reminders match the source event. 

Release notes for 2.2.8.0

December 6, 2021

What's new
  • Added the ability to filter Exchange email and archived messages based on date sent or received.
What's fixed
  • Fixed an issue where a scan reported incorrect results if the crawl rule was set to User Drive discovery.
  • Fixed an issue where the encryption setup was skipped if the database details were entered using the service management app, prior to setting up the platform.
  • Added a clearer warning when, during a remigration, a file is moved to a new folder on the target domain but its content is not altered. The warning is also shown when the file can't be updated because the file on the destination account is newer. The warning indicates that the content can’t be updated and additional information is provided if the item was moved by Google Workspace Migrate. You can use the drive audit log and search by item ID to investigate further. You can also get information on the item's source and destination location.
  • Fixed an issue where the hierarchy of mixed ownership items on source My Drive might be broken on the target domain. The issue is seen if you map orphaned content to a folder on the target My Drive.
  • Fixed an issue where newly-added items might fail to migrate in a delta migration. The issue is seen when you map orphaned content to a folder. Then, an item is added to a source account folder that has mixed ownership on the source My Drive. The folder is migrated and appears under its parent on the target domain and, subsequently, a delta migration is run.
  • Fixed a logging issue where Google Workspace Migrate outputs unnecessary "Object reference not set to an instance of an object" as fatal errors when the connection is shut down.
  • Fixed an issue where email messages sent with high importance were starred instead of setting the importance marker.
  • Fixed an issue where the Google Workspace depth report showed the folder name instead of the folder ID in the ID column.
  • Fixed an issue where bridge partitions occasionally froze when migrating SharePoint files.

Release notes for 2.2.6.0

September 23, 2021

What's new
  • Due date migration for Exchange Tasks is now optional and can be enabled in the settings template (disabled by default). If the admin enables task due date migration, they must also select the appropriate timezone in the settings template.
What's fixed
  • Fixed an issue where a scan of Box data occasionally failed with a timeout error. 
  • Fixed an Exchange Online setup issue that occurred when creating a new connection. Now, if the Exchange admin isn't allowed to impersonate themselves, you see an impersonation error message in the UI.
  • Fixed an issue where, if you clicked Cancel in response to Retry failures, the bridge no longer responded to clicks on any action buttons.
  • Fixed an issue where, in SharePoint migrations, partitions were occasionally marked as cancelled during the source connection initialization.
  • Fixed an issue where folders that contain ISO control characters or the caret symbol (^), multiple sequential spaces, or a space at the beginning or end of the folder name don't directly match label names on the target account. Learn more
  • Fixed an issue where UI components were not sorted into alphabetical order by default.
  • Fixed an issue that enables TLS versions 1.1 and 1.2 connections to work with MySQL.

Release notes for 2.2.4.0

August 26, 2021

What's new
  • Added support for a user list when configuring an Exchange Online (Office 365) connection. This matches similar functionality for Exchange Server connections. For details, go to Add or edit an Exchange connection.
What's fixed
  • Fixed an issue where the latest revision of an updated file wasn't pinned following a delta migration. Now, the latest version is also pinned.
  • Fixed an issue where a node reports high CPU utilization after cancelling a scan or bridge.
  • Fixed an issue where Google Workspace Migrate created multi-parented data on the target account.

Release notes for 2.2.2.0

July 29, 2021

What's fixed
  • Fixed an issue where a duplicate shared drive could be created when using the sub path feature if the migrating user already had access to more than 1000 shared drives.
  • Fixed an issue where a migrated calendar that was shared with users failed to show under My Calendars for the users.
  • Fixed an issue where a scoped view or mapping would fail to validate if it contained nested organizational units.

Release notes for 2.2.0.0

July 15, 2021

What's new

Google Workspace Migrate no longer adds Google Drive files and folders to multiple locations during a migration. It now enforces one parent folder for each Drive item.

During a migration to My Drive from Box, file shares, Google Drive, or SharePoint:

  • If a source item is multi-parented—The item has only one parent on the target account (the last one migrated) following a migration.
  • If an item is moved on the source or target account and then remigrated—The item is moved to its latest correct location on the target account during a remigration.
  • If an item is remigrated with a new target location due to a mapping change—The item is moved to its latest correct location on the target account during a remigration.

Release notes for 2.1.60.0

July 1, 2021

What's new
  • Box settings templates now have a Pin revisions option when migrating to My Drive or shared drives. Learn more
  • The Include list permissions option in the SharePoint to My Drive settings template is now turned off by default. 
What's fixed
  • Fixed a bug where, in some cases, a file migration failed when both its source location and content were changed since the previous bridge.
  • Fixed a known issue where task details weren't migrated from Exchange 2010.

Release notes for 2.1.58.0

June 3, 2021

What's new
  • When migrating from SharePoint, the Migrate SharePoint webs to folders setting is now turned on by default.
What's fixed
  • Fixed an issue that caused email messages to fail to migrate when migrating from Exchange to Gmail and the message is in an Exchange folder that must be modified in order to be migrated to Gmail. This issue is likely present when email messages fail to migrate with error 60008 and one or more folders successfully migrate with a different source and target name.
  • Added missing "Operation" column in execution logs export.
  • Fixed an issue that prevented email attachments with special characters in their names from migrating to Drive.
  • Fixed an issue when mapping at the service level (using the GService header in the mapping to map the Calendar, Contacts, Gmail, or Drive service) for Google to Google migrations. All transactions would fail with error code 60008 unless Map content only was turned on.

Release notes for 2.1.56.0

May 7, 2021

What's fixed
  • Fixed an issue that occurred when migrating an item with more than 200 pinned revisions to Drive. Previously, revisions after the 200th would be pinned inconsistently. Now, the earliest pinned revision is unpinned and the new revision is pinned correctly.
  • Fixed an issue that, in rare cases, caused recurring Google Calendar event instances to fail to migrate with a 403 error when migrating from Google Workspace to Google Workspace.
  • Fixed a known issue where a bridge partition can incorrectly show in the logs as Canceled instead of Done.

Release notes for 2.1.54.3

April 22, 2021

What's new
  • Added error reporting for Gmail label conflict. For details, to go error 409.
What's fixed
  • When migrating from SharePoint with the Include SharePoint folder permissions setting unchecked, folder permissions are now excluded from the crawl. Previously, they were included in the crawl but marked as Skipped in the transaction log.
  • Fixed error handling when an email message doesn't migrate because a dependent label failed to migrate.

Release notes for 2.1.52.1

March 24, 2021

What's new
  • Exchange 2010 contact notes are now migrated.
What's fixed
  • Fixed an issue where hyperlinks in Exchange calendar descriptions weren't migrated.

Release notes for 2.1.50.1

February 17, 2021

What's new
  • When migrating from Box to Google Drive, only objects owned by a user are migrated when migrating the user. Any object shared with a user is migrated under the object’s owner.
  • The Box collaboration set field has been removed from the Box object totals report. 
What's fixed
  • Fixed an issue that was causing the Retry failures action to fail without attempting to migrate data.

Release notes for 2.1.50.0

February 11, 2021

What's new
  • The Exclude users outside range option has been removed for Box, Exchange, and Google Workspace scans. If you want to scan specific users, we recommend that you use a scoped view instead.
What's fixed
  • Google Workspace Migrate now retries 429 responses during migrations to Google Groups.

Release notes for 2.1.48.0

January 14, 2021

What's new
  • When viewing the bridge summary, the warning count is now broken down into transaction and execution warnings. To view the breakdown, click Warnings. Note that the breakdown for warnings is only accurate for bridge executions that have been run on this version or later.
What's fixed
  • The default signature for the primary Gmail account is now migrated for Google Workspace to Google Workspace migrations.
  • Fixed an issue where a file share connection validated in some cases, despite being invalid.
  • Fixed an issue where transaction logs failed to download when filtering by error code.
  • Fixed an issue where some Exchange messages failed to migrate to Google Groups.
  • Fixed an issue where the Accelerate old messages option for mail migrations degraded performance by making unnecessary requests.
  • Fixed an issue where altered guest permissions on the target domain could cause calendar event migration failures.
  • Fixed an issue where comments were not updated with delta migrations for Google Drive native file types (for example, Docs, Sheets, and Slides). Now, if the source object has been updated more recently than the target, the target object is replaced entirely.
  • Fixed an issue during delta migrations when migrating file revisions to a shared drive. If the revision author was granted inherited read access (but not write access) on the target object, the revision transaction failed.

Release notes for 2.1.46.0

December 3, 2020

What's new
  • G Suite Migrate is now Google Workspace Migrate.
  • You can now view information on failures in the bridge summary by clicking Failures, instead of the dropdown arrow.
  • Added a warning dialog to clarify that previous scan results will be deleted when rerunning a scan.
What's fixed
  • Fixed an issue where using a subpath in the migration mapping sometimes resulted in Drive permissions on the target domain being removed. 
  • Fixed an issue where migrating to Google Groups generated a large number of temp files without deleting them.
  • Fixed an issue when migrating to Google Groups where the first post in a group conversation migrated correctly but reported a transaction failure.

Release notes for 2.1.44.1

November 5, 2020

What's new
  • Tasks migrated from Google now maintain their subtask structure and order.
  • Updated the bundled CouchDB installer from version 2.2.0 to 2.3.1.

    Note: If you're already using G Suite Migrate, you don’t need to upgrade CouchDB.

  • Changed the default from enabled to disabled for the following SharePoint settings:
    • Migrate webs to folders
    • Migrate lists to sheets
    • Migrate document metadata to sheets
  • The bridge settings report (included when you download logs, such as the transaction or execution logs) now includes the platform version number.
  • Removed the option to filter out specific versions when migrating from Box or Google Drive. The option frequently resulted in unexpected errors.
  • Added an option to filter out specific files when migrating from Box, to match the functionality for other data sources.
  • When viewing the bridge summary, the failure count is now broken down into execution and transaction failures. To see the breakdown, next to the failure count, click the Down arrow . Note that the breakdown is only accurate for bridge executions that have been run on this version or later. Earlier bridge executions categorize all failures as transaction failures.
  • Removed the following from the Shared drive candidate reports:
    • Fields relating to unique permissions and additional permissions.
    • The % allowed with additional permissions setting.
  • Removed the Migrate x with additional permissions settings options from shared drive settings templates. 
What's fixed
  • Fixed an issue with file share migrations where certain files were migrated to Drive with no data, but marked as completed. You can now scan your target Drive environment and use the new Google Drive empty file report to identify potentially-affected data.
  • Fixed an issue where scans could crash when using a scoped view with a large number of entries.
  • Fixed an issue where scans weren't logging their error codes correctly.

Release notes for 2.1.42.0

October 8, 2020

What's new
  • Added support for migrating subfolder permissions to shared drives. The Migrate shared drive permissions setting has been renamed Migrate folder permissions and now controls all folder permissions instead of only those migrated to the shared drive root.
  • Renamed Migrate additional file permissions setting in shared drive-based settings templates to Migrate file permissions to more accurately reflect its purpose. The setting is now enabled by default for Box and Google.
  • Updated the default for the Max pinned revisions setting for Box and SharePoint migrations from 200 to 20.
  • When editing a connection, the associated credentials are now revalidated.
What's fixed
  • Fixed an issue when migrating to shared drives where restricted permission transactions were marked as completed, even though the restriction wasn't migrated (because shared drives don't support restricted permissions). The transactions are now marked with a warning and contain detail about the restrictions that couldn't be migrated.
  • Fixed an issue where the Max pinned revisions setting didn't pin any versions when copying data from Box.
  • Fixed an issue with the Max pinned revisions setting when migrating from SharePoint where G Suite Migrate attempted to pin more than the configured number of revisions. Additionally, the current revision is no longer pinned.
  • Fixed an issue with the Pin major versions only setting when copying from SharePoint. G Suite Migrate attempted to pin too many versions if old versions had been discarded by SharePoint's configured version limit.
  • Fixed an issue where the Sub Path value in a mapping for a Box migration was ignored.
  • Removed the option to filter out specific versions when copying from SharePoint as it almost always resulted in unexpected errors.
  • The SharePoint connection now correctly flags issues when sub-site URLs are listed in site lists. Previously, the connection failed with unhelpful errors.

Release notes for 2.1.40.0

September 22, 2020

What's new
  • G Suite to G Suite migrations are now supported. Go to Migrate data from G Suite.
  • Exchange mail items can now be filtered by item class.
What's fixed
  • Fixed an issue where some transaction details don't appear in the transaction log after bridge completion.
  • Fixed an issue where SharePoint external sharing permissions and unmapped user permissions were not being migrated.
  • Fixed an error that could occur when determining the well-known name of mail folders in Exchange 2010.
  • Removed the erroneous "Child Root" field from the file share scan depth report.
  • Fixed an occasional issue with Box connections where collaborations failed to scan with a service_unavailable error.
  • Fixed an issue where Exchange migrations would generate large numbers of temp files without deleting them.
  • If a transaction fails to map its target identity after a successful write, the transaction is now marked as a failure. Doing so better exposes the issue for troubleshooting and ensures that future deltas don't fail dependent transactions for unknown reasons.
  • Exchange scans no longer show an error for users with the In-Place Archives feature disabled.

Release notes for 2.1.36.0

July 16, 2020

What's fixed
  • Fixed an issue where the bridge page would fail to load if a mapping that is used by a bridge is deleted.
  • Fixed an issue where content filters could misidentify some permissions as additions when migrating from file shares to shared drives.

Release notes for 2.1.34.0

June 18, 2020

What's new
  • Better security on temporary files stored on nodes during migration.
What's fixed
  • Fixed an issue where failures during bridge partitioning could result in the bridge failing entirely instead of individual failures in the execution log.
  • Fixed the error message on the login page that displayed if the product was misconfigured.
  • Added scan-related warnings to bridge and scan execution logs. You can see a per-scan warning count when you click Scans.
  • Clarified revision pinning setting names for SharePoint and Box settings templates.
  • Updated the platform and node installers to populate .NET TLS registry keys in accordance with Microsoft's best practices.

Release notes for 2.1.32.1

May 20, 2020

What's new
  • Added a new Exchange Online connection type for connecting to Exchange Online with OAuth, and relabeled the existing Exchange connection type to Exchange Server. Use the appropriate connection type for any new Exchange connections. See Add or edit an Exchange connection.
    Note: Existing connections to Exchange Online with the Exchange Server connection type will continue to work until Microsoft disables basic authentication for Exchange Online, currently scheduled for October 2020.
What's fixed
  • Fixed error handling if you run a bridge without first setting a mapping.
  • Fixed an issue where a bridge would run even when no mappings were defined.
  • Exchange archives messages and folders now appear in the Exchange scan reports.
  • If you have previously set up an Exchange Server connection that is pointed at Exchange Online, you can edit that connection without having to change the configured Exchange server version.
  • Fixed an issue for Box connections where shared files that aren't inside a shared folder did not migrate correctly. 

Release notes for 2.1.30.0

April 9, 2020

What's fixed
Removed the following settings from the Exchange settings template:
  • Include auto forwarding settings
  • Include forwarding settings
  • Include IMAP settings
  • Include POP settings

Release notes for 2.1.28.0

March 12, 2020

What's new
  • Error codes shown throughout the product now link directly to the GSM error code documentation.
  • Improved the loading of calendar resources to significantly reduce the load on the Google calendar resource API in the average migration case.
What's fixed
  • Update filter setting names in settings templates to use "Exclude" instead of "Filter" to more clearly reflect behavior.
  • Updated settings templates to consistently use "migrate" rather than "convert" or "copy" for settings that control whether a particular type of data is migrated.
  • Updated settings template names to more clearly reflect their purpose. For file-based source systems, the two options are now "Migrate to My Drives" and "Migrate to shared drives".
  • Fixed an issue where troubleshooting details didn't load correctly the first time they were accessed from the transaction log or tree view.
  • Fixed an issue where Exchange mailboxes without signatures caused erroneous failures in the execution log.
  • Fixed an issue where reports failed to download if bridge or scan names contained periods or special characters.
  • Fixed an issue where some Box mappings failed to validate. For any mapping where the specified BoxUser didn't match the owner of the listed BoxFolder, validation failed due to an unresolved bug in the Box API.

Release notes for 2.1.26.0

February 20, 2020

What's new
  • Improved error handling when adding nodes from a CSV file.
  • Removed the ability to migrate Exchange Delegation and Send As settings.
What's fixed
  • Fixed migration support for Google calendar resources created after January 21, 2020. For details see Calendar resources–Created after January 21, 2020.
  • Fixed an issue where nodes sometimes show as "Ready" instead of "Busy" even when they're doing work.
  • Fixed an issue where, although nodes imported correctly from a CSV file, the status bar would spin forever and failures weren't communicated. Now, results are correctly reported.
  • Improved error messaging for mappings and scoped views where there is content that has been moved from its original location.

Release notes for 2.1.24.0

January 16, 2020

What's new
  • Added the ability to filter out common system attachments (*.ics, *.vcf) during calendar migrations.
  • Added Google Groups to the tree view for Google connections.
  • Calendar sharing changes made during a migration will no longer trigger notifications.
  • Removed obsolete options from the management app's host settings dialog.
What's fixed
  • Fixed an issue where permissions for Box files in a user's root All Files folder weren't migrated.
  • Fixed an issue where the "last modified by" user was incorrect on files with one revision migrated to shared drives.
  • Fixed an issue that could cause Calendar event migrations with calendar resources on the event to slow or halt over time.
  • Fixed an issue that could cause random failures when interacting with empty Google Groups or Google domains without groups or calendar resources.
  • Fixed an issue that could cause random project creation failures if a domain has admin roles without users assigned to them.

Release notes for 2.1.22.0

December 5, 2019

What's new
  • If you create a file share connection to a specific share or folder (instead of to a server) you can map the root of that connection. Previously, you could only map subfolders.
  • Downloaded reports from scans now include the scan name and time information in their filenames.
  • Exchange 2010 SP3 is now supported for Exchange connections.
  • All text-based filters (for example, the source and target filters in the transaction logs view) are now case insensitive.
  • Made minor performance improvements for Exchange 2013 and later.
  • Row actions in the transaction log table are now a dropdown menu rather than icons.
  • You can now view all transaction logs within a partition from the transaction log table. To do so, point to a row in the transaction log, then click and thenPartition transaction log.
  • You can now view all execution logs within a partition from the execution log table. To do so, point to a row in the execution log, then click and thenPartition transaction log. (Note that this option is only available for execution log entries that are associated with a partition.)
What's fixed
  • Fixed naming inconsistencies in state filtering for bridges and scans.
  • Fixed an issue where the migration summary table wasn't displaying the correct table headers according to the current grouping.
  • Fixed an issue where migration summary filters would not take effect.
  • Fixed an issue where failed transactions weren't displaying their error codes.
  • Fixed an issue that was blocking shared disks from appearing on connections to file share servers.
  • Fixed an issue where events in Exchange without ICalUIDs (such as those imported using CSV files through Outlook) couldn't be migrated.
  • Improved presentation of long error messages for mapping validation.
  • Improved error logging during login.
  • Improved calendar migration performance by skipping unnecessary delete requests that would occur when incrementally migrating a recurring event.
  • Improved page load performance on the partition logs view.
  • Removed unhelpful errors that occurred when reading Exchange calendar sharing rights for users outside an organization. The sharing rights still won't migrate and the errors that they cause have been fixed.
  • Fixed an issue where offline nodes could get stuck in the "Unknown" state.
  • Fixed a bug where the scan partition log wouldn’t load when the page was refreshed.

Release notes for 2.1.20.1

November 21, 2019

What's fixed

Supplementary Unicode characters in object identity fields, such as SharePoint folder names, will no longer cause silent errors or missing transactions.

Release notes for 2.1.20.0

November 12, 2019

What's new
  • Timestamps in log views (for example, transaction log, partition log) now include the time zone.
  • The mappings table now shows the source and target connection for each mapping.
  • Connection and connection type dropdown lists are now sorted alphabetically.
  • The scans page can now be filtered by scan state.
  • Exchange mail folders can now be filtered based on path, name, or well-known folder name. This can be configured in the settings template.
  • Super admins with Calendar API access disabled are now skipped during migrations when the Use all super admins to write calendar resource events setting is enabled. Previously, this would cause migration failures with error code 401.
What's fixed
  • Fixed an issue where content failed to migrate inside SharePoint or OneDrive folders that have URL-encoded characters (for example, "%20") in their name.
  • Removed G Suite as a possible source connection type for settings templates.
  • Fixed an issue where the user was incorrectly routed to the host settings page when prompted to set the callback address from the nodes page. The user is now routed to the callback address setting page.
  • Fixed an issue where the UI displayed an error message when the user attempted to switch to the current project.
  • Fixed an issue where certain boolean settings in the default settings templates would be read incorrectly during a migration.
  • Fixed an issue in long-running bridges where completed partitions could be re-queued, causing additional unnecessary work that degraded performance.

Release notes for 2.1.18.1

October 30, 2019

What's new
  • You can now enable Exchange In-Place Archive copying in the Exchange settings template. 

Release notes for 2.1.18.0

October 15, 2019

What's new
  • A new connector to handle SharePoint Online (Office 365) migrations separately from SharePoint 2013 migrations. The new connector replaces user-based authentication with app-based authentication for SharePoint Online, as recommended by Microsoft. As a result, projects with existing SharePoint Online connections must be updated with new credentials. When you open a project with affected connections, you'll be prompted to complete this update. For details, see Update SharePoint Online connection credentials.
  • Super admin accounts are now used to write calendar events to the target domain to address quota issues for large migrations. The new behavior can be controlled with the Use all super admins to write resource calendar events setting in the Exchange settings template. For details, see Watchpoints and best practices for Exchange.
  • You can now export and download partition logs for bridges and scans.
  • Application error log timestamps now include the time zone.
  • You can now see the current Google settings (client ID, service account name, admin user email) in the Google Settings dialog in the management app. Previously you could only enter new values.
  • If you attempt to migrate the same source content to more than one shared drive within a project, the resulting error is now a failure instead of a warning. Error code 1081344 is displayed with a detailed message describing the cause.
What's fixed
  • Fixed an issue where primary Exchange calendars are migrated to secondary G Suite calendars when mapping source user to target user.
  • Fixed an issue where sharding user list settings were missing from the user interface.
  • Fixed an issue where Other Mappings failed to load when refreshing the page.
  • Fixed an issue where the user interface would stop working if it was left inactive for a long time.
  • Fixed an issue where some scan reports might be missing rows in large, high performance deployments.
  • Fixed an issue where source and target values (which you can click to inspect element details) in bridge transaction logs and mappings didn't render as links and weren't reachable by screen readers.
  • Fixed misalignment between column headings and data rows in mappings and settings templates.

Release notes for 2.1.16.0

September 12, 2019

What's new
  • Improved performance of filtering of transaction logs by state.
What's fixed
  • Fixed a case where migrations using the SOAP version compatibility flag could experience a higher than expected impact from throttling errors.
  • Fixed an issue that could cause data duplication if you canceled and then re-ran a bridge.
  • Fixed an issue where extremely long-running file migrations provoked errors related to "Commit service did not respond to the request for a transaction to be committed" or "The requested connection is unavailable". Those messages might still occur in cancelled bridges or action failure and recovery.
  • Fixed missing/inconsistent refresh button in tree views.

Release notes for 2.1.14.1

August 29, 2019

What's fixed
  • Fixed a SharePoint issue where large libraries could not be migrated due to a "list view threshold" error.
  • Fixed an issue where SharePoint retries and request backoff longer than 2 minutes caused persistent degraded connector performance.

Release notes for 2.1.14.0

August 15, 2019

What's new
  • A status page is displayed for troubleshooting nodes and to confirm they are running.
What's fixed
  • Fixed an issue where a new user signing in was required to create a new project instead of being able to select an existing project.
  • Fixed an issue where a new user signing in was taken to a setup screen even when the product was previously configured by another admin.
  • Fixed an issue where a user would be signed out when switching projects.
  • Fixed a "user not found" error that occurred when reading the versions of a document in SharePoint where the author had been completely removed from the site collection.
  • Fixed an issue with the mapping importer for Google Calendar.
  • Fixed an issue where reports were sometimes missing data.

Release notes for 2.1.12.0

July 18, 2019

What's new
  • Added support for a new resource email format.
  • Added the ability to map source calendars to individual target calendars.
  • Modified throttling logic to include hints from server side messages, such as provided retry-after headers.
  • Included documentation links in the onboarding flow.
  • Clarified node status in a new status page at http://nodehost:5131.
  • Improved size-related report column headers.
  • Installing updates no longer requires reentering port settings.
  • Nodes will appear in the Ready state immediately after association, not in the Unknown state.
What's fixed
  • Errors no longer occur for documents in SharePoint libraries when you migrate with versioning enabled, and you pin specific version numbers.
  • Fixed an issue that caused "Property not initialized" exceptions from SharePoint when certain capacity related errors occurred.
  • Fixed an issue that caused slow mass action canceling.
  • Logs with no error codes display a dash.
  • Removed Sites objects for Google Service Account connection.
  • Eliminated "CouchDB inserts are delayed" errors in the application error log.
  • Fixed an issue so notes are reported correctly in the Box connections depth report.
  • Eliminated 0 values in Error columns.

Release notes for 2.1.10.0

June 20, 2019

What's new

Added Calendar resources to the tree. Calendar resources can be imported into mappings using the GCalendarResource header when migrating calendar content. When using explicit resource calendar migration from Exchange, other users should be migrated with the Add events to resource calendars setting disabled in the settings template. Learn more about Exchange settings templates

What's fixed
  • The names of partitions in the logs now reflect the information contained in that partition in a more useful way.
  • Onboarding flow updated to provide more context.
  • Fixed an issue with the resource mapping feature in Exchange calendar migrations. The resource booking would get an unexpected 1028 error for out-of-migration-scope content.
  • Updated shared drive naming.

Release notes for 2.1.8.2

June 6, 2019

What's fixed

Fixed an issue that occurred when using the resource mapping feature with Exchange calendar migrations. The resource booking received unexpected 1028 errors for out-of-migration-scope content.

Release notes for 2.1.8.1

June 3, 2019

What's new
  • Added support for connections from Box.  Learn more about how to migrate data from Box
  • By default, the transaction log now only includes detailed troubleshooting information for errors and warnings. Previously, all transaction results generated detailed processing logs. This change is intended to improve the stability of the platform for extremely large migrations and avoid filling the CouchDB disk. The change to the default behavior only applies to new installations. Existing installations will continue with detailed logging, even after an upgrade. For information on how to change the setting, see Troubleshoot CouchDB.
  • Location mappings have been removed from the Other Mappings section. Mappings replace the functionality of location mappings. 
  • When you create a new Microsoft SharePoint connection (for all SharePoint versions, except SharePoint 2010), you must select SharePoint 2013 client or SharePoint Online from the dropdown menu.
What's fixed
  • Fixed an issue that caused the element counts in scan summaries to be incorrect.
  • A mapping validation no longer incorrectly validates service locations for users that are suspended or do not exist.
  • A new confirmation step has been added when you make a selection from the list of projects, if you aren't already a member of the selected project.
  • Search consistently displays on searchable connection types (Exchange and G Suite) when you click Mappings and then Entries.
  • Target subpath example text has been improved to better reflect the required format.
  • Improvements to filter functionality for execution logs.
  • Added adaptive throttling and associated tuning settings to the Exchange connector.
  • Improved the speed of SharePoint List and Library copying to Google Drive.

Release notes for 2.1.4.0

April 25, 2019

What's new
  • Enabled New bridge, New scan, and New connection buttons for empty projects.
  • Project can be switched from the list view of projects.
  • You can edit the sublocation target from the UI.
  • You can navigate to scoped view entries when creating a new scoped view in Scans.
  • You can now view settings from the bridge when a bridge is running.
  • Identities are now searchable when creating mappings in tree view.
  • Bridges and scans are sorted alphabetically by default.
  • Character limit for object names has been increased from 30 to 250 characters.
What's fixed
  • Fixed an issue where an expired MySQL password could cause the application to hang on startup.
  • Fixed an issue where imported SharePoint mapping entries fail due to a case-sensitive URL comparison.
  • Fixed an issue where mappings that use the Map Children Only and Target Sub Path settings do not work correctly for SharePoint to Drive migrations.
  • Fixed a specific issue where Drive system updates were racing migration updates causing the final modified time to be set incorrectly.

Release notes for 2.1.2.1

April 12, 2019

What's fixed
  • Fixed an issue that can cause SharePoint versions to be copied out of order.
  • Fixed an issue where permissions copied from SharePoint are not applied to shared drives.

Release notes for 2.1.2.0

March 28, 2019

What's new
  • Added support for fileOrganizer role in shared drives.
  • Enabled Exchange 2016 Connector.
  • Added ability to send the port number to the platform and node installers using a command line flag.
What's fixed
  • Updated the default MySQL configuration so that long host names no longer cause a crash.
  • Fix default role mappings from SharePoint to shared drives. All roles were previously mapped incorrectly to Organizer.

Release notes for 2.1.0.1

March 4, 2019

What's new
  • SharePoint lists and libraries can now be filtered by base template.
  • Revision pinning settings are now available when migrating from SharePoint to shared drives.
  • Execution and transaction logs are now downloadable from the migration summary.
  • Execution logs are now downloadable from the execution log view.
  • Users can clear couch data from stand-alone page to be linked from documentation.
  • When using an installer, you are prompted to enter a port number, even during upgrades.
  • CouchDB requires admin credentials for any access.
What's fixed
  • Fixed a bug that caused crashed nodes to appear in the "Busy" state.
  • SharePoint list attachments with spaces in the filename now migrate correctly.
  • Fixed scan generation so it properly validates scoped views prior to running.
  • Bridges with failures now correctly create and run partitions to retry only the errors.
  • The retry failures action now works as expected to resolve transaction failures.
  • SharePoint bridge partition names now always include the URL of the source object being migrated.
  • Transactions still in the queue when a bridge partition completes are logged as failures, rather than warnings.
  • Fixed an issue where permissions waiting for inherited permissions would not be triggered and never validate.
  • Fixed an issue where the Exclude inherited permissions option wasn't applied.
  • Fixed an issue that caused the creation of duplicate partitions.

Collapse all & go to top


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.

Search
Clear search
Close search
Google apps
Main menu