Please see the release notes and download links for the latest version of CloudM Migrate (v18.104.22.168 released on May 18th 2023 ) below. To view previous CloudM Migrate release notes, please refer to the CloudM Migrate Changelog article.
v22.214.171.124 Download Links
CloudM Migrate x64
Any platform except GroupWise or Notes
SHA1 - c1c902c8349ec373cce492eacb9263b70fb5f454
MD5 - f3f6602452fd537217dbaa4bd6a1d604
CloudM Migrate x86
Required for GroupWise and Lotus Domino/Notes
SHA1 - 1282c4e7c6fc344e3802128e9cd41aff4d3de441
MD5 - ccc83535534bbeb1d55c19253e90e98b
126.96.36.199 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.
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 sign in to leave a comment.