Release Notes

Find out what's new in the latest version of CloudM Migrate.

Please see the release notes and download links for the latest version of CloudM Migrate (v3.41.16.0 released on August 29th 2023 ) below. Release Notes (August 29th 2023)


  • Updated Migrate to match CloudM’s new branding


  • Resolved an issue for Migrate hosted M365 to M365 migrations where the migration could hang on the final closing step, and as such still show as processing in the UI


v3.41.16.0 Download Links 

CloudM Migrate x64

Any platform except GroupWise or Notes

SHA1 - 425f8e7205468b62a5aa7d7bda2876eb723ff741

MD5 - 5549915507859d219e2e0d33e3eb2590


CloudM Migrate x86

Required for GroupWise and Lotus Domino/Notes

SHA1 - 8eb7c46deeb71943860912520eb28d90fdac51d7

MD5 - 9f177ae3c0f9935170ef6abea61ac36c Release Notes (August 15th 2023)


  • Resolved an issue for M365 to Google migrations, where duplicate files and folders could be created.
    • This issue was only present if the "Use Cached Items Mapping" setting was disabled, or if the same items were migrated on multiple secondary servers.
  • Resolved an issue for M365 to M365 migrations of Teams chat messages, where exporting the chat items could result in Migrate getting stuck in a long running process. Release Notes (July 19th 2023)


  • (MS) Resolved an issue where the ‘Create Azure Ad Application’ would not complete.
  • (Google) Resolved an issue when exporting resources from Google.


3.41 Release Notes (July 19th 2023)

Enhancements Platform Links to article(s) in Knowledge Base

Added an option for additional reporting in the environment scan mail report for M365 sources. Selecting this option will include information on the total attachment size, mailbox type (shared or user) and archived mailbox folders.


Microsoft Environment Scan

Removed basic authentication as an option for M365, as this option is no longer supported by Microsoft



Modern Authentication for Microsoft 365

Improved how private channels are migrated to MS teams - these are created by Migrate automatically, removing the need for manual provision of the private channel.



Teams to Teams

Added a new advanced setting within config settings - email, allowing for email to be skipped in the migration (e.g. when specific emails are encrypted) when a specific header value matches the regex specified.


Google and Microsoft

Advanced Settings (Config Settings)

Added support for migration of Dropbox TeamSpaces.


Google and Microsoft

Dropbox Team Folders and Spaces

Changed how the creation of the Azure AD app is handled with CloudM Migrate. Upon creation of the app, Migrate will now direct you to your M365 Admin portal to approve the application creation.



Modern Authentication for Microsoft 365



  • (Google) Improved how CloudM Migrate handles very large Vault migrations to reduce memory usage.


  • (Google) Adjusted the retry logic within Migrate to better handle 403 errors from Google and retry these where appropriate.
  • (Google and MS) Resolved an issues where setting up Box as a source using JWT authentication would incorrectly fail connection tests.
  • (MS) Fixed a rare issue for Exchange source migrations where a missing notes folder within the users mailbox would cause the migration to fail.
  • (MS) Fixed an issue where migrations to Microsoft Exchange could result in task due dates being 1 day incorrect
  • (MS) Resolved an issue where, for migrations to M365, if a parent folder was deleted mid migration whilst items were being migrated to that folder, the statistics would not reflect the items that had successfully migrated before the parent folder was deleted
  • (MS) Implemented a change to how Migrate handles stalling M365 migrations so they error sooner
  • (Google) Fixed an issue where the migration readiness scan would incorrectly identify Shared Drives in Google as users
  • (Google) Migration readiness scan is no longer case sensitve, and as such will no longer highlight mismatches which only related to different cases
  • (Google) Resolved an issue with the "Remove Shared Drive Default Managers" feature where the default managers were not being removed correctly
  • (MS) Improved how Migrate handles invalid characters in migrations to M365 - invalid ASCII control characters will be removed from filenames
  • (Google) Resolved an issue where migrations from SharePoint to a Google shared drive could cause duplicate folders on re-runs
  • (MS) Improved handling of reserved folder names in Gmail to M365 migrations. "Tasks" and "Notes" folders created by users in Gmail are now correctly recognised as reserved for M365, and renamed in the destination to avoid failures
  • (MS) Resolved an issue where the "Public Folder Username" field in M365 source advanced settings was missing from the UI
  • (Google) Resolved an issue where migrations of tasks to Google destinations could result in task due dates being 1 day incorrect
  • (MS) Made a change to prevent the autofilling of the "SharePoint Admin URL" field within M365 source and destination advanced settings, as this was causing Exchange only migrations to fail
  • (Google) Resolved an issue in Google to Google migrations where Calendar appointment colours were not migrating correctly
  • (MS) Fixed an issue where, if the "Description" column in a SharePoint library had been deleted in the source, the migration would fail
  • (MS) Resolved a rare issue for M365 migrations when enabling version history could cause the migration to fail
  • (Google and MS) Fixed a bug which occured when viewing migration archives and switching between configurations whilst in this view - editing the labels and deleting items will no longer error
  • (MS) Resolved a rare issue for Google to M365 migrations where the end of the filename had spaces between disallowed characters in M365, causing the item to fail. Migrate will now correctly trim the filename replacing spaces with "_" Release Notes (May 18th 2023)


  • Resolved an error where, due to recent changes to the API’s utilised, migrations involving contacts or tasks either to or from M365 resulted in a “MapiReplyToBlob” error, and the migration would fail.
  • Fixed an issue for Zimbra source migrations where the server address field was only accepting IP addresses, it now correctly accepts both IP addresses and hostnames as valid inputs.


