Following recent acquisition of another company we faced the following situation:

Company A has Exchange 2013 Organization up and running and already using new Public Folders migrated from 2010 when we upgraded.

Company B has Exchange 2010 Organization with their own PF infrastructure.

When it comes to migration, there's already public folder mailbox which was created when first migration occured.

I cant figure next steps to merge those PF infrastructures at the moment, as removing public folder mailbox prior migration is not an option, since we already have big amount of data in 2013 Organization.

Have anyone done similiar task and if so, how did you overcome this limitation?

You're looking at a third-party product.  MigrationWiz does public folders.  There are other cloud-based migration solutions, but I don't know whether they support public folder migrations.

MigrationWiz doesnt seem to be working with On-Premises Exchange 2013.

I'll test import/export to pst scenario, but still hope that there's another way.

It should work fine if Exchange Web Services is reachable from the Internet.  Where do you see that it doe

This is exactly the case, as EWS is not exposed to outside because of security configuration.

Well, PST import/export worked just fine.

• Marked as answer by Vladimir Zanadvorov 13 hours 29 minutes ago

This is exactly the case, as EWS is not exposed to outside because of security configuration.

Well, PST import/export worked just fine.

• Marked as answer by Vladimir Zanadvorov Monday, May 18, 2015 5:56 PM

Hi,

Thanks for your response. It's great to hear the good news.

Best regards,