This guide will give you the necessary information to complete a G Suite to On-Premises Microsoft Exchange (versions 2007+).
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.
To verify what items are and are not moved during this migration, visit What items are migrated with MigrationWiz?
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.
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 the user accounts
- Create an admin account for migration that has full access permissions to all mailboxes. KB004725
- In the PowerShell script above, change the -User account to match the name of the admin account that was set up for migration.
- Any user account that is a part of the domain administrator, schema administrator, or enterprise administrator groups will not have any administrative rights to mailboxes, no matter how many permissions are granted. A security default of Exchange Server is to explicitly deny any user that is a member of these groups. This is why we recommend creating a new user account specific for migration.
- Set up a remote PowerShell session with Exchange 2010+. KB005111
- To manually grant administrative access for migration, execute the following PowerShell command in the Exchange PowerShell Console:
Get-Mailbox -ResultSize Unlimited | Add-MailboxPermission -AccessRights FullAccess -Automapping $false -User MigrationWizNotes:
- Increase message size limits. KB004613
- Increase maximum accepted content length. KB004609
- Increase maximum receive message size. KB004532
- Increase maximum accepted request length. This is only valid if your Destination server is running Exchange 2007. KB004610
- 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
- 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. It will speed up your migration passes.
- You will remove this folder filter before performing your final migration pass. These steps are included later in this section.
- Under Support/Support options, add:
- 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