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.

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.

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.

Optional: 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.

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.

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.

Purchase User Migration Bundle licenses. 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. Refer to these articles for more information:

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.

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.

Add PSTCustomEndpointSuffix=Azure URI under 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: 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 which Destination mailbox to inject each PST file into.

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, 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.

Comments

I have one user who has a PST file on his local PC attached to his local Outlook client. He has been using this local PST file for email storage for years. I want to migrate this to a mailbox on the company's Office 365 Tenant. For this company I also have an Azure tenant and can easily setup a storage account with the migrationwiz blob container and copy the PST file there. Your instructions are clear. My question is if the PST file I want to migrate has a password will I be able to configure the PST password in your setup somehow. Or, will I need to remove the PST password before copying the PST file to Azure and attempting the migration?