Introduction

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

• 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.

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.

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.

Before you begin your migration

• We are not able to support migrations with two-factor or multifactor authentication. 
• 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.
• 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.
• 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.

Migrations from Exchange 2010+

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 below to disable throttling for the admin account that is being used for migration.

Exchange Server has very low throttling policy limits. We recommend disabling the throttling limits during the migration. This is only relevant if throttling policies are enabled in the Exchange environment.

When migrating to Office 365, you cannot disable throttling on Office 365.

If you are creating or applying a throttling policy on Exchange, you will need to use delegation for this endpoint.

Option 1

Disable throttling against only the migrating account (if not using impersonation). This way, the admin account can migrate at a faster rate because it is not subjected to any throttling.

Use this option if using impersonation during the migration. If migrating using admin credentials, it is only necessary to disable throttling against the admin account, rather than all users.

If migrating mailboxes using administrative credentials at the Source, but not using impersonation, we recommend disabling throttling limits on this administrative account in order to improve the speed of migration.

We recommend the creation of a migration administrative account and disabling policy enforcement for this account.

Disable Admin throttling in Exchange Server 2010

To disable all throttling parameters for an admin account called "MigrationWiz":

1. On a computer that hosts the Microsoft Exchange Management Shell, open the Microsoft Exchange Management Shell.
2. Type the following command and press Enter.
   New-ThrottlingPolicy MigrationWizPolicy
3. Type the following command and press Enter.
   Set-ThrottlingPolicy MigrationWizPolicy -RCAMaxConcurrency $null -RCAPercentTimeInAD $null -RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC $null -EWSMaxConcurrency $null -EWSPercentTimeInAD $null -EWSPercentTimeInCAS $null -EWSPercentTimeInMailboxRPC $null -EWSMaxSubscriptions $null -EWSFastSearchTimeoutInSeconds $null -EWSFindCountLimit $null -CPAMaxConcurrency $null -CPAPercentTimeInCAS $null -CPAPercentTimeInMailboxRPC $null -CPUStartPercent $null
4. Type the following command and press Enter.
   Set-Mailbox "MigrationWiz" -ThrottlingPolicy MigrationWizPolicy

Exchange Server 2013 or 2016

To disable all throttling parameters for an admin account called "MigrationWiz":

1. Open the Exchange Management Shell.
2. Type the following command and press Enter.

   New-ThrottlingPolicy MigrationWizPolicy

3. Type the following command and press Enter.

   Set-ThrottlingPolicy MigrationWizPolicy -RCAMaxConcurrency Unlimited -EWSMaxConcurrency Unlimited -EWSMaxSubscriptions Unlimited -CPAMaxConcurrency Unlimited -EwsCutoffBalance Unlimited -EwsMaxBurst Unlimited -EwsRechargeRate Unlimited

4. Type the following command and press Enter.

   Set-Mailbox "MigrationWiz" -ThrottlingPolicy MigrationWizPolicy

Option 2

Disable throttling against all user accounts (if migrating using an admin account and using impersonation). This way the admin account can migrate at a faster rate because it impersonates user accounts, which are not subjected to throttling.

If migrating mailboxes using administrative credentials at the Source, and using impersonation, disabling throttling limits on all mailboxes will improve the speed of migration, but it is a security risk. The throttling limits are working together to protect an Exchange server from being overwhelmed by accepting and delivering messages.

Read Message Rates & Throttling before you execute the scripts below.

Exchange Server 2010

To disable all throttling parameters for all mailboxes:

1. On a computer that hosts the Microsoft Exchange Management Shell, open the Microsoft Exchange Management Shell.
2. Type the following command and press Enter.
   New-ThrottlingPolicy MigrationWizPolicy
3. Type the following command and press Enter. 
   Set-ThrottlingPolicy MigrationWizPolicy -RCAMaxConcurrency $null -RCAPercentTimeInAD $null -RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC $null -EWSMaxConcurrency $null -EWSPercentTimeInAD $null -EWSPercentTimeInCAS $null -EWSPercentTimeInMailboxRPC $null -EWSMaxSubscriptions $null -EWSFastSearchTimeoutInSeconds $null -EWSFindCountLimit $null -CPAMaxConcurrency $null -CPAPercentTimeInCAS $null -CPAPercentTimeInMailboxRPC $null -CPUStartPercent $null
