- 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
- Grant MigrationWiz OAuth 2.0 access to G Suite. For guidance, see Enable access to G Suite using OAuth 2.0.
- If migrating from multiple domains, repeat these steps for each domain.
- G Suite as the Source (read-only scopes):
https://www.googleapis.com/auth/calendar.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.directory.user.readonly,
Note: OAuth administrative credentials will not function properly with G Suite for Business Legacy free accounts. If a G Suite tenant is a G Suite for Business Legacy free account, end user credentials must be used. Refer to KB005124 for more information on migrating with end user credentials.
- Ensure that IMAP access is enabled for all users. For details on how to check this, refer to the Google support article here.
- Ensure the folder size limits on IMAP folders have been removed for all users. For each user, click on the gear icon > Settings >Forwarding and POP/IMAP tab> Folder Size Limits >Select the radio button for Do not limit the number of messages in an IMAP folder (default). Note: This is an end user setting, which can only be set on a per-user basis. Therefore, we recommend that you send instructions to your end users to check this setting. KB005104
- Export mailboxes to CSV file(s). From the Google Admin portal > click Users > click on ⁝ (3 vertical dots) > Download Users > Download All Users > Click OK > Save.
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 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.
- For the Source endpoint:
- Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select G Suite/Gmail.
- It is necessary to add ALL domains that will be migrated from. This means that if there are users in one project with domain names Sourcedomain.com and Destinationdomain.com, then it is important to ensure that both of these are added under Your Domains, when creating the endpoints. When you add a domain, you need to click on the "+" button.
- Enter Administrative email address. Note: This is the account that has admin access level to the Google admin portal.
- 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.
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.
- The following options are the most valuable for this migration scenario:
- Under Filtering, add: (^All Mail$|^All Mail/) KB005626
- This will filter out the All Mail label from your migration passes, which will speed them up.
- You will remove this folder filter before performing your final migration pass. These steps are included lower in this section.
- Set the Maximum concurrent migrations value. Note: The default value is 100. For cloud to cloud migrations, this value can be set to a very high number, such as 500, because both the Source and Destination environments can handle a large number of concurrent migrations.
- Under Support/Support options, add: StoreOverflowGooglePropertiesInNotes=1 KB005056
- Under Support/Support options, add: StoreOverflowGooglePropertiesInNotesPrefix="enter your text here" KB005056
- Under Support/Support options, add: SuppressReminderDays=N KB004203
- If migrating in batches, you will not be cutting over the MX records until your final batch of users has been migrated.
- If mail coexistence is required, you must set up mail forwards against those user accounts that are in the migration batches. Options:
- Manually set forwards during a migration on a per-user basis, from the individual users' portal. Note: This is only a valid option if there are a small number of users. KB004316
- Manually set forwards during a migration on a per-user basis, from the admin portal. Note: This is a suitable option for small- to medium-sized projects. KB004374
- Automate the setup of mail coexistence (forwards) for G Suite through the MigrationWiz management console tool. Note: This is the best option for large projects. KB005168
- Under Project Advanced Options > Filtering section, delete: (^All Mail$|^All Mail/) KB005626
- Select the users > Click on theStart button from the top, select Full Migration > Click onStart Migration. KB004938
- Click on the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. KB004626