We just finished our 2007 to 2013 public folder migration. It appeared at first that everything went well. There were no errors reported in any of the jobs. There was about a 2 week period from when we started the migration to when we did the finalization and cutover. During that 2 week period I ran several incremental sync jobs using the "Resume-PublicFolderMigrationRequest \PublicFolderMigration " from the Microsoft serial migration whitepaper. 

We just discovered that we're missing all content that was added after we started our initial migration job, meaning that all the incremental sync jobs didn't copy any of the changes.  I was wondering if anyone else had encountered this.  We did this migration by the book and we have both 2007 and 2013 exchange environments up to date with the latest exchange updates.

Hi,

Based on the description, you run the Set-OrganizationConfig -PublicFoldersLockedForMigration:$true command to lock the legacy public folders for finalization.  After about two weeks, you then remove the PreventCompletion flag and resume the migration request to finalize the migration.

But after you resume the migration request, the change in public folder permissions or hierarchy, or content posted to public folders that occurred during the two weeks period are lost.

Generally speaking, the change made on public folders after you migration to Exchange 2013 will be lost only when you roll back the migration.

Do you have backup of public folders?

Besides, please check the following blog and see if it will help you to restore public folder information.

http://blogs.technet.com/b/exchange/archive/2013/08/23/recovering-public-folder-information-in-exchange-2013.aspx

Best regards,

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

Hi,

Is there any update with your issue?

Best regards,

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com