Source and Target Exchange Organizations
On-Premises Migration
On-premises Exchange migration involves moving mailboxes (including calendars and free/busy status information) and public folders. The following table shows the supported paths for on-premises migration. For details about the specifics of mailbox, calendar and public folder synchronization, including handling of different Exchange versions, see the Mailbox Migration Process and Calendar Synchronization Process topics in the Migration Manager for Exchange User Guide.
Microsoft Exchange 2003 Service Pack 2 or later |
Yes |
Yes |
Yes |
No |
No |
No |
Microsoft Exchange 2007 Service Pack 2 or later |
Yes |
Yes |
Yes |
No |
No |
No |
Microsoft Exchange 2010 Service Pack 2 Rollup 6 or later |
Yes |
Yes |
Yes |
Yes |
Yes |
No |
Microsoft Exchange 2013 Cumulative Update 10 (CU10) or later |
Yes |
Yes |
Yes |
Yes |
Yes |
No |
Microsoft Exchange 2016 |
Yes |
Yes |
Yes |
Yes |
Yes |
No |
Microsoft Exchange 2019 |
No |
No |
Yes
|
Yes
|
Yes
|
Yes |
|
NOTE:
|
|
TIP: How to migrate Exchange 2007 to Exchange 2016/2019 via Native Move
In order to migrate Exchange 2007 to Exchange 2016/2019 via Native Move, use Exchange 2010 or Exchange 2013 as an intermediary migration step.
- Install Exchange 2010 or Exchange 2013 in your Exchange 2007 environment.
- Perform the migration from Exchange 2007.
- Migrate the resulting Exchange 2010 / 2013 to Exchange 2016/2019.
|
Cloud Migration
Mailbox, calendar and public folder synchronization to Microsoft Office 365 can be performed from the following Exchange versions:
- Microsoft Exchange 2019
- Microsoft Exchange 2016
- Microsoft Exchange 2013 Service Pack 1 or later
- Microsoft Exchange 2010 Service Pack 2 Rollup 6 or later
- Microsoft Exchange 2007 Service Pack 2 or later
- Microsoft Exchange 2003 Service Pack 2 or later
|
NOTE: Migration Manager also supports certain migration scenarios that involve hybrid deployments as migration destination. For detailed information, refer to the Hybrid Migration Scenarios section of Migrating to Microsoft Office 365 document. |
|
NOTE: Migration to Office 365 China tenants (operated by 21Vianet) and Office 365 Germany tenants (operated by T-Systems) is not supported. |
Exchange Servers
Migration Manager for AD supports the following Microsoft Exchange Server versions for Active Directory migration, synchronization and processing (by Active Directory Processing Wizard and by Exchange Processing Wizard):
- Microsoft Exchange Server 2019
- Microsoft Exchange Server 2016
- Microsoft Exchange Server 2013
- Microsoft Exchange Server 2010
- Microsoft Exchange Server 2003
Resource Updating Manager
- Resource Updating Manager can update computers running one of the following operating systems:
- Microsoft Windows Server 2019
- Microsoft Windows Server 2016
- Microsoft Windows Server 2012 R2
- Microsoft Windows Server 2012
- Microsoft Windows 10 (x86 and x64 editions)
- Microsoft Windows 8.1 (x86 and x64 editions)
- Microsoft Windows Server 2008 R2
- Microsoft Windows Server 2008 (x86 and x64 editions)
- Microsoft Windows 7 (x86 and x64 editions)
- Microsoft Windows Vista (x86 and x64 editions)
- Microsoft Windows Server 2003 (x86 and x64 editions)
- Microsoft Windows XP (x86 and x64 editions)
- Microsoft Windows 2000
|
NOTE:
- On computers running Windows Vista or Windows 7, before you start resource processing, you are required to set the Remote Registry service startup type to Automatic (for example, using Group Policy).
- To process computers running Windows Server 2008 R2 Server Core without the WOW64 feature installed, you must either configure the Process computers remotely option or run Vmover (x64 edition) directly on these computers.
- Resource Updating Manager does not support processing of Dynamic Access Control (DAC) on computers running Windows 8.1 or higher and Windows Server 2012 or higher.
|
- Resource Updating Manager supports processing of IIS up to version 10.0.
- To process COM+ permissions remotely configure the following:
- Install the COM+ Network Access feature on computers running Windows Server 2008 or Windows Server 2008 R2. To install the COM+ Network Access feature in the Application Server role, use Server Manager.
- Configure firewall settings to allow COM+ Network Access, as follows: on computers running Windows Server 2008 enable the COM+ Network Access predefined firewall rule; on computers running Windows Server 2008 R2 enable the COM+ Network Access and COM+ Remote Administration predefined firewall rules.
|
NOTE: On computers running Windows Vista and Windows 7, relevant predefined firewall rules are not available. |
Systems Management Servers
The SMS Processing Wizard processes the following Systems Management Servers:
- Microsoft Systems Management Server 2003
- Microsoft System Center Configuration Manager 2007