4. Type the following command and press Enter.
   Get-Mailbox | Set-Mailbox -ThrottlingPolicy MigrationWizPolicy

The steps above will remove throttling policies against all user accounts at your Source. You still need to enable impersonation within your MigrationWiz project, so that the admin account can impersonate the user accounts during migrations, and so that the migrations use the bandwidth available to the individual user accounts, rather than just the bandwidth available to the admin account. 

Exchange Server 2013 or 2016

To disable all throttling parameters for all mailboxes:

1. Open the Exchange Management Shell.
2. Type the following command and press Enter.

   New-ThrottlingPolicy MigrationWizPolicy

3. Type the following command and press Enter.

   Set-ThrottlingPolicy MigrationWizPolicy -RCAMaxConcurrency Unlimited -EWSMaxConcurrency Unlimited -EWSMaxSubscriptions Unlimited -CPAMaxConcurrency Unlimited -EwsCutoffBalance Unlimited -EwsMaxBurst Unlimited -EwsRechargeRate Unlimited

4. Enter the following command and press Enter. 

   Get-Mailbox | Set-Mailbox -ThrottlingPolicy MigrationWizPolicy

The steps above will remove throttling policies against all user accounts at your Source. You still need to enable impersonation within your MigrationWiz project, so that the admin account can impersonate the user accounts during migrations, and so that the migrations use the bandwidth available to the individual user accounts, rather than just the bandwidth available to the admin account. 

Prerequisites

• Run the Active Directory Migration Tool (ADMT) to migrate objects over to the new server.
• Install Exchange 2013 or 2016 server into the Destination server.
• Create Exchange users on the new Exchange server.
• Set up router ports for OWA traffic. Set different OWA URLs for each environment, and configure the router ports to accept inbound/outbound mail traffic for those OWA URLs. 

Set up router ports

If you have multiple ports on your router:
Set it up like this:
Set different OWA URLS for each environment. Let’s say SBS Exchange 2003 server has OWA = owa.Sourcedomain.com and Exchange 2013 server has OWA = webmail.Destinationdomain.com

• The first router port would be configured with IP address 1, and accept inbound/outbound mail traffic for http://owa.Sourcedomain.com:443/owa
• The second router port would be configured with IP address 2, and accept inbound/outbound mail traffic on http://webmail.Destinationdomain.com:443/owa

If you have just one port on your router, as is the case with some small companies, then you’ll need to either set up port translation and port redirection to handle the traffic routing.
For example, you could add, say, port 4443 to accept traffic for webmail.Destinationdomain.com and leave port 443 to accept traffic for owa.Sourcedomain.com.

• Port translation would need to be configured on the router so that incoming traffic on port 4443 would then be translated to port 443.
• Port redirection would need to be configured on the router so that after translation this traffic would then be redirected (using port redirection) to the new (Destination) Exchange 2013 server.
• For traffic coming into port 443 there is no port translation. It is just redirected to the old Exchange 2003 (Source) server.

Prepare the Source Environment

Admin Account

Set up an admin account for migration on the Source Exchange mailbox server.

Create an administrator account in Exchange to be used for migration or use the global admin account for the tenant. The administrator account must have either full access to the user mailboxes or be granted impersonation rights. We recommend using impersonation as it will help reduce the likelihood of the migration being throttled by Microsoft. 

1. Open the Exchange Management Console.
2. Expand the Recipient Configuration
3. Right-click on the Mailbox
4. Click on New Mailbox.
5. Click on Next.
6. Click on Next.
7. Enter "MigrationWiz" as the first name.
8. Enter "MigrationWiz" as the user logon name, and optionally select a user principal name (UPN) domain.
9. Enter a password and confirm the password.
10. Click on Next.
11. Click on Browseto select a Mailbox database.
12. Click on Next.
13. Click on New.
14. Click on Finish.

To grant the account access, perform the following from the Exchange Server machine:

1. Open the Exchange Management Shell.
2. Enter the following command:
   -ResultSize Unlimited | Add-MailboxPermission -AccessRights FullAccess -User MigrationWiz

The above command needs to be applied each time a new mailbox is created, since permissions are set directly on each mailbox. The administrative account will not have access until the permissions are applied.

In the above script, the username "MigrationWiz" should be replaced with the name of the administrative account that was set up, by following the earlier instructions in this article.

This username is the Administrative Username that needs to be entered under project source or destination settings, within MigrationWiz, when checkmarking the box labeled: Use Administrative Login.

Test OWA Access

OWA must be working on the Source Exchange server.

There are some instances in which the login page for OWA is different than the actual OWA URL for the mailbox, as you may get redirected to a different server after logging in. To determine the true OWA URL, perform the following:

1. Close all browser instances. This ensures that all session state browser cache is flushed.
2. Open a new browser instance.
3. Navigate to your OWA login page.
4. Log in to OWA.
5. Once you see the inbox, copy the URL from the navigation bar of the browser. This is the exact OWA URL that should be entered into MigrationWiz​.

Another method for determining the OWA URL is to use the "whatismyipaddress" website to determine the company public IP address, and then add /owa to the end of it.

Now that your OWA URL has been determined, we need to ensure that the username and password combination work. The username and password that you use to log in to OWA is the exact same username and password that you should be entering into MigrationWiz. To determine if your username and password is working, perform the following:

1. Close all browser instances. This ensures that all session state browser cache is flushed.
2. Open a new browser instance.
3. Navigate to the same OWA login page as determined by Step 5 above.
4. Log in to OWA. Pay special attention to the login name, i.e.​,:
• Email address means "user@example.com" format.
• Domain\user name means "example\user" format.
• User name means "user" format.
5. Once you see the inbox, you have successfully logged into OWA.  Enter the exact same username and password used into MigrationWiz.

Test mailbox access

1. Browse to https://testconnectivity.microsoft.com. This is a Microsoft-owned tool.
2. If using Office 365, click on the Office 365
3. Select Service Account Access (Developers)and click on Next.
4. Specify the target mailbox email address.
5. Specify the service account user name (if using admin credentials on the connector, enter the exact same user name).
6. Specify the service account password (if using admin credentials on the connector, enter the exact same password).
7. Check Specify Exchange Web Services URL and specify the URL (example: https://server/EWS/Exchange.asmx).
8. If using Exchange Server, do notcheck Use Exchange Impersonation. If you are using Office 365, and using impersonation, do check the box.
9. Check Ignore Trust for SSL.
10. Click on Perform Test.
11. Once results are displayed, check the overall result, and also click on Expand All.

It may be necessary to first grant permissions.

Prepare the Destination Environment

First, set up user accounts, then complete the following steps.

Create Admin Account

Create an administrator account in Exchange to be used for migration or use the global admin account for the tenant. The administrator account must have either full access to the user mailboxes or be granted impersonation rights. We recommend using impersonation as it will help reduce the likelihood of the migration being throttled by Microsoft. 

1. Open the Exchange Management Console.
2. Expand the Recipient Configuration
3. Right-click on the Mailbox
4. Click on New Mailbox.
5. Click on Next.
6. Click on Next.
7. Enter "MigrationWiz" as the first name.
8. Enter "MigrationWiz" as the user logon name, and optionally select a user principal name (UPN) domain.
9. Enter a password and confirm the password.
10. Click on Next.
11. Click on Browseto select a Mailbox database.
12. Click on Next.
13. Click on New.
14. Click on Finish.

To grant the account access, perform the following from the Exchange Server machine:

1. Open the Exchange Management Shell.
2. Enter the following command:
   Get-Mailbox -ResultSize Unlimited | Add-MailboxPermission -AccessRights FullAccess -User MigrationWiz

The above command needs to be applied each time a new mailbox is created, since permissions are set directly on each mailbox. The administrative account will not have access until the permissions are applied.

In the above script, the username "MigrationWiz" should be replaced with the name of the administrative account that was set up, by following the earlier instructions in this article.

This username is the Administrative Username that needs to be entered under project source or destination settings, within MigrationWiz, when checkmarking the box labeled: Use Administrative Login.

Set up PowerShell session

Set up a remote PowerShell session with Exchange 2010+. 

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

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.

Disable Throttling

Disable throttling against the admin account. Use Option 1 in the Migrating from Exchange 2010+ section above.

Verify mailbox accessibility using EWS

 You can verify independently if a mailbox is accessible using EWS with the following steps:

1. Go to https://testconnectivity.microsoft.com. 
2. If using Office 365, click the Office 365 tab.
3. Select Service Account Access (Developers) and click Next.
4. Specify the target mailbox email address.
5. Specify the service account user name. If using admin credentials on the connector, enter the exact same user name.
6. Specify the service account password. If using admin credentials on the connector, enter the exact same password.
7. Check Specify Exchange Web Services URL and specify the URL (example: https://server/EWS/Exchange.asmx).
8. If using Exchange Server, do not check Use Exchange Impersonation. If you are using Office 365, and using impersonation, do check the box.
9. Check Ignore Trust for SSL.
10. Click Perform Test.
11. Once results are displayed, check the overall result, and click Expand All.

It may be necessary to first manage permissions.

If you want to be able to migrate messages with attachments larger than 10MB, the following limits need to be increased:

MSPComplete Steps

Create the customer

Each customer you add will be displayed in your customer list unless you archive it. There are two ways to add customers.

From the All Customer Page

1. Click the Add button in the top navigation bar
2. Click the Add Customer button on the All Customers page
3. In the left navigation pane, select the appropriate workgroup and then click All Customers.
4. Click Add Customer.
5. Enter the new customer’s information in the Add Customer form. Primary Email Domain and Company Name are required. The rest are optional.
6. Click Save.
7. Repeat steps 1 through 4 for each customer you want to add. 

Add Button

Add customers from the Add button in the top navigation bar

1. In the left navigation pane, select the appropriate workgroup.
2. Click Add in the top navigation bar, and then click Add in the drop-down list.
3. Enter the new customer’s information in the Add Customer form.
4. Click Save.
   
   Tip: When you click a customer in the list in the main pane, the name appears under Recent Customers in the left navigation pane.

Licensing

Purchase licenses. We recommend that you use the User Migration Bundle license for this migration scenario. 

• These licenses enable multiple migrations of user mailboxes, documents, and in-place archives. It also allows the use of DeploymentPro to perform post-migration Outlook email profile configuration.
• User Migration Bundle Licenses have unlimited data available per license.
• User Migration Bundle Licenses are applied to the customer's users and expire 12 months after their purchase date. 
• Document, Personal Archive, and DeploymentPro projects are all included when using User Migration Bundle Licenses.
• This license type must be applied manually.

Apply licenses

1. Sign in to MSPComplete at https://manage.bittitan.com.
   • When you sign in, make sure to select the MSPComplete button above the email field.
2. Select the correct workgroup on the top of the left navigation pane. This is the workgroup that the customer and migration project were created under. Your account must be part of the workgroup if the project was not created under your account.
3. On the left navigation pane, click Customers.
4. Click the customer that employs the user to whom you want to apply a User Migration Bundle license.
5. Click the Users tab at the top of the page.
6. Check the box to the left of the email for the user(s) to whom you want to apply a license.
7. Click the Apply User Migration Bundle License button at the top of the page. It is recommended that users be added to the Customer page with the vanity domain. Then have the User Migration Bundle Licenses applied, before editing to show the .onmicrosoft domain, if the .onmicrosoft domain will be used for the migration.
8. If there is at least one unassigned User Migration Bundle license available for each selected user, click Confirm.
   Important: If there are no User Migration Bundle licenses currently available to be assigned and your role in the workgroup is Manager or higher, the form that appears provides all the necessary information and will walk you through the steps of purchasing User Migration Bundle licenses.

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:

• • Via Group Policy Object (GPO). This is the recommended methodology because no end user interaction is required. 
  • Via email, as outlined in the DMA Installation Guide. 

Deploy the Device Management Agent with a Group Policy Object (GPO)

To deploy the BitTitan Device Management Agent (DMA) using a Group Policy Object (GPO), complete each of the steps detailed below, in order:

Step 1: Download the DMA setup file from MSPComplete.

1. In MSPComplete, click on All Customers from the navigation sidebar.
2. Click on the customer name for which you wish to deploy DMA.
3. On the horizontal menu bar, click on Users.
4. Click on Add Users, and then click on Add Users via Device Management Agent.
5. On the Add Users via Device Management panel, click on Device Management Agent setup file to download the DMA setup file to your local drive.

Step 2: Create a network share that is accessible to all of your customer’s computers, and put the DMA setup file in the share folder.

For more information about Windows Server file and storage services, read the File and Storage Services Overview TechNet article.

1. Log on to the file server as an administrator.
2. Click on Start and search for Server Manager.
3. Click on Server Manager from the search results.
4. Click on File and Storage Services.
5. Click on Shares.
6. Next to Shares, click on Tasks.
7. Click on New Share.
8. Continue through the New Share Wizard prompts until finished, then click on Create.
9. Right-click on the new share in Server Manager, and click on Open Share.
10. Put the DMA setup file in the share.
11. Write down the share's network path; this will be needed when creating the scheduled task.

Step 3: Create a Group Policy Object that forces the domain joined computers in a security filter to execute the DMA setup file through a scheduled task.

1. Log on to the Active Directory Domain Controller as an administrator.
2. Click on Start, and search for Group Policy Management.
3. Click on Group Policy Management.
4. Right-click on the desired Active Directory domain, and then click on Create a GPO in this domain, and Link it here.
5. Enter a name for the GPO, and then click on OK.
   Note: By default, the GPO will apply to all users and computers that successfully authenticate to the Active Directory domain.
6. To narrow the scope of computers that install DMA, select Authenticated Users, and click on Remove.
7. To confirm the removal, click OK.
8. To add a new security filter, click Add.
9. Type the name of the security group that the target computers are a member of, and click on Check names.
10. Click OK.
11. Right-click on the new GPO, and then click on Edit.
12. In the console tree, under Computer Configuration, click on Preferences > Control Panel > Scheduled Tasks.
13. Right-click under Scheduled Tasks and click on New, and then click on Immediate Task (At least Windows 7).
    For more information about Scheduled Task Items, read the Configure a Scheduled Task Item TechNet article.
14. Enter a name and a description for the Scheduled Task.
15. Click on Change User or Group.
16. Type "system" into the Object name text box.
17. Click on Check Names. Make sure that the system object name resolves to NT Authority\System.
18. Under Security options, click on Run whether a user is logged on or not and add a checkmark next to Run with highest privileges.
19. In the Configure for drop-down menu, select Windows 7®, Windows Server™ 2008 R2.
20. Click on the Actions tab
21. Click on New.
22. In the Action drop-down menu, select Start a program.
23. In the Programs/script text box, enter the network path for the DMA setup file. If you use the Browse button to find the location of the script, then it will add the path as c:\xxxx. This is incorrect since the script needs to include the UNC path and not the local path. Be sure to replace the c:\ format with the \\servername\sharename\ format.​
24. If the customer's computers use a proxy, you must add a command line parameter into the Add arguments field to ensure that DMA is able to transmit data through the proxy. Read the How do I deploy the Device Management Agent on computers that use a proxy?​​ article for more information.​
25. Click OK.
26. Click on the Conditions tab.
27. Add a checkmark next to Start only if the following network connection is available, and then select Any connection.
28. Click OK.
29. Close Group Policy Management Editor, and then close Group Policy Management.

The DMA setup file will execute on user computers at the next Group Policy refresh, typically every 90 minutes, with a random offset of 0 to 30 minutes.

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. 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. 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. 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.
   • 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

Create a Mailbox Migration project

1. Click the Go to My Projects button.
2. Click the Create Project button.
3. Click on the type of project that you wish to create. For this migration:

• Mailbox: Mailbox projects are used to migrate the contents of the primary user mailbox from the previous environment to the new environment. Most mailbox migrations can migrate email, calendars, and contacts.

For mailbox migrations, use administrative credentials to access mailboxes​. In most migration scenarios, the admin account needs to have full access rights to the Source mailboxes. 

1. Click Next Step.
2. Enter a Project name and select a Customer.
3. Click Next Step.
4. Select Exchange Server 2003+ from the Endpoint dropdown menu. 

5. Enter the OWA URL. 

6. 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.

7. Select Exchange Server 2003+ from the Endpoint dropdown menu.

8. Enter the OWA URL. 

9. 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.

10. Click Save and Go to Summary.

Mailbox Migration Settings: Every setting on the project is applied to all mailboxes associated with that project. For settings that are represented as checkboxes, only selected settings are applied to the project. Not selecting a checkbox does not disable a selected setting inherited from the project.

Add Users

Add the user accounts that will be migrated to the project. This may be done in several ways, depending on the size of the project. Steps for each option are in the accordion below, simply click to show the option you select and follow the guidance there.

Small Migrations:

For small migrations, it is easy to add users one-at-a-time using Quick Add. The steps for this are below. 

Larger Migrations:

For larger migrations, we recommend either using the Autodiscover or Bulk Add option.

Autodiscover will add all users found on the source tenant. This can then be edited in the project to remove users not being migrated. All users will be added with the source and destination email addresses set to match the source email. This can be changed by using the Change Domain Name button at the top of the project page. If the usernames are changing during the migration, we recommend using the Bulk Add option.

Bulk Add uses a CSV containing the source and destination email addresses for the users to add the users to the project. If migrating only a specific group from a tenant, we recommend using the Bulk Add option.

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.

Run Verify Credentials

1. ​Sign in to your MigrationWiz account​.
2. Open the Project containing items you wish to validate​.
3. Select the items you wish to validate.
4. Click on the Start button in your dashboard.
5. Select Verify Credentials from the drop-down list.

Once complete, the results of the verification will be shown in the Status section.​ 

Notify Users

Notify users that a migration is occurring. Send email to all users telling them the time and date of the migration.

Run Migration

Pre-Stage pass

1. Select the users you wish to migrate
2. Click the Start button from the top
3. Select Pre-Stage Migration
4. Under the Migration Scheduling section, from the drop-down list, select 90 days ago
5. Click Start Migration.

MX Record Cutover

Change over MX records on the DNS provider's portal. If migrating in batches and mail coexistence is required, you will not be cutting over the MX records until your final batch of users has been migrated, and you must perform this extra step:

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 Sample email to send to users before their Outlook profile is reconfigured for some sample text and screen shots that can be included in this email.

Set up mail forwarding

Through Exchange Management Console:

The first step is to create the forwarding objects in your local Active Directory. These forwarding objects will be hidden from the address book, and will be used purely to forward mail for mailboxes that are migrated. Note that these objects are created but not used until you set the forwarding, so these steps can be done ahead of time.

1. Download our script to create forwarding objects to a computer that is joined to the domain.
2. Modify the script in a text editor (like Notepad) and change the forwarding domain in the top of the script to the temporary domain in the new environment, for example, company.onmicrosoft.com.
3. Run the script. You will know the script is complete when you see a confirmation.

The next step is to set up forwarding for mailboxes prior to migration. Before submitting a mailbox for migration, set the forward by performing the following:

1. Launch the Exchange Management Console from the Start Menu.
2. Expand the Recipient Configuration note from the navigation tree.
3. Click on the Mailbox node from the navigation tree.
4. Right-click on the mailbox to set the forward for and click Properties.
5. Click on the Mailbox Flow Settings tab.
6. Select Delivery Options and click on Properties.
7. Do not select the option "Deliver message to both forwarding address and mailbox". This is important to ensure that Delta passes do not cause duplicates. If you do save a local copy, then when you perform Delta passes, MigrationWiz will migrate the items that it previously hasn't migrated (and watermarked). This will cause duplicates on your Destination.
8. Click the checkbox Forward to, then click Browse.
9. Select the name of the user that contains the prefix (External Forward) in the display name. This is the forwarding object created previously.
10. Click on OK.
11. Click on OK​.

Full (Delta) pass

1. Select the users
2. Click the Start button from the top
3. Select Full Migration
4. Click Start Migration

Run Retry Errors

Look through the user list and click any red "failed migration" errors. Review the information and act accordingly.

If problems persist, contact Support.

Request Statistics

Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics.