Are your OneDrive for Business jobs failing because the SPO personal site URL format does not match what MigrationWiz expects?

MigrationWiz maps OneDrive for Business migrations using each user SharePoint Online personal site URL, not UPN or SMTP address. The source URL is built from the tenant SPO my-site host plus the personal site path, where UPN special characters are converted to underscores. The destination URL follows the same pattern with the target tenant name substituted.

The failure I see most often is a subtle URL string mismatch: teams correctly convert the period separator in the source UPN to an underscore, but miss that a hyphen in the domain portion of the email address also needs to become an underscore in the SPO URL path. With one character wrong, MigrationWiz may accept the endpoint during configuration and then fail at the item level when it attempts to bind to the source personal site.

In my experience, OneDrive migrations often run alongside M365 and Teams inside 45-day acquisition windows, so there is not time to discover URL mapping problems after jobs are already submitted.

How are you generating and validating SPO personal site URLs before uploading them into MigrationWiz?

#BitTitan #MigrationWiz