This migration guide contains the necessary steps to perform the actual migration, but there are many steps to preparing for migration. If this is your first time performing a migration, we have created a Migration Planning & Strategy Guide to walk you through planning, set-up, and general migration best practices.
To discover what items are moved with MigrationWiz in this scenario, and which items will not be moved, see Moved Items. Note that these items will vary by source and destination, so check the proper environment listings carefully.
MigrationWiz is a migration tool, not a syncing tool. If changes are made at the source after migration, they will not sync to the destination, nor will changes made at the destination sync to the source. 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.
OAuth administrative credentials will not function properly with G Suite for Business Legacy free accounts, G Suite Legacy free accounts, or Google Apps Legacy free accounts. Unfortunately, migration of Google Legacy free accounts is not supported.
Important: Migrating from a G Suite/Gmail endpoint requires an administrator email address which matches the end user domain.
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 you are migrating from multiple domains, repeat these steps for each domain.
- OAuth administrative credentials will not function properly with G Suite for Business Legacy free accounts, G Suite Legacy free accounts, or Google Apps Legacy free accounts. Unfortunately, migrating any Google Legacy free accounts is not supported.
- Ensure 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 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 Google Admin portal > Click Users > Click ⁝ (3 vertical dots) > Download Users > Download All Users > Click OK > Save.
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
- Create a 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
- Under Filtering, add:
(^All Mail$|^All Mail/)KB005626
- Under Support/Support options, add:
StoreOverflowGooglePropertiesInNotesPrefix="enter your text here"KB005056
- This will filter out the All Mail label from your migration passes. This will speed up your migration passes.
- You will remove this folder filter before performing your final migration pass. These steps are included lower in this section.
- Under Filtering, add:
- 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 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 Start Migration. KB004938
- MX Record Cutover. Change over MX records on the DNS provider's portal. Also, include the AutoDiscover (CName) setting.
- 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
- If you are migrating in batches, you will not be cutting over the MX records until your final batch of users has been migrated.
- Under Project Advanced Options > Filtering section, delete:
(^All Mail$|^All Mail/)KB005626
- Select the users > Click the Start button from the top, select Full Migration > Click Start Migration. KB004938