This article will guide you through the steps for migrating mailboxes from a Hosted Exchange Provider to G Suite. There are some tools and resources that will make the migration easier.

Exchange questions and troubleshooting

Our Exchange Mailbox FAQ, Exchange Migration Setup and Planning, and Exchange Mailbox Migration Troubleshooting guides contain a number of common questions and concerns, along with more information, guidance, and steps to resolve issues such as throttling.

First migration?

We have created a guide on scoping, planning, and managing the migration process for your use. If this is your first migration, we recommend reading this guide carefully.

The maximum file size for migration through MigrationWiz varies by migration type and environment, but may never exceed 60GB.

DeploymentPro & DMA

DeploymentPro currently can only officially be used with migration projects where Office 365 is the Destination.

MigrationWiz

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.

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. 

We are not able to support migrations with two-factor or multifactor authentication. 

Prepare the Source Environment

Create access account

Ask the Hosted Exchange Provider to create an account for migration purposes (e.g., named MigrationWiz) and grant full access rights to each mailbox, by running this PowerShell script against the newly created account:
Get-Mailbox -ResultSize Unlimited | Add-MailboxPermission -AccessRights FullAccess -User MigrationWiz

Some Hosted Exchange providers allow this access to be granted via their web portal. In this case, you could log in to each mailbox via their portal and then grant the migration account (e.g., MigrationWiz) to have read/write access to each mailbox. This is laborious and time-consuming, and so it is preferred that the Hosted Exchange provider run the PowerShell script above, particularly if you have a large number of users.

Some Hosted Exchange Providers will not grant this access. If that is the case, then you can request credentials from your end users during the migration. 

Request user credentials

Create a project without admin credentials, and request credentials from users.

1. Create a MigrationWiz mailbox migration project. When entering the Source information, do not click on the checkbox to enter admin credentials.
2. Click on the green bar Bulk Add.
3. Click on the checkbox I don't know the login name and password for the Source mailboxes.
4. Click on the Upload bar.
5. Click on the Choose File button, and select and upload your CSV file that contains the list of mailbox names.
6. Click on the Save button.

When you submit the mailbox for migration, we will send an email with a secure link in which allows the end user to provide their credentials directly to the system. The sequence of steps are as follows:

1. You submit the item for migration.
2. An email is sent to the email address configured with a secure link to provide the credentials.
3. The end user clicks on the provided link, which opens a secure web page.
4. The end user provides their credentials directly to our system.
5. The credentials are verified.
6. The item is immediately submitted for migration.

The status of the migration will remain as "Waiting For End User" until the end user provides their credentials to the system.

Optional - Large Projects

If this is a very large project, the best results will be achieved by setting the project to use impersonation at the Source. In order to enable this, the PowerShell script below needs to be run by your Hosted Exchange provider, if they are willing.
New-ManagementRoleAssignment -Role ApplicationImpersonation -User <admin_user_name>

The second part of this process is to set your MigrationWiz project Advanced Options to use impersonation at the Source. This step is included in the MigrationWiz section in this guide.

Prepare Mailboxes

1. Test mailbox access. 
2. Export mailboxes to CSV file(s).
   • Ask the Hosted Exchange provider to provide them. 
   • If the provider has an admin console which includes this capability, run their tool to export the user list (and, if necessary, the passwords) to the CSV file.
   • If you have admin credentials on the Hosted Exchange environment, you only need a list of the email addresses. You do not need the password for each mailbox being migrated (because MigrationWiz will use delegation and perform the migration based on the admin credentials).
   • If you do not have admin credentials on the Hosted Exchange environment (which is common), you must obtain all the email addresses and passwords for the users.
   • If the list of mailboxes and passwords from the Hosted Exchange provider is not available, request that the users send these to MigrationWiz as part of the migration process.

Prepare the Destination Environment

1. Create users on G Suite. 
2. Grant MigrationWiz OAuth 2.0 access to G Suite. Note that Google is currently updating admin console UI, and the process is slightly different if this has occurred in your instance. Verify which version you have before beginning the steps below. 
3. Go to https://admin.google.com and authenticate as a Super Administrator.
4. Click Security. If you do not see the security icon on your admin console home page, you do not have the necessary rights on your account to make these changes. Request Super Administrator access from the customer to implement these changes.
5. Click Advanced settings. Google limits accessing and changing this setting to only G Suite Super Administrator accounts.
6. You will now have one of two options, depending on whether your tenant has been updated to the new Google API or not. 

7. Old Google Tenant:

   • Go to the G Suite admin page at google.com
   • Click on Security
   • Click on Advanced Settings
   • Click Manage API Client Access.

   OR If your account shows the latest UI updates from Google, as shown below:

   • Go to the G Suite admin page at google.com
   • Click on Security
   • Click Advanced Settings
   • Under ‘Domain-wide delegation’, click Manage domain-wide delegation
   • On the Manage domain-wide delegation page, click Add new
