Skip Ribbon Commands
Skip to main content

IMAP to On-Premises Exchange Migration Guide

Last Update: 7/21/2017 11:30 AM
This article has been moved to our new Help Center. Please update your bookmarks.

​​​IMAP to On-Premises Exchange Migration Guide

Important: When you sign in to MigrationWiz, you are redirected to the Getting Started page in MSPComplete. To get to a migration project created before April 4, 2017, click the Go to Projects button on the Getting Started Page. To create a new project for the migration scenario documented in this article, go to the Delivery Center and add a Mail: IMAP to On-Premises Exchange​ service to the customer. Read the Delivery Center article for more information about adding services to a customer.



  • This is the complete onboarding task flow for migrating mailboxes from IMAP systems to Office 365.
  • Complete each step in order. Links to corresponding Knowledge Base articles are provided.
  • Due to API limitations, IMAP migrations will only migrate mail items.
  • 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 recommend that you use DeploymentPro to reconfigure the Outlook profiles in this migration scenario if end users are using Microsoft Outlook as their email client. 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).
    • Note: We can only migrate mail items that are stored on the IMAP server. Verify that a copy of the mail remains on the server. If there is no mail on the IMAP server and it's stored in a local PST, use the PST migration process. If the data is stored in a local Outlook OST file (Outlook 2013 and Outlook 2016), export the mailbox to a PST and use the PST migration process.​​​


  • There are many different versions of IMAP mail systems available. For this reason, we recommend running a trial migration on one or more mailbox(es) prior to the actual full migration project.
    • Note: Once the trial migration completes, check on the folder structure at the Destination to ensure that the directory structure is as desired. KB004671

Prepare the Source Environment

  1. Test connectivity to the IMAP server by going here. Fill in the form, and click on the Test button.
  2. Export user list to a CSV file.
    • Notes:
      • Administrator accounts with at least read rights can export a user list.
      • If you do not have an administrator account, you will need to ask your IMAP host to provide you with a complete user list, in CSV file format.
      • This CSV file will be used to bulk add users into your MigrationWiz mailbox project.

Prepare the Destination Environment

  1. Set up user accounts.
  2. 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
    • Notes:
      • 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.
  3. Disable throttling against the admin account. Refer to Option 1 in KB004945.
  4. Verify mailbox accessibility, using EWS.​ KB004304

  5. If you want to be able to migrate messages with attachments larger than 10MB, the following limits need to be increased:
    • Increase message size limits. KB004613
    • Increase maximum accepted content length. KB004609
    • Increase maximum receive message size. KB004532
    • Increase maximum accepted re​​​​quest length. This is only valid if your Destination server is running Exchange 2007. KB004610

MSPComplete Steps

  1. Create the customer. KB005421
  2. Create the Source and Destination endpoints. KB005427
    • For the Source endpoint:

      • Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type select IMAP.

      • Server Name should follow format:

      • Enter server port. As a general rule, the server port will be either 143 or 993 (if using SSL). Note: If using SSL, checkmark the Use SSL box.

    • For the Destination endpoint:
      • Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type select Exchange Server 2003+
      • Enter the 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.

  3. 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
  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:
    • Via Group Policy Object (GPO). Note: This is the recommended methodology, because no end user interaction is required. ​KB005412  video
    • Via email. KB005411

DeploymentPro Steps

  1. Launch DeploymentPro.
    • 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 the customer DeploymentPro module:
      • Enter the 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.
  2. Activate DeploymentPro module for users.
    • 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.
  3. Schedule the profile cutover date.
    • Set the date and time for the Outlook profile configuration to occur, and click on the Run Module 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

Watch this video to see a walk-through of the steps below.

  1. Create the Mailbox Migration project. KB004380

    • Create the Mailbox Migration project > Select the customer > Select the Source endpoint > Select the Destination endpoint.
  2. Add the accounts (also referred to as items) that will be migrated to the project. KB004842
    • Use Bulk Add, with a CSV file that contains your user list.
    • Source:
      • If you have an admin account on the Source IMAP system, the format will be as follows. Note: Most IMAP systems do not support administrative credentials. Refer to KB004344 for a list of supported IMAP systems.
        • Source Email: SMTP email address.
        • Source Login Name: Consists of two combined names: the user name of the person whose email is being migrated, and the user name of the mailbox admin account. For example, for Exchange IMAP: Domain/Admin_UserName/User_UserName.  Important: To determine the correct format to follow for this value, refer to KB005830.
        • Source Password: Enter the administrator's password.

      • If you do not have an admin account, enter the Source Email addresses in the Source Email column, and checkmark the I don't know the login name and password for the Source mailboxes box. Note: Users will then be requested to provide their credentials during the migration process. KB004666 Video
    • Destination:

      • For the Destination, you only need to enter the Destination email address of each user.

  3. Set the Project Advanced Options. KB004834
  4. Run Verify Credentials. KB004511
  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 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
  7. MX Record Cutover. Change over MX records on the DNS provider's 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 KB005799 for some sample text and screen shots that can be included in this email.
  9. Full (Delta) pass: Select the users > Click on the Start button from the top, select Full Migration > Click on Start Migration. KB004938
  10. Run Retry Errors. KB004658
    • Note: If errors are listed in the MigrationWiz dashboard with the following error message:  "Unexpected extra arguments to Examine Context: FolderNameWithQuote", then follow the steps below to add the support option flag AllowQuoteInFolder=1 at the item level, and run retry errors. KB005859
      • Steps: Click the Edit Item icon to the right of the item that you wish to edit > Under the Support section, enter the support option: AllowQuoteInFolder=1 > Click Save Item > Select the line item in your MigrationWiz dashboard > Click Start > Retry Errors
  11. Look through the user list and click on any red "failed migration" errors. Review information and act accordingly.
  12. If problems persist, contact Support. KB004529
  13. 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.
  14. Click on the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. KB004626