Toll Free: +1 888 900 4529 |   Toll Free: +44 800 088 5522

Migrate Exchange 2010 Public Folders to 2013

Paul Ryan | December 10th, 2014 | exchange 2010

Architectural considerations and preferences makes each updated version of Exchange Server application different from the previous one. Consecutively, Public Folder migration to the updated version can become quite daunting as this requires fulfilling some pre-requisites beforehand.

Getting started with the task to migrate Exchange 2010 Public Folders to 2013, requires creating snapshots for all existing Public Folders and then exporting them to CSV file to retain the original structure, statistics and the assigned permissions. These snapshots can be used for verification purpose, once migration is been accomplished successfully.

Required Pre-Requisites

Pre Requisite #1: Cmdlet to Create Snapshots:

The next section introduces the cmdlet syntax that can be used to take snapshots for Public Folder’s various elements:

  • Execute following cmdlet commands to take the snapshot of original structure of the Public Folders:

1-pf-snapshot

  • Further, run this syntax to take snapshot of all the statistical elements such as size, item count, owner, etc.:

2-pf-snapshot-csv

  • At last, execute following command to take snapshot for assigned permissions:

3-pf-snapshot-csv

Pre Requisite #2: Turn Migration Records to ‘False’:

Afterwards, on Exchange Server 2010, ensure that no previous records for Personal Folders migration exist. If any of such records exists, then it is required to set the corresponding value to ‘False’. Otherwise, the migration process might fail if the value sets to ‘True’.

If the value for either of the following options is set as ‘True’; then try executing the following cmdlet to turn the value to ‘False’.

i.        PublicFoldersLockedforMigration; or

ii.        PublicFolderMigrationComplete

4-pf-snapshot-false

MS Exchange Server might take few minutes to apply these settings. By restarting the ‘Microsoft Exchange Information Store’ services, this process can be speed-up.

Pre Requisite #3: Check for Previous Migration Request:

Now, the next step involves assuring that no migration request for Public Folders exists on Exchange Server 2013 and this can be done by executing the following commands:

5-pf-snapshot-remove-request

Make sure that no Public Folders exists on Exchange Server 2013 by performing the under mentioned commands:

i.        “Get-PublicFolder”

ii.        “Get-Mailbox –PublicFolder”

Pre Requisite #4: Public Folders Mapping:

Mapping Public Folders requires creating CSV file that will suggest Exchange about which Public Folders mailbox has to be used corresponding to each existing Public Folder.

Then copy the respective folders from Exchange Server 2013 to Exchange Server 2010 by following the given location “<install_dir>\Exchange Server\V15\Scripts\”

i.        ‘Export-PublicFolderStatistics.ps1’; and

ii.        ‘Export-PublicFolderStatistics.strings.psd1’

After copying the above mentioned files; run the following script from Exchange 2010; in order to generate the mapping file.

6-pf-snapshot-export

Where;

  • Folder to size map file path is the name of the file as well as the path where the CSV file has to be created. This file has to be copied in Exchange 2013.

  • Source server is the name of the Mailbox Server that hosts the Public Folder structure or hierarchy.

Pre Requisite #5: Create Public Folder Mailboxes:

Next step is to create Public Folder Mailbox corresponding to all the names mentioned in ‘TargetMailbox’ field in CSV file. ‘NextMailbox’ cmdlet is used to create Public Folder Mailboxes. With this, all the pre requirements for migration have been set and you can now migrate Exchange 2010 Public Folders to 2013 Server.

Getting Started with Public Folders Migration

Migration process can be initiated by using “New-PublicFolderMigrationRequest” cmdlet as well as the CSV file that we created earlier. This will command Exchange 2013 to create Public Folders and start transformation of data.

Following cmdlet can be executed from Exchange Server 2013 mailbox:

7-pf-snapshot-source-database

  • Track Migration Process:

To track the migration process and to ensure if the task is running smoothly; following commands can be performed:

i.        ‘Get-PublicFolderMigrationRequest’; and

ii.        ‘Get-PublicFolderMigrationRequestStatistics’

Note: The migration time solely depends upon the volume of data that is being copied and the location of Source as well as the Target Server.

When the migration process reaches ‘AutoSuspended’ status, we can proceed towards finalizing migration.

  • Finalizing Migration Procedure:

Till this stage, user can log on to the Public Folders in Exchange Server 2010 environment. The next step involves log-off the users from Public Folders in Exchange 2010 and then to lock the existing Public Folders so that the user could not access these folders until migration reaches the synchronization stage.

The following cmdlet can be used to lock the users:

8-pf-snapshot-locked-database

Locking process might take some time so meanwhile try restarting Microsoft Excahnge Information Store services.

In order to complete migration process, several task needs to be executed in Exchange 2013:

i.        The value for ‘PublicFolderMigrationComplete’ needs to be set to ‘True’.

9-pf-snapshot-locked-database

i i.        It is required to remove ‘PreventCompletion’ flag and then resume the same in PublicFolderMigrationRequest.

10-pf-snapshot-resume

All the changes made in Exchange Server 2010 Public Folders will get synchronized. The Public Folders remain locked as the lock has not yet released. It is not recommended to release it as it can affect the synchronization process and any modification will not get synchronized to Exchange Server 2013.

The migration progress can be traced by using the same cmdlet that was used earlier while creating Public Folder Mailboxes.

  • Test New Public Folders:

Check the migration status to ensure if the task is going smooth before enabling Public Folders to the existing users. Initialize this task by releasing lock from single folder on test basis. This also requires releasing lock from master hierarchy mailbox i.e. PF-Hierarchy. Once, everything seems to be as per command, the lock from all other users can also be released.

Once the process to migration public folder exchange 2010 to 2013 is completed successfully, compare snapshots taken in the initial stage and verify that all the components have restored successfully along with the assigned permissions.

Post Migration Tasks

At this point, all the migration operations have been executed as well as the status of migration is well known. Now the time is to remove the Public Folder databases from Exchange Server 2010 and once this is accomplished, we are done with migration task.

Eliminate Migration Complexities with Commercial Solution

Each version of Exchange Server comes with apparent updates and modifications. Therefore, for getting started with any sort of Server tasks, Administrators themselves have to refurbish their plans, procedures and implementation methods.

A simplified approach towards migrating Public Folders to Exchange 2013 form any lower version of the respective application can be deployed for accomplishing uncomplicated migration. Exchange Recovery helps avoiding complicated cmdlets involved in the migration procedure and transfers folders without compromising with internal structure.

The following two tabs change content below.

Paul Ryan

Paul Ryan is a technical blogger and he’s passionate about writing technical blogs and covering all popular issues related to Exchange server / Outlook apps. He is MCSE certified and putting all his knowledge and experience in providing solutions to the Exchange users/administrators.