Cross-Forest Migration Exchange 2010 to 2016

Want to do cross-forest mailbox move Exchange 2010 to Exchange 2016? Looking for a Microsoft Exchange 2010 migration? With the release of Exchange 2016, Microsoft has come up with the latest cloud-based enhancements. MS Exchange has come up with various beneficial features that make easy for users to manage and utilize their data accordingly. Therefore, to upgrade the version of Exchange most of the users need to move their database from Microsoft Exchange 2010 to 2016. In this write-up, we will walk through the process to execute the cross-forest migration Exchange 2010 to 2016 edition. Note: We will not work on withdrawing MS Exchange 2010 server. Moreover, we do not have any public folder on MS Exchange 2010, which requires migration to Exchange 2016 server.

Pre-Requisites for Cross Forest Mailbox Migration Exchange 2010 to 2016

There are some pre-requisites for Microsoft Exchange 2010 cross forest migration, which are required to be followed before execution as mentioned:

• Active Directory Schema
• Namespace for Exchange 2016
• SSL Certificate
• Hardware Sizing for Exchange 2016
• High Availability of Exchange 2016
• Mail flow
• End user Impact
• End user Communication
• Exchange 2010 Health Check

Technique for Exchange 2010 to 2016 Cross Forest Migration

Execute the mentioned steps for Microsoft Exchange 2010 cross-forest migration are as discussed:

1. Sign in to MS Exchange Administrative Center by using the admin credentials.
2. Direct to Recipients and click on Migration option.
3. Now, select +icon after that migrate to a diverse database.

4. Under choose users that you need to move, select an icon Add + to add users or simply you can upload the list of mailboxes by using CSV file.

5. From window of Select Mailbox, choose mailboxes, which is required to be migrated then, select + icon to add >> then OK.

6. Identify a name for new mailbox migration. Make sure that you have chosen an option to migrate both primary as well as archive mailbox. In case, you do not have an archive mailbox then, skip that option.
7. In the Target database, simply click Browse button and choose the target database of MS Exchange 2016 Server.

8. Choose an option to automatically begin the batch migration to start batch immediately. You can even uncheck an option as well as manually begin the batch further.
9. Plan for completion of Exchange mailbox migration, you can choose an option to automatically finish the batch migration. At the finalization phase, the mailbox will be unavailable for a small time. If you select to manually finish mailbox move, you can adopt when the move is confirmed and you can plan for a batch conclusion in after hours to escape end-user interruption.

Once the data migration is finished, an end user will obtain a pop-up message, which states " Administrator has made a change that requires you to restart outlook client." Once user restarts, the Outlook client will be connected to the mailbox on MS Exchange Server 2016.

Conclusion

There are many users who want to Microsoft Exchange 2010 to 2016 cross forest migration. Once all Exchange mailboxes have been moved to Exchange 2016 server then, you can plan for MS Exchange Server 2010 decommissioning to eliminate from messaging infrastructure. The above-written blog discussed the cross-forest migration Exchange 2010 to 2016. If still, you have any issue then, feel free to drop a comment below.