PST to G Suite Migration Guide

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. Read the What tools do you recommend to fix corrupt PST files? article for a list of some recommended PST recovery tools.
  • 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.
  • We are not able to support migrations with two-factor or multifactor authentication. 

Set up a project using BitTitan Azure Storage. Read the How do I create a PST archive migration project using BitTitan PST Storage? article for more information.

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.

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. 

What items are migrated with MigrationWiz?

Prepare the Azure Environment

  1. Estimate Azure storage costs. This step is optional, but is useful in order to provide the customer with upfront storage costs ahead of time. Read the Estimate Azure Storage costs for migrations article for more information.
  2. Buy an Azure subscription, or use the free one-month trial and be aware that this option is only viable if you are performing a very small migration. Read the How do I buy an Azure subscription? article for more information.
  3. Create an Azure storage account, and take note of the Storage Account Name and the Primary Access Key. Log in to https://manage.windowsazure.com > Click Storage > 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. Read the How do I Create an Azure Storage Account? article for more information.
  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. Read the What are some best practice tips when creating a container in Azure? article for more information.

 

Prepare the Destination Environment

  1. Create users on G Suite. Read the Options for adding users article from Google.
  2. Grant MigrationWiz OAuth 2.0 access to G Suite. Read the Enable access to G Suite using OAuth 2.0 article for more information.
    Notes:
    • If you are migrating to multiple domains, repeat these steps for each domain.

 

Discover PST Files and Upload to Azure

  1. Discover PST files on the network, and upload them into Azure. Detailed instructions for discovering PST files can be found in these articles:

 

MigrationWiz Steps

  1. Purchase UMB licences.
  2. Set up the Project. Read the How do I create a new migration project? article for more information.
  3. Set Project Advanced Options. Read the What project Advanced Options are available?
  4. article for more information.
    • Optional: Add PSTCustomEndpointSuffix=Azure URI under Support/Support options. Read the How do I set the Azure location for PST migrations? article for more information.
      Note:
      The Azure URI needs to be changed to one of the following values:
      • core.chinacloudapi.cn (China)
      • core.cloudapi.de (Germany)
      • core.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.
      Note:
      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. Read the Can I add folder mapping in MigrationWiz? article for more information.
    • Set the Preferred BitTitan Data Center. For the fastest migration speeds, select the data center that is closest to your Office 365 Destination tenant.  Read the How do I specify the data center to use for my migration? article for more information.
  5. Import PST files into the MigrationWiz PST archive project. Steps: Click the Autodiscover Items bar > Click the Start Autodiscover button > Once the PST files have been discovered, click the green + Import Items button.
    Note:
    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.
  6. Choose which Destination mailbox to inject each PST file into.
    Notes:
    • The owner's email address should be displayed under the "Destination Email" column.
      Note:
      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 > under the Destination Email Address field, enter the mailbox that this file will be ingested into. Read the How do I choose which Destination mailbox to ingest files into? article for more information.
    • 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). Read the How do I add multiple entries to a line item in MigrationWiz? article for more information.
  7. Run Verify Credentials. Read the How do I verify credentials? article for more information.
  8. Perform a Full Migration pass.  Read the How do I start a migration? article for more information.

 

Post-Migration Step

  • Optional (does not apply to Microsoft storage): Delete the Azure blob container that was created during the upload to Azure.
    Note:
    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.
Was this article helpful?
0 out of 0 found this helpful