This article provides detailed instructions on configuring a migration batch to migrate public folders and their data between two Microsoft 365 tenants. The process covers migrating Mail.
Before you start, make sure you have already set up your migration project and created a public folder batch as outlined in our Migration Guide.
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
Note: Each public folder and public folder sub-folder will require a license. For example, migrating a public folder with two sub-folders will require 3 licenses.
1. Adding entities to your batch
The Automatic Method (Recommended)
It is possible to automatically populate your Items to migrate list with all public folders from the source, however, there is one prerequisite configuration:
1.1 After creating your Public Folders batch, go to Configuration > Source > Public folders.
1.2 Include public folders in user list: Set to Enabled.
1.3 Public folder username: Enter the username of an admin account at your source.
Note: This account must have owner permissions on all of the public folders and subfolders that you plan to migrate.
1.4 Go back to the Items to migrate screen.
1.5 Click on Add items to migrate > Get items from source.
1.6 The Items to migrate list will now be populated with the public folders from your source.
The Manual Method
Before configuring settings, you must add entities to your migration batch. This defines what is being migrated and where their data will go. Use the following format for each entity you add.
-
*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
*Mandatory Field
Further instructions on adding entities to your batch can be found here: Adding Items to a migration batch
For each entity added, you can select the specific data types you wish to migrate. Ensure the 'Migrate' checkbox is enabled for all entities you intend to include in the migration run.
2. Configuration Settings
Once public folders are added, you must review and configure the migration settings. These are separated into several sections.
General Settings
- Review Domain Names: Correctly configure all domain mappings. This is essential for replacing the source domain with the destination domain on email addresses and permissions during the migration.
- Date Filters: You can apply date range filters to migrate data created within a specific timeframe. If no filter is set, all items will be migrated regardless of age.
Source Platform 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.
If you would like to modify any additional source settings, please review the below article.
Microsoft 365 - Source Settings
Destination Platform 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.
If you would like to modify any additional destination settings, please review the below article.
Microsoft 365 - Destination Settings
Advanced Settings
While most advanced settings can be left at their defaults, the following is highly recommended for any M365 to M365 migration:
-
Address Replacement: Uploading an Address Replacement CSV file is critical for maintaining data fidelity. This file maps all source user email addresses to their new destination addresses.
- Why is this important? This process ensures that permissions on shared files, calendar entries, and other collaborative content are correctly re-assigned to the new user accounts. Without it, users may lose access to shared data or errors may occur during the migration process.
- For more information, refer to the Address Replacements article.
If you would like to modify any additional advanced settings, please review the below article.
3. The Migration Process
For a complete, in-depth guide that covers project planning, user communication, and detailed pre- and post-migration checklists, please review our comprehensive recommended strategy article: