Our organization has already moved its user mailboxes to Microsoft 365, but the public folders are still hosted on Exchange Server 2010. These folders contain shared emails, calendars, contacts, and department records that employees continue to use. We need to move this information without disrupting access or losing the existing folder structure.
I am researching how to
migrate Legacy Public Folders to Exchange Online and would appreciate advice from administrators who have completed a similar project. Since public folders are handled differently in Exchange Online, I understand that the migration needs separate planning rather than being treated like a standard mailbox move.
One concern is preserving folder permissions and ensuring that users can access the migrated content after the transition. Before starting, I would also like to export the folder hierarchy, review statistics, and document the existing permissions. This should make it easier to compare the source and destination environments and identify anything that needs attention.
I came across the
SysInfo Office 365 to PST Export Toolwhile looking into alternative migration methods. Its listed features include public folder selection, user mapping, filtering, duplicate removal, and progress reporting. These options may be helpful for managing the migration, although I would want to confirm the exact requirements for my Exchange 2010 environment before proceeding.
For administrators planning to migrate public folders to Office 365, what approach worked best for you? Did you use Microsoft's PowerShell migration process, or did you evaluate a third-party solution? I am particularly interested in practical advice about permission validation, handling large folder hierarchies, and checking the migrated data before decommissioning the old Exchange server.
Locked
