This is the complete onboarding task flow for migrating PST files (Outlook Data File) into Microsoft 365 mailboxes using Graph API.

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. 

First migration?

We’ve created a guide on scoping, planning, and managing the migration process for your use. If this is your first migration, we recommend reading this guide carefully.

For more information on how to set up a project using Azure Storage, read the Azure for MigrationWiz article.

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.

Prerequisites

Review and meet the following requirements for PST files:

• PST files need to be in Outlook 2003 (or later) format.
• PST files cannot be corrupted. We do not provide an automated solution for repairing or migrating corrupted PST files. In case there are corrupted PST files, fix them before performing a migration.
• If UploaderWiz is installed:
  • Windows Vista or later is required for desktops. Mac OS is not supported.
  • Installed .NET 4.6 or later.
  • Permission 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.

Licensing

We recommend that you purchase User Migration Bundle licenses for this migration scenario. User Migration Bundle licenses allow the performance of multiple migrations with a single license. For questions on licensing, visit Which Migration License Do I Need?.

To use your license by following the next steps:

1. Review Considerations.
2. Purchase Licenses.
3. Create a Customer.
4. Apply Licenses.

Limitations

• Archive Mailbox as a destination is currently not supported. Support for this option is planned for a future release.
• Due to Microsoft limitations, using Delegate Permissions with Graph API is not supported at this time. Only Application Permissions can be used.
• Pinned/Flagged Emails are migrated but not Pinned/Flagged in the destination environment.
• Threading (email messages that belong to the same conversation) is not supported and will require Manual implementation. 
• Delegate-level calendar access isn't supported by Microsoft Graph. It's automatically downgraded to Free/Busy-only.

Migrated Items

Please click the bars below to check the migrated and non-migrated items. We are constantly working to create a better migration experience for you so these items may change over time.

Prepare the Azure Environment

1. Estimate Azure storage costs. This step is optional but is useful to provide the customer with upfront storage costs ahead of time. 
2. Buy an Azure subscription, or use the free one-month trial. The trial option is only viable if you are performing a very small migration. 
3. Create an Azure storage account. You will need to set up a STORAGE (General Purpose v2) account rather than a storage blob.
4. Take note of the storage account name and the primary access key. (In Azure, from the storage screen, click Manage Access Keys at the bottom of the screen). These need to be entered into the MigrationWiz migration project when specifying the destination settings. 

To create the Azure storage account, follow the steps below:

1. Visit the Azure portal.
2. Click Storage accounts.
3. Click Create.
4. Select the Subscription and create a new Resource group or use a current one.
5. Name the Storage account.
6. For Region, select a geographic region for the storage account.
7. For Performance, select Standard general-purpose V2 account.
8. In the Redundancy field, select Locally-redundant storage (LRS).
9. Click the Review button.
10. When the validation ends, click the Create button.
11. Once the deployment of the storage account is complete, click the Go to resource button or open up the home page for the new storage account.
12. In the Security + networking section of the left sidebar, click on Access Keys.
13. On a notepad, copy the Storage account name and the key1 and save them.

Now the storage account appears in the storage list.

Prepare the Destination Environment

Modern Authentication Requirements

The KBs listed in the Exchange Online Authentication options using Graph API section will help you configure the destination tenant when using Microsoft 365 with the Microsoft Graph API. A Global Administrator account is required to consent to the BT app or create and consent to the BYO app, since the Entra app's permission types require global admin approval.

Set up Accounts in Microsoft 365

Set up accounts on Microsoft 365 and assign licenses. These can be created in several ways:

• Manually, one at a time.
• By bulk import, via CSV file. 
• By PowerShell script. 

Prepare the Tenant to Send & Receive Large Items

We do not impose any limit on item/attachment sizes. However, large items/attachments can fail to migrate because of external factors.  There are two considerations:​

Add Users

Add the user accounts that will be migrated to the project.

Advanced Options

The following sections describe the tabs available for Advanced Options in this kind of migration.

Support Tab

Consider that each Support Option includes the "=" character and is to be entered under the Support tab in the section named Support Options.

Add additional blank fields for new Support Options by clicking on the "+" button. In case you want to delete a field click the trash can icon.

Optional Settings

• PSTCustomEndpointSuffix=Azure URI 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, or ger. The Azure URI needs to be changed to one of these values:
  • cloudapi.de (Germany)
  • usgovcloudapi.gov (government)

• Folder Mapping Folder mapping is optional, but you can control the mapping of folders on the destination by using regular expressions. Read the Folder Filtering & Mapping in MigrationWiz article for more information.

  Important

   By default, MigrationWiz mirrors 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.), with each item type migrated in a separate migration pass.

Source/Destination Tab

Ensure Mailbox is selected. Archive is not supported at this time.

Bulk Load

To upload a large list of Advanced Support options, see the Bulk Load - Advanced Options when Migrating Mailbox projects using Graph API for additional guidance.

Import PST files

Import PST files into the MigrationWiz PST archive project.

1. Click the Autodiscover Items bar.
2. Click the Start Autodiscover button.
3. Once the PST files have been discovered, click the green + Import Items.
4. 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 Destination Mailbox

Choose which Destination mailbox to inject each PST file into.

The owner's email address should be displayed under the "Destination Email" column.
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. Then, under the Destination Email Address field, enter the mailbox that this file will be ingested into.

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

Run Verify Credentials

1. Open the Project containing items you wish to validate.
2. Select the items you wish to validate.
3. Click the Start button in your dashboard.
4. Select Verify Credentials from the drop-down list.

Once complete, the verification results will be shown in the Status section.​ 

Start migration

1. Select the users.
2. Click the Start button from the top.
3. Select Full Migration.
4. Click Start Migration.

Run Retry Errors

Look through the user list and click any red "failed migration" errors. Review the information and act accordingly.

If problems persist, contact Support.

Final Steps

Users must create new Outlook profiles, set up their signatures again, and reattach any PST files attached to their previous profile.

Click the bar chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. 

Related Topics

• Authentication Options using Graph API
• Exchange Online Advanced Options using Graph API