Migration scenarios

The main purpose of CodeTwo Exchange Migration is to allow you to perform a flawless migration of items from your existing Exchange/IMAP server(s) or from Office 365 to another Exchange environment. However, there are different ways how you can organize the entire migration process. This article will help you get to know them better so you can find the best solution.

Standard cutover

This is the most popular method, especially useful for small and mid-sized companies. Basically, you can use our software to migrate all mailboxes to your target environment in one step. Of course, you may apply different item filters regarding type or time. Once the migration process is complete, simply change the mail flow so that the new server handles it. Finally, use the Rescan button to migrate any new items that appeared on the old server during the migration. 

Quick cutover

If you have a mid-sized or huge company and you wish to allow users to work normally during the migration, this option might be the best. Instead of migrating everything at once, you can consider splitting the process into two steps. The main idea is to first migrate items from a desired period of time (e.g. last two months) and then change the mail flow so that your new server handles it. This can be done by creating a migration job with an appropriate time filter. Thanks to this approach your users will be able to continue their work, since all the most needed items will be available on the target environment. Of course, if there are any new items that appeared on the source server, you can upload them as well by using the Rescan button.

Once this initial migration is done, you can create a second job which will migrate the rest of your items (from other periods than those specified in the first job). What is more, if you do not want to affect the performance of the target server, you can schedule the job to run outside of working hours.

Gradual migration

This option might be useful for the companies which want to migrate their departments one by one. In a nutshell, you need to create multiple migration jobs - each job for all the mailboxes that reside in one particular department. This could be easily done by configuring appropriate mailbox filters. After one job is finished, you can move to another. Change the mail flow at any time and use the Rescan button to migrate any recent items from your source server.

One-way synchronization

Consider this approach if you need to keep both environments active for a longer period of time. Basically, after an initial migration (of any type) you can stay with your current mail flow settings. This could be useful for any companies running two domains: the older server handles the mail flow for the older domain, and the new server handles the mail flow for the new domain. By using the Rescan button you can upload the newest items (from the source server) to the target environment.

IMAP migration

As an alternative, our product allows you to perform IMAP migrations with all the previously mentioned scenarios. As your migration source you can also use the most common free mail providers, such as Google or Yahoo, or entire platforms like Zimbra. However, please note that due to the limitations of the IMAP protocol, only emails can be migrated. 

Double-hop migration

This particular scenario is popular in the case of Exchange migrations. Due to the limitations of Exchange, a native migration between Exchange 2003 and Exchange 2013/2016 is not possible. Therefore, you are forced to migrate your Exchange 2003 to a newer version (e.g. Exchange 2010) first and then migrate to Exchange 2013/2016. However, our software does not require a double-hop migration - you can migrate Exchange 2003 directly to Exchange 2013/2016.

Was this information useful?