Are users missing from your MigrationWiz project after uploading the mapping CSV, with no error message explaining why they were dropped?

MigrationWiz uses a CSV to map source UPNs to destination UPNs: source SMTP address in column one and destination SMTP address in column two. The file needs to be clean, no BOM at the start, no trailing whitespace on addresses, and no blank rows between records.

The issue that catches teams most often is the BOM. If you save the file from Excel as CSV UTF-8, Excel inserts a byte order mark at the beginning. MigrationWiz then reads the first UPN in row one with that BOM prepended, cannot match it to the source tenant directory, and silently skips the user. The job still shows as complete, but with zero items migrated.

To avoid this, save the file as CSV comma delimited, not CSV UTF-8. Alternatively, open it in a hex-aware text editor and verify the encoding is UTF-8 without BOM before you upload.

After each upload, compare the number of rows in the CSV to the user count shown in the MigrationWiz project. If the numbers do not match, accounts were skipped without warning.

Are you validating the MigrationWiz project user count against the CSV row count after every mapping file upload?

#BitTitan #MigrationWiz