1. What is the maximum attachment size allowed by the Destination system? 
• ​Most email systems impose size limits. For example, if the Destination system has a 30MB limit, any item/attachment larger than 30MB will fail to migrate.
2. What is the connection timeout for the Source and Destination system? 
• ​​For security reasons, most email systems close opened connections after a predetermined amount of time. For example, if the Destination system only has 512Kbps of network bandwidth and closes connections after 30 seconds, we may be unable to transfer large items/attachments before the connection is closed.

MigrationWiz will automatically make multiple attempts to migrate large items. Upon completion of a migration, you may resubmit it in error retry mode to try to migrate failed items. This is always free of charge.:

When migrating from or to Office 365 use the steps provided here to increase the Max Send and Max Recieve quotas, Change message size limits in Office 365.

Discover PST Files and Upload to Azure

Discover PST files on the network, and upload them into Azure.

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

MSPComplete Steps

Create Customer

1. Click the Add button in the top navigation bar.
2. Click the Add Customer button on the All Customers page.
3. In the left navigation pane, select the appropriate workgroup and then click All Customers.
4. Click Add Customer.
5. Enter the new customer’s information in the Add Customer form. Primary Email Domain and Company Name are required. The rest are optional.
6. Click Save.
7. Repeat steps 1 through 4 for each customer you want to add. 

Purchase licenses

We recommend that you purchase the User Migration Bundle license for this migration scenario. 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. For questions on licensing, visit MigrationWiz Licenses

To purchase licenses:

1. Sign in to your BitTitan account. 
2. In the top navigation bar, click Purchase.
3. Click the Select button and choose User Migration Bundle licenses.
4. Enter the number of licenses you want to purchase. Click Buy Now.
5. Enter a Billing address if applicable.
6. Click Next.
7. Review the Order Summary and enter a payment method.
8. Click Place Your Order.

Apply licenses

1. Select the correct workgroup on the top of the left navigation pane. This is the workgroup that the customer and migration project were created under. Your account must be part of the workgroup if the project was not created under your account.
2. On the left navigation pane, click Customers.
3. Click the customer that employs the user to whom you want to apply a User Migration Bundle license.
4. Click the Users tab at the top of the page.
5. Check the box to the left of the email for the user(s) to whom you want to apply a license.
6. Click the Apply User Migration Bundle License button at the top of the page. It is recommended that users be added to the Customer page with the vanity domain. Then have the User Migration Bundle Licenses applied, before editing to show the .onmicrosoft domain, if the .onmicrosoft domain will be used for the migration.
7. If there is at least one unassigned User Migration Bundle license available for each selected user, click Confirm. Important: If there are no User Migration Bundle licenses currently available to be assigned and your role in the workgroup is Manager or higher, the form that appears provides all the necessary information and will walk you through the steps of purchasing User Migration Bundle licenses.

MigrationWiz Steps

Create a Personal Archive Migration project

1. Click the Go to My Projects button.
2. Click the Create Project button.
3. Select Personal Archive as the migration type.
4. Click Next Step.
5. Enter a Project name and select a Customer.
6. Click Next Step.

Endpoints

Endpoints are now created through MigrationWiz, rather than through MSPComplete. The steps for this section outline how to create the endpoints in MigrationWiz.

If you are selecting an existing endpoint, keep in mind that only ten endpoints will show in the drop-down. If you have more than ten, you may need to search. 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.

You may either use existing endpoints, or create new ones. 

To create a new source endpoint:

1. Click Endpoints.
2. Click Add Endpoint.
3. Select PST.

4. Enter Storage Account Name and Access Key in the fields provided. When entering the Azure Storage Account Name for the source endpoint, only numbers and lowercase letters can be used. If you enter an upper case letter, your migration will fail.

To create a new destination endpoint:

1. Click Endpoints.
2. Click Add Endpoint.
3. Enter endpoint name.
4. For endpoint type, select Office 365.
5. Fill out required fields.

Add Users

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

Add Advanced Options

Under Support/Support Options and Advanced Options:

• 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.
• 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 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 Microsoft 365 Destination tenant. Read the BitTitan - Data Security and Privacy Policy 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. The Azure URI needs to be changed to one of these values:
  • chinacloudapi.cn (China)
  • cloudapi.de (Germany)
  • usgovcloudapi.gov (government)

Import PST files

Import PST files into the MigrationWiz PST archive project.

Steps:

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