Office 365 to On-Premises Exchange 2007, 2010, 2013, or 2016 Migration Guide
- This is the complete onboarding task flow for migrating mailboxes from Office 365 to On-Premises Exchange, versions 2007, 2010, 2013, or 2016.
- Complete each step in order. Links to corresponding Knowledge Base articles are provided.
- 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.
- DeploymentPro can be used to configure the Outlook profiles. Note: DeploymentPro requires licenses to be purchased before it can be used. Refer to Scenario 2 in KB004875 to read why it is recommended (but not mandatory).
Prepare the Source Environment
- Create an administrator account in Office 365 to be used for migration, or use the global admin account for the tenant. KB004948
- Export the user list to a CSV file. This can be used when bulk-adding users to your MigrationWiz project later. You can copy and paste the user list into the Source and Destination Email column within your MigrationWiz project dashboard under Add > Bulk Add. Steps: From Office 365 admin portal > Users > Active Users > Export > Continue.
Prepare the Destination Environment
- Set up the user accounts.
- Create an admin account for migration that has full access permissions to all mailboxes. KB004725
- Set up a remote PowerShell session with Exchange 2010+. KB005111
- 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
Disable throttling against the admin account. Refer to Option 1 in KB004945. Note: This is only required if your Destination server is running Exchange versions 2010 or later.
Verify mailbox accessibility using EWS. KB004304
If you want to be able to migrate messages with attachments larger than 10MB, the following limits need to be increased:
- In the PowerScript 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.
- Increase maximum accepted content length. KB004609
- Increase maximum receive message size. KB004532
- Increase maximum accepted request length. This is only valid if your Destination server is running Exchange 2007. KB004610
- Create the customer. KB005421
- Create the Source and Destination endpoints. KB005427
Purchase licenses. From your MSPComplete dashboard, click on Purchase > Mailbox Migration > select MigrationWiz-Mailbox and enter the number of licenses you wish to purchase. Note: Check to see if there are any available bundles for discounts (e.g., MigrationWiz-Mailbox and DeploymentPro Bundle). KB004647
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:
- For the Source endpoint:
- Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select Office 365.
- Click on the Provide Credentials radio button, and enter the admin account credentials. Note: This should be a global admin account. If creating a separate admin account for the purpose of migration, refer to the Office 365 section in KB004725.
- For the Destination endpoint:
- Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type select Exchange Server 2003+
- Enter OWA URL KB004392
- Click on the Provide Credentials radio button, and enter the admin account credentials for the account that was set up under the Prepare The Destination Environment of this guide.
- Via Group Policy Object (GPO). Note: This is the recommended methodology, because no end user interaction is required. KB005412 video
- Via email. KB005411
- Launch DeploymentPro.
Activate the DeploymentPro module for users.
- Go to All Products > DeploymentPro and follow the prompts to launch.
- 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.
- Configure customer DeploymentPro module:
- Enter Domain.
- Select the Destination endpoint.
- Checkmark the Auto-populate box.
- 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.
- Save and continue.
Schedule profile cutover date.
- Either select all users (by checkmarking the box to the left of the Primary Email column heading), or select the individual users (by checkmarking the boxes to the left of the user email addresses). Note: You will need to purchase DeploymentPro licenses for each user that will be using DeploymentPro. KB004647
- Click on the Run Module button.
On the profile cutover date, users will be guided through the reconfiguration of their Outlook profile.
- Set the date and time for the Outlook profile configuration to occur, and click on the Run Module button.
- 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.
Watch this video to see a walk-through of the steps below.
- Create the Mailbox Migration project. KB004380
Add the accounts (also referred to as "items") that will be migrated to the project. KB004842
Set the Project Advanced Options. KB004834
- Create the Mailbox Migration project > Select the customer > Select the Source endpoint > Select the Destination endpoint.
Run Verify Credentials. KB004511
Notify users that a migration is occurring. Send email to all users telling them the time and date of the migration.
Pre-Stage pass: Select the users > Click on 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 on Start Migration. KB004938
MX Record Cutover. Change over MX records on the DNS provider's portal. Also include the AutoDiscover (CName) setting.
Send email to end users to let them know what to expect for their Outlook profile reconfiguration. If using DeploymentPro, refer to KB005799 for some sample text and screen shots that can be included in this email.
Full (Delta) pass: Select the users > Click on the Start button from the top, select Full Migration > Click on Start Migration. KB004938
Run Retry Errors. KB004658
Look through the user list and click on any red "failed migration" errors. Review information and act accordingly.
If problems persist, contact Support. KB004529
If not using DeploymentPro, users must create new Outlook profiles, and set up their signatures again, and reattach any PST files that were attached to their previous profile.
Click on the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. KB004626
- The following options are the most valuable for this migration scenario:
- Set to use impersonation at the Source. Checkmark the Use impersonation at Source box. KB004727
- If this is a large migration project, increase the value for Maximum concurrent migrations, under the Performance section, e.g.,1000. Note: This can be set to a high number if impersonation is set to be used at the Source, and your Destination Exchange server has plenty of resources available.