On-Premises 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 () in the top navigation bar of MSPComplete, and select the appropriate migration product.
- This is the complete onboarding task flow for migrating mailboxes from On-Premises 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
- Set up an administrator account for migration on the Source Exchange mailbox server. KB004725
- EWS must be working on the Source Exchange server. KB004392
- Test mailbox access. KB004616
- Disable the Exchange throttling policy during migration. KB004945
If you want to migrate archived email with in-flight stub rehydration, deploy the archive extractor agent in the Source environment. KB005639
- This is only relevant for Exchange 2010+. Exchange versions 2007 and earlier do not have throttling policies.
- If you are running Exchange 2010 and later, we highly recommend disabling the Exchange throttling policy in order to speed up your migrations.
- Follow the instructions under Option 1 in KB004945 to disable throttling for only the admin account, rather for than all users.
Note: Archived email migration is only supported for Veritas Enterprise Vault 9 or later. Read KB005463 to learn more about archive email migration with in-flight stub rehydration.
Important: BitTitan cannot migrate items in vault stores that are not associated with a vault store group; that is, when a vault store’s group version field is empty.
Prepare the Destination Environment (full details can be found in the Amazon WorkMail admin guide here)
- Add an Organization to Amazon WorkMail. For more information, see Add an Organization.
- Add your domain to Amazon WorkMail. For more information, see Add a Domain.
- Create new users, or enable your existing directory of users, for Amazon WorkMail. For more information, see Create New Users.
- 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.
- Create the customer. KB005421
- Create the Source and Destination endpoints. KB005427
For the Source 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.
- 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.
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
Watch this video to see a walk-through of the steps below.
Create the Mailbox Migration project. KB004380
If you want to migrate archived email with in-flight stub rehydration, provide additional Source configuration information, such as the Enterprise Vault SQL server and Active Directory information. KB005489
- Create the Mailbox Migration project > Select the customer > Select the Source endpoint > Select the Destination endpoint.
Note: Archived email migration is only supported for Veritas Enterprise Vault 9 or later. Read KB005463 to learn more about archived email migration with in-flight stub rehydration.
Add the accounts (also referred to as "items") that will be migrated to the project. KB004842
Set the Project Advanced Options. KB004834
Run Verify Credentials. KB004511
Notify users that a migration is occurring. Send email to all users telling them the time and date of the migration.
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
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.
- 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 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.
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.
Full (Delta) pass: Select the users > Click on the Start button from the top, Select Full Migration > Click on Start Migration. KB004938
Run Retry Errors. KB004658
Look through the user list and click on any red "failed migration" errors. Review information and act accordingly.
If problems persist, contact Support. KB004529
- 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:
Reconfigure the 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.
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.
Click on the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. KB004626