On-Premises Exchange 2007+ to On-Premises Exchange 2010+ Migration Guide

Introduction

This is the complete onboarding task flow for migrating mailboxes from On-Premises Exchange 2007 to Exchange 2010, 2013 or 2016. Complete each step in the order listed. Links to corresponding Knowledge Base articles are provided.

  • Note: DeploymentPro currently can only officially be used with migration projects where Office 365 is the Destination. If using DeploymentPro with Exchange (either On-Premises or Hosted) as a Destination, then a Proof Of Concept should be run first.

    Exchange environments can have complex AutoDiscover settings, along with UPN and SMTP address mis-matches, which can require troubleshooting and reconfiguration before DeploymentPro can be made to work against such environments.

    A Proof Of Concept will uncover any complications. 

If your Source server is running Exchange version 2003, or Small Business Server (SBS), refer to the On-Premises Exchange 2003/SBS to On-Premises Exchange (versions 2007 and later) Migration Guide article for more information.

If migrating from Exchange 2010+ instead of Exchange server 2007, the steps will be the same. However, when preparing your Source server, you should follow the instructions under Option 1 in the How do I disable the throttling policy on Exchange? article to disable throttling for the admin account that is being used for migration.

The MSPComplete section includes steps to deploy the Device Management Agent (DMA) to end users. Deploying DMA to end users is a prerequisite if you will be using DeploymentPro.

We strongly recommend that you use DeploymentPro to reconfigure the Outlook profiles in this migration scenario.

This migration guide contains the necessary steps to perform the actual migration, but there are many steps to preparing for migration. If this is your first time performing a migration, we have created a Migration Planning & Strategy Guide to walk you through planning, set-up, and general migration best practices.

To discover what items are moved with MigrationWiz in this scenario, and which items will not be moved, see Moved Items. Note that these items will vary by source and destination, so check the proper environment listings carefully.

MigrationWiz is a migration tool, not a syncing tool. If changes are made at the source after migration, they will not sync to the destination, nor will changes made at the destination sync to the source. We do not have “live” monitoring of changes (as with a sync agent) and we cannot handle scenarios such as conflict resolution without user interaction.

  • Note: DeploymentPro is included with the User Migration Bundle license. DeploymentPro cannot be purchased as a standalone service license, and it cannot be added to the single-use mailbox migration license. If you wish to remotely configure Outlook mail profiles using DeploymentPro after a migration, purchase the User Migration Bundle license.

Important: It is not possible to install Exchange 2016 into the same forest as an Exchange 2007 server. Therefore, it is imperative to complete all the prerequisite steps (as listed below) before beginning your migration project. More details can be found in the Can't install Exchange 2016 in a forest that contains Exchange 2007 servers TechNet article.

We are not able to support migrations with two-factor or multifactor authentication. 

 

Prerequisites

 

Prepare the Source Environment

  1. Set up an admin account for migration on the Source Exchange mailbox server. Refer to the How do I create an administrator account for login? article for more information.
  2. OWA must be working on the Source Exchange server. Refer to the How do I verify if my OWA URL is correct? article for more information.
  3. Test mailbox access. Refer to the How do I test mailbox access? article for more information.
  4. Set up router ports for OWA traffic. Set different OWA URLs for each environment and configure router ports to accept inbound/outbound mail traffic for those OWA URLs. Refer to the How do I set up router ports for OWA traffic when performing an On-Premises Exchange to On-Premises Exchange migration? article for more information.

 

Prepare the Destination Environment

  1. Set up user accounts.
  2. Create an admin account for migration that has full access permissions to all mailboxes. Refer to the How do I create an administrator account for login? article for more information.
    • Set up a remote PowerShell session with Exchange 2010+. Refer to the How do I set up a remote PowerShell session with Exchange 2010+? article for more information.
    • To manually grant administrative access for migration, execute the following PowerShell command in the Exchange PowerShell Console:
      Get-Mailbox -ResultSize Unlimited | Add-MailboxPermission -AccessRights FullAccess -Automapping $false -User MigrationWiz
      Notes:
      • In the PowerShell script above, change the -User account to match the name of the admin account that was set up for migration.
      • Any user account that is a part of the domain administrator, schema administrator, or enterprise administrator groups will not have any administrative rights to mailboxes, no matter how many permissions are granted. A security default of Exchange Server is to explicitly deny any user that is a member of these groups. This is why we recommend creating a new user account specific for migration.
  3. Disable throttling against the admin account. Refer to Option 1 in the How do I disable the throttling policy on Exchange? article.
  4. Verify mailbox accessibility using EWS. Refer to the How can I verify mailbox accessibility using EWS? article for more information.
  5. If you want to be able to migrate messages with attachments larger than 10MB, the following limits need to be increased:

 