8. Click MANAGE DOMAIN WIDE DELEGATION.
9. Click Add New.
10. Enter 113321175602709078332 into the Client ID field. 
11. Enter the following groups of scopes into the OAuth Scopes (comma-delimited) field:
    
    • G Suite as the Destination (full scopes):
      https://mail.google.com/, https://www.google.com/m8/feeds, https://www.googleapis.com/auth/contacts.readonly, https://www.googleapis.com/auth/calendar, https://www.googleapis.com/auth/admin.directory.group, https://www.googleapis.com/auth/admin.directory.user, https://www.googleapis.com/auth/drive, https://sites.google.com/feeds/, https://www.googleapis.com/auth/gmail.settings.sharing, https://www.googleapis.com/auth/gmail.settings.basic,https://www.googleapis.com/auth/contacts 
12. Click Authorize.
13.  The client name is 113321175602709078332 (make sure there are no leading or trailing spaces, as this may cause the error "URL ends with an invalid top-level domain name."). This will grant BitTitan products access to the appropriate scopes.
14. If you are migrating to multiple domains, repeat these steps for each domain.

MSPComplete Steps

Create Customer

1. Click the Add button in the top navigation bar
2. Click the Add Customer button on the All Customers page
3. In the left navigation pane, select the appropriate workgroup and then click All Customers.
4. Click Add Customer.
5. Enter the new customer’s information in the Add Customer form. Primary Email Domain and Company Name are required. The rest are optional.
6. Click Save.
7. Repeat steps 1 through 4 for each customer you want to add. 

Purchase licenses

We recommend that you purchase the User Migration Bundle license for this migration scenario. User Migration Bundle licenses allow multiple types of migrations to be performed with a single license. They also allow DeploymentPro to be used to configure Outlook email profiles. For questions on licensing, visit MigrationWiz Licenses

To purchase licenses:

1. Sign in to your BitTitan account. 
2. In the top navigation bar, click Purchase.
3. Click the Select button and choose User Migration Bundle licenses.
4. Enter the number of licenses you want to purchase. Click Buy Now.
5. Enter a Billing address if applicable.
6. Click Next.
7. Review the Order Summary and enter a payment method.
8. Click Place Your Order.

Apply licenses

1. Select the correct workgroup on the top of the left navigation pane. This is the workgroup that the customer and migration project were created under. Your account must be part of the workgroup if the project was not created under your account.
2. On the left navigation pane, click Customers.
3. Click the customer that employs the user to whom you want to apply a User Migration Bundle license.
4. Click the Users tab at the top of the page.
5. Check the box to the left of the email for the user(s) to whom you want to apply a license.
6. Click the Apply User Migration Bundle License button at the top of the page. It is recommended that users be added to the Customer page with the vanity domain. Then have the User Migration Bundle Licenses applied, before editing to show the .onmicrosoft domain, if the .onmicrosoft domain will be used for the migration.
7. If there is at least one unassigned User Migration Bundle license available for each selected user, click Confirm. Important: If there are no User Migration Bundle licenses currently available to be assigned and your role in the workgroup is Manager or higher, the form that appears provides all the necessary information and will walk you through the steps of purchasing User Migration Bundle licenses.

1. 1.  

MigrationWiz Steps

Create a Mailbox Migration project

1. Click the Go to My Projects button.
2. Click the Create Project button.
3. Click on the type of project that you wish to create. For this migration:

• Mailbox: Mailbox projects are used to migrate the contents of the primary user mailbox from the previous environment to the new environment. Most mailbox migrations can migrate email, calendars, and contacts.

For mailbox migrations, use administrative credentials to access mailboxes​. In most migration scenarios, the admin account needs to have full access rights to the Source mailboxes. 

1. Click Next Step.
2. Enter a Project name and select a Customer.
3. Click Next Step.

Endpoints

Endpoints are now created through MigrationWiz, rather than through MSPComplete. The steps for this section outline how to create the endpoints in MigrationWiz.

If you are selecting an existing endpoint, keep in mind that only ten endpoints will show in the drop-down. If you have more than ten, you may need to search. Endpoint search is case and character specific. For example, Cust0mer will not show up if the search is customer. We recommend keeping a list of endpoints you have created, along with any unique spellings or capitalization you may have used.

You may either use existing endpoints, or create new ones. 

To create a new source endpoint:

1. Click Endpoints
2. Click Add Endpoint
3. Click + Find My Service Provider button
4. 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.
5. Or, instead of clicking on the + Find My Service Provider button, click the Exchange Server 2003+ button and manually enter the Outlook Web Access URL.
6. It is necessary to add all domains that will be part of the migration on either the Source or the Destination. 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 adding a domain, you need to click the "+" button.
7. 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 Source Environment" section of this guide.

To create a new destination endpoint:

8. Click Endpoints
9. Click Add Endpoint
10. Enter endpoint name
11. For endpoint type, select G Suite/Gmail.
12. It is necessary to add ALL domains that will be migrated to. 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.
13. Enter Administrative email address. This is the account that has admin access level to the Google admin portal.

Add Users

Add the user accounts that will be migrated to the project. MigrationWiz allows you to bulk import mailboxes into the system.

Use the Bulk Add option, and import from the CSV file that you prepared under the Prepare the Source section of this guide. 

• If the list of mailboxes and passwords from the Hosted Exchange provider is not available, request that the users send these to MigrationWiz as part of the migration process.

