This is the complete onboarding task flow for migrating PST files into Office 365 mailboxes.
The following requirements for PST files need to be met:
- PST files need to be in Outlook 2003 (or later) format.
- PST files must not 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 more information about fixing corrupted PST files.
- 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 the BitTitan PST storage on Azure instead. For the steps to follow to use this, refer to the section "BitTitan Azure Storage" under step 2 "Set The UploaderWiz parameters" in the Using UploaderWiz in PST Discovery Mode article.
To set up a project using BitTitan Azure Storage. Read the How do I create a PST archive migration project? 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.
Prepare the Azure Environment
- Estimate Azure storage costs. This step is optional, but is useful in order to provide the customer with 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 store account name and the primary access key. These need to be entered when creating the MSPComplete Source endpoint. Log in at https://manage.windowsazure.com > Click Storage > click Manage Access Keys at the bottom of the screen.
Note: 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 storage. Take note of the name of the Blob to be entered in the Bucket Name field in the project advanced options. Read the Best practices when creating an Azure container article for more information.
Prepare Destination Office 365 Environment
Note: If you have already completed a mailbox migration project against this Source environment, these steps will already have been completed.
- Create an administrator account in Office 365 to be used for migration, or use the global admin account for the tenant. Read the Create an Office 365 administrator account for migration article for more information.
- Set up accounts on Office 365 and assign licenses. These can be created in several ways:
- Manually, one at a time. Read the Microsoft instructions to add users individually article for more information.
- By bulk import, via CSV file. Read the Microsoft instructions to bulk add users article for more information.
- By PowerShell script. Read the Create user accounts with Office 365 PowerShell article from Microsoft for more information.
- By DirSync, AAD Sync, or AAD connect. Read this very important Knowledge Base article before running synchronization. Read the Synchronize Active Directory objects to Office 365 article for more information.
- By BitTitan Sync tool. Read the BitTitan Sync Program article for more information.
- Prepare the tenant to send and receive large mail items. Read the How do I migrate large mail items to Office 365? article for more information.
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, then enter the 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, then enter the endpoint name. For endpoint type, select Office 365, then fill in the required fields.
- Launch In-Place Archive Migration (select All Products/In-Place Archive Migration).
- Set up the Project. Read the How do I create a new migration project? article for more information.
- Set Project Advanced Options. Read the What Project Advanced Options are available? article for more information.
- To choose the appropriate license, please refer to Which migration license should I choose?
- Under Source/Bucket Name, set the bucket name to "migrationwiz". If you are using your own Azure storage and uploaded your PST files into a container that has a different name, change the bucket name to "migrationwiz". If the container name and bucket name do not match, you will get an error when trying to import your PST files.
- Under Destination, choose whether to ingest the PST files into mailboxes or archives.
- Enable impersonation at Destination by selecting the check box Use impersonation at Destination. Read the How do I migrate to Office 365 or Exchange 2010+ using impersonation? article for more information.
- Folder Mapping. Folder mapping is optional, but you can control the mapping of folders on the destination by using regular expressions. Read the Can I add folder mapping in MigrationWiz? article for more information.
Important: By default, MigrationWiz will mirror the folder structure that exists on the Source when migrating to the Destination. When a migration starts and you are taking the default folder mappings (that is, a single folder at the root), MigrationWiz creates the Destination folder based on the item type of the first item migrated. If the first item is a calendar item, then the Destination is mapped to the root of the calendar folder. You can control this by migrating item types in batches (mail items, calendar items, etc.), each item type migrated in a separate migration pass.
- 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? article for more information.
PSTCustomEndpointSuffix=Azure URIunder Support options. This advanced option is only needed when uploading your PST files to a specific Azure data center, using the UploaderWiz optional parameter of azurelocation=gov, ger or china. 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 these values:
- core.chinacloudapi.cn (China)
- core.cloudapi.de (Germany)
- core.usgovcloudapi.gov (government)
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, and then 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? 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 in-place 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 storage 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.