Announcing the availability of modern public folder migration to Exchange Online


We are happy to announce the availability of public folder migration from Exchange Server 2013/2016 on-premises to Exchange Online! Many of our customers asked us for this, and the full documentation is now here. To ensure that any version-specific instructions are addressed appropriately, we have two articles to point you to:

While all of the information is located in the documentation, the key requirements are:

  • Exchange Server 2013 CU15 (or later), Exchange Server 2016 CU4 (or later)
  • Exchange on-premises hybrid configured with Exchange Online

If you have any additional questions, let us know in comments below. Enjoy!

Public Folder Migration Team

Comments (4)

  1. RZK says:

    It would be good if anyone could tell us whats the meaning of PAW attribute

    1. Kapil says:

      PAW is a new Migration feature, end users just need to ensure that this feature is enabled.

  2. How to migrate Exchange 2007\2010 legacy Public Folders to Exchange Online?

    Use batch migration to migrate legacy public folders to Office 365 and Exchange Online:
    “This topic describes how to migrate your public folders in a cutover or staged migration from Update Rollup 8 for Exchange Server 2010 Service Pack 3 (SP3) or Update Rollup 15 for Exchange 2007 SP3 to Office 365 or Exchange Online.”

    TechNet article mentions cutover or staged migration.
    If a customer runs Exchange 2010 on-prem in a hybrid deployment, is it possible to use batch migration to migrate legacy public folders?

    1. Kapil says:

      “If a customer runs Exchange 2010 on-prem in a hybrid deployment, is it possible to use batch migration to migrate legacy public folders?” -> Yes, you can use batch Migration.

Skip to main content