Are you assuming MigrationWiz will migrate Exchange Online distribution lists, only to discover after cutover that your mail-enabled groups did not move?

MigrationWiz migrates IPM.Contact objects that live in a user personal Contacts folder inside the Exchange mailbox. It does not migrate Active Directory distribution groups, mail-enabled security groups, Exchange Online dynamic distribution lists, or Global Address List entries.

If distribution groups and mail-enabled security groups are in scope, they need their own migration workstream. One option is PowerShell: export from the source tenant with Get-DistributionGroup and Get-DistributionGroupMember, then recreate and repopulate in the destination with New-DistributionGroup and Add-DistributionGroupMember. Another option is directory synchronization, if the acquisition roadmap includes eventual AD consolidation between tenants.

The GAL is different: once user accounts exist in the destination tenant and Exchange Online processes the new recipient objects, the GAL populates automatically from the directory. MigrationWiz is not responsible for GAL population.

The recurring scope problem is that “migrate all mailbox data” gets interpreted by business stakeholders as “migrate everything, including distribution groups.” Those are not the same object types. The fix is to itemize scope explicitly by object type before the migration begins, not after post-cutover complaints start.

Have you clearly documented which Exchange recipient object types MigrationWiz covers and which ones require a separate process?

#BitTitan #MigrationWiz