In this blog post I wanted to go through the documented TechNet process for migrating legacy public folders to Exchange 2013/2016, expanded with real world guidance gained from field support. I have ...
Updated Oct 12, 2020
Version 5.0
Blog Post
@Marc - thank you for the remarks, and thank you for making me aware of the duplication aspects of Parts 6 & 7. I'll get that cleaned up ASAP.
@Thomas - thank you for the original script and the guidance on the updated version of it for Exchange 2007. Speaking about the roll back, I have yet to see a customer roll back a production environment, but the guidance on the TechNet article is clear. If you run the command to re-enable legacy public folders (Set-OrganizationConfig -PublicFoldersLockedForMigration:$False), you will lose the delta of data created in the modern public folders while they were in production as there is no replication mechanism between legacy and modern public folders. The only recovery mechanism I can imagine would be to move the data to .pst file in Outlook before the roll back and move it back into the legacy after it is put back into production. Exchange 2016 does index public folders, so there may be options there, but I have not lab tested that yet.