Chat now with support
Chat with Support

Migration Manager for Exchange 8.14 - User Guide

Pre-Migration Activities Migration Process Calendar Synchronization Mailbox Migration Public Folder Synchronization Free/Busy Synchronization Tracking the Migration Progress Creating Batches of Synchronization Jobs Outlook Profile Update Fine-Tuning the Agents Using Agent Hosts for Migration Agents Configuring Migration Using PowerShell Appendix A. Measurement of Migration Agent for Exchange Performance Appendix B. Migrating Large Public Folders to Exchange 2013 (or Higher) and Office 365

Determining Public Folders Size

Determining Public Folders Size

As a first step, you need to analyze the overall size of public folders that are planned to be migrated to Exchange organization. This can be done by reviewing information in Exchange System Manager (applicable to Exchange 2003) or by invoking theGet-PublicFolderStatistics cmdlet (applicable for Exchange 2007 or 2010).

  • If the size is less than the size limit, you don’t need to follow the below procedures. Instead you can simply migrate all public folders to a single public folder mailbox using Migration Manager for Exchange. For more information, see Public Folder Synchronization.
  • If the size is almost equal to or more than the size limit, you will need to split public folders into branches where each branch is less than the size limit and then migrate branches of public folders to separate Exchange public folder mailbox, as described in subsequent topics.

Planning Public Folder Migration

Planning Public Folder Migration

This document contains information on one-way public folder synchronization using legacy agents in migration scenarios from Microsoft Exchange 2010/2013/2016 to Microsoft Office 365. In case you prefer alternative method of one-way public folders synchronization by enhanced Migration Agent for Exchange (MAgE) combined with extended MMEx PowerShell module refer to Public Folder Synchronization (MAgE) document. This synchronization method does not currently have an appropriate user interface and is intended for advanced PowerShell users only.

Prior to actual public folder migration, you need to plan how public folders should be migrated:

  1. Estimate how many Exchange public folder mailboxes you will need to keep your existing public folder content. Take into account that each public folder mailbox can contain up to 100GB of content for Exchange organization and 50GB for Microsoft Office 365, but some space is recommended to be left free. For example, if your source public folders size is 240GB, you need to have at least 3 public folder mailboxes in target Exchange organization or 5 public folder mailboxes in Microsoft Office 365.
  2. Analyze how to split public folders into branches where content of each branches is less maximum size limit and plan mapping those branches to target public folder mailboxes.

    NOTE: If you migrate form Exchange 2007 or 2010, you can use the Export-PublicFolderStatistics.ps1 script to identify public folder sizes. That script creates file with public folders names and their sizes. For more information, see this TechNet article.


Migrating Public Folders

Migrating Public Folders

Now you can actually migrate public folders according to your migration plan by taking the following steps:

  1. According to your public folder migration plan, create public folder mailboxes in the target Exchange organization and in each of them create a root public folder where the corresponding branch of source public folders will be migrated. For that, use the following cmdlets:
    New-Mailbox -PublicFolder -Name <mailbox_name>
    New-PublicFolder -Name <public_folder_name> –Path <path_to_public_folder> -Mailbox <mailbox_name>
    NOTE: Prior to creating public folders mailboxes for migration, ensure that your Exchange 2013 organization already has at least one public folder mailbox, or create it otherwise. That mailbox will be the primary hierarchy public folder mailbox.
  2. Configure a public folder synchronization job in Migration Manager for Exchange. For more information, see Public Folder Synchronization Process
  3. Add public folders collections with pairs of source public folder branches and corresponding root public folders according to your migration plan.
  4. Start public folders synchronization.

For more information, review information in the Sample Migration Scenario section that describes a real-world example of migrating large public folders to Exchange 2013.

Frequently Asked Questions

Frequently Asked Questions

Q: How agents match public folders?

A: Generally, agents match public folders by the folder’s PR_SOURCE_KEY. However if the public folder selected in public folder collection as a target root public folder already exists in the target organization, then its PR_SOURCE_KEY will not be the same as PR_SOURCE_KEY of the corresponding source root public folder. PFSA and PFTA store matching information for such public folders in their Config.mdb databases.

Q: Is it possible to move public folder between public folder mailboxes in Exchange 2013 or higher organization after synchronization begins?

A: Yes, public folder created by PFTA in Exchange 2013 organization can be moved to another public folder mailbox using New-PublicFolderMoveRequest. That does not require change of synchronization settings for public folders. This approach is useful if after you start synchronizing public folders, you reveal that there is not enough space for public folder content in a certain target public folder mailbox.

Related Documents