CloudM Migrate x64

Any platform except GroupWise or Notes

SHA1 - ea90745730a120e26278af89111fff4a5ecf515a

MD5 - e84e0002438292cd55686f8af1e09fab



CloudM Migrate x86

Required for GroupWise and Lotus Domino/Notes

SHA1 - cf4cacf958c4c8ada426e5e156a24bdb2916ff4c

MD5 - b99c56551e9e35c1c774cb34a2ce1cc3



3.40 Release Notes (April 20th 2023)

Enhancement Description Platform Links to article(s) in Knowledge Base

Support document versions for M365 to M365 migrations

When carrying out migrations from Microsoft 365 to Microsoft 365, the document versioning feature allows you to migrate previous major versions of documents, as well as the most recent version

Microsoft Microsoft 365 - Document Versioning


Enhancements / Improvements:

  • Improved how Teams Channels are migrated - You can now create empty Teams Channels in a migration by selecting to Migrate a team site, but not selecting any items. Previously, Migrate required at least conversations to be migrated to create the Teams Channel. 
  • Improved the validation on user input fields within Migrate to help prevent misconfiguration and improve security across the platform.
  • Clarified the tooltip for the "Migrate items only from listed users" feature
  • Improved how shortcuts to files are created in Google Drive. Since the removal of multiparented files in Google Drive, duplicate file locations have been replaced with a shortcut to the original location. Migrate could sometimes fail in the creation of the shortcut if it did not have the correct permissions for the user. It will now try to create the shortcut as the owner of the folder before failing.
  • Changed the Azure AD application to utilise application permissions rather than delegated user permissions for M365 Teams Planner migrations.



  • Tidied UI for the file system source platform, removing extra padding to be consistent with other source platforms
  • Fixed UI mistakenly referencing Box admin in Dropbox Source
  • Updated Dropbox authorisation prompt UI to reference Cloud Migrator App
  • Fixed the Azure AD app creation erroring if the Cloud deployment selected was either China or US government. Removed the unsupported delegate application option for these cloud deployment options
  • Removed the bespoke option for Germany within the cloud deployment option for M365 migrations, Germany is now supported within the default “Global Service” option
  • Fixed a bug where document migrations were failing if there were multiple tenant domains (i.e. onmicrosoft domains) 
  • Fixed a bug with the “allow multiple sources” feature when migrating multiple source SharePoint sites to a single destination SharePoint site. Selecting different document destination paths will now correctly migrate each source to its defined destination path.
  • Resolved a UI bug where the administrate option in the navigation pane could be duplicated
  • Fixed an issue where the environment scan feature for Google Drive was returning deleted items 
  • Fixed a bug in the environment scan report, where it was not warning if an individual user was over the number of files limit for Sharepoint or Google Drive
  • Resolved an issue for migrations to Exchange where task due dates could be a day behind
  • Fixed an issue for migrations from Google where calendars with the same name could cause events to be duplicated in the user statistics report
  • Resolved an issue for migrations from Google to M365 where files and folders where the modified dates metadata was empty or the epoch date/time (00:00 1/1/1970) would cause the item to fail to be migrated. Files will now successfully migrate with the metadata populated with the epoch date of 1/1/1970 (which may then be shifted depending on local timezones)
  • Removed the redundant “Multi-server drive migration” option within the advanced settings for Google destinations (all migrations now use this feature)
  • Removed the Microsoft Teams connection test for M365 to Google migrations within the test connections feature
  • Fixed a rare issue where some item IDs were not showing in the migration report
  • Resolved an issue where supported tabs in Teams channels were not migrating.
  • Fixed a fatal error that could occur when migrating from Google Drive to OneDrive if duplicate folders/files exist in the source (e.g. after being restored from deleted items). Migrate will now pre-append duplicate folders with “_” and append duplicate files with “_”.
  • Fixed a rare issue with attaching reports to email notifications
  • Resolved an issue where if orphaned folders existed they could fail to migrate
  • Included SourceType metadata for Migrations to SharePoint as this is now required by Microsoft

