Have you run a full enterprise MigrationWiz program and realized the certification prepared you for maybe 60 percent of what production actually looks like?

Across two acquisition migrations, I reconciled and migrated 300 plus accounts through MigrationWiz. The certification covers the fundamentals of the tooling. Real production work is where the edge cases show up, especially the ones the documentation does not address.

Three lessons stood out from production. First, SMTP addresses containing non-ASCII characters require encoding validation in the user list CSV before upload. The silent-drop behavior is real, and the portal may not show any error.

Second, shared mailboxes that have more than 10 active delegates need explicit delegate access testing in the destination tenant after migration, not just a basic connectivity check. Full Access delegate permission replication to the destination is not always immediate, so a mailbox can appear clean while delegate access remains broken for hours after cutover.

Third, source tenants that never fully completed Exchange hybrid decommissioning, where Exchange Server attributes were not cleared from cloud-only recipient objects after a past hybrid migration, can cause MigrationWiz routing to act unexpectedly for those specific accounts. In the admin center the mailboxes look like Exchange Online mailboxes, but MigrationWiz can route them incorrectly because legacy on-premises Exchange attributes still exist in the directory.

None of these scenarios are covered in the BitTitan documentation. All three came directly from running migrations against production tenants.

What is the most unexpected MigrationWiz behavior you have encountered in a production migration that you could not find documented anywhere?

#BitTitan #MigrationWiz