What Advanced Options should I set for a PST migration project?
However, the most important Advanced Options to a PST migration project are outlined below:
- Under Source/Bucket Name, the default bucket name is set to "migrationwiz". If you are using your own Azure storage and uploaded your PST files into a container that has a different name than "migrationwiz" then change the bucket name to be the same name. For example, if your Azure storage container is named "pstblob" then change the bucket name in Advanced Options to be "pstblob". If these do not match, you will get an error when trying to import your PST files from Azure into your MigrationWiz dashboard.
- Under Destination, you can choose whether to inject the PST files into mailboxes or archives.
- Under Destination, you can choose to use impersonation to authenticate. We recommend that you check this box. This will improve the performance of your migration, since the administrator account will then impersonate each mailbox account during migration and thus utilize the bandwidth associated to each mailbox during migration.
- Under Licensing, the default value is "1" for the number of licenses to consume per pass. Each PST license covers for up to 10GB of data to be migrated. This is the maximum supported size, as per KB004888. If you have PST files larger than 10GB, you must divide the PST file down into separate PST files that are each less than 10GB in size each, and, then, use the advanced option to increase the license consumption for each item in the migration project. Read the How do I enable consumption of multiple licenses for a single item? article for more information.