Introduction

This is the complete onboarding task flow for migrating PST (Portable Storage Table) files into G Suite mailboxes.

The following requirements for PST files need to be met:

• PST files need to be in Outlook 2003 (or later) format.
• PST files cannot be corrupted. We do not offer a solution for automatically fixing corrupted PST files and migrating them. Any corrupted PST files must be fixed before a migration can be performed. 
• If UploaderWiz is installed: All end users' desktops need to be Windows-based (running at least Windows Vista or later; Mac OS is not supported), have .NET 4.6 installed, and have the ability to run a command prompt as Administrator.

The key difference for PST migrations, when compared to standard mailbox migrations, is that the PST files need to first be discovered and then uploaded to a secure Azure Storage account before they can be migrated into the mailboxes on the Destination, using MigrationWiz.

First migration?

We’ve 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.

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. 

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

Below is a list of items that can and cannot be migrated when PST is the source. This list can change without notice, so double check this list before any and all migrations.

Prepare the Azure Environment

1. Estimate Azure storage costs. This step is optional but is useful in providing the customer with upfront storage costs ahead of time.
2. Buy an Azure subscription, or use the free one-month trial (this option is only viable if you are performing a very small migration).
3. Create an Azure storage account:

1. Log in to https://manage.windowsazure.com.
2. Click Storage.
3. Click Manage Access Keys at the bottom of the screen. The access keys need to be entered when creating the MSPComplete Source endpoint. We recommend that you create an Azure Storage Account in the same Microsoft data center as the Destination Office 365 tenant. 
4. Take note of the Storage Account Name and the Primary Access Key.

4. Create an Azure BLOB container. Take note of the name of the BLOB to be entered in the Bucket Name field in the project Advanced Options.

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:

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

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

   1. Go to the G Suite admin page at google.com.
   2. Click Security.
   3. Click Advanced Settings.
   4. Under ‘Domain-wide delegation’, click Manage domain-wide delegation.
   5. 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.

Discover PST Files and Upload to Azure

Discover PST files on the network, and upload them into Azure.

• Discover PST files and upload them to Azure via UploaderWiz in PST Discovery Mode
• Discover PST files and upload them to Azure via a Group Policy Object?
  Important: Each PST file that will be migrated must be equal to or less than 10GB. PST files that are larger than 10GB must be divided into separate files that are each smaller than the 10GB limit; otherwise, the migration will fail.
• Password-protected PSTs cannot be migrated while protected. Remove the password from any protected PSTs before migration. After migration, re-apply the passwords to protect the documents. 

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.

MigrationWiz Steps

Create a Personal Archive Migration project

1. Click the Go to My Projects button.
2. Click the Create Project button.
3. Select Personal Archive as the migration type.
4. Click Next Step.
5. Enter a Project name and select a Customer.
6. 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. Select PST.

4. It is necessary to add all 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.

5. Enter Storage Account Name and Access Key in the fields provided. When entering the Azure Storage Account Name for the source endpoint, only numbers and lowercase letters can be used. If you enter an upper case letter, your migration will fail.

To create a new destination endpoint:

1. Click Endpoints.
2. Click Add Endpoint.
3. Enter endpoint name.
4. For endpoint type, select G Suite/Gmail.
5. 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.
6. 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.

Add Advanced Options

Under Support/Support Options and Advanced Options:

• Each PST migration license allows for up to 10GB of data to be migrated. If the total file size for a single line item in MigrationWiz is greater than 10GB, then you must configure that line item to consume more than a single license; otherwise, the migration will fail for that item.
  1. Ensure that you've purchased a pool of licenses to account for a potential overrun.
  2. Enter the maximum number of licenses consumed per line item.
  3. Click Save. Items in the migration project now have permission to consume more than a single license.
• Optional: Add PSTCustomEndpointSuffix=Azure URI. The Azure URI needs to be changed to one of the following values:
  • chinacloudapi.cn (China)
  • cloudapi.de (Germany)
  • usgovcloudapi.de (government)
  • Important: This Advanced Option only needs to be added if you are uploading your PST files to a specific Azure data center, using the UploaderWiz optional parameter of azurelocation=gov, ger, or china.
• Under Source/Bucket Name, the default bucket name is set to "migrationwiz". If you are using your own Azure storage and have uploaded your PST files into a container that has a different name than "migrationwiz", change the bucket name to be the same name. For example, if your Azure storage container is named "pstblob", change the bucket name in Advanced Options to be "pstblob". If these do not match, you will get an error when trying to import your PST files from Azure into your MigrationWiz dashboard.
• Add FolderMapping="^->PST/" under Support/Support options. We recommend that you add this Advanced Option so that the items in the PST file will be mapped to a folder on the Destination, rather than into the root of the Inbox, and maintain the folder hierarchy. This helps your end users locate the items in their PST files, once migrated. 
• Set the Preferred BitTitan Data Center. For the fastest migration speeds, select the data center that is closest to your Office 365 Destination tenant.  

Import PST files

Import PST files into the MigrationWiz PST archive project.

Steps:

1. Click the Autodiscover Items bar.
2. Click the Start Autodiscover button.
3. Once the PST files have been discovered, click the green + Import Items.
4. If 0 items are discovered, a common mistake is that the Source/Bucket Name under Project Advanced Options has not been set to the correct Azure container name.

Choose destination mailbox

Choose which Destination mailbox to inject each PST file into.

The owner's email address should be displayed under the "Destination Email" column.
If change.me@bittitan.com is displayed as the Destination email address instead of the actual owner's email address, click the Edit Item (pencil icon) to the right of the row. Then, under the Destination Email Address field, enter the mailbox that this file will be ingested into.

If you have multiple PST files to migrate into a single mailbox, click the pencil icon next to the individual migration item. Then, under Source PST Path, click the Add button (the +) to add the additional PST path(s).

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.

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

Start migration

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.

Post Migration

Optional (does not apply to Microsoft storage): Delete the Azure blob container that was created during the upload to Azure. This will prevent incurring post-migration Azure costs for these containers. Be careful to only delete the container that was created for this migration project.