This is the complete onboarding task flow for migrating mailboxes from G Suite to Hosted Exchange. Complete each step in the order listed. Links to corresponding Knowledge Base articles are provided.
The MSPComplete section includes steps to deploy the Device Management Agent (DMA) to end users. Deploying DMA to end users is a prerequisite if you will be using DeploymentPro.
DeploymentPro can possibly be used to configure the Outlook profiles, however, it is not officially supported for use with Exchange.
- Note: DeploymentPro is included with the User Migration Bundle license. DeploymentPro cannot be purchased as a standalone service license, and it cannot be added to the single-use mailbox migration license. If you wish to remotely configure Outlook mail profiles using DeploymentPro after a migration, purchase the User Migration Bundle license.
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
- 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 the customer. KB005421
- Create the Source and Destination endpoints. KB005427
- Click 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, 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 the "+" button.
- Enter Administrative email address.
Note: This is the account that has admin access level to the Google admin portal.
- Click Endpoints > Add Endpoint > + Find My Service Provider button > click the down arrow in the Service Provider field, and select the Hosted Exchange Provider (taking care to select the correct version of Exchange that the customer is running). This will auto-populate the Outlook Web Access URL with their verified URL. (Or, instead of clicking on + Find My Service Provider button, click theExchange Server 2003+ button and manually enter the Outlook Web Access URL.)
- Click the Provide Credentials radio button, and enter the admin account credentials. These are the credentials that you obtained from your Hosted Exchange Provider when following the steps under the "Prepare the Destination Environment" section of this guide.
- For the Source endpoint:
- For the Destination endpoint:
- Via Group Policy Object (GPO).
Note: This is the recommended methodology because no end user interaction is required. KB005412
- Via email. KB005411
- Launch DeploymentPro.
- Enter the Domain.
- Select the Destination endpoint.
- Checkmark the Auto-populate box.
- In the Client Interface Configurations section, upload your company logo and add supporting text.
Note: We strongly recommend doing this, because this is the logo and text that end users will see in a desktop pop-up when they are prompted to reconfigure their Outlook profiles. If you do not upload your own logo, the default BitTitan logo will be included instead.
- Save and continue.
- Go to All Products > DeploymentPro and follow the prompts to launch.
- Select a customer from the list by clicking on the customer name.
Note: The status column will show enabled when a customer account has had DMA deployed.
- Configure customer DeploymentPro module:
- Activate DeploymentPro module for users.
- Either select all or select individual users.
Note: DeploymentPro is included with the User Migration Bundle license. DeploymentPro cannot be purchased as a standalone service license, and it cannot be added to the single-use mailbox migration license. If you wish to remotely configure Outlook mail profiles using DeploymentPro after a migration, purchase the User Migration Bundle license.
- Click the Schedule Cutover button.
- Set the date and time for the Outlook profile configuration to occur, and click the Schedule Cutover button.
- The DeploymentPro module will install on user devices immediately and then run silently until this date.
- The profile cutover date should be set to a date and time that is shortly after MX record cutover.
- 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