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
During an on-going synctonization between Exchange 2010 and Exchange Online, is it possible to split a large public folder into several target PF-mailboxed in flight, or do we have to roll back, re-create the CSV-files and start all over again?
All - apologies for the wait on the replies. The life of a transactional PFE... ;-)
@Rolf - I must defer to the product group (Brian Day is the product group as far as I'm concerned) on this one.
@Nguyen - you absolutely may remove legacy public folders as part of your overall Exchange 2010 decommissioning process. There is no demand to move them to Exchange 2013/2016.
@Andreas K - I see no issue with creating the necessary public folder mailbox and public folder in Exchange 2013, then moving the contents of the PST into the folder via Outlook.
@Peter - from what I've seen, temporarily increasing the MaxSendSize and MaxReceiveSize with a Set-TransportConfig command to something larger than your largest public folder item will allow the process to go through. As mentioned above in the post, you have the option of manually saving the items off and using the -LargeItemLimit parameter to allow the synchronization to complete.