Skip Ribbon Commands
Skip to main content

Hosted Exchange to Amazon WorkMail Migration Guide

Last Update: 4/5/2017 12:38 PM
​​Hosted Exchange to Amazon WorkMail 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, click the waffle icon (waffle.png) in the top navigation bar of MSPComplete, and select the appropriate migration product.

​​

Introduction

  • This is the complete onboarding task flow for migrating mailboxes from Hosted Exchange servers (versions 2007 and later) to Amazon WorkMail.
  • Complete each step in order. Links to corresponding Knowledge Base articles are provided.

Prepare the Source Environment

  1. Ask the Hosted Exchange Provider to create an account for migration purposes (e.g., named "MigrationWiz") and grant full access rights to each mailbox, by running this PowerShell script against the account called "MigrationWiz":
    • Get-Mailbox -ResultSize Unlimited | Add-MailboxPermission -AccessRights FullAccess -User MigrationWiz

    • Notes:
      • Some Hosted Exchange providers allow this access to be granted via their web portal. In this case, you could log in to each mailbox via their portal, and grant the migration account (e.g., "MigrationWiz") to have read/write access to each mailbox. Obviously this is laborious and time-consuming, and so it is preferable that the Hosted Exchange provider run the PowerShell script above, particularly if you have a large number of users.

      • Some Hosted Exchange Providers will not grant this access. If that is the case, you can request credentials from your end users during the migration. Exact steps for this are provided under Option 2 in KB005086.
  2. If this is a very large project, the best results will be achieved by setting the project to use impersonation at the Source. In order to enable this, the PowerShell script below needs to be run by your Hosted Exchange provider. KB004727
    New-ManagementRoleAssignment -Role ApplicationImpersonation -User <admin_user_name>
    • Notes:
      • Many Hosted providers will not accommodate this request.
      • The second part of this process is to set your MigrationWiz project Advanced Options to use impersonation at the Source. This step is included in the MigrationWiz section in this guide.
  3. Test mailbox access. KB004616
  4. Export the mailboxes to CSV file(s).
    • If you have admin credentials on the Hosted Exchange environment, you only need a list of the email addresses. You do not need the password for each mailbox being migrated (because MigrationWiz will use delegation and perform the migration based on the admin credentials).
    • If you do not have admin credentials on the Hosted Exchange environment (which is common), you must obtain all the email addresses and passwords for the users.

    Options to obtain these:

        • Ask the Hosted Exchange provider to provide them.
        • If the provider has an admin console which includes this capability, run their tool to export the user list (and, if neccessary, the passwords) to the CSV file.
    • If the list of mailboxes and passwords from the Hosted Exchange provider is not available, request that the users send these to MigrationWiz as part of the migration process. KB004666 Video

Prepare the Destination Environment (full details can be found in the Amazon WorkMail admin guide here)

  1. Add Organization to Amazon WorkMail. For more information, see Add an Organization.
  2. Add your domain to Amazon WorkMail. For more information, see Add a Domain.
  3. Create new users or enable your existing directory users for Amazon WorkMail. For more information, see Create New Users.
  4. Create an admin account for migration that has full access permissions to all mailboxes. Steps: Add the new user migration_admin in the Amazon WorkMail console, or create the user migration_admin in your Active Directory, and enable this user for Amazon WorkMail. For more information, see Migrate to Amazon WorkMail. Note: When you are setting the Destination endpoint, the administrative login name must be entered in the form of an email address.

MSPComplete Steps

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

      • Click on EndPoints > Add Endpoint > + Find My Service Provider button > Click on 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 on the Exchange Server 2003+ button and manually enter the Outlook Web Access URL.)
      • Click on 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 Source Environment section.
    • For the Destination endpoint:
      • Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select AWS WorkMail.
      • 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.
      • From the drop-down list, select the WorkMail Region.
  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. KB004647

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. Use the Bulk Add option, and then import from the CSV file that you prepared when following the steps under Prerequisites section of this guide. KB004842.

      • If the list of mailboxes and passwords from the Hosted Exchange provider is not available, request that the users send these to MigrationWiz as part of the migration process. KB004666 Video
    3. Set the Project Advanced Options. KB004834
      • The following options are the most valuable for this migration scenario:
        • If this is a very large project, the best results will be achieved by setting the project to use impersonation at the Source (as documented in the Prepare Source Environment section of this guide). However, many Hosted providers will not accommodate this request. If they do, checkmark the box for Use impersonation at source. Note: Exchange impersonation (not delegation) utilizes per-user throttling quotas, which allows for a very large number of users to be migrated concurrently.​ 
          • If using impersonation, the value for Maximum concurrent migrations, under the Performance section, can be set to a very high value, e.g.,1000.  Note: There is no limit for this value if using impersonation.​
          • If not using impersonation, we recommend that you set the Maximum concurrent migrations​ value to a low number, such as 20.
    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. For more information, see Use AutoDiscover to Configure Endpoints.
      • Note: If you are 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:
    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. Enable Autodiscover again, so that users can create new profiles via Autodiscover. KB005363
    10. Full (Delta) pass: Select the users > Click on the Start button from the top, select Full Migration > Click on Start Migration. KB004938
    11. Run Retry Errors. KB004658
    12. Look through the user list and click on any red "failed migration" errors. Review information and act accordingly.
    13. If problems persist, contact Support. KB004529
    14. Reconfigure Outlook profiles to use Amazon WorkMail. For more information, see Connect Microsoft Outlook to Your Amazon WorkMail Account. Note: Users must create new Outlook profiles, and set up their signatures again, and reattach any PST files that were attached to their previous profile.

    15. Set up Amazon WorkMail on your Kindle, Android, iPad, iPhone, or Windows Phone. For more information, see Connect Your iOS Device and Connect Your Android Device.

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