Fix IMAP Migration Importing Email into the Wrong Microsoft 365 Mailboxes
Question details
The user needs to ensure that an IMAP migration imports each user's messages into the correct Microsoft 365 mailbox.

- Product
- Microsoft 365 Data migration
- Device & OS
- not provided
- Scenario
- An administrator is migrating mail from an IMAP server to Microsoft 365 using a migration CSV file.
- Observed behavior
- Imported messages may appear in every destination mailbox instead of only the intended mailbox.
Identify the affected migration batch and obtain the source mailbox paths and destination addresses for each user. Check your IMAP provider's documentation for its mailbox path format and the authentication method used by the migration.
Verify the UserRoot paths and mailbox mappings
Use this approach when messages appear in multiple destination mailboxes and the source mailbox paths may be missing or incorrect.
UserRoot identifies a source mailbox path in configurations that use it. Confirm with your IMAP provider and Microsoft's current migration documentation how UserRoot must be supplied; it is not a universal column for every IMAP migration CSV.
In the Microsoft 365 admin center, open Settings > Data migration and check the available IMAP migration option. Confirm with the source provider that its server supports the required IMAP access and authentication.
Open the migration CSV in a spreadsheet or text editor. Check that each destination email address is paired with the correct source account and credentials.
Where your migration configuration requires a UserRoot attribute, add or correct it according to the provider's instructions. A path such as /users/alberta is an example; use the actual path for each source mailbox.
Use the Microsoft 365 admin center's Data migration workflow to validate the corrected file and test a small batch. Check the destination mailboxes before migrating the remaining users.

Consider another Microsoft 365 migration method
Use an alternative if the IMAP server or its authentication method is not supported, or the mapping problem persists.
Review migration spreadsheets with WPS Office
WPS Office is a free, lightweight alternative for reviewing spreadsheet data in a familiar interface. It supports common Microsoft Office formats for an easier move between office suites, but it does not fix or run Microsoft 365 email migrations.

Frequently Asked Questions
Why did messages appear in multiple Microsoft 365 mailboxes?
The migration may be accessing the same source mailbox for multiple rows because the source account or mailbox path is incorrect. Review the CSV mappings and any required UserRoot values against your IMAP provider's configuration.
Does every IMAP migration CSV need a UserRoot column?
No. The required CSV fields and the way a mailbox path is supplied depend on the migration method and source server. Check Microsoft's current IMAP migration instructions and your provider's documentation before adding the attribute.
Will correcting the CSV remove messages already imported into the wrong mailbox?
No. Correcting the mapping helps prevent further incorrect imports, but messages already imported must be reviewed and handled separately.
Can the Microsoft 365 Import service connect directly to my IMAP server?
The Import service is used to import PST files, not as a direct replacement for an IMAP connection. Check whether you can export the source mail to PST and follow Microsoft's Import service requirements.




