“How long will my migration take?” We are sure you have either been asked that question or asked that to someone else. There is no clear answer. Every mailbox contains a unique set of data which results in different speeds. When adding in other factors related to networks, mailboxes, and others, the answer becomes even less clear. We are certain that if you are migrating data to or from a cloud-based system, there is no other migration solution that can push data faster than MigrationWiz. When planning the timeline of your migration project, there are a few things to note:
- Migration speed depends on many factors including system load, network bandwidth, average item size, throttling, etc.
- Migrations cannot run faster than what both the source and destination allow. Bottlenecks on each end directly affect performance.
- Migrated data is encrypted, encapsulated, converted, etc. Network bandwidth tests use raw byte copies and ignore all overheads.
- MigrationWiz will never be the bottleneck by never throttling data transfers and connecting to the fastest networks worldwide with servers located globally.
- MigrationWiz uses parallel processing. For example, 10 mailboxes migrating at a rate of 500 MB / hour means 5,000 MB / hour total.
- MigrationWiz only opens one single TCP or HTTP connection per mailbox. This is designed to scale many concurrent mailboxes. MigrationWiz can migrate as many mailboxes as you want as long as the source and destination systems can handle it.
If you have very large mailboxes, we suggest a delta migration to spread the load of each pass. Use the first pass to migrate the bulk of the data (ex. emails from the 180 days) and then switch the user to the destination mailbox. After switching, use remaining passes to migrate the rest of the data in the background. Floyd Pena from Albuquerque Bernalillo County Water Utility Authority prefers this method when he migrated 600 mailboxes.
“We did a first pass about a month before we actually moved to Office 365. This way, most of the mailbox data would already be migrated over with the initial pass. A couple weeks later, we quickly ran a second pass to pick up any new items. We performed the 3rd pass just before and a 4th pass just after cutting over to Office 365. The 5th pass was performed about a week later to pick up any more data that were not picked while we were changing the MX record.”
