Are you setting up your MigrationWiz destination endpoint before destination mailboxes are licensed and provisioned, and then wondering why jobs show complete with zero items migrated?

During destination endpoint setup, MigrationWiz checks that the credentials work. What it does not do at that stage is validate whether destination recipient objects actually exist. That means you can successfully create a destination endpoint for a tenant that has zero provisioned mailboxes, and you will not see an error at endpoint creation.

The problem appears when jobs execute. MigrationWiz authenticates to the destination tenant using the endpoint credentials, searches the destination directory for the recipient that matches the destination UPN in your user mapping, and then finds no provisioned mailbox. That results in an item-level error, while the job itself closes as complete with zero items migrated.

The tricky part is that three separate conditions can produce the same dashboard outcome: the source mailbox exists, the destination endpoint authenticates, but the destination mailbox is not provisioned, so the job shows completed status and zero items migrated.

Before you submit any MigrationWiz batch, pull the destination user list from the Exchange Admin Center or via Get-EXOMailbox. Confirm that every UPN in your MigrationWiz project maps to an active mailbox object, and verify Exchange Online licenses are assigned and not stuck in a pending provisioning state.

Are you verifying destination mailbox existence and Exchange Online license assignment before submitting your first MigrationWiz batch?

#BitTitan #MigrationWiz