Skip Ribbon Commands
Skip to main content

PST to G Suite Migration Guide

Last Update: 7/21/2017 11:34 AM
This article has been moved to our new Help Center. Please update your bookmarks.

​​​​​PST to G Suite Migration Guide

Important: When you sign in to MigrationWiz, you are redirected to the Getting Started page in MSPComplete. To get to a migration project created before April 4, 2017, click the Go to Projects button on the Getting Started Page. To create a new project for the migration scenario documented in this article, click the waffle icon (waffle.png) in the top navigation bar of MSPComplete, and select the appropriate migration product.


  • This is the complete onboarding task flow for migrating PST files into G Suite mailboxes.
  • Important: When exporting PST files, Outlook tasks and Outlook notes are not migrated.
  • 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. The following article provides a list of some recommended PST recovery tools: KB004929
    • All end users' desktops need to be Windows-based (running at least Windows XP or later; Mac OS is not supported), have .NET 4.0 installed, and have the ability to run a command prompt as Administrator.
  • This migration guide presumes that you have your own Azure storage subscription. If you have a small PST migration project (<100GB total storage for all PST files), you could use BitTitan's PST storage on Azure instead. For the steps to follow to use this, refer to the section "BitTitan's Azure Storage" under Step 2 "Set The UploaderWiz parameters" in KB005175.
  • To set up a project using BitTitan Azure Storage, see KB004912.
  • 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.

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. KB005177
  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. KB004996

  3. Create an Azure storage account, and take note of the Storage Account Name and the Primary Access Key. (Log in to: > Click on Storage > click on Manage Access Keys at the bottom of the screen.) These 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. KB004832

  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. KB008059​

Prepare the Destination Environment

  1. Create users on G Suite. Refer to the G Suite admin help article here.
  2. Grant MigrationWiz OAuth 2.0 access to G Suite. KB005019
    • Notes:
      • If you are migrating to multiple domains, repeat these steps for each domain.
      • G Suite as the Destination (full scopes):,,,,,,

Discover PST​ Files and Upload to Azure

  • Discover PST files on the network, and upload them into Azure. Important: Detailed instructions for this can be found in KB005858.

MSPComplete Steps (

  1. Create the customer. KB005421
  2. Create the Source and Destination endpoints.
  3. For the Source endpoint:
    • Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select PST.
    • Enter Storage Account Name and Access Key in fields provided.
  4. For the Destination endpoint:
    • Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type select G Suite/Gmail.
    • 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 and, then 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 on the "+" button.
    • Enter the Administrative email address. Note: This is the account that has admin access level to the Google admin portal.
  5. Launch the Personal Archive Migration (select All Products/Personal Archive Migration).

MigrationWiz Steps

  1. Set up the Project. Create project >Create a Personal Archive Project >Name project, and Select MSPComplete customer >Select Source endpoint >Select Destination endpoint.
  2. Set Project Advanced Options KB004834

    • Set the value for Licensing/Maximum licenses to consume a per item per pass licensing count. The default value = 1. This allows up to 10GB to be migrated. For example: If the largest PST file = 27GB, set this value to 3, otherwise this migration will pause at 10GB. KB004890
    • 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. KB005017
    • Set the Preferred BitTitan Data Center. For the fastest migration speeds, select the data center that is closest to your Office 365 Destination tenant.  KB004268
    • Add PSTCustomEndpointSuffix=Azure URI under Support/Support options. KB005894
      • Note: The Azure URI needs to be changed to one of the following values:
        • (China)
        • (Germany)

        • (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.

  3. Import PST files into the MigrationWiz PST archive project. Steps: Click on the Autodiscover Items bar > Click on the Start Autodiscover button > Once the PST files have been discovered, click on 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.
  4. 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 is displayed as the Destination email address instead of the actual owner's email address, click on 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. KB004937

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

  5. Run Verify Credentials. KB004511
  6. Purchase licenses. Steps: Click on Purchase > Personal Archive Migration > MigrationWiz-PST Migration & Discovery Bundle. KB004647
  7. Perform a Full Migration pass (Checkmark the box next to the Root Path >From the drop-down list, select the Start button > Select Full Migration >Click on the Start Migration button). KB004938

Post-Migration Step

           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.