If you build MigrationWiz projects without first checking your BitTitan customer portal account-level settings, you may be inheriting defaults that change how every project behaves. These account-level options apply across all MigrationWiz projects created under that account.

Key settings include migration speed, how aggressively MigrationWiz submits EWS API requests to the source and destination; email notification thresholds, when error counts trigger alerts; and the data residency setting, where BitTitan stores migration metadata.

Migration speed is the setting that most often causes trouble. The default is conservative, and in tenant-to-tenant migrations where the migration service account is excluded from Exchange Online service protection policies on both sides, increasing that speed can shorten pre-stage duration significantly.

Pushing speed higher in a tenant where the account does not have throttling exemptions can trigger EWS service protection policies more quickly. In the worst case, the migration account can be temporarily suspended at the tenant level, which halts every job in the project at once.

Before your first pre-stage, have you reviewed the account-level migration speed setting and confirmed whether the service account has throttling exemption status?

#BitTitan #MigrationWiz