How long does a migration take? What is the speed that we can expect?
It can be difficult to accurately predict how long a migration will take. Several factors that will have an impact on timing are system load, bandwidth, average item size, and Source or Destination bottlenecks.
MigrationWiz will not be the bottleneck, because we are connected to the largest migration farms, and we do not throttle data.
However, here is a very rough breakdown of what can be expected. Note: This is not an SLA; it is an example based on a very large sample of migration speeds experienced by our Partners.
- Low end: 250mb per hr/per user
- Mid end: 750mb per hr/per user
- High end: 1.25gb per hr/per user
Here are some factors that will affect migration speeds:
Simultaneous Mailbox Migrations
We have reached speeds of over 1.5 GB/hour/mailbox when connecting to a high-availability infrastructure. Migrating more mailboxes at the same time allows parallel processing, shrinking the duration of your migration. MigrationWiz is able to migrate hundreds of thousands of mailboxes simultaneously. If all of your mailboxes are migrated at the same time, the migration duration is the time it takes to migrate the largest mailbox.
How fast are the Source and Destination servers connected to the internet? The entire process is only as fast as the slowest link. MigrationWiz was built to work across even the slowest links. We've connected to networks that range from a T1 to networks that host multiple gigabit connections. There is no need to worry about our network speed. Depending on the data center that the migration server is located in, we will be connected with a gigabit or 10-gigabit connection.
The network latency is dependent on the quality of the connection between our data center and the Source and Destination. We utilize the fastest internet backbones available globally. We sometimes encounter connections to servers that look like they were purchased from a flea-market. Because of our global migration farm, our connections are made from networks with low latencies.
Number of Mailbox Items:
There is a per-item transaction overhead and cost. For example, given two mailboxes with the same size but different number of items, the one with less items will migrate faster than the one with more items.
MigrationWiz was built from the ground up, and optimized to reduce network chatter. We have seen our patent-pending technology move over a thousand items in less than a minute in some cases.
This one is obvious. The more data there is, the longer the migration. When migrating between two hosted providers, the size of the mailbox is hardly a factor because of our massive connections to the internet. Some Destinations might have capacity issues. When mailboxes are bigger than a certain amount of GB, speed reduction may occur because of those scalability issues.
Errors can occur for a number of reasons: corrupt items, network outages, etc. MigrationWiz contains automated, self-corrective technology that deals with errors automatically in most cases.
What type of equipment is the Source and Destination mailbox deployed on? Our migration process is not usually noticeable if your server is sized appropriately for your organization.
Does the Source or Destination system throttle the amount of data that can be read or written? Several systems implement throttling policies that prevent full utilization of available network bandwidth.
Number of Folders:
Depending on the number of folders and the Source system, enumeration of the folders might slow down the migration process. Read more on this topic in KB004385.