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.
Set users on Office 365 to access legacy on-premises Public Folders and if migrating the on-premises Public Folders to Office 365,
configure the admin account to look at Office 365 folders by default while all other users look at on-premises Public Folders.
Once migration is complete,
configure Office365 users to access Office365 Public Folders:
Once the tool is complete, you must run the migration from the new project, and can then delete the original project.
set-MailPublicFolder -Identity PFAlias -PrimarySmtpAddress
email@example.com –emailaddresspolicy $false
get-publicfolder -identity "\PFAlias" | Add-PublicFolderClientPermission -User Anonymous -AccessRights CreateItems
get-publicfolder -recurse | Add-PublicFolderClientPermission -User Anonymous -AccessRights CreateItems
Note: This step is important if external domains cannot send mail to the mail-enabled Public Folder email addresses.
Note: Without setting this, Office 365 bounces the message before it even checks whether a valid Public Folder address exists.
Note: This is important, in order to migrate any residual items that were sent to the Source Public Folders after the second migration pass began, when the Organization Configuration was set to remote, during migration.