Fix Exchange Online Migration Back to Exchange 2007
Question details
Investigate a failed mailbox move from Exchange Online back to Exchange 2007 and determine whether recipient attributes or hybrid support requirements are responsible.

- Product
- Microsoft Exchange Online and Exchange Server 2007
- Device & OS
- not provided
- Scenario
- An administrator is moving a mailbox from Exchange Online to an on-premises Exchange 2007 environment.
- Observed behavior
- The move pauses during synchronization after a transient failure involving an Active Directory attribute conversion error.
Identify the affected mailbox and migration batch, and confirm that the corresponding user exists in on-premises Active Directory. Have an Exchange or identity administrator review the current recipient configuration and the supported migration path before changing attributes.
Review the Migration Error and Recipient Attributes
Use the migration report to identify the failing attribute, then correct obsolete recipient values only under administrator guidance.
Recipient attributes can affect mailbox identity, synchronization, and mail routing. Do not clear them as a group: determine which values are incorrect for the affected recipient and use supported Exchange management tools where possible.
In Exchange Online PowerShell, run Get-MigrationBatch -Identity "<batch name>" and review the batch status and reported error.
Run Get-MigrationUserStatistics -Identity "<user email address>" -IncludeReport | Format-List and identify the attribute or conversion error in the report.
With an Exchange or identity administrator, inspect the corresponding on-premises Active Directory recipient. Values to review may include homeMDB, homeMTA, msExchHomeServerName, msExchVersion, msExchRecipientDisplayType, msExchRecipientTypeDetails, msExchRemoteRecipientType, and targetAddress.
Document the current values and approved rollback procedure. Using the appropriate Exchange management tools, change or clear only attributes the administrator has confirmed are obsolete and safe to modify.
Allow any required directory synchronization to complete, then use the Exchange admin center or Exchange Online PowerShell to resume the affected migration and review its status.

Verify the Supported Hybrid Migration Path
Use this check before retrying if the destination is Exchange 2007 or the hybrid deployment relies on an older Exchange server.
Use WPS Office for Documents During Your Exchange Migration
WPS Office is a free, lightweight Office alternative with a familiar interface and Microsoft Office format compatibility for a seamless transition to everyday document work. It does not perform or repair Exchange mailbox migrations.

Frequently Asked Questions
Where can I find the detailed mailbox migration error?
In Exchange Online PowerShell, run Get-MigrationUserStatistics -Identity "<user email address>" -IncludeReport | Format-List and inspect the report for the failing attribute or conversion error.
Should I clear all Exchange recipient attributes before retrying?
No. Attributes such as homeMDB and targetAddress can be necessary for mailbox configuration or routing. Have an Exchange or identity administrator identify and correct only values confirmed to be obsolete.
Does adding Exchange 2010 make a move to Exchange 2007 supported?
Not necessarily. Exchange 2010 SP2 or later was a historical hybrid requirement, but both Exchange 2007 and Exchange 2010 are out of support. Check Microsoft's current requirements and plan a supported path with an Exchange specialist.
Can WPS Office fix the Exchange migration error?
No. The error must be investigated in Exchange, Active Directory, and the hybrid configuration. WPS Office can be used to edit related documents and checklists.




