Migrating Hosted Microsoft Exchange Public Folders to Microsoft 365 Public Folders

This article provides instructions on configuring a migration batch for migrating public folders from Hosted Microsoft Exchange to Microsoft 365. The setup process outlined here focuses on migrating Mail, this is the only available data type for this scenario.

Before proceeding, ensure you have completed the steps in the Hosted Microsoft Exchange to Microsoft 365 Migration Guide to set up your migration project and added your public folders migration batch.

Additionally, you will need to ensure you have followed the steps in the below article to create a public folder mailbox at the destination.

How to Create a Public Folder Mailbox

Adding Items to Migrate

When preparing to migrate users to corresponding accounts at the destination, follow the format below:

  • Export Type: Public folder
  • Export Name: Path to source public folder
  • Import Type: Public folder
  • Import Name: Path to destination public folder
  • Given Name: Not required
  • Family Name: Not required
  • Documents Path: Not required
  • Documents Destination Path: Not required
Each public folder and sub-folder will need to be added as an item to migrate. Each item will also consume a license. Sub-folders are not included when specifying the parent public folder.

For each entry, select the specific items you wish to migrate. Make sure the 'Migrate' option is enabled for all public folders included in the migration.

General Settings

In the General Settings section, ensure all domain mappings are configured correctly to facilitate replacing the source domain with the destination domain during the migration.

You can also apply date range filters for various data types to migrate information within a specific timeframe. Specify the date ranges you wish to include.

Source Settings

For a standard public folder-to-public folder migration, it is recommended to keep most of the source settings at their default values. However, you will need to ensure you modify the below.

  • Public folders -> Public folder username: You will need to enter the username of an admin account at your source that has owner permissions on all of the public folders and subfolders that you plan to migrate.

More details on the available settings can be found in the below article.

Hosted Microsoft Exchange - Source Settings

Destination Settings

Depending on your migration plan, you may need to modify several settings in this section:

  • Public folders -> Nest public folders: With this option enabled, you can specify a nested public folder name. All migrating public folders will be created within this top level folder at the destination.

  • Public folders -> Nested public folder name: If the above option is enabled, you can specify the name of the top level folder here.

More details on the available settings can be found in the below article.

Microsoft 365 - Destination Settings

Advanced Settings

For a straightforward public folder-to-public folder migration, most advanced settings can remain at their default values. However, consider the following:

  • Address Replacement: It is highly recommended to upload an address replacement CSV that maps source users, groups and aliases to their corresponding destination users, groups and aliases. For more information, please refer to the Address Replacements article.

Migration Process

The migration process will vary depending on your project's specific approach. Generally, it is advisable to start with a bulk migration and perform delta migrations closer to the final migration cutover date.

Was this article helpful?
0 out of 0 found this helpful