Are you building a cutover plan around BitTitan published MigrationWiz throughput benchmarks and then missing your maintenance window in production?

BitTitan throughput figures for mailbox migrations reflect best-case conditions: no EWS throttling on either tenant, jobs running during off-peak periods, and mailboxes with typical item sizes and counts.

Real environments rarely match that. Exchange Online service protection throttling is applied at the tenant level based on concurrent EWS connections and overall hourly volume. Mailboxes with very high item counts, especially those with years of archived mail made up of small items, often migrate more slowly per GB than mailboxes dominated by fewer, larger attachments, because throttling is triggered per API operation rather than per byte transferred.

A scheduling approach that consistently works is to run a 24-hour throughput test across a representative sample, roughly 10 to 15 mailboxes spanning different size and item-count profiles. Use that measured throughput to build the schedule, treating BitTitan benchmark as a starting point rather than the plan.

Are you running a measured throughput test before you lock in your MigrationWiz cutover schedule?

#BitTitan #MigrationWiz