This guide explains the key factors that influence migration performance with CloudM Migrate. Understanding these elements is the first step toward a fast and efficient migration.
Key Performance Factors
Migration speed is not determined by a single factor but rather by a combination of internal and external variables.
Network and Bandwidth
The most common bottleneck is network throughput, specifically your upstream bandwidth. This is the speed at which data can be uploaded from your network to the destination system.
Infrastructure
The speed of your migration workstation(s) is critical. This includes:
-
Processing Power (CPU): Handles data processing tasks.
-
Available Memory (RAM): Used for temporary data storage and processing.
-
Disk Speed (SSD vs. HDD): The read/write speed of your hard drive.
For a complete list of hardware and software recommendations, consult the CloudM Migrate System Requirements.
Best Practice: Use Cloud-Hosted VMs
For optimal performance and scalability, CloudM Migrate can be set up using Cloud-Hosted Virtual Machines (VMs). Using services like Google Cloud Platform (GCP), Microsoft Azure, or Amazon EC2 is a recommended strategy. Aligning your migration VMs with the destination platform offers a significant performance advantage. For example, using a GCP VM for a Google Workspace migration or an Azure VM for a Microsoft 365 migration can significantly reduce network latency.
The Critical Role of Concurrency
CloudM Migrate is designed to run multiple user migrations simultaneously, which is the most efficient way to utilize resources. The Maximum User Migrations setting in the CloudM Migrate Service Manager controls this.
-
Optimal Performance: Migrations are most efficient when at full capacity, typically with 20 migration threads running concurrently across all secondary/worker servers.
-
Small Migrations: A common misconception is that a small, 10-user migration should be fast. However, it will be slower than a large migration because it can't achieve full concurrency.
-
Single-User Migrations: A single user/entity migration will, by its nature, be slower. This is because only one thread is active, and it cannot take full advantage of the available hardware, network bandwidth, and API quotas.
Why this matters: When you have a large number of users to migrate, the CloudM Migrate Service Manager will distribute the workload across multiple threads and servers, maximizing your overall throughput.
Destination System Limits
Source and destination services, such as Google Workspace and Microsoft 365, often have built-in rate limits, API quotas, and throttling policies. This is the single most common cause of slow migrations, even when your local network and hardware are optimized.
| Term | Definition |
| Throttling | A reactive measure to slow down an application making too many requests. It's a warning to pace yourself before getting blocked. |
| Rate Limiting | A proactive, hard limit on the number of requests you can make within a specific, short timeframe (e.g., 100 requests per second). Hitting this limit will block requests. |
| API Quotas | A cumulative, hard limit on the total number of requests you can make over a longer period, such as a day. All further requests are blocked until the quota resets. |
CloudM Migrate is built to handle all of these mechanisms, but they still act as a hard cap on your migration speed. For more detailed information, consult the official documentation for each platform (e.g., Google Workspace API limits, Microsoft 365 Exchange throttling).
Data Characteristics
The sheer volume of data is a major factor. The size of user mailboxes and the number of individual items directly impact how long a migration takes. Items include:
-
Emails & email labels/folders
-
Files & folders
-
Calendar entries
-
Contacts
How to Optimize Performance
The most effective way to understand your migration speed is to perform a pilot migration.
-
Pilot Migration: A pilot migration is the best way to determine the actual performance you can expect from your specific environment. By migrating a representative sample of users, you get an accurate benchmark of real-world migration speeds.
-
Finalize Your Plan: Use the data from your pilot migration to create a realistic timeline for your full migration. This includes determining the ideal number of simultaneous users and migration workstations needed.
For a detailed breakdown of specific strategies, including configuring your environment and scaling your migration, see our guide: Strategies for Optimizing Migration Performance.