Important: When you sign in to MigrationWiz, you are redirected to the Getting Started page in MSPComplete. To get to a migration project created before April 4, 2017, click the Go to Projects button on the Getting Started Page. To create a new project for the migration scenario documented in this article, click the waffle icon () in the top navigation bar of MSPComplete, and select the appropriate migration product.
Note: You will not be able to run the PowerShell commands on your Hosted Exchange environment. Ask the Hosted Exchange provider to add this permission to the account that is being used for migration. If they do not want to provide "owner" access rights, ask them to add "read" access rights instead.
This is the PowerShell script that your Hosted Exchange provider must run in order to obtain that PublicFolderRootEntryId:
Get-PublicFolder "\the path of the PF" | fl entryid*
Note: Record the output of this script. This needs to be entered under the MigrationWiz project's Advanced Options (as indicated in the MigrationWiz Steps section below).
(Default value = 1. This allows up to 10GB to be migrated. For example: If migrating all Public Folders, using a forward slash ( / ), and the total data size = 39GB, then increase this value to 4, otherwise the migration will pause at 10GB).
For fastest migration speeds, select the Data Center that is closest to your Office 365 Destination tenant.
This flag is required if Public Folders contain items other than mail, such as calendar and contact items.
Note: You cannot use the Autodiscover option when migrating from Hosted Exchange environments. If Autodiscover is tried, it will time out, since it will attempt (unsuccessfully) to discover all Public Folders from the top-level root folder, which is protected..