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 (18)
  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.

  3. Yesai Tchouldjian says:

    Hello Team,

    I am getting this error everytime I try to run it:

    “Public Folder mailboxes migration has not been enabled for Tenant”.

    I confirmed that PAW is enabled and there are no active migration batches.

    Any inputs/thoughts?

    1. Kapil says:

      Do let us know your tenant details, can you drop an email to with your tenant details?
      We will check and get back to you.

  4. Robin K. says:

    Hi Guys,

    That are great news!
    Could you already give an outlook when modern public folder migration to Exchange Online will be available to Exchange Online Germany (Office 365 Germany)?

    Thanks in Advance!

    1. Kapil says:

      It is available Worldwide, let us know if you are facing any issues.

  5. Jeremy says:

    Hello Team,

    In my case, my public folders and mailboxes are hosted in Exchange 2010. But two Exchange 2013 servers have been deployed, and configured as hybrid servers with HCW (dedicated public FQDN is used between Exchange On-Premise and Office 365).

    Can I use this new procedure ? Or do I have to use PF Migration procedure from Exchange 2010 to Office 365 ?


    1. Kapil says:

      If your public folders are on 2010 you need to use the 2010 migration steps.

      1. vmann says:

        Kapil, I know this isn’t the right place for it, but could you link to those 2010 migration steps?

        1. Kapil says:

          You can use the steps mentioned here
          These steps are for migrating 2010 PFs to Exchange Online.

          1. Kapil says:

            Ignore my previous comment, use this link instead

  6. Aleh says:

    we used the following link previously to make some availability for public folders from Office 365 to Exchange onpremises.
    We use Exchange 2013 CU15 in hybrid. We used Sync-MailPublicFolders.ps1 script to migrate some public folder mail addresses to office 365.
    In case, we will plan using whole public folders migration to Office Online, can we do some step to undo steps or new wizard will work good with that?

    1. Kapil says:

      There is no need to undo what Sync-MailPublicFolders script has done. Migration requires all Mail enabled Public FOlders to be present in the Exchange Online.
      So as part of Public Folder migration to Exchange Online you need to run Sync-MailPublicFolders script.

      1. Aleh says:


  7. Aleh says:

    Somebody read this topic from MS side?
    Your comment is awaiting moderation.
    From May 16, 2017 at 1:23 am

  8. Andrea Gaviraghi says:

    first of all thanks for this.
    We have Exchange 2013 CU15 On-Premise (we also used hybrid configuration but now it’s “disabled”) and after reading the entire document, we decided to proceed with the migration.
    Unfortunately the process return an error during the creation of the public folder migration endpoint and the public folder migration request:

    PS C:\PFScripts> $PublicFolderEndpoint = New-MigrationEndpoint -PublicFolder -Name PublicFolderEndpoint -RemoteServer $S
    ource_RemoteServer -Credentials $Source_Credential
    You cannot perform two types of Public Folder migration at the same time.
    + CategoryInfo : NotSpecified: (:) [New-MigrationEndpoint], MigrationPermanentException
    + FullyQualifiedErrorId : [Server=AMXPR07MB086,RequestId=7dde36ac-9e42-4602-82fd-ee8a1716abb5,TimeStamp=30/05/2017
    08:35:26] [FailureCategory=Cmdlet-MigrationPermanentException] 53B06304,Microsoft.Exchange.Management.Migration.M
    + PSComputerName :

    I don’t undertsand the reason of this.
    I already checked if there are batch/serial migration requests but none found.

    I would appreciate any help on this cause I’m stucked.


    Andrea Gaviraghi

Comments are closed.

Skip to main content