Please see the release notes and download links for the latest version of CloudM Migrate (v3.39.29 released on March 1st 2023 ) below. To view previous CloudM Migrate release notes, please refer to the CloudM Migrate Changelog article.


v3.39.29 Download Links 


CloudM Migrate x64

Any platform except GroupWise or Notes

SHA1 - 1ff91224e111e01c0ea010bfdf93f1a940396e96

MD5 - a083756d97f3c5519c531776afd221c1



CloudM Migrate x86

Required for GroupWise and Lotus Domino/Notes

SHA1 - b9d084030e641fbc2dded20051406c2fde5709a0

MD5 - 3d668a043b72a644e432b9b15029aa88



3.39.29 Release Notes

Improvement: Improved session security by increasing security of session cookies.

Improvement: Password requirements have been improved and now must include at least 1 upper case, 1 lowercase, 1 number, and 1 special character. The minimum password length has also been changed to 12 characters. 

Improvement: Improved account security by adding an account lock when the account password has been entered incorrectly 5 times. The account will be locked for 60 minutes, however this is configurable.

Improvement: Improved UI by removing the ‘Endpoint’ terminology and replacing it with ‘Platform’.

Improvement: Improved how non-matched replacements are handled when using a CSV file for address replacements. Items without a match will now use the destination domain when migrated, rather than the source domain.

Improvement: Added exceptions for the “to” “cc” and “bcc” headers when migrating to M365 to ensure they don’t fail oversized header checks.


Fix: Fixed an issue with the Team Site migration item not being available for SharePoint to Google Drive migrations.

Fix: Fixed an issue causing the environment scan report to not be generated for some mail only hosted environment scans. 

Fix: Fixed an issue with environment scans not scanning all mail items for some users.

Fix: Fixed an issue with mail items that have multiple labels not being included in the environment scan.

Fix: Fixed ‘Object reference not set to an instance of an object.’ error that occurred in some circumstances when migrating email attachments.



3.39 Release Notes (February 1st 2023)

Enhancement Description Platform Links to article(s) in Knowledge Base

‘Include Document Metadata’ for M365 to M365 migrations

CloudM Migrate now supports migrating custom document metadata in M365 to M365 migrations. With this new ‘‘Include Document Metadata’ feature enabled (within the Microsoft Office 365 destination Advanced Settings, Sharepoint online section) Migrate will export the following custom metadata; Single line text, Multi line text, Number, Yes/No and DateTime.

Microsoft Microsoft 365 - Document Metadata

Re-enabled ‘Rehydrate Private Chats’ feature for M365 to M365 migrations

This feature has been enabled to allow for the last 10 messages in private chats to be migrated directly into the destination Teams client.

In order to support this, the ‘Use EWS API for Teams Private Chats’ option has been removed. Private chats can now only be migrated using the Microsoft Graph API.