To import one or more mailboxes:

1. Sign in to your MigrationWiz account.
2. Select the Project for which you want to perform the bulk import.
3. Click Add.
4. Click Bulk Add.
5. Follow the instructions on the page.

Add Advanced Options

Under Support/Support options:

• If using impersonation, the value for Maximum concurrent migrations, under the Performance section, can be set to a very high value, e.g.,1000. There is no limit for this value if using impersonation.
• If not using impersonation, we recommend that you set the Maximum concurrent migrations value to a low number, such as 20.
• If this is a very large project, the best results will be achieved by setting the project to use impersonation at the Source (as documented in the Prepare Source Environment section of this guide). However, many Hosted providers will not accommodate this request. If they do, checkmark the box for Use impersonation at source. Note: Exchange impersonation (not delegation) utilizes per-user throttling quotas, which allows for a very large number of users to be migrated concurrently.
• Add folder mapping: FolderMapping="^INBOX/->" This will map folders to the root label on the Destination mailboxes, rather than under inbox/label name. 

Run Verify Credentials

1. Open the Project containing items you wish to validate​.
2. Select the items you wish to validate.
3. Click on the Start button in your dashboard.
4. Select Verify Credentials from the drop-down list.

Once complete, the results of the verification will be shown in the Status section.​ 

Notify Users

Notify users that a migration is occurring. Send email to all users telling them the time and date of the migration.

Run Migration

Pre-Stage pass

1. Select the users you wish to migrate
2. Click the Start button from the top
3. Select Pre-Stage Migration
4. Under the Migration Scheduling section, from the drop-down list, select 90 days ago
5. Click Start Migration.

MX Record Cutover

Change over MX records on the DNS provider's portal.

Also, include the AutoDiscover (CName) setting.

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 set up mail forwarding.

Mail Forwarding

If you are not cutting over an entire domain/organization at once by changing the MX records, you can perform a phased migration and set up coexistence by setting up forwards on the mailboxes you wish to migrate.

This can be done either through the use of PowerShell scripts, or through your Exchange Management Console. We do not recommend setting up Exchange email contacts and a DNS Internal Relay for this, since this will not allow for any Delta Migration passes to be made afterwards because the mailbox no longer exists.

By PowerShell:

Forward email to internal recipient and DON'T save local copy.

PowerShell command syntax:

Set-Mailbox -Identity <Identity> -ForwardingAddress <Office 365 User Email Address> -DeliverToMailboxAndForward $False

• Example: Set-Mailbox -Identity John -ForwardingAddress Suzan@o365info.com -DeliverToMailboxAndForward $False
• The email address specifed on the 'ForwardingAddress' parameter should exist as a Mail Contact.

Because you set DeliverToMailboxAndForward to false, a copy of the email will NOT be kept in the on-premises mailbox. When setting up forwards, make sure that you do NOT save a local copy before the forward. If you do save a local copy, then when you peform Delta passes, MigrationWiz will migrate the items that it previously hasn’t migrated (and watermarked). This will cause duplicates at your Destination.

Through Exchange Management Console:

The first step is to create the forwarding objects in your local Active Directory. These forwarding objects will be hidden from the address book, and will be used purely to forward mail for mailboxes that are migrated. Note that these objects are created but not used until you set the forwarding, so these steps can be done ahead of time.

1. Download our script to create forwarding objects to a computer that is joined to the domain.
2. Modify the script in a text editor (like Notepad) and change the forwarding domain in the top of the script to the temporary domain in the new environment, for example, company.onmicrosoft.com.
3. Run the script. You will know the script is complete when you see a confirmation.

The next step is to set up forwarding for mailboxes prior to migration. Before submitting a mailbox for migration, set the forward by performing the following:

1. Launch the Exchange Management Console from the Start Menu .
2. Expand the Recipient Configuration note from the navigation tree.
3. Click the Mailbox node from the navigation tree.
4. Right-click on the mailbox to set the forward for and click Properties.
5. Click the Mailbox Flow Settings tab.
6. Select Delivery Options and click Properties. Do not select the option "Deliver message to both forwarding address and mailbox". This is important to ensure that Delta passes do not cause duplicates. If you do save a local copy, then when you perform Delta passes, MigrationWiz will migrate the items that it previously hasn't migrated (and watermarked). This will cause duplicates on your Destination.
7. Click the checkbox Forward to, then click Browse.
8. Select the name of the user that contains the prefix (External Forward) in the display name. This is the forwarding object created previously.
9. Click OK.
10. Click OK​.

Notify users

Send email to end users to let them know what to expect for their Outlook profile reconfiguration. Samples and screenshots can be found in our DeploymentPro documentation.

Enable AutoDiscover again, so that users can create new profiles via AutoDiscover, or use DeploymentPro to automate the configuration of new Outlook profiles. 

Full (Delta) pass

1. Select the users
2. Click the Start button from the top
3. Select Full Migration
4. Click Start Migration

Run Retry Errors

Look through the user list and click any red "failed migration" errors. Review the information and act accordingly.

If problems persist, contact Support.

 

Request Statistics

Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics.