Modern Public Folders
Microsoft introduced “modern” public folders in Exchange 2013. The only modern aspect of the implementation is storing public folders in mailboxes, where they can take advantage of Exchange’s Native Data Protection functionality instead of depending on the creaky replication mechanism used since the introduction of public folders in Exchange 4.0 in 1996.
Initially, Microsoft supported the migration of old-style public folders from on-premises servers to Exchange Online. For whatever reason, customers who went through the torturous process of migrating old-style public folders to modern public folders in Exchange 2013 hit a brick wall. They could not move those modern public folders to Exchange Online, even though the folders were the same type on both side of the cloud divide.
Onto the Cloud
Microsoft eventually solved the problem and introduced the ability to move modern public folders from Exchange 2013 and 2016 servers to Exchange Online in March 2017. All you need is to make sure that you run the latest cumulative updates on your on-premises servers and follow Microsoft’s directions to flow data to the cloud. The process is manual and tiresome and involves manipulation of CSV files, but it does work.
It is reasonable to ask why it took Microsoft so long to deliver this functionality. I think it comes down to priorities and available development resources. When Microsoft delivered the public folder migration tools for Exchange 2013, the goal was to move customers off old-style public folders. Later, when Exchange Online introduced support for modern public folders, the tools could accommodate migration from old-style public folders, which suited Microsoft’s strategic direction at the time.
On-Premises or Cloud
Customers face a fundamental decision to move to the cloud or stay on-premises. Relatively few customers would incur the cost of upgrading to Exchange 2016 and then decide to move to Exchange Online. That doesn’t make sense. Once customers take a decision about the platform to use, it is reasonable to assume that they want to use modern public folders on their chosen platform.
Microsoft knows that those who move to Office 365 migrate mailboxes first. Public folders are typically handled last in a migration. This is not a big problem because cloud mailboxes can access on-premises public folders. Overall, it is unsurprising that Microsoft decided to delay introducing migration tools to move modern public folders from on-premises to the cloud.
Conspiracy theorists will say that Microsoft’s real goal is to convince customers to move public folders to SharePoint or another repository and therefore they did not want to support migration of modern public folders to the cloud. Although a nice conspiracy always drives debate on social media, there’s really nothing in it. The idea gained currency in the Exchange 2007/SharePoint 2007 era but was never more than idle chatter. No migration tools were produced and no serious effort was put into figuring out all the complexities of moving all the various kinds of data found in public folders to SharePoint entities.
Bringing Old Stuff to Modern Collaboration
Public folders have served as a collaboration platform for Exchange for over twenty years. However, much better collaboration technology exists inside Office 365. Although no one has yet proposed migrating public folders to Microsoft Teams (no doubt this idea will surface in time), ISVs offer tools that can move public folders to shared mailboxes or Office 365 Groups – or even to modern public folders running on Exchange Online.
Three examples that can handle modern public folders are BitTitan MigrationWiz, Binary Tree E2E Complete, CodeTwo Office 365 Migration, and QUADROtech PublicFolderShuttle. These products can move the data found in public folders to various destinations in the cloud including shared mailboxes (which are free in terms of licensing). PublicFolderShuttle also includes Office 365 Groups as a destination, which is a good choice if you use public folders for collaboration rather than a convenient dumping ground for shared email. If you do, a shared mailbox is a better option.
Interestingly, before doing any migration, PublicFolderShuttle analyzes the public folder hierarchy and data to determine the best destination for different folders. Experience gained from analyzing many public folder hierarchies reveals that relatively few public folders (probably 10% or less) are good candidates to be transformed into Office 365 Groups. Suitable folders are highly active, mail-enabled, and hold both email items and documents – or just documents.
Other public folders are better moved to shared mailboxes, especially those that only hold email items. The remainder of public folders that contain valuable data could be moved to modern public folders within Exchange Online, even if those folders then become archives.
Another interesting fact gleaned by analyzing public folder hierarchies is that it is common to discover that a large percentage of public folders have not been used recently. These folders are candidates to be pruned and discarded rather than being moved to the cloud.
The cost of commercial solutions is outweighed by the automation and flexibility of the toolsets. Of course, you can do-it-yourself by exporting public folder content to PSTs and importing the data into whatever target you think is reasonable. Such an approach is only useful when you have only a small number of folders to move.
The Cockroaches Persist
I have often referred to public folders as the “cockroaches of Exchange” because of their ability to survive for so long despite so little tender loving care from Microsoft. The nice thing is that we now have some real opportunities to move public folders to modern collaboration platform. Not Teams (yet, if ever), but definitely Office 365 Groups.
Follow Tony on Twitter @12Knocksinna.
Want to know more about how to manage Office 365? Find what you need to know in “Office 365 for IT Pros”, the most comprehensive eBook covering all aspects of Office 365. Available in PDF and EPUB formats (suitable for iBooks) or for Amazon Kindle.