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 the order listed. Links to corresponding Knowledge Base articles are provided.
MigrationWiz is a migration solution (not a synchronization solution) and will NOT propagate updates, deletes, or moves of the items previously migrated in the first migration pass because 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.
MigrationWiz supports the capability to share migration projects across a Workgroup. When the Project Sharing feature is turned on, all Agents besides those who are Inactive can view all migrations projects. For more information, visit Project Sharing in MigrationWiz.
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
- 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.
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
- Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select Exchange Server 2003+.
- Enter the OWA URL KB004392
- 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 Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select AWS WorkMail.
- 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.
- From the drop-down list, select the WorkMail Region.
- For the Source endpoint:
- For the Destination endpoint:
- Create the Mailbox Migration project. Read the How do I create a new migration project? article for more information.
- Add the accounts (also referred to as "items") that will be migrated to the project. KB004842
- Set the Project Advanced Options. KB004834
- 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.
- Set up mail forwarding. KB004315
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:
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.