MSPComplete Steps

  1. Create the customer. Refer to the View, Add, and Edit Your Customers article for more information.
  2. Create the Source and Destination endpoints. Refer to the View, Add, and Edit Customer Endpoints article for more information.
    • For the Source endpoint:
      • Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select Exchange Server 2003+
      • Enter the OWA URL. Refer to the How do I verify if my OWA URL is correct? article for more information.
      • Click the Provide Credentials radio button, and enter the admin account credentials for the account that was set up under the "Prepare the Destination Environment" section of this guide.
    • For the Destination endpoint:
      • Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type select Exchange Server 2003+
      • Enter the OWA URL. Refer to the How do I verify if my OWA URL is correct? article for more information.
      • Click the Provide Credentials radio button, and enter the admin account credentials for the account that was set up under the "Prepare the Destination Environment" section of this guide.
  3. Purchase licenses. We recommend that you purchase the User Migration Bundle license for this migration scenario. User Migration Bundle licenses allow multiple types of migrations to be performed with a single license. They also allow DeploymentPro to be used to configure Outlook email profiles. Refer to these articles for more information:
  4. Deploy DMA to users. Once DMA has been deployed to users, check the Users tab in MSPComplete. This will be populated with the user accounts that have DMA installed. DMA can be deployed by either of these options:

 

DeploymentPro Steps

  1. Launch DeploymentPro.
    1. Go to All Products > Device Management, then click DeploymentPro on the far left and follow the prompts to launch.
    2. Select a customer from the list by clicking on the customer name.
      Note: The status column will show enabled when a customer account has had DMA deployed.
    3. Configure customer DeploymentPro module:
      1. Enter the Domain.
      2. Select the Destination endpoint.
      3. Checkmark the Auto-populate box.
      4. In the Client Interface Configurations section, upload your company logo and add supporting text.
        Note: We strongly recommend doing this, because this is the logo and text that end users will see in a desktop pop-up when they are prompted to reconfigure their Outlook profiles. If you do not upload your own logo, the default BitTitan logo will be included instead.
      5. Save and continue.
  2. Activate DeploymentPro module for users.
    1. Either select all users or select individual users.
      Note: DeploymentPro is included with the User Migration Bundle license. DeploymentPro cannot be purchased as a standalone service license, and it cannot be added to the single-use mailbox migration license. If you wish to remotely configure Outlook mail profiles using DeploymentPro after a migration, purchase the User Migration Bundle license.
    2. Click the Schedule Cutover button.
  3. Schedule profile cutover date.
    • Set the date and time for the Outlook profile configuration to occur, and click the Schedule Cutover button.
      Notes:
    • The DeploymentPro module will install on user devices immediately and then run silently until this date.
    • The profile cutover date should be set to a date and time that is shortly after MX record cutover.
  4. On the profile cutover date, users will be guided through the reconfiguration of their Outlook profile.

 

MigrationWiz Steps

  1. Create a Mailbox Migration project. Read the How do I create a new migration project? article for more information.
  2. Add the accounts (also referred to as "items") that will be migrated to the project. Refer to the How do I add items to my migration project? article for more information.
  3. Set the Project Advanced Options. Refer to the What project Advanced Options are available? article for more information.
    • The following options are the most valuable for this migration scenario:
      • Set Maximum concurrent migrations. If the Source server has enough server resources, set this parameter based on the bandwidth guideline of three (3) mailboxes per 1MBPS of bandwidth. Therefore, for example, if there is a 10MBPS connection, we recommend setting the maximum concurrent migrations parameter to be 30. If the Source server has very few available server resources (e.g., it is running low on memory or it has a very high CPU utilization), we recommend setting this value to a lower number to avoid overwhelming the Source server with requests.
  4. Run Verify Credentials. Refer to the How do I verify credentials? article for more information.
  5. Notify users that a migration is occurring. Send email to all users telling them the time and date of the migration.
  6. Pre-Stage pass: Select the users > Click the Start button from the top, and select Pre-Stage Migration > Under the Migration Scheduling section, from the drop-down list, select 90 days ago > Click Start Migration. Refer to the How do I start a migration? article for more information.
  7. MX Record Cutover. Change over MX records on the DNS providers' portal. Also, include the AutoDiscover (CName) setting.
  8. Send email to end users to let them know what to expect for their Outlook profile reconfiguration. If using DeploymentPro, refer to the Sample email to send to users before their Outlook profile is reconfigured article for some sample text and screen shots that can be included in this email.
  9. Full (Delta) pass: Select the users > Click the Start button from the top, select Full Migration > Click Start Migration. Refer to the How do I start a migration? article for more information.
  10. Run Retry Errors. Refer to the How do I retry failed items? article for more information.
  11. Look through the user list and click any red "failed migration" errors. Review the information and act accordingly.
  12. If problems persist, contact Support. Refer to the How do I get support for your products? article for more information.
  13. If not using DeploymentPro, users must create new Outlook profiles, set up their signatures again, and reattach any PST files that were attached to their previous profile.
  14. Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. Refer to the How do I request statistics for my migration project? article for more information.

 

Was this article helpful?
1 out of 1 found this helpful