CodeTwo Exchange Cross Forest Migration

Mailbox Migration in cross forest scenarios is always been a difficult , challenging and will  definitely vary according to the environment, scenario and requirement basis.

In this article i would like to explain the cross forest migration scenarios using the code two exchange migration tool.

In this example we are trying to migrate the mailbox from source different forest to target different forest using the CodeTwo migration tool.

The source will be Exchange 2010 SP3 and the Target will be Exchange 2013 CU10

Lets see the prerequisites before we start this migration job:

Code two says only network and EWS connectivity is enough. But its better to have all these below things in place before starting the migration so that migration can be completed in the provided timeline.

1.Prepare a healthy network link speed for this migration from source to target.

2.Make sure All the required ports/connectivity are open between source Exchange   server\DCs to Target Exchange 2013/and DCs
3.Create a DNS name resolution in source as well as target using conditional forwarders        or by using dummy zones

4.Create AD trust between domains Source and target (Not Mandatory required only if you need to migrate Group)
5. Add the Target domain admin in the built in admin group of source domain.

6. Make sure the MRS proxy is enabled for cross forest move in the target or source domain according to your requirement pull or push
Set-WebServicesVirtualDirectory -Identity “\ews (default web site)” -MRSProxyEnabled $true

Perform the above action depending on the mailbox move you are going to Trigger.

7.Change the autodiscover SRV DNS record to point to Target domain

Once the above prerequisites are set in-place we have to download the software and install them

The setup is normal just need to install with the default settings. You need to install the software where the connectivity is reachable for the EWS .


a) You can install the CodeTwo setup either on the source forest or on the target based on your requirement.( Push migration or Pull Migration)

b) You should to be able to reach the EWS url of the target domain from the server where you are installing them.

Better to install them on the CAS server where you can reach the EWS of the other domain if  all the prerequisites are set in place.

You will get the welcome screen as below


You will run through a normal installation as below


On a successful completion of the installation you will get a below GUI



Now we need to configure the source and the Target domains in the setup

Inorder to perform that do the following steps

Configure the below settings as source where you have installed this application

Go to server connections and select source server

Here we have 2 options to establish a connection

First one will discover the source ews url automatically if its resolvable from the server where this software is installewd.

Second option where we need to manually enter the CAS server FQDN and EWS URL .


post which we will get the below screen


After successful configuration you will get a green signal as below.


The same procedure needs to be followed in the target domain as well .

Need to install the Target server as well


Once after the source and target domains are defined and successful you can create a new Migration Batch.

Good Features which have identified in this application are below

We have an option to choose the migration batch per OU , Users , Group etc..,



You have an option to auto-match the MEU as well

Note: You have to choose the option Auto-match selected mailboxes  only  if similar already existing users are present in the target domain on a different OU.


We have an option to schedule the migration as well  which is really good.


The amazing option which is found really beneficiary is below

This is something great option which will help in planning for a migration where we have a weak n/w bandwidth between the source and the forest. By having this we can very well plan a smooth migration without choking the network bandwidth in these kind of scenarios.



Finally we have an option to choose only the required items to migrate


This option is very amazing for scenarios where a company is merging or during acquisition.


Finally we can view the migration job status in the console as below

We have an option to manually choose the target mailbox as well.





It keeps us posted about the good status and bad status about the migration as well which is very good.

We also have an option to send notifications to admin mailbox about the migration status as well.


We have an option to set the maximum number of concurrent moves as well



As per my understanding this CodeTwo software uses an excellent coded API .When configured all the prerequisite for the cross forest migration this works in the background with the EWS and gives us these many options features during the migration.

This makes the migration job very smooth and keeps the admin informed about the migration status.We can customize the cross forest migration based on our requirement by using this tool.Once the migration is done you need to perform the normal procedure of shifting the MX records and you are done.

To get Started with them you can refer more on this  CodeTwo Migration

Thanks & Regards

Sathish Veerapandian

MVP – Office Services & Servers

6 thoughts on “CodeTwo Exchange Cross Forest Migration

  1. Mike March 10, 2016 at 1:26 pm Reply

    Great information. Would love to see this same process for an Exchange 2007 to Exchange 2016 migration cross-forest.


    • sathishveerapandian March 11, 2016 at 7:22 am Reply

      Haven’t done this R & D yet with this coexistence. Will do it in future and will post the results.


  2. Mike March 24, 2016 at 1:41 pm Reply

    Do you also have detailed steps that are required to setup connectors between the Source and Target when there is a coexistence period required? For example the following is one of the pre-req requirements for Ex2007 to Ex2016 migration:

    Step 3: Configure mail flow between the Source and the Target server
    Configure SMTP Connector on Exchange 2007
    Configure Send and Receive Connectors on Exchange 2010.
    Configure Send and Receive Connectors on Exchange 2013 (default Receive Connector is typically created during Exchange Server installation process)
    Configure Send and Receive Connectors on Exchange 2016 (default Receive Connector is typically created during Exchange Server installation process)


  3. Merti October 31, 2017 at 8:44 am Reply


    I’m looking at CodeTwo at the moment and I noticed that the migration targets need to be mailboxes. As both forest need a working mailflow during the migration I’m wondering how I can achieve that the source mailboxes still receive emails from the target forest until the final cutover.
    Normally I would creat MEU with prepare-moverequest and sync the data with new-moverequest autosuspend.


    • sathishveerapandian November 1, 2017 at 2:41 pm Reply

      Hi Merti the migration targets needs to be MEU only. The good thing is it will automatch the MEU


      • Merti November 3, 2017 at 8:43 pm

        Thanks foe your reply.

        Then I’ll have to check that out again; automatch wasn’t able to find the existing MEU and when I’ve entered the proxy address manually it also didn’t work ( no mailbox found).
        I’m also wondering who the target mailbox is defìned.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: