In-Place Exchange 2007/2010/2013 To Exchange 2013/2016 Migration Procedure
Important: Migration to Exchange 2016 is available only
This article describes the process of In-Place migration from Exchange 2007/2010 to 2013/2016 and 2010/2013 to 2016.
The majority of services is migrated automatically unless specified in the table below.
Migration pre-requisites:
End-user experience:
|
Following services are manually migrated by Intermedia to Exchange 2013/2016:
An assigned Migration Concierge from dedicated migrations team will assist with the above. Following services cannot be migrated to Exchange 2013/2016:
|
To initiate In-place Migration, contact your Account Manager or Sales team.
Once In-place Migration Wizard is enabled on your account you can start migration by navigating to HostPilotĀ® Control Panel > Services > In-place Migration.
In-Place Migration wizard walks you through the migration in
Step 1: Check services
Step 2: Learn more about migration
Step 3: Prepare for data migration
Step 4: Data migration
Step 5: Cutover
Step 6: Configure email
Step 7: Finish
Step 1: Check services
You will see the preselected plan that includes most of your current services and some new. The plan can be changed after the migration is complete. You will be charged for the new plan at the 1st day of the month after the migration.
Step 2: Learn more about migration
You can find out more about the services that will not be migrated. If you need to keep data from the services you need to back them up. Click on the links to see the info about the ways to back up the services.
Note: The services that cannot be migrated will be uninstalled.
Step 3: Prepare for data migration
After this step, it is not possible to cancel the migration process.
You need to make sure that:
- Autodiscover records are in place for the domains.
- End users have Outlook client version 2007 or higher.
Note: If the
Note: you can manage pending requests from users under 'Manage pending service requests from your users'.
Step 4: Data migration
Objects are created on the new account and data migrated alongside with services.
Note: ETA for Data migration depends on the size of the account.
Once the data migration is completed you are prompted to confirm that you are ready for cutover.
Step 5: Cutover
During the Cutover the account cannot be managed via HostPilot only the migration wizard is available in the control panel at this step. End users will not be able to sign
- the MX records for the domains should be updated. For more information about MX records read the following article: What Is An MX Record? What Is The Correct Syntax For MX Records? What Is Priority?
- the Autodiscover record should be updated. Read the Knowledge Base article on What Is An Autodiscover Record And Why Do I Need It? for more information.
Note: If the
Also on this
Skype for Business or Lync clients
Step 7: Finish