Product release – CloudM Migrate 4.2: Centralized logging and hassle-free Dropbox migrations

The new year is off to a good start for CloudM Migrate users. Read on to find out more about how we are keeping your log files and configurations safe, why it’s now easier to move from Dropbox and which platform has just been added as a source.

Watch the video summary below:

Centralized logging for CloudM Migrate self-hosted users

If you are a user of CloudM Migrate’s self-hosted version, you will see a number of improvements when upgrading to Migrate 4.2. As this newest version enables automated uploading of your self-hosted trace files and configurations to your own Google Storage bucket or Azure Storage container, you can:

• Save storage space on your migration servers
• Safely decommission or remove secondary servers without the risk of losing log files
• Get quicker help from the CloudM Support team by easily sharing access to your logs

Export failed item lists from the progress page

We’ve also added the ability to export a list of failed items during an active migration. This can be done for specific entities (users, drives, shared drives) or all entities in the migration list and provides greater visibility and diagnostics. Click here to learn more.

With Migrate 4.2, you can now export a list of failed items for specific or all entities in the migration list.

Read the full release notes

Read about feature releases, bug fixes and system improvements for this and previous releases