Microsoft  Migrating Microsoft Teams Private Chats


  • Improvement: Teams Private Chat Messages test added to connection tests when ‘Rehydrate Private Chats’ option is enabled.

  • Improvement: Title and Description columns have been added to default SharePoint and OneDrive document metadata migrations.

  • Improvement: Improved status messaging during Google Drive migrations.

  • Improvement: ‘Exclude Explicit Domain Permissions’ option added to Google Drive migrations. This option takes in a list of domains that will be removed from item permissions during export. 

  • Improvement: ‘Migrate Deleted Items To Litigation Hold’ option added to Advanced Settings for Google migrations. When enabled, purged emails will be migrated to the Purges folder in Litigation Hold.

  • Improvement: Orphaned files are now migrated to a new ‘Orphaned Documents’ folder for Microsoft 365, Google Cloud Storage and Azure Cloud Storage migrations.

  • Improvement: Google Workspace failed emails no longer fail migrations and are instead listed as failed migration items.

  • Improvement: Duplicate Document Sharing/Permissions option has been removed from the Office 365 Destination Advanced Settings.

  • Improvement: Improved tooltips across a number migration options.

  • Improvement: Items can now be migrated to a specific Microsoft Team.

  • Improvement: Removed a number of UI options that are no longer supported. These include ‘Startup Delay’ for Lotus Notes migrations, ‘Incoming Shared Folders’ for Groupwise migrations and ‘Shared Folders’ for Scalix migrations.

  • Fix: Fixed an issue with folders not migrating correctly when the ‘Migrate Top Level Folders’ setting was disabled.
  • Fix: Fixed ‘Object reference not set to an instance of an object’ error that occurred in rare circumstances when running a Google archive.
  • Fix: Fixed error ‘Unable to cast object of type 'ImportGroup' to type 'ImportUser'’ when migrating SharePoint groups.
  • Fix: Fixed error ‘Detected duplicated users with different login names in UserGroup.xml’ that occurred when SharePoint users had conflicting permissions.
  • Fix: Fixed error ‘Uploaded message hash does not match, this item has failed to upload’ when archiving Google Vault.
  • Fix: Fixed error ‘Invalid or missing password: password does not exist in the directory for this user’ encountered in some circumstances when performing a Microsoft 365 to Google migration.
  • Fix: Fixed an issue with files with size 0kb not being included in a managed archive.
  • Fix: Fixed an issue where the Folder Import Failure count was not being added to Project Level Report CSV files.
  • Fix: Fixed an issue that allowed duplicate entries to be added to Address Replacements.
  • Fix: Fixed an issue with dates not being displayed using the correct localization.
  • Fix: Fixed an issue where, in the event that a parent folder cannot be found, child items are being migrated to the folder root instead of respecting the Top Level Folder and Destination Folder settings.

    3.38.17 Release Notes (14th December 2022)

    • Fix: Fixed an issue with Google Vault to Microsoft 365 migration reports not displaying the correct number of export and import items
    • Fix: Fixed an issue with Google migrations failing due to changes to the Google API, specifically caused by 403 errors causing migrations to fail instead of triggering retry logic.
    • Fix: Temporary removal of the “Rehydrate Teams Private Chats” option from the destination settings whilst enhancements to this feature are being developed
    • Improvement: Improved efficiency of Google Vault migrations to boost throughput


    3.38.11 Release Notes (30th November 2022)

    • Essential updates for Google Drive to Google Drive migrations to adhere to Google Drive API rules around multi-parenting of files and folders. Please refer to the Important notification concerning all Google Drive migrations article for more details.
    • The optional ability to trash duplicate items during a Google Drive has been added as a Destination setting (Destination > Google Workspace > Advanced Settings > Document > Trash Duplicate Items). It is enabled by default.
      • The Migration Readiness Test will flag if the setting has been disabled.
    • Updated CloudM Migrate Installer License Terms.

    3.38 Release Notes (9th November 2022)

    Enhancement Description Platform Links to article(s) in Knowledge Base

    Change of URL for CloudM Migrate Self Hosted

    When you upgrade from v3.37 (or earlier) to v3.38 (or later), the web path URL for CloudM Migrate Self Hosted will change from http://cloudmigrator.local/ to https://cloudm.local/

    Google and Microsoft Logging In

    Restart Failed Users as part of the Environment Scan

    If the Environment Scan shows Failed Users, you can press the Retry Failed Users button to run the scan for failed users only, instead of the entire scan again.

    This allows you to restart at the point where the Environment Scan failed or stopped.

    Google and Microsoft  Environment Scan

    Use a JSON key when creating a Service Account 

    You can now create and use a JSON key (or a P12 key) when setting up a Service Account.


    Setting up the Service Account and enable the APIs within Google Workspace for CloudM Migrate

    Teams to Teams Private Chat rehydration

    When carrying out a Microsoft 365 to Microsoft 365 migration, there is a new configuration option allowing for Teams private chat messages between users to be rehydrated so that they are available to view via the destination Teams client

    Migrate previously supported migrating these messages into a specific folder within the users mailbox. With the addition of this new feature, the last 10 messages will be migrated into a Teams chat in the destination, as well as into the users mail folder.

    By allowing users to easily access their last messages within Teams the end user experience is improved. Additionally, within the migrated messages, the users will also be informed that the remainder of the messages are available in the relevant folder within their mailbox. This will allow users to find and access older messages more quickly and easily, and ultimately make supporting users post migration simpler.


    Migrating Microsoft Teams Private Chats


    • Improvement: ‘Teams Direct Migration’ and ‘Migrate Team Channel Tabs’ settings moved from Office 365 Import options to Office 365 Export
    • Improvement: Improved logging messages for Google Vault migrations to be more informative
    • Improvement: UI labels improved for Office 365 destination settings
    • Improvement: Google Authentication Method tooltip updated to be more accurate
    • Improvement: Added support for Drive item search terms when migrating Google Vault
    • Improvement: Introduced support for Microsoft Graph Delegate permissions
    • Improvement: Reduced Logging Level to Trace for processing Google Folder Permissions
    • Improvement: Added the ability to list IMAP folders for a configuration
    • Improvement: Introduced support for migrating spam items when migrating from Google Vault
    • Improvement: Environment Scan failed users can now be individually restarted 
    • Improvement: "Get users" no longer automatic for Migrate Hosted
    • Improvement: Updated logging for Microsoft group migration failures to include group name
    • Improvement: Moved Environment Scan into a stand alone service
    • Improvement: Updated to version 3 of the Google Vault API for Mail export, providing a more robust and faster experience.


    • Fix: Fixed an issue with SharePoint permissions not migrating correctly
    • Fix: Fixed an issue with Google Vault failed items not being listed correctly in the UI
    • Fix: Fixed ‘Unexpected segment DynamicPathSegment’ error when migrating documents from Azure Storage to SharePoint Online
    • Fix: Fixed ‘Destination: Uploaded message hash does not match, this item has failed to upload’ error when Archiving Google Drive
    • Fix: Fixed issue with Vault exports not displaying correct number of exported items
    • Fix: Fixed ‘Source: Notes database files must be specified as SERVER_NAME!!path.nsf, found names.nsf’ error when migrating from Lotus Notes
    • Fix: Fixed ‘Unexpected exception processing import. Message is: One or more errors occurred.’ Archive error
    • Fix: Fixed ‘Object reference not set to an instance of an object.’ error when migrating Google Forms
    • Fix: Fixed ‘File Processing Error’ for Google Vault migrations
    • Fix: Fixed an issue with incorrect address replacements for Google to Office 365 migrations
    • Fix: Fixed issue with Get Items from Source button not working for hosted on-premise Exchange migrations
    • Fix: Fixed an issue with Teams document libraries migrating incorrectly
    • Fix: Fixed ‘Failed: Unexpected error.’ for Google Workspace migrations
    • Fix: Fixed an issue with Shared Drive permissions not migrating correctly
    • Fix: Fixed an issue with Out of Office settings not migrating properly from Google to Office 365
    • Fix: Fixed issue with trashed items not migrating for Groupwise to Google migrations
    • Fix: Fixed an issue with secondary calendars not migrating for Google to Google migrations
    • Fix: Fixed an issue with clearing migration history for individual users not working as expected
    • Fix: Fixed an issue with recoverable items not migrating correctly to the DISCOVERYHOLDS folder for Office 365 migrations
    • Fix: Fixed ‘Object reference not set to an instance of an object.’ error that caused Environment Scans to fail
    • Fix: Fixed issue with account delegates and auto forwarding not migrating for both Office 365 and Google migrations
    • Fix: Fixed help link incorrectly redirecting to non-existent page
    • Fix: Fixed formatting for migration csv result documents 
    • Fix: Fixed an issue causing East/West US virtual machine creation to fail
    • Fix: Fixed an issue resolving permissions and breaking inheritance with some folders and files when migrating to OneDrive/SharePoint Online using the Migration API
    • Fix: Fixed a rare issue causing email migrations to fail with ArgumentOutOfRangeException


Was this article helpful?
0 out of 0 found this helpful