- This is the complete onboarding task flow for migrating mailboxes from IMAP systems to Hosted Exchange.
- Complete each step in the order listed. 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.
Note: The steps in this guide for DMA and DeploymentPro are only necessary if end users are using Microsoft Outlook as their email client.
- 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).
- 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
- Test connectivity to the IMAP server, by going here. Fill in the form, and click the button marked Test.
- Export user list to a CSV file.
- Administrator accounts with at least read rights can export a user list.
- If you do not have an administrator account, you 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 MigraitonWiz mailbox project.
Prepare the Destination Environment
- Set up user accounts
- Ask the Hosted Exchange provider to create an account for migration that has full access permissions to all mailboxes.
- If you do not provide an admin account when setting up your Destination endpoint, it will be necessary to provide SMTP email addresses, login names, and passwords when adding Destination users to your MigrationWiz project. If you do provide an admin account, you only need to provide the SMTP email addresses.
- Below is an example PowerShell script which grants full access rights to an account called MigrationWiz. Your Hosted Exchange provider needs to change the user to match your admin account before running the script.
Get-Mailbox -ResultSize Unlimited | Add-MailboxPermission -AccessRights FullAccess -User MigrationWiz
- For the Source endpoint:
- Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type select IMAP.
- Server Name should follow format: imap.example.com
- Enter the 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 Endpoints > Add Endpoint > + Find My Service Provider button > click the down arrow in the Service Provider field, and select the Hosted Exchange Provider (taking care to select the correct version of Exchange that the customer is running). This will autopopulate the Outlook Web Access URL with their verified URL. (Or, instead of clicking on the + Find My Service Provider button, click the Exchange Server 2003+ button and manually enter the Outlook Web Access URL.)
- Click the Provide Credentials radio button, and enter the admin account credentials. These are the credentials that you obtained from your Hosted Exchange Provider when following the steps under the Prepare Destination Environment section.
Note: Check to see if there are any available bundles for discounts (e.g., MigrationWiz-Mailbox and DeploymentPro Bundle). KB004647
- 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.
- 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.
- 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 the Schedule Cutover button.
- 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.
- Watch this video to see a walk-through of the steps below.
- Create the Mailbox Migration project. KB004380
- Create the Mailbox Migration project > Select the customer > Select the Source endpoint > Select the Destination endpoint.
- Use Bulk Add, with a CSV file that contains your user list.
- 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. Video
- For the Destination, you only need to enter the Destination email address of each user.
- 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