cloudM

power2Cloud proudly partners with cloudM. Our expert team is poised to ensure the secure migration of your data, while also overseeing the synchronisation of all your business signatures.

As ever, you'll have a dedicated account to guide you throughout the entire process.

The cloudM Platform features a tool designed to project migration timelines, indicating the remaining time once the process is underway. This is determined by evaluating the total data volume and the current throughput, which reflects the rate of data processing.

This tool is operational only when the migration has started, providing a rough estimate of the remaining time. Predicting the exact duration of a migration before it starts is challenging due to numerous variables and limiting factors such as bandwidth, machine specifications, and potential platform throttling.

To effectively estimate the migration duration both overall and per user, it is ideal to gather the following data:

• Total number of users/units/sites for migration 

• Data volume

• Total number of email messages and files

• Data distribution (number/volume of items per user)

• Number of file permissions

• Number of file folders

For further assistance, please reach out to our team.

Migration architecture: Understanding the source platform can aid in crafting the migration architecture, such as determining the number of CloudM Migrate Self-Hosted secondary instances required. Each instance, by default, runs 20 concurrent threads. Given that the primary constraints in most migrations involve cloud platform throttling and API quotas, the number of threads is crucial for predicting the expected duration.

Calculation: As platform constraints during migrations are often related to the number of elements per second/user, the quantity of elements can be as significant, if not more so, than the data volume. Based on our internal testing, which incorporates real-world migration outcomes and best practices, we've found an average of 40,000 mail items per instance and 2,000 items per thread per hour. Typically, a migration extends as long as its largest user, so this can be used to estimate the total duration, assuming there are enough threads to handle the remaining users within this period.

Using migration batches can help ensure that the largest users make the most efficient use of available thread time.

File migrations: When migrating to platforms like Google Drive or SharePoint/OneDrive, consider additional factors. Specifically, the number of permissions can increase the API calls required and the likelihood of throttling; the number of folders must also be accounted for, as they need to be retrieved with each migration execution, unlike files, which are processed only if they've changed since the initial execution.

The time required varies based on the number of users involved, such as whether it's a single organisational unit with a specific number of users or a larger organisational unit that includes multiple sub-units and additional users. Another factor is the amount of data contained in the signatures that need synchronisation with each user account.

Generally, most changes are completed within 30 minutes to 2 hours.