Migration from Exchange Server to Office 365
I. Pre-migration activities
Below you will find the list of key points to be considered:
Step 1: (Optional) Add a custom domain to target Office 365
If you want to migrate to your own (custom) domain, you need to make sure that it's registered and verified in your target Office 365. If necessary, add your custom domain to the target Office 365 tenant and verify it.
Skip this step if you already have your own domain registered in the target Office 365 or you would like to migrate to the vanity domain (e.g. yourcompany.onmicrosoft.com) that was assigned to you by Microsoft when you created your target Office 365 tenant.
Step 2: (Optional) Recreate source Office 365 users in target Office 365
The program is able to automatically create mailbox-enabled accounts in the target Office 365, under the previously added custom domain. Our software will allow you to configure various options (e.g. assign an SMTP address pattern for the target mailboxes) when you configure your migration job. Learn more
If necessary, you can manually recreate all source users in the target Office 365 beforehand. All these target accounts have to be mailbox-enabled.
If you choose either to manually create the mailboxes or allow the program to prepare them for you, be advised that the account data (such as permissions) will not be migrated. However, if you set the program to automatically create new mailbox-enabled user in the target environment, there is an option to copy main AD attributes from the source user account. Learn more
Learn more about importing multiple users to Office 365 via CSV files
Step 3: Make sure the target Office 365 administrator's email address corresponds to the right domain
- Log in to the target administrator's Office 365 account.
- Go to Office 365 admin center.
- Choose Users > Active users from the menu on the left and the table with all organization users will display.
- Select the administrator's account and check in the User name / Email section if the address corresponds to the right domain.
- If not, click Edit, locate the drop-down menu that contains all available domains within your organization and select the domain you will be migrating to. Save the changes.
Step 4: Assign licenses on Office 365
Learn more about assigning licenses
Step 5: Installation of components required to install CodeTwo Office 365 Migration (the installation wizard will guide you through this process)
- MAPI CDO (MAPI Client and Collaboration Data Objects, required on any system except for systems with coexisting MS Outlook x86 older than version 2016)
- .NET 4.0 (required on any system, might be already installed)
- PowerShell 2.0 (or higher, must be installed on Windows Server 2008)
- Download Windows Management Framework Core (WinRM 2.0 and Windows PowerShell 2.0) for Windows Server 2008
- Newer Windows releases (Windows 7 or higher, Windows Server 2008 R2 or higher) already have PowerShell 2.0 (or higher) built-in.
- Small Business Server 2008 (SBS2008) users might stumble upon a problem with installing PowerShell. See our Knowledge Base article on that.
Step 6: Installation of CodeTwo Office 365 Migration
The program needs to be installed and activated on a machine within the source server domain.
Please note that it is recommended that you install the migration tool directly on the source server except Windows Server 2003 and old machines - read why.
II. Migration process
Step 1: Connect to the source server
Once the program's installation is completed, you will see the Dashboard view. Click Create a new migration job link on the How to start card. Select the source server type: Exchange. The create Exchange migration job wizard will open. Set the name of the job and hit Next to proceed to the Source mailboxes step. If this is your first migration job, you will need to configure connection to your on-premises Exchange Server which will be used as the source of the migration. Click Add new source connection and a wizard will open. First, choose a protocol. If you migrate via the MAPI protocol, you need to go through the steps below:
- Service account - in this step, the program creates a service responsible for accessing mailboxes selected for migration. As the service works under the administrator's MAPI profile, enter the administrator's email address and password. Note that this user needs to belong to Domain Admins group. By default, the currently logged administrator's email address is filled automatically. However, you can change it by clicking Browse and selecting another user's email address from the picker.
- Connection method - there you can allow the program to automatically recognize the Exchange Server located within your network or select it manually from the picker.
- Configuration - this step configures your source server connection based on the entered settings.
If you want to configure connection to the source Exchange Server via EWS, read this article for guidelines.
If all data has been correctly entered, the Source server mailboxes should be listed later.
Step 2: Select mailboxes you want to migrate and define target connection
After successfully configuring the source connection, you will get back to the migration job wizard.
The Source mailboxes step now allows you to include or exclude mailboxes by using multiple filters. You may, for example, include all users' mailboxes from a particular Organizational Unit or Active Directory group. By default program includes All users along with the Public Folders as it is a most common scenario. Choose the mailboxes you want to migrate and proceed to the next step (Target mailboxes).
Now set up a new target server connection by choosing Add new target connection... from the Target server drop-down menu. A simple wizard will open.
- Admin's credentials - specify the UPN and password of the target Office 365 administrator (see this article for requirements). Enter the admin's credentials and move on to Configuration.
- Configuration - this process configures the Office 365 target server connection.
- Once the configuration ends successfully, you will see green check marks. If any errors appear, see Troubleshooting.
- Before you finish, you can test connection to your target server. Use the Test link, select an Office 365 user and click Test. The program will check if the administrator has impersonation access permissions to a chosen target mailbox. If these rights are successfully granted, you will be notified about that.
After your connection is established, click Finish and proceed to the next step (Match mailboxes).
Step 3: Match target and source mailboxes
Matching the source with the target mailbox can be done in two ways: automatically via the built-in Automatch feature or manually. Either way, hit the Match mailboxes button.
To match manually a single mailbox, click on Click to match target link in the Target user mailbox column and choose most appropriate option for this user. After selecting an option you may be asked to provide further details (e.g. password for newly created users). The available approaches are:
- Create a new user - to create both Active Directory user and corresponding mailbox, using the defaults values that you can also change.
- Choose an existing user from the list - to select an existing user in the target environment that does not have mailbox created yet.
- Manually specify the mailbox address - this option should be used in the case you are unable to list the target environment.
However, when it comes to match hundredths of mailboxes the process may be extremely time consuming. To automatically set the best available actions for desired users, simply select them on the list (you can use Ctrl+A shortcut to choose all entries) and eventually hit Automatch. Select desired options and start the process.
What is more, you can define what type of Office 365 license is going to be assigned for particular users.
When you have matched all your mailboxes you can continue to configure additional options.
Step 4: Customize all necessary aspects of the migration job
You may configure the following additional options:
- Scheduler - allows you to set the job to be automatically started in desired period of times, so you do not have to control it manually.
- Time filter - is used to exclude items that are older or newer than a particular date.
- Folder filter - may completely exclude specific folders from the migration process.
- Advanced settings - provides an option to define how many mailboxes should be migrated at same time. This number should correspond to the amount of CPU cores.
Step 5: Start the migration
Move on to the JOBS tab and click Start on the toolbar to begin the migration. Once you start the migration, all items from the source mailboxes will be migrated to their corresponding target mailboxes.
The migration processing time depends on several different factors, e.g. the number of mailboxes and items, the speed of internet connection, EWS throttling settings. We have published more details here.
Step 6: Check if the number of migrated items in the target mailbox folder corresponds to its equivalent on the source server
If you notice any missing items in the target mailbox restart the migration by using the Rescan feature.
Please be aware that the program does not migrate some specific folders at all. Those are i.e. Sync Issues or ones created while putting a mailbox on a litigation hold.
If any problems appear during the migration process they will be indicated by the yellow or red triangle visible in the Migration Status column in the main window of the program. Details of the problems may be checked in the diagnostic files.
Step 7: Check if there are any new items in the source mailbox after migration
Once the migration is finished and you have noticed that some new items appeared in the migrated source mailbox, just restart the migration by using the Rescan feature. Please keep in mind that the Rescan feature uploads only new items, not the changed ones.
III. Post-migration cleanup
Step 1: MX records
Change MX records to enable mail flow to new servers. Please note that this process may take several hours.
If any new items appear in a source mailbox while the MX records are being changed, it is possible to migrate them after the records migration process is completed. It can be done via the Administration Panel of the program by choosing the Rescan feature.
Step 2: The previous domain
Disconnect the previous domain.
If you have any problems with disconnecting your domain, please consult your Domain Provider.