Note that the 25 GB limit cited here only applies to the public folder and not to any child or sub-folders the folder in question may have.

For details, see Add Members to a Role Group.īefore you begin the public folder migration, if any single public folder in your organization is larger than 25 GB, we recommend that you delete content from that folder to make it smaller, or divide the public folder's content into multiple, smaller public folders. In Exchange Server, you need to be a member of the Organization Management or Server Management RBAC role groups. For details about how to enable the Organization Management role group, see Manage role groups. This role group is different from the permissions assigned to you when you subscribe to Microsoft 365, Office 365, or Exchange Online. In Exchange Online, you need to be a member of the Organization Management role group. See Prepare Active Directory and domains for more information. This Active Directory preparation ensures that all relevant PowerShell cmdlets and parameters are available to you for preparing for and running the migration. When you upgrade to Exchange Server 2013 CU15 or later, or to Exchange Server 2016 CU4 or later, you must also prepare Active Directory or your public folder migration will fail. We strongly recommend you review FAQ: Public folders before you attempt a migration. What do you need to know before you begin? If you have a mixed environment of both Exchange 2013 and Exchange 2016/2019 public folders in your organization, and you want to move them all to Exchange Online, the instructions in this article will work for you, provided your Exchange 2013 servers have CU15 or later installed.įor instructions on migrating Exchange Server 2010 public folders to Exchange Online, see Use batch migration to migrate legacy public folders to Exchange Online. All versions of Exchange Server 2019 are supported for batch migrations of public folders. Migrating your Exchange Server public folders to Exchange Online requires Exchange Server 2013 CU15 or later, or Exchange Server 2016 CU4 or later, to be running in your on-premises environment.

Applies to: Exchange Server 2013, Exchange Server 2016, and Exchange Server 2019

Pfs explorer rename