In the current article, we will review optional mail migration tools/methods that we can use…
Mail Migration to Office 365 | Measure and estimate Mail Migration throughputs | Part 4/4
In this article, we review the subject of mail migration throughput when migrating existing mail infrastructure to Office 365.
Table of contents
- Mail migration to Office 365 | Optimizing the Mail Migration throughput | The article series
- Mail migration to Office 365 throughputs
- Mail migration to Office 365 common questions
- Mail migration to Office 365 | Performance of different migration methods
- General conclusions from the “Performance for migration methods”
- Calculating mail migration throughput
- Calculating mail migration time
- Mailbox migration to Office 365 calculator
Mail migration to Office 365 | Optimizing the Mail Migration throughput | The article series
The article series includes the following articles:
- Mail migration to Office 365 | Mail Migration methods
- Mail migration to Office 365 | Factors that impact mail Migration performance
- Mail migration to Office 365 | Optimizing the Mail Migration throughput
- Mail Migration to Office 365 | Measure and estimate Mail Migration throughputs (this article)
Mail migration to Office 365 throughputs
We need the answer about the mail migration throughputs for two main reasons:
- Reason 1 -in a mail migration project, we need to provide a due date for the completion of the migration process.
- Reason 2 – when implementing the mail migration, we need to have some baseline or a reference that could help us to understand if the existing results of the mail migration throughput’s are reasonable or in case that we notice that the mail migration throughput’s is very low, find the reasons for the “Low throughput’s” and possible solution that will help us to optimize and improve the throughput’s (Transfer rate) of the mailbox content to the cloud.
Mail migration to Office 365 common questions
One of the first questions we could ask is: What is the required time for migrating a mailbox to the cloud?
The next question could be: What is the exact definition of a standard mailbox? (A user mailbox could be 1GB mailbox or 20GB with hundreds or thousands of mail items).
Let’s assume that we can define the size of an “average or standard mailbox.” We still need to know how much time it will take to migrate all the organization mailboxes to the cloud or in other words, what is the expected or the average transfer rate when migrating mailboxes to Exchange Online?
Let’s assume that we have implemented some pilot, migrate 10 mailboxes to Exchange Online, measure the average transfer rate and come off with some numeric results.
The question now is: does this result consider as bad? Average? Good? Do we have some guideline for the expected transfer rate result?
Mail migration to Office 365 | Performance of different migration methods
In the following section, we will estimate the expected mail migration throughput based on the Microsoft article Exchange Online Migration performance and best practices.
In the following screenshot, we can see a data table named – “Performance for migration methods.”
Before we start to analyze the information in the table a couple of notes:
- Many important details appear in the “note section” under the table.
- The information in the table includes some “holes” because the measurement and the results that appear in the table (and in the note section) relate to different values of concurrent mailbox’s migration. For example, the mail migration throughput’s for Cutover and Stage migration relate to 100 concurrencies vs. the throughput’s results of Hybrid migration that relate to 20 concurrencies.
To be able to display the data more clearly, I have created the following table:
|Migration method||Single mailbox||20 concurrency||50 concurrency||100 concurrency|
|IMAP Migration||10-15 GB|
|Cutover Migration||10-15 GB|
|Staged Migration||10-15 GB|
|Hybrid Migration||0.3-1.0 GB||10-15 GB||15-50 GB|
|Third-party MAPI Migration||0.1-0.5 GB||4-12 GB|
|Third-party EWS Migration||0.2-0.5 GB||5-10 GB||20-50 GB|
|Client Uploading (From Outlook PST)||0.5 GB|
General conclusions from the “Performance for migration methods”
1. MAPI/RPC mail migration vs. EWS method
As was mentioned in the previous article Mail migration to Office 365 | Optimizing the Mail Migration throughput | Part 3/4, when we perform mail migration from Exchange on-Premises server, we can “address” the Exchange on-Premises server in two ways: MAPI/RPC or EWS.
By looking at the data, it is very clear that when we perform the mail migration by addressing the Exchange EWS “listeners” that mail migration throughput are much better.
For example, Cutover and Stage mail migration are implemented by using MAPI/RPC connection to the Exchange on-Premises server vs. Hybrid Migration that addresses the EWS “listener.”
We can see that the results for 100 concurrency mailbox migration are very different when we compare the Cutover and Stage mail migration vs. the Hybrid mail migration, the results range for Cutover and Stage mail migration for 100 concurrencies is: 10-15GB and the results of Hybrid mail migration are: 20-50GB.
Note: The comparison is between the Office 365 native mail migration option vs. Third party EWS Migration because the article doesn’t include information about 100 concurrencies when using the option of Hybrid mail migration.
2. Single mailbox migration vs. multiple mailbox migrations
Another interesting piece of information in the data table relates to a scenario of Single mailbox migration vs. multiple mailbox migrations.
In the following screenshot, I have highlighted the information the estimated throughput of Single mailbox migration vs. multiple mailbox migrations when we use the option of Hybrid migration. Clearly, the throughput results of Single mailbox migration are inferior vs. the throughput results when we perform multiple mailbox migrations.
The reason for this difference.
I try to understand the reason for this difference. The article includes the following note:
Observed single mailbox move throughput is in the 0.3–1.0 GB/hour range. More concurrent mailbox migrations can be used to achieve higher data migration rates. For example, with 50 concurrent moves, the overall throughput will be in the 15–50 GB/hour range. Single mailbox move throughput will slow down when the on-premises CAS (MRSProxy) server is at hardware capacity. Consider adding more servers to increase migration velocity
It’s unclear to me if this note relates to a scenario of performing multiple mailbox migrations from multiple Exchange on-Premises server or performing multiple mailbox migrations from a single Exchange on-Premises server, but the general conclusion is that we will get much better results when we implement multiple mailbox migrations.
3. Hybrid mail migration vs. Third party EWS Migration
The preferred method for performing mail migration in an Exchange-based environment is addressing the EWS services of the Exchange server.
The data in the table include information about EWS mail migration that performed by using the Hybrid migration vs. Third party EWS Migration. The conclusion from the results is that Hybrid migration provides a better throughput result than Third Party EWS Migration tools.
Calculating mail migration throughput
In the following section, we will try to “translate” the data in the “Performance for migration methods” to time units.
Let’s start with the concept of: “Range of values.” For example: the information in the “Performance for migration methods” table says that when using the option of Hybrid configuration with 20 concurrency (multiple mailbox migration) the throughput could be a value starting from 10GB per hour and ending with 20GB per hour.
The reason for using a range of values instead of proving a “single number” is that there are many possible factors, which we review in the article Mail migration to Office 365 | Factors that impact mail Migration performance | Part 2/4 that can impact the mail migration process and by doing so, provide different results.
Although it’s not written in the Microsoft article, I assume that the “numbers” that appear in the data table are some average that was created from analyzing the data (the results) from many “cloud mail migration projects.”
To simplify the use of the data range, I have created the following diagram.
In the “low range” we get a mail migration throughput of 10GB per hour, in the “High range” we get a mail migration throughput of 15GB per hour, and additionally, I have added a “Mid-range” that is calculated as the “Half Way” between the Low range and the High range. In our scenario, the “Mid-range” mail migration throughput of 12.5GB per hour.
Q1: Can we use these values/numbers as an absolute number when we need to provide an estimation for the mail migration throughput?
A1: My opinion is that we cannot relate to these numbers as an “absolute asset value” because these results are based on averages. In the reality, our infrastructure could lead to much worse results or, in a “best-case scenario” case scenario” provided that our organization has unlimited resources or all of our infrastructure is “perfect,” theoretically, we can get better results.
Calculating mail migration time
Scenario 1: Hybrid migration | Single Mailbox Move| Data transfer rate: GB per Hour
The information in the “Performance for migration methods” table says that when using the option of Hybrid configuration for a single mailbox migration, the throughput could be a value starting from 0.3GB per hour and ending with 1GB per hour.
It is quite easy to understand that the estimated throughput of a single mailbox migration is “Inferior” vs. the throughput that we achieve when implementing multiple mailbox moves.
If we use a graph for drawing the range, we will get the following graph:
In case we want to provide an estimate for the time that we need to migrate a single 10GB mailbox, the worst-case scenario transfer rate (Low range) is 32.7~ hours, and in the best-case scenario (High range), that time which is required to migrate the mailbox to Exchange Online is 10~ hours.
Hybrid migration | Single Mailbox Move | time range calculation
To make the information more “real”, I have created the following table that includes three optional scenarios for a single mailbox move:
|Mailbox size||Low Range||Mid Range||High Range|
|2GB||6.5~ hours||3.3~ hours||2~ hours|
|5GB||16.3~ hours||8.2~ hours||5~ hours|
|10GB||32.7~ hours||16.3~ hours||10~ hours|
The calculation formula
If you are interested in calculating these values, the formula is very simple.
For example, the article says, “Observed single mailbox move throughput is in the 0.3–1.0 GB/hour range.” To be able to calculate the time that will take to migrate 2GB Mailbox using the “Low range” option, we use the following formula.
1GB = 1,024 Megabytes
2GB = 2,048 Megabytes
The “Low range” transfer rate is 300 Megabytes per hour (or if we want to be more precise the number is 306 Megabytes because that present article data that measured in Gigabytes)
So the formula will be: 2,048/306 = 6.69
In straightforward words, in case that we want to relate to the Low-range transfer rate, it will take six and a half hours to move a Mailbox size of 2GB to the cloud.
Scenario 2: Hybrid migration | Multiple Mailbox Move| Data transfer rate: GB per Hour
In the following chart, we can see the presentation of the information about the transfer rate. The Low-range value is: 10GB, meaning that when we migrate multiple mailboxes to the cloud the worst-case scenario is based on the transfer rate of 10 Gigabytes per hour, the “Mid-range” (the article doesn’t provide a mid-range. I have used the value by calculating the “half-way between the way between the low-end value and the High-end value) enable us to move of 10 Gigabytes per hour to the cloud in the best-case scenario; we can expect to move of 15 Gigabytes per hour of mailbox data to the cloud.
Example table: Hybrid migration Multiple mailbox move (20 mailboxes).
In this example, the calculation is based on the assumption that we use Hybrid migration for migrating 20 mailboxes at the same time.
In this scenario, we add additional variables to the calculation formula because when we deal with a “group of mailboxes” first, we need to define some estimation of the average size of each of the mailboxes and second, we need to calculate the total amount of the data that will be “transferred.” For example, if we want to migrate 20 mailboxes when the average size of each of the mailboxes is 2GB, the total amount of data that transferred is – 40 Gigabytes.
For example: in a scenario in which we use Hybrid migration and implement multiple mailbox migrations for mailbox with an average size of 5GB, the time estimation for the compilation of the migration could be as follows:
- Low range scenario: 10.2~ hours
- Mid-range scenario: 8.2~ hours
- High range scenario: 6.8~ hours
Hybrid migration | Multiple Mailbox Move | 20 concurrency
The following table includes estimation of the average time that will take to migrate Exchange on-Premises server mailbox to Exchange Online when we use a migration batch that migrate 20 mailboxes (20 concurrency).
|Mailbox size||Low Range||Mid Range||High Range|
|2GB (Total size of 40 GB)||4~ hours||3.3~ hours||2.7~ hours|
|5GB (Total size of 100 GB)||10.2~ hours||8.2~ hours||6.8~ hours|
|10GB (Total size of 200 GB)||20.5~ hours||16.4~ hours||13.7~ hours|
Mailbox migration to Office 365 calculator
Download Single Mailbox and Multiple Migration throughput calculator (Excel sheet).
Based on the data in the “Performance for migration methods” table, I have created an Excel-based calculator that will help you to get a general estimation of the time that it will take to migrate existing mail infrastructure to Exchange Online.
The “results” are different when using single mailbox migration vs. multiple mailbox migrations, when using various methods of mail migration, and when we use a different number of concurrent mailbox moves.
How to use the Office 365 mail migration calculator
In the following screenshot, we can see an example of the Office 365 mail migration calculator when we use a scenario of Hybrid migration of multiple mailboxes (20 concurrent moves).
We will need to provide the average size of the mailbox (number 1) and the number of the mailboxes that migrated (number 2).
After we enter the required information, we can see the total amount of data that we are going to migrate. In our example, 20 mailboxes with an average size of 10,000 MB will create a total of 195 GB (number 3).
The result defines a time range of possible results (number 4).
For example, in case that our infrastructure is not optimized or overloaded, the time that it will take to migrate 20 mailboxes (each mailbox size is 10GB) is -19.5 hours.
In case that we have “best-case scenario,” case scenario”, the time that it will take to migrate 20 mailboxes is – 13 hours.
Single Mailbox Migration throughput calculator
Enter the value of the mailbox size in MB in the green field, and the result will then provide a light blue field.
Multiple Mailbox Migration throughput calculator
Enter the value of the average mailbox size in MB in the green field + the number of mailboxes that will be migrated, and the result will then be provided in a light blue field.
This ends our Mail migration to Office 365 | Optimizing the Mail Migration throughput article series.
This Post Has 2 Comments
Love the Calculator you created…………..AWESOME!!!!