- This is the complete onboarding task flow for migrating PST 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.
- 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.
- This migration guide presumes that you have your own Azure storage subscription. If you have a small PST migration project (less than 100GB total storage for all PST files), you could use BitTitan's PST storage on Azure instead. Refer to the "BitTitan's Azure Storage" section under Step 2 "Set The UploaderWiz parameters" in the Using UploaderWiz in PST Discovery Mode article.
- 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 now supports the capability to share migration projects across a Workgroup. Migration projects are no longer tied to individual accounts, they are tied to Workgroups. When Workgroup Administrators turn on the Project Sharing feature, all Agents besides those who are Inactive are able to view all migrations projects. For more information, visit Project Sharing in MigrationWiz.
Prepare the Azure Environment
- 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.
- 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.
- 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.
- 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
- Create users on G Suite. Read the Options for adding users article from Google.
- Grant MigrationWiz OAuth 2.0 access to G Suite. Read the Enable access to G Suite using OAuth 2.0 article for more information.
- If you are migrating to multiple domains, repeat these steps for each domain.
- 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
Discover PST Files and Upload to Azure
- Discover PST files on the network, and upload them into Azure. Detailed instructions for discovering PST files can be found in these articles:
- 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.
- Create the customer. Read the View, Add, and Edit Your Customers article for more information.
- Create the Source and Destination endpoints.
- For the Source endpoint:
- Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select PST.
- Enter Storage Account Name and Access Key in fields provided.
- For the Destination endpoint:
- Click 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 Sourcedomain.com and Destinationdomain.com, 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 the "+" button.
- Enter the Administrative email address.
Note: This is the account that has admin access level to the Google admin portal.
- For the Source endpoint:
- Launch the Personal Archive Migration (select All Products/Personal Archive Migration).
- Set up the Project. Create project >Create a Personal Archive Project >Name project, and Select MSPComplete customer >Select Source endpoint >Select Destination endpoint.
- Set Project Advanced Options. Read the What project Advanced Options are available? article for more information.
- 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. Read the How do I enable consumption of multiple licenses for a single item? article for more information.
- 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.
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.
PSTCustomEndpointSuffix=Azure URIunder 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.
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.
- The owner's email address should be displayed under the "Destination Email" column.
Note: If firstname.lastname@example.org 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.
Note: We recommend that you purchase the User Migration Bundle license for this migration scenario. User Migration Bundle licenses allow you to perform multiple migrations of User mailboxes, documents, and personal archives, plus Google coexistence configuration, and allows the use of DeploymentPro to perform post-migration Outlook email profile configuration. Refer to these articles for more information:
- 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.