Introduction
Microsoft's Free Public Folder Migration Tools
Microsoft provides native PowerShell cmdlets and batch migration scripts at no additional cost for migrating Exchange Public Folders to Exchange Online. These tools support both legacy (2010) and modern (2013+) Public Folders.
Organizations moving to Microsoft 365 often need to migrate their Exchange Public Folders to Exchange Online. Microsoft provides robust, free tools for this migration through the Exchange Management Shell and Exchange admin center.
This guide walks through the batch migration process using Microsoft's native tools, which is the recommended approach for most organizations. The process involves running PowerShell scripts to inventory your Public Folders, creating migration batches, and synchronizing data to Exchange Online before the final cutover.
What Are Exchange Public Folders?
Exchange Public Folders are a legacy collaboration feature that predates modern SharePoint and Microsoft Teams. They serve as shared repositories accessible to multiple users and support various content types:
- Mail-enabled folders that receive and store emails like a shared mailbox
- Calendar folders for shared schedules, appointments, and meeting coordination
- Contact folders containing organizational or departmental contact databases
- Document folders storing files, templates, and shared resources
- Task folders for project management and workflow tracking
Public Folder Versions
- Legacy Public Folders (Exchange 2010 and earlier): Data stored in dedicated Public Folder databases
- Modern Public Folders (Exchange 2013+): Data stored in Public Folder mailboxes, providing better scalability and management
The migration process differs slightly based on your source Exchange version. Microsoft provides specific documentation and scripts for each scenario.
While Public Folders remain fully supported in Exchange Online, Microsoft recommends evaluating whether to modernize to Microsoft 365 Groups, which offer better integration with Teams, Outlook, and SharePoint. However, for organizations that need to maintain the traditional Public Folder experience, Exchange Online provides the same functionality.
Migration Methods
Microsoft provides several approaches for migrating Public Folders to Exchange Online:
Batch Migration
Microsoft's recommended method using PowerShell cmdlets for large-scale migrations
Serial Migration
Folder-by-folder migration suitable for smaller deployments
PST Export/Import
Export to PST files and import to Exchange Online for specific scenarios
Recommended: Batch Migration
Microsoft recommends batch migration for most organizations. This method:
- Supports incremental synchronization for minimal downtime
- Handles large volumes of data efficiently
- Provides progress monitoring and error reporting
- Automatically creates Public Folder mailboxes based on your mapping
- Preserves all content types, permissions, and folder hierarchy
Batch Migration Process
The batch migration uses the Mailbox Replication Service (MRS) to copy Public Folder data to Exchange Online. Here's what gets migrated:
Key PowerShell Cmdlets
Get-PublicFolder Retrieve Public Folder information and hierarchy
Get-PublicFolderStatistics Get size and item count for each folder
New-MigrationBatch Create the migration batch job
Start-MigrationBatch Begin the migration process
Get-MigrationBatch Monitor migration progress
Complete-MigrationBatch Finalize and complete migration
Prerequisites
Before starting the migration, ensure the following requirements are met:
Exchange Server Version
Exchange Server 2010 SP3 RU8+, Exchange 2013 CU15+, Exchange 2016 CU4+, or Exchange 2019
Admin Permissions
Organization Management role in Exchange on-premises and Exchange Online. Global Administrator or Exchange Administrator in Microsoft 365.
Hybrid Configuration
Exchange Hybrid configured with MRS Proxy enabled on the Exchange on-premises server
Migration Scripts
Download the latest Public Folder migration scripts from Microsoft (available in Exchange installation directory or Microsoft Docs)
No Existing Public Folders in EXO
Exchange Online should not have any existing Public Folder mailboxes (except the root hierarchy mailbox if present)
Step-by-Step Migration
Follow these steps to migrate your Public Folders using Microsoft's batch migration tools:
Prepare On-Premises Environment
Run pre-migration scripts to inventory Public Folders, identify issues, and generate migration files. Use Export-PublicFolderStatistics.ps1 and Export-PublicFolderPermissions.ps1 scripts.
Create Migration Endpoint
Configure the migration endpoint in Exchange Online that connects to your on-premises Exchange server using MRS Proxy.
Create Public Folder Mailboxes
Create target Public Folder mailboxes in Exchange Online using New-Mailbox cmdlet with -PublicFolder parameter based on the CSV mapping file.
Start Migration Batch
Create and start the migration batch using New-MigrationBatch cmdlet. This begins the initial data copy and can run for days.
Complete Incremental Sync
Let incremental synchronization continue to catch up with changes. Monitor progress in Exchange admin center or via Get-MigrationBatch cmdlet.
Lock and Complete Migration
Lock source Public Folders, complete final sync, and switch users to Exchange Online Public Folders. Update DNS and client configurations as needed.
Example: Creating Migration Batch
# Connect to Exchange Online PowerShell
Connect-ExchangeOnline
# Create the migration batch
New-MigrationBatch -Name PublicFolderMigration `
-SourceEndpoint $endpoint `
-CSVData ([System.IO.File]::ReadAllBytes("C:\PFMigration\folder_mapping.csv")) `
-NotificationEmails [email protected] `
-PublicFolder
# Start the migration
Start-MigrationBatch -Identity PublicFolderMigration
# Monitor progress
Get-MigrationBatch -Identity PublicFolderMigration | Format-ListMicrosoft Documentation
For detailed instructions specific to your Exchange version, refer to Microsoft's official documentation:
Best Practices
Follow these proven best practices to ensure a successful Public Folder migration:
Audit and Clean Up Before Migration
Review your Public Folder hierarchy and identify inactive or obsolete folders. Archive or delete unnecessary content to reduce migration time and Exchange Online storage consumption.
Run Pre-Migration Reports
Execute the PublicFolderToMailboxMapGenerator.ps1 script to generate the folder-to-mailbox mapping file. Review the output to ensure proper distribution across target Public Folder mailboxes.
Test with a Pilot Batch
Create a test migration batch with a subset of folders to validate the process before migrating all Public Folders. This helps identify potential issues early.
Allow Sufficient Time for Initial Sync
The initial synchronization can take days or weeks for large Public Folder deployments. Start the batch migration early to ensure adequate time for data copy before the planned cutover date.
Communicate with Users
Inform users about the migration timeline, expected brief period of read-only access during cutover, and any changes to how they'll access Public Folders after migration.
Verify After Cutover
After completing the migration, verify folder counts, item counts, and permissions. Test user access to critical Public Folders and mail-enabled folder functionality.
Need Help with Your Migration?
While Public Folder migration uses Microsoft's native tools, our team can help with planning, troubleshooting, or other migration scenarios including mailbox, Teams, and SharePoint migrations.
Frequently Asked Questions
What are Exchange Public Folders?
Exchange Public Folders are shared repositories that store emails, calendar items, contacts, tasks, and documents accessible to multiple users within an organization. They provide a centralized location for team collaboration and information sharing, with granular permission controls at folder and sub-folder levels.
Does Microsoft provide free tools for Public Folder migration?
Yes, Microsoft provides free native tools for migrating Public Folders to Exchange Online. This includes PowerShell cmdlets in the Exchange Management Shell (EMS) and batch migration scripts available in the Exchange admin center. These tools support both legacy Public Folders (Exchange 2010 and earlier) and modern Public Folders (Exchange 2013 and later).
What is the difference between legacy and modern Public Folders?
Legacy Public Folders (Exchange 2007/2010) store data in Public Folder databases, while modern Public Folders (Exchange 2013/2016/2019) store data in specially designated mailboxes called Public Folder mailboxes. The migration process differs based on your source version, but Microsoft provides specific cmdlets for both scenarios.
How long does a Public Folder migration take?
Migration duration depends on the total data volume, number of folders, and network bandwidth. Microsoft's batch migration supports incremental sync, allowing initial data copy to run over days or weeks without user impact. Final cutover can typically be completed during a maintenance window of 4-8 hours depending on delta changes.
Can I migrate calendar and contact Public Folders?
Yes, Microsoft's native migration tools support all Public Folder content types including mail, calendars, contacts, tasks, notes, and documents. All items are migrated with their metadata and folder structure preserved.
What permissions are required for Public Folder migration?
You need Organization Management role group membership in both on-premises Exchange and Exchange Online. Additionally, the account running the migration scripts needs Mailbox Import Export role assignment and Public Folder management permissions. Global Administrator or Exchange Administrator role is required in Microsoft 365.
Should I migrate Public Folders to Exchange Online Public Folders or Microsoft 365 Groups?
Microsoft recommends evaluating whether to modernize to Microsoft 365 Groups instead of migrating to Exchange Online Public Folders. Groups provide better integration with Teams, Outlook, and SharePoint. However, if you need to maintain the traditional Public Folder experience, Exchange Online fully supports Public Folders with the same functionality.
