This guide provides the process and information necessary to migrate an instance of Microsoft 365 to G Suite. 

First time?

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.

Limitations

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.

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

App password usage is not supported by this endpoint. 

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

The maximum size of a single email message according to Google is 25 MB, including all attachments. Please note that the process of adding a file to a message increases its size (by adding encoding necessary for transmission)

Exchange Web Services (EWS) must be enabled for the mailboxes in the Exchange Online tenant for this migration type

Preparing the Source

Modern Authentication Requirements

Create Global Administrator Account

Create a Global Administrator account in Microsoft 365 to be used for migration or use the Global Administrator account for the tenant. In order to have administrative permissions to migrate mailbox data, grant the account permissions on each mailbox.

• Having administrative access to the Microsoft 365 control panel to manage users does not mean the same account has permissions to access all mailboxes for migration.
• Having delegated admin access to accounts does not provide enough access.

Enabling an administrative account the ability to access Microsoft 365 user mailboxes can be performed by adding the Impersonation role or Full Access mailbox permissions.  The below steps will explain how to configure the permissions access for both options.

Impersonation

To enable the admin account to impersonate users, run the below PowerShell commands:

$LiveCred = Get-Credential

Install-Module -Name ExchangeOnlineManagement
Import-Module -Name ExchangeOnlineManagement
Connect-ExchangeOnline -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred

Enable-OrganizationCustomization

New-ManagementRoleAssignment -Role ApplicationImpersonation -User <admin_user_name>

More information about this PowerShell command can be found here.

• MigrationWiz uses delegation by default to log in to individual user mailboxes using administrative credentials specified on the connector. 

It is highly recommended to use impersonation when migrating from or to Microsoft 365.

Benefits:

Using impersonation, it is possible to stop sharing the throttling quota and connection limits associated with a single administrative account. Instead, the throttling quota of each user is used to log in to each user mailbox.

Using impersonation means:

• Eliminating most "Connection did not succeed" errors
• Allowing migration of more mailboxes concurrently
• Reducing the impact of throttling and connection limits
• Using an admin account without assigning a license to it

Full Access

To manually grant administrative access for migration, execute the following remote PowerShell commands: 

$LiveCred = Get-Credential


Install-Module -Name ExchangeOnlineManagement
Import-Module -Name ExchangeOnlineManagement
Connect-ExchangeOnline -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred


Get-Mailbox -ResultSize Unlimited | Add-MailboxPermission -AccessRights FullAccess -Automapping $false -User <admin_user_name>

• The command needs to be applied each time a new mailbox is created since permissions are set directly on each mailbox. The administrative account will not have access until the permissions are applied.
• This username is the Administrative Username that needs to be entered under the project's Source or Destination settings, within MigrationWiz, when checking the box labeled Use Administrative Login.

Preparing the Destination

For this scenario, the Google IMAP or the API endpoints may be used. 

Licensing

Licenses are required to run a migration project in MigrationWiz. To obtain license pricing information, or to purchase licenses, click the Purchase button in the top of your MSPComplete or MigrationWiz dashboard.

Payment: We accept credit cards, and wire transfer in certain situations.  

• When purchasing with a credit card, payment is immediately processed during checkout. If successful, licenses are granted to your account instantly.
• Wire transfers are available for purchases of 100 or more licenses. If you are purchasing at least 100 licenses, you will be presented an option to purchase via wire transfer during checkout. A wire transfer checkout will generate an invoice with wiring information for your accounts payable department and bank. Once the funds are received by our system, the licenses are granted to your account immediately. 

Create A Project

Create a Mailbox Migration Project

1. Click Go To My Projects.
2. Click Create Project.
3. Select a Mailbox migration type. 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.
4. Click Next Step.
5. Enter a Project name and select a Customer.
6. Click Next Step.
7. Select a Source Endpoint from the Endpoint drop-down menu. If an Endpoint has not been created, click New and provide the requested information in the Endpoint creation flyout window.
8. Select a Destination Endpoint from the Endpoint drop-down menu. If an Endpoint has not been created, click New and provide the requested information in the Endpoint creation flyout window.
9. Click Save and Go to Summary.

Set up the Google API endpoint during project creation

1. During the project creation process, click New for the Destination Endpoint.
2. From the dropdown menu, select G Suite (Gmail API).
3. Click Select File.
4. Navigate to and select the JSON file that contains the Google Service Account key that was saved during the service account setup process.
5. Enter the administrator email address.
6. Click Add. 

Add Accounts (Items)

Add the accounts that will be migrated, also referred to as items, to a project using one of the following options:

• Quick Add: This option allows you to add items one at a time. You have to enter an email address, login name, and password for each user if you didn't enter administrative credentials when setting up the project. You only have to provide an email address if you entered administrative credentials when setting up the project.

• Autodiscover Items: MigrationWiz detects the mailboxes directly at the Source using Autodiscover. 
  1. Navigate to the project you want to import users into.
  2. Ensure that you have created an endpoint for the source project.
  3. Once in the project, on the top navigation bar, click on the Add drop-down, then select Autodiscover Items. This will begin the Autodiscover process.
  4. Once discovered, click on the Import button, to import the items into your MigrationWiz project.

• Bulk Add: This option allows you to add multiple items at once by copying and pasting from a spreadsheet or by importing a CSV file. The domain names at the Source and at the Destination might be different. Make sure to provide the right information in the project. If they are different, it's best to modify these in your CSV file, and then use the Bulk Add feature to import the users into the dashboard.
  1. Select the Project for which you want to perform the bulk import.
  2. Click on Add.
  3. Click on Bulk Add.
  4. Follow the instructions on the page.

Add User Migration Bundle licenses 

For this project type it is recommended to use our User Migration Bundle licenses. 

1. Sign in to MigrationWiz at https://migrationwiz.bittitan.com.
   • You can either sign in and make sure to select the MigrationWiz button above the email field or sign into MSPComplete page, then click the All Products button and select MigrationWiz.
2. 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 and project sharing must be enabled, if the project was not created under your account.
3. Click the project that requires licenses to be applied.
4. Check the box to the left of the email for the user(s) to whom you want to apply a User Migration Bundle license.
5. Click the More menu (3 stacked lines) at the top of the project page.
6. Click Apply User Migration Bundle License.

Set Advanced and Support Options

Advanced Options allow you to choose your notifications, filtering, maintenance, licensing, performance, and some configuration options.

Support Options are advanced configurations that make use of PowerShell or code blocks to provide extra options or resources for your migration.

The following options are the most valuable for this migration scenario:

Set the Project Advanced Options

• Under Support/Support options add: 
  FolderMapping="^INBOX/->" under Support/Support options.
  This will map folders to the root label on the Destination mailboxes, rather than under inbox/labelname. 

Run Migration

The following sections will guide you through setting up and launching your migration. Each header is one step, with its component steps below. Follow these steps in order, and read the notes for important information about dependencies or best practices.

Run Verify Credentials

1. Open the Project containing items you wish to validate.
2. Select the items you wish to validate.
3. Click the Start button in your dashboard.
4. Select Verify Credentials from the drop-down list.
5. Once complete, the results of the verification will be shown in the Status section.

Notify Users

Send out the final notification that the migration is beginning. Include when the migration will start, expected duration, any usage instructions during migration, and any expected steps or notifications for the post-migration timeline.

Pre-Stage Pass

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

MX Record Cutover

Change over MX records on the DNS provider's portal once the Pre-Stage Pass has completed for the users. Also, include the AutoDiscover (CName) setting. There are several options for this, based on the size of your project.

If Mail Coexistence is Required

If mail coexistence is required, you must set up mail forwards against those user accounts that are in the migration batches. This Google documentation explains how. 

Run Full (Delta) Pass Migration

1. Select the users – you may either select individual users, or select all users in a project by clicking the checkbox to the left of Source Email.
2. Click the Start button from the top
3. Select Full Migration. If you want to delay your migration, then select the checkbox marked "Automatically start the migration at", and enter the date and time to have the migration start. To start a migration immediately, you do not need to select the scheduling option.
4. Click Start Migration. 

Run Retry Errors

Each error logged represents an item that was not migrated. MigrationWiz contains a mode in which you can resubmit the migration to retry failed items. This mode of operation is always free of charge. You may only submit mailboxes in this mode only if they satisfy all of the following conditions:

1. The last migration completed successfully.
2. The mailbox contains at least one error.

If your mailbox does not satisfy these conditions, you will receive a warning when submitting the migration in this mode and your request will not be fulfilled.

To submit one or more mailboxes in retry mode, perform the following steps:

1. Click the Go To My Projects button.
2. Select the project that contains the mailboxes that you want to retry.
3. Select the mailboxes that have migration errors.
4. Click on the Start button.
5. Select Retry Errors from the menu.
6. Click the Retry Errors button.

When errors are repaired, they will disappear from the error log. Some errors may not disappear if the Source item was not reprocessed (due to filters, for example), has been deleted or moved, or if the item failed again.

Review the information and act accordingly. If problems persist, contact Support.

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