This is the complete onboarding task flow for exporting either regular mailboxes or in-place archive mailboxes from Exchange Online to PST (Outlook Data Fil) files. 

For this scenario, the Destination is a Bring Your Own storage container on Azure. This will hold all of the PST files after the mailboxes have been exported to PST. The export of the selected mailboxes will be saved, in the Azure container, as one or more PST files per user mailbox. BitTitan Azure Storage is only available as a Source endpoint for PST migration.

A new PST will be created for every 10GB of data in a mailbox. This increases the export speed and leads to efficiency improvements.

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.

MigrationWiz

MigrationWiz is a migration tool, not a syncing tool. If changes are made at the source after migration, they will not sync to the destination, nor will changes made at the destination sync to the source. 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. 

Prerequisites

Licensing

Purchase and apply User Migration Bundle licenses for all the users being migrated. For this migration type, we suggest the User Migration Bundle. For questions on licensing, visit Which Migration License Do I Need?.

• User Migration Bundle Licenses have unlimited data available per license.
• User Migration Bundle Licenses are applied to the customer's users and expire 12 months after their purchase date. 
• Document and Personal Archive projects are all included when using User Migration Bundle Licenses.
• This license type must be applied manually.

To use your license by following the next steps:

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

Limitations

Please review the following limitations before performing this type of migration.

• We are not able to support migrations with two-factor or multifactor authentication. 

Prepare the Source Environment

# Check current status:
Get-OrganizationConfig | fl EWSEnabled 
# Enable EWS: 
Set-OrganizationConfig -EWSEnabled $true

# Check a specific mailbox 
Get-CASMailbox -Identity user@domain.com | fl EWSEnabled 
# Enable EWS for a specific mailbox 
Set-CASMailbox -Identity user@domain.com -EWSEnabled $true 
# Enable EWS for ALL mailboxes (use with caution) 
Get-CASMailbox -ResultSize Unlimited | Set-CASMailbox -EWSEnabled $true

Get-OrganizationConfig -RetrieveEwsOperationAccessPolicy | Format-List EwsAllowedAppIDs

Set-OrganizationConfig -EwsAllowedAppIDs "11111111-2222-3333-4444-555555555555,aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee"

Get-OrganizationConfig -RetrieveEwsOperationAccessPolicy | Format-List EwsAllowedAppIDs

# Read the current allow list
$current = (Get-OrganizationConfig -RetrieveEwsOperationAccessPolicy | Select-Object -ExpandProperty EwsAllowedAppIDs)
# Define the new App ID to add
$newAppId = "99999999-8888-7777-6666-555555555555"
# Combine existing and new values
$updated = @($current, $newAppId)
# Write the updated allow list back
Set-OrganizationConfig -EwsAllowedAppIDs ($updated -join ",")

# Read the current allow list
$current = (Get-OrganizationConfig -RetrieveEwsOperationAccessPolicy | Select-Object -ExpandProperty EwsAllowedAppIDs)
# Define the App ID to remove
$removeAppId = "99999999-8888-7777-6666-555555555555"
# Split the comma-separated list into individual App IDs
$appIds = $current -split ","
# Remove the specified App ID
$updated = $appIds | Where-Object { $_ -ne $removeAppId }
# Write the updated allow list back
Set-OrganizationConfig -EwsAllowedAppIDs ($updated -join ",")

Modern Authentication Requirements

The steps listed in the Required Permission for Performing M365 Mailbox and Archive Migrations article apply to both the source and destination tenant when they are Exchange Online, in regards to Exchange Web Services (EWS) in the mailbox and archive mailbox. Use a Global Administrator for the configuration steps.

Please review the documentation before preparing the source.

Create a Migration Service Account

Create a migration service account in Microsoft 365 for the tenant, this account does not require any admin role assigned. However, it must have full access to the user mailboxes or have the required API Permissions.

We recommend adding the necessary API permissions to the Modern Authentication app you are using for your O365 mailbox or archive mailbox endpoint. You can follow the steps outlined in this guide, as this is BitTitan's recommended approach.

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:​

Prepare the Destination Environment

1. Estimate Azure storage costs. This step is optional but is useful in providing the customer with upfront storage costs ahead of time.
2. Buy an Azure subscription, or use the free one-month trial (option only viable for very small migration).
3. Create an Azure storage account:
   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.
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.

MigrationWiz Steps

Create a Mailbox Migration Project

Create the Mailbox Migration project or Archive Migration project (depending on whether you are exporting regular or in-place archive mailboxes to PST). Read the How do I create a new migration project? article for more information.

1. Create the Mailbox Migration Project or In-Place Archive Project

2. Select the customer, or create a new one.

   Important

   If you are migrating a mixture of regular mailboxes and in-place archive mailboxes, create one mailbox migration project and one archive project.

3. Create source and destination endpoints.

Endpoints

Endpoints are created through MigrationWiz. If you select an existing endpoint from the dropdown, it will only show ten endpoints. If you have more than ten, you may need to search it.

Consider that endpoint search is case and character-specific. For example, Cust0mer will not show up if the search is customer. We recommend keeping a list of endpoints you have created, along with any unique spellings or capitalization you may have used.

Create your Endpoints

Please review the following tabs to create your destination and source endpoints.

Create the Source and Destination endpoints. 

Region of Destination Tenant

The Region of Destination Tenant feature optimizes the migration performance and speed by choosing the region closest to the destination tenant. MigrationWiz displays a dropdown that allows you to select the destination region when configuring your destination endpoint. 

Add Accounts

Using Bulk Add, add the accounts, also referred to as "items", that will be migrated to the project:

1. Sign in to your MigrationWiz account.
2. Select the Project for which you want to perform the bulk import.
3. Click Add.
4. Click Bulk Add.
5. Follow the instructions on the page.  

Please consider the following information when adding your accounts.

• The Source will be the SMTP address for each mailbox.
• The Destination will be the name that you want for the PST file. It must include .pst at the end of each entry. A good format to follow is to name each file after the username that the PST file will belong to, e.g., user1.pst, user2.pst.

Advanced Options

The following advanced options show you some options that will help you to perform o complete a migration.

Source/Destination Tab

• Bucket Name = migrationwiz
  • This field can be left as it is if you did not create your own Azure container when preparing your Destination environment. The PST files will be exported to a container named "migrationwiz".
  • If you created an Azure container with a different name, this entry must be changed to match the name of your container.

Run Verify Credentials

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

Once complete, the results of the verification 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.

Post Migration

Optional (does not apply to Microsoft storage): Delete the Azure blob container that was created during the upload to Azure. 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.