Are users opening post-cutover support tickets because their migrated destination mailboxes show folder layouts they were not expecting?

MigrationWiz migrates Exchange mailbox folders by translating MAPI well-known folder names from the source into the matching well-known folders in the destination. IPF.Note.Inbox maps to Inbox, IPF.Appointment maps to Calendar, and IPF.Contact maps to Contacts. User-created custom folders migrate as well, and their hierarchy is preserved as it appears in the source mailbox.

Where things get confusing is an edge case: when a source mailbox has custom top-level folders that use the same names as Exchange well-known folders. A user-created top-level folder named Archive, separate from the Exchange Online In-Place Archive or the Outlook AutoArchive folder, can end up in an unexpected location in the destination if MigrationWiz has to resolve that name collision.

During your test account pass, validate this scenario explicitly. Use a source account that includes custom top-level folders with well-known folder naming conflicts, and do not assume standard hierarchy behavior will cover non-standard naming.

Are you testing custom top-level folder migration in your MigrationWiz test account pass, specifically for well-known folder name conflicts?

#BitTitan #MigrationWiz