How to Migrate Legacy Public Folders to Exchange Online Easily

Trying to migrate Legacy Public Folders to Exchange Online but running into compatibility issues? This usually happens because legacy public folders – those created on Exchange Server 2010 or earlier – rely on an older replication technology that is structurally incompatible with how Exchange Online handles folder data. Most IT administrators end up confused about the right process, especially when dealing with large shared folder datasets, mail-enabled folders, and complex permission mappings. In this blog, you will learn everything you need to know to transfer Legacy Public Folders to Exchange Online, including the use of the Aryson Microsoft 365 Migration Tool for quick and reliable migration. Download Now   Purchase Now

What are Legacy Public Folders in Exchange?

Legacy Public Folders are the shared repositories in Exchange Server 2010 and previous versions that allow multiple users to store & access emails, contacts, calendars, tasks, and documents centrally. Unlike modern public folders introduced with Exchange 2013, they store data inside dedicated Public Folder databases using a proprietary replication technology. It is fundamentally incompatible with how Exchange Online manages folder data today.

Checklist to Follow Before Exchange Public Folder Migration 

The user must verify the following requirements to avoid failures when you move public folders to Office 365. 

• The source must run Exchange 2010 SP3 Update Rollup 8 or later.
• Organisation Management role membership is required in both on-premises Exchange & Exchange Online.
• All user mailboxes must be migrated to Exchange Online before public folders can be moved – Exchange 2010 mailboxes cannot access Exchange Online public folders.
• External OA access must be configured on the legacy server as a strict migration prerequisite.
• Exchange Online must have no pre-existing public folder mailboxes before migration.
• Confirm there are no Active Directory objects without a corresponding Exchange object.
• The Exchange Admin Center cannot perform this migration – Exchange Management Shell and Exchange Online PowerShell are required.

Migrate Legacy Public Folders to Exchange Online Manually

The manual approach is suitable for organisations that have a moderate amount of data and an IT administrator who can easily operate with PowerShell. In this method, we will use Microsoft’s official batch migration scripts and the Exchange Management Shell that can move the legacy public folders into Exchange Online public folder mailboxes.

Easy to Follow Legacy Public Folder Migration Steps:

• First, take snapshots of the existing environment by running Get-PublicFolder -Recurse | Export-CliXML and Get-PublicFolderStatistics | Export-CliXML on the Exchange 2010 server to capture folder structure, sizes, and permissions.
• Download Microsoft’s official migration scripts

 – Export-PublicFolderStatistics.ps1, PublicFolderToMailboxMapGenerator.ps1, and SourceSideValidations.ps1 – from the Microsoft documentation repository.

• Run SourceSideValidations.ps1 on the legacy server to detect known issues such as oversized folders, permission conflicts, and orphaned objects.
• Execute Export-PublicFolderStatistics.ps1 on the Exchange 2010 server to generate a folder name-to-size mapping CSV file.
• Run PublicFolderToMailboxMapGenerator.ps1 using the size mapping output to determine how many public folder mailboxes are required in Exchange Online.
• Connect to Exchange Online PowerShell, create the required public folder mailboxes, and place the first one in HoldForMigration mode to hold the hierarchy during sync.
• Submit the migration request using New-PublicFolderMigrationRequest, supplying the Outlook Anywhere hostname, authentication method, and the migration administrator’s LegacyExchangeDN.
• Monitor progress with Get-PublicFolderMigrationRequestStatistics until the status shows Synced.
• Schedule a maintenance window, lock legacy public folders using Set-OrganizationConfig –PublicFoldersLockedForMigration $true, remove PreventCompletion, and finalise the batch.
• After completion, run Set-OrganizationConfig -PublicFolderMigrationComplete $true and unlock the modern public folders for all users in Exchange Online.

Drawbacks of the Manual Methods

• Users must invest long hours to process the large volumes of data. 
• Even connectivity issues might disrupt the synchronization process.
• Administrators may misconfigure the migration endpoint or mapping CSV files.
• You have to perform the additional pre-migration steps using the SyncMailPublicFolders.ps1 script to enable public folders. 
• Also, it is very risky to roll back a completed migration since the changed data during the migration window is not copied back to the legacy environment.

Conclusion

In this blog, we explored the different ways to migrate Legacy Public Folders to Exchange Online. If your organisation has a small dataset and a technically confident administrator, the manual PowerShell-based batch migration can work. But, it requires the user to carefully perform the prerequisites & the mandatory downtime window. But when data volume is large, or you want to avoid scripting risks & rollback complications, using automated software is the faster and safer choice. Choose a method that protects your folder data and does not make the process more disruptive than it needs to be – and act before October 2025 if you are still on Exchange 2010.

FAQs

About The Author:

Rohan Wiese

Rohan Wiese is a Technical Writer at Aryson Technologies. He is an expert Email Forensic, Cloud Computing, and a passionate nerd with over 10 years of experience in technical content writing. He writes about Cloud Migration, Database Recovery, Email Backup, Windows, Mac, and Tech.