This is the complete onboarding task flow for migrating mailboxes from Microsoft 365 to Hosted Exchange or On-Premises Exchange, version 2013+.
First time?
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.
Limitations
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.
App password usage is not supported by this endpoint.
The maximum file size for migration through MigrationWiz varies by migration type and environment, but may never exceed 60GB.
Below is a list of items that are and are not migrated using MigrationWiz on Microsoft 365 migrations. Please note that this list is updated frequently, so double-check it before any and all migrations.
Exchange Web Services (EWS) must be enabled for the mailboxes in the Exchange Online tenant and the Hosted/On-Premise Exchange environment for this migration type
- Inbox
- Folders
- Contacts
- Calendars
- Tasks
- Journals
- Notes
- Post (when the destination is Exchange or Microsoft 365)
- Calendar acceptance status emails
- Server-Side mailbox rules
- Client-Side mailbox rules for Outlook (Exchange 2013 and 2016 only)
- Automatic Replies (Out of Office Messages for Exchange 2013 and 2016 only) Important: It is recommended to only migrate Automatic Replies in the last migration pass for the user.
- Personal Folder and Calendar Permissions (Exchange 2013 and 2016 only)
- Safe Sender/Block Lists
Groups
- Notebooks
- For Group documents: anything not in a document library (See SharePoint)
For additional features and limitations, please visit MigrationWiz: Migrated and Not Migrated Items.
Prepare the Source Environment
Modern Authentication Requirements
The steps listed below apply to both the source and/or destination tenant when they are Exchange Online, in regards to Exchange Web Services (EWS) in mailbox, archive mailbox, and public folder projects. Use a Global Administrator for the configuration steps.
For setup steps that include images, see under Enabling Modern Authentication for EWS between MigrationWiz and your Exchange Online Tenant in the following KB: Authentication Methods for Microsoft 365 (All Products) Migrations
Important
Failure to perform the steps for your Microsoft 365 endpoints, can result in failed jobs with 401 errors like the following in your project: Http POST request to 'autodiscover-s.outlook.com' failed - 401 Unauthorized
The administrator account being used for the project needs to be excluded from any MFA/2FA policies or Conditional Access policies that can block access for the administrator account. This requirement does not apply to the items or users being migrated in the project.
Configuring Modern Authentication to work with MigrationWiz for mailbox, archive mailbox, and public folder projects in Exchange Online is now the default method after Microsoft discontinued support for Basic Authentication in Exchange Online after December 2022. The following Microsoft documentation outlines this change in more detail. Should you have additional questions on how this change may impact your tenant, please contact Microsoft to assist with providing that information: Deprecation of Basic authentication in Exchange Online
The Azure Security Defaults must also be disabled in the tenant. (This is often enabled by default for all new Exchange Online tenants and there is no workaround for this requirement). For steps on where to enable/disable the Azure Security Defaults, see Enabling security defaults in the following Microsoft documentation. To disable, set Enable Security defaults to No: Security defaults in Azure AD
Modern Authentication Steps- Log in to the Azure AD admin console with a Global Administrator login.
- Select Azure Active Directory in the Azure Active Directory Admin Center.
- Select App Registrations, which is found under Manage.
- Select New Registration at the top of the screen.
- Give the app a distinct name. You can change this later if necessary.
- Select the Accounts in any organizational directory button.
- Under Redirect Uri, select Public Client (mobile & desktop) and set it to urn:ietf:wg:oauth:2.0:oob
- Click Register.
- Go back to App registrations.
- Select the App you just created.
- In the Overview, you will find a ClientId (aka Application) and Directory (Tenant) ID.
- Copy both of these to another application, such as Notepad, for use later in this process.
- Under the Manage menu, select Authentication.
- Set the option Allow public client flows to Yes.
- Click Save.
- From the Manage menu, select API permissions.
- If API permission named User.Read under Microsoft Graph is already present, this can be removed. The Microsoft Graph API is not applicable to this project type and is not used.
- Select Add a Permission.
-
Select APIs my organization uses
-
Scroll down and select Office 365 Exchange Online
-
Then select Delegated Permissions
-
Select EWS
- Check the box under EWS for EWS.AccessAsUser.All.
- Click Add permissions. This permission only allows the OAuth application (MigrationWiz) to be associated with EWS.
Important
This does not grant access to all mailbox data.
- Click Grant admin consent.
- Click Yes to confirm the settings.
- In MigrationWiz, select the project that needs to be configured for Modern Authentication.
- Click the Edit Project menu.
- Select Advanced Options.
- Under Support Options enter the ClientID and TenantID information you saved earlier in the following format:
- If enabling Modern Authentication for the Source:
ModernAuthClientIdExport=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
ModernAuthTenantIdExport=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
- If enabling Modern Authentication for the Destination:
ModernAuthClientIdImport=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
-
ModernAuthTenantIdImport=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
- Enter the specific ClientID and TenantID for your tenant in place of the xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.
- These options can be entered for either the Source or the Destination, or both, depending on the settings on the tenants.
- These options need to be configured for each MigrationWiz project that needs to have Modern Authentication enabled.
- If enabling Modern Authentication for the Source:
- Run a Verify Credentials to confirm that MigrationWiz can connect using Modern Authentication.
- Click on the item that was verified. There will be a message in the MigrationWiz Migration Information page that Modern Authentication is being used. This message will show in the “Migration Errors” box; however, it is not an error. This is just a message confirming that Modern Authentication is now active and being used for the connection.
Create an Administrator Account
Create an administrator account in Microsoft 365 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.
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 columns within your MigrationWiz project dashboard under Add > Bulk Add.
To export the user list:
- Go to the Microsoft 365 admin portal.
- Click Users.
- Click Active Users.
- Click Export Users.
- Click Continue.
Be sure to save the csv somewhere you can access it for upload later in the migration.
Disable throttling against the admin account
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. If you are creating or applying a throttling policy on Exchange, you will need to use delegation for this endpoint.
There are two options for this process. Choose which one works for you, and then expand the relevant set of instructions below.
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 you are not using impersonation during the migration, but instead using delegation. 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 you Set Up an Exchange Administrator Account and disable policy enforcement for this account.
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 rate limits and throttling before you execute the scripts below.
To disable all throttling parameters for an admin account called "MigrationWiz":
- On a computer that hosts the Microsoft Exchange Management Shell, open the Microsoft Exchange Management Shell.
- Type the following command and press Enter.
New-ThrottlingPolicy MigrationWizPolicy
- 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
- Type the following command and press Enter.
Set-Mailbox "MigrationWiz" -ThrottlingPolicy MigrationWizPolicy
To disable all throttling parameters for an admin account called "MigrationWiz":
- Open the Exchange Management Shell.
- Type the following command and press Enter.
New-ThrottlingPolicy MigrationWizPolicy
- Type the following command and press Enter.
Set-ThrottlingPolicy MigrationWizPolicy -RCAMaxConcurrency Unlimited -EWSMaxConcurrency Unlimited -EWSMaxSubscriptions Unlimited -CPAMaxConcurrency Unlimited -EwsCutoffBalance Unlimited -EwsMaxBurst Unlimited -EwsRechargeRate Unlimited
- 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 rate limits and throttling before you execute the scripts below.
To disable all throttling parameters for all mailboxes:
- On a computer that hosts the Microsoft Exchange Management Shell, open the Microsoft Exchange Management Shell.
- Type the following command and press Enter.
New-ThrottlingPolicy MigrationWizPolicy
- 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
- Type the following command and press Enter.
Get-Mailbox -ResultSize Unlimited| 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. Follow the directions in the Help Center article Impersonation and Delegation to enable this.
To disable all throttling parameters for all mailboxes:
- Open the Exchange Management Shell.
- Type the following command and press Enter.
New-ThrottlingPolicy MigrationWizPolicy
- Type the following command and press Enter.
Set-ThrottlingPolicy MigrationWizPolicy -RCAMaxConcurrency Unlimited -EWSMaxConcurrency Unlimited -EWSMaxSubscriptions Unlimited -CPAMaxConcurrency Unlimited -EwsCutoffBalance Unlimited -EwsMaxBurst Unlimited -EwsRechargeRate Unlimited
- 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 Destination. 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.
Prepare the Destination Environment
Set up the user accounts
You can use the csv acquired in the previous step as an easy reference point for creating these accounts.
Create Admin Account
Create an admin account for migration that has full access permissions to all mailboxes. 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.
- Open the Exchange Admin Console.
- Click New and select User Mailbox.
- Click New User.
- Enter "MigrationWiz" as the Display name.
- Enter "MigrationWiz" as the Name.
- Enter "MigrationWiz" as the User logon name.
- Enter the service account password.
- Select Save.
To grant the account access, perform the following steps while in the Exchange Server machine. The 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.
- Open the Exchange Management Shell.
- Enter the following command:
Get-Mailbox -ResultSize Unlimited | Add-MailboxPermission -AccessRights FullAccess -User MigrationWiz.
Change the -User account to match the name of the admin account that was set up for migration. 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.
Optional: Large Messages
If you want to be able to migrate messages with attachments larger than 10MB, the following limits need to be increased:
This is a two-step process. The reason for this is that if the message size limits of Exchange are increased, the IIS limits will also have to be increased to allow increased payloads. There are other non-standard settings that can also cause size restrictions for the IIS or EWS connections, but we are unable to troubleshoot or identify specific environment restrictions outside of these settings.
To display current message size limits:
- Open the Exchange Management Shell.
- Enter the following commands:
Get-TransportConfig | Format-List -Property MaxReceiveSize, MaxSendSize
Get-SendConnector | Format-List -Property Identity, MaxMessageSize
Get-ReceiveConnector | Format-List -Property Identity, MaxMessageSize
Get-MailBox | Format-List -Property PrimarySmtpAddress, MaxSendSize, MaxReceiveSize
To increase message size limits on the Exchange Server:
- Open the Exchange Management Shell.
- Enter the following commands:
Set-TransportConfig -MaxReceiveSize 150MB -MaxSendSize 150MB
Get-SendConnector | Set-SendConnector -MaxMessageSize 150MB
Get-ReceiveConnector | Set-ReceiveConnector -MaxMessageSize 150MB
Get-Mailbox | Set-Mailbox -MaxSendSize 150MB -MaxReceiveSize 150MB
Increase IIS Limits to Allow Accepting Payloads
There are three limits that should be increased in IIS:
- maxRequestLength
- maxAllowedContentLength
- maxReceivedMessageSize
Follow these steps to increase the Exchange message size limits on your client access server:
- Open Windows Explorer.
- Navigate to %ExchangeInstallPath%FrontEnd\HttpProxy\ews\.
- Open the file Web.Config in a text editor, such as Notepad.
- Find the XML tag starting with for each change.
- Change the existing value to maxRequestLength="200000" -- this occurs in one place in the Web.Config file.
- Change the existing values to maxAllowedContentLength="200000000" -- this occurs one place in the Web.Config file.
- Change the existing values to maxReceivedMessageSize="200000000" -- this entry occurs up to 12 times. This needs to be changed for each Authentication method.
For example:
<httpsTransport maxReceivedMessageSize="200000000" authenticationScheme="Anonymous" maxBufferSize="81920" transferMode="Streamed" />
<httpsTransport maxReceivedMessageSize="200000000" authenticationScheme="Basic" maxBufferSize="81920" transferMode="Streamed" />
etc. - If you are running IIS7 and Windows 2008, it may be necessary to increase WCF settings.
- Save the file.
- IIS Reset is not needed, web.config changes are picked up by the next connection.
Follow these steps to increase the Exchange message size limits on your mailbox server:
- Open Windows Explorer.
- Navigate to %ExchangeInstallPath%ClientAccess\exchweb\ews\.
- Open the file Web.Config in a text editor, such as Notepad.
- Find the XML tag starting with for each change.
- Change the existing value to maxRequestLength="200000" -- this occurs in one place in the Web.Config file.
- Change the existing values to maxAllowedContentLength="200000000" -- this occurs one place in the Web.Config file.
- Change the existing values to maxReceivedMessageSize="200000000" -- this entry occurs up to 12 times. This needs to be changed for each Authentication method.
- If you are running IIS7 and Windows 2008, it may be necessary to increase WCF settings.
- Save the file.
- IIS Reset is not needed, web.config changes are picked up by the next connection.
You may increase the maximum accepted content length by following these directions:
- Open Windows Explorer.
- Navigate to C:\Program Files\Microsoft\Exchange Server\ClientAccess\exchweb\ews.
- Open the file Web.Config in a text editor such as Notepad.
- Go to the end of the file.
- Insert or edit the following XML code before the </configuration> tag:
<system.webServer>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="104857600" />
</requestFiltering>
</security>
</system.webServer>
If XML code is already present in the Web.Config file, edit it to match what is shown above.
Sample Web.Config before changes:
<configuration>
<system.web>
...
...
</system.web>
</configuration>
Sample Web.Config after changes:
<configuration>
<system.web>
...
...
</system.web>
<system.webServer>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="104857600" />
</requestFiltering>
</security>
</system.webServer>
</configuration>
If you are running IIS7 and Windows 2008, you may need to increase WCF settings:
- Open Windows Explorer.
- Navigate to C:\Program Files\Microsoft\Exchange Server\ClientAccess\exchweb\ews.
- Open the file Web.Config in a text editor like Notepad.
- Find all XML tags starting with maxReceivedMessageSize=.
- Change existing values to maxReceivedMessageSize="104857600".
- Save the file.
- Open a Command Prompt (cmd.exe).
- Type: cd %windir%\system32\inetsrv.
- Type: appcmd.exe set config "Default Web Site/ews" -section:requestFiltering -requestLimits.maxAllowedContentLength:104857600.
- Run: iisreset.
Licensing
To purchase licenses
- Sign in to your BitTitan account.
- In the top navigation bar, click Purchase.
- Click the Select button and choose the UMB license type.
- Enter the number of licenses you want to purchase. Click Buy Now.
- Enter a Billing address if applicable.
- Click Next.
- Review the Order Summary and enter a payment method.
- Click Place Your Order.
MigrationWiz Steps
Create a Mailbox Migration project
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.
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.
- Click the Go to My Projects button.
- Click the Create Project button.
- Select Mailbox migration type.
- Click Next Step.
- Enter a Project name and select a Customer.
- Click Next Step.
Endpoints
The steps for this section outline how to create the endpoints in MigrationWiz.
If you are selecting an existing endpoint, keep in mind that only ten endpoints will show in the drop-down. If you have more than ten, you may need to search. Endpoint search is case and character specific. For example, Cust0mer will not show up if the search is customer. We recommend keeping a list of endpoints you have created, along with any unique spellings or capitalization you may have used.
- Select a Source Endpoint or create a new endpoint.
- To create a new source endpoint:
- Click New.
- Name the endpoint.
- Select type Office 365.
- Provide credentials: 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.
- Click Add.
- Click Next Step.
- Select or create a new destination endpoint.
- To create a new destination endpoint:
- Click New.
- Name the endpoint.
- Select type Exchange Server 2003+.
- Enter the OWA URL.
- Provide credentials: 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.
- Click Add.
- Click Next Step.
- Click Save and Go to Summary.
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.
This option allows you to add items one at a time. To do so, you only have to provide an email address if you entered administrative credentials when setting up the project. If you did not, enter the following user information:
- An email address
- Login name
- Password
- Mailbox status
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.
MigrationWiz allows you to bulk import mailboxes into the system.
To import one or more mailboxes:
- Sign in to your MigrationWiz account.
- Select the Project for which you want to perform the bulk import.
- Click Add.
- Click Bulk Add.
- Follow the instructions on the page. (Note: After adding new users to the Bulk Add Items page, make sure to select the radio button All newly detected mailboxes will be migrated as shown below before clicking on the green Save button)
Autodiscover process within MigrationWiz can be used to discover items from the Source environment so that they can be imported into your projects. This can then be edited in the project to remove users not being migrated. All users are 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.
There are few requirements in order for this to work:
- The Source has to be Exchange 2007 or later, or Microsoft 365, or G Suite. If you are using Autodiscover from G Suite, all G Suite domains must be added to the list of domains in the Endpoint.
- The endpoint on the Source needs to use admin credentials.
- For mailbox migration projects, the admin account that is specified within the Source endpoint needs to have a mailbox associated with it.
- The admin mailbox must be listed in the public Global Address List (GAL).
- The migration project type needs to be a Mailbox migration. For the exact steps to be followed during your migration, refer to the relevant Migration Guide. All Migration Guides can be found on the Help Center site.
One additional item to note here is that there is not a way to restrict the IP addresses that the connection will come from. This means that the steps outlined in our IP Lockdown guide will not apply here. If your environment requires that any IP addresses be whitelisted, it is recommended that items be added to your project using on of the other available options.
Autodiscover of items will not work while using Modern Authentication
Autodiscovery exposes the following items:
- For mailbox migration, autodiscovery will list all mailboxes at the Source.
Steps to Run Autodiscover
-
Navigate to the project you want to import users into.
-
Ensure that you have created an endpoint for the source project.
-
Once in the project, on the top navigation bar, click on the Add drop-down, then select Autodiscover Items. This will begin the Autodiscover process.
-
Once discovered, click on the Import button, to import the items into your MigrationWiz project.
Set the Project Advanced Options
Impersonation
Set to use impersonation at the Destination. Checkmark the Use impersonation at Destination box if you chose to use Impersonation instead of Delegation. If you chose to use Delegation, this box needs to remain unchecked.
For large projects only: If this is a large migration project, increase the value for Maximum concurrent migrations, under the Performance section, e.g., 200. 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.
Run Verify Credentials
You may verify the credentials of items in MigrationWiz without migrating data or consuming any licenses.
- Open the Project containing items you wish to validate.
- Select the items you wish to validate.
- Click the Start button in your dashboard.
- 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 an email to all users telling them the time and date of the migration.
Begin Migration
Pre-Stage pass
- Select the users you wish to migrate.
- Click the Start button from the top.
- Select Pre-Stage Migration.
- Uncheck the box named Automatic Replies (This option will be removed from the Pre-Stage pass at a later date)
- Under the Migration Scheduling section, from the drop-down list, select 90 days ago.
- Click Start Migration.
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 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.
Full (Delta) pass
- Select the users.
- Click the Start button from the top.
- Select Full Migration. IMPORTANT: It is recommended to only migrate Automatic Replies in the last migration pass for the user.
- 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.
Post-Migration
Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics.