If you leave MigrationWiz migration speed on the default setting, do you know what that choice is doing to your EWS request rate?

MigrationWiz provides four speed settings: Full, High, Medium, and Low. They control how aggressively MigrationWiz submits API requests to the source and destination tenants while jobs are running. Full runs at the maximum rate the connection supports, while Low intentionally adds delays between EWS or Graph API calls.

Full speed makes sense when the migration service account on both the source and destination tenants is excluded from Exchange Online service protection throttling policies, you are migrating during off-peak hours, and you have confirmed other tenant workloads are not competing for EWS resources.

Medium or Low is a better choice when you are working with a third-party source tenant that has not granted throttling exemptions, when migration is happening during business hours with active mail flow on the source tenant, or when the source tenant has already hit service protection policy activations during migration.

In a well-configured environment, the throughput gap between Full and Medium can be substantial, often 2x or more in items per hour. But if you push Full speed against a throttle-sensitive source tenant, service protection policies can kick in, throughput can drop to near zero, and jobs may require a multi-hour cooldown before they can continue.

Have you selected your MigrationWiz migration speed deliberately based on source and destination tenant throttling exemption status?

#BitTitan #MigrationWiz