Important notification concerning all Google Drive migrations

**Update - December 13th - Please read before continuing**

We have been made aware of an issue where 403 errors are causing the early failure of a migration instead of retrying. This is due to a change in the information included within the 403 error message which we previously used to determine whether to retry or not.

If you are experiencing this issue, we are redeploying a fix version of CloudM Migrate on Wednesday December 14th 2022 that will address this change.

In September 2020, Google changed the architecture of Google Drive so that a single file or folder could no longer be placed in multiple locations (known as the multi-parenting approach). 

CloudM had been given special dispensation, by Google, that allowed us to continue to migrate any multi-parented files and folders from one Google Drive to another. Without this dispensation, these items would have failed during the migration process. Google will be removing this special dispensation by mid December 2022.

In partnership with Google, we have agreed to completely remove the ability to add multi-parented items using their Drive API in CloudM Migrate by December 1st 2022. 

We will be releasing a new version of CloudM Migrate that will adhere to these new Drive API rules around multi-parenting. CloudM Migrate will automatically convert an attempt to multi-parent a File or Folder to a Shortcut (the method that Google currently uses), and this will stop these items from failing.

This version has been released on November 30th 2022 and is available for download from the Latest Release Notes and Download Links for CloudM Migrate page.

What does that mean for you? Anyone migrating from Google Workspace to Google Workspace should upgrade to the latest version of CloudM Migrate on November 30th 2022 and must upgrade prior to Google ending support for multi-parenting by mid December 2022. The upgrade will need to be completed on the primary server and all secondary servers by this date.

If you do not upgrade:

• Any Google Workspace to Google Workspace migration items queued or scheduled to start after November 30th 2022 will fail our licensing step and you will be prompted to upgrade to the latest version of CloudM Migrate.
• Any Google Workspace to Google Workspace migration items in progress and started before November 30th 2022 on older versions of CloudM Migrate will continue to work until Google removes multi-parenting support mid December 2022. At this point migrations will start to experience item failures. Upgrading to the latest version of CloudM Migrate will be mandatory at this point.