Public Folder Migration Guide From On-Premises Exchange to On-Premises Exchange

Introduction

This is the complete Onboarding Task flow for migrating Public Folders from On-Premises Exchange 2007 or later to On-Premises Exchange 2010 or later in another organization.

Important: MigrationWiz is not a sync tool. Once you have started the migrations, items updated at the Source will not be updated at the Destination. There is no process by which the calendars, contacts, tasks, etc., can be updated after being migration has started.

Complete each step in the order listed. If additional instructions are required, a link to a corresponding Knowledge Base article is provided.

Due to a code defect in Exchange 2010, timestamps will not be preserved for Public Folders at the Destination. See Why are timestamps not preserved when migrating Public Folders to Exchange 2010?

This migration is typically run in three migration passes to move over all selected items and security group permissions. (Migrating of permissions is only supported for Exchange 2010+.)

For a list of prerequisites and best practices, see Public Folder Migration Best Practices.

To see what items are included in the migration, see What items are migrated with MigrationWiz? and What items are not migrated with MigrationWiz?

MigrationWiz supports the capability to share migration projects across a Workgroup. When the Project Sharing feature is turned on, all Agents besides those who are Inactive can view all migrations projects. For more information, visit Project Sharing in MigrationWiz.

We are not able to support migrations with 2-factor or multifactor authentication. 

Prepare Destination Environment

  1. Grant elevated 'Organization Management' administrator role to the migrating administrator account. Refer to How do I assign the elevated admin role 'Organization Management' to the account that is performing a Public Folder migration?
  2. Ensure that the destination administrator account has a mailbox enabled and is located on the same Exchange server as the source Public Folder database or mailbox.
  3. Create your public folder mailbox on the destination Exchange server.
  4. Ensure that the destination administrator account has permission to access all Public Folders ("Owner" access rights need to be permitted to the account being used for migration). See How do I ensure the admin account being used for Public Folder migration has permissions on all Public Folders?
  5. Enable remote PowerShell on the Destination Exchange server (this is important, so that MigrationWiz can mail-enable the Public Folders during migration). For more information, see Are migrated Public Folders mail-enabled?

Prepare Source Environment

  1. Grant elevated 'Organization Management' administrator role to the migrating administrator account. Refer to How do I assign the elevated admin role 'Organization Management' to the account that is performing a Public Folder migration?
  2. Ensure that the source administrator account has a mailbox enabled and is located on the same Exchange server as the source Public Folder database or mailbox.
  3. Ensure that the migrating administrator account has permission in all Public Folders (Read only or "Reviewer" access rights should be enough). For more information, see How do I ensure the admin account being used for Public Folder migration has permissions on all Public Folders?
  4. Split up large Public Folders: if any Public Folders contain more than 20,000 items (if Source = Exchange 2007), or 100,000 items (if Source = Exchange 2010 or later), these should be split into multiple Public Folders. This will speed up your migration. For more information, see How do I find the size of Source Public Folders? 
  5. Any individual Public Folders that are over 20GB in size should be split up into smaller folders of 20GB or less. Failure to complete this step can negatively impact migration performance and speed.

 

MigrationWiz Steps

  1. Set up the Public Folder migration project. Read the How do I create a new migration project? article for more information.
  2. Create the Source and Destination Endpoints (select Exchange Server Public Folder for both the Source and Destination Endpoints). For specific instructions, see View, Add, and Edit Customer Endpoints.
  3. Add Public Folders (select Add > Quick Add and enter a forward slash ( / ) in the Root Folder Path field). We recommend this method because it will migrate all Public Folders, and you will only need one Public Folder license per 10GB of data, regardless of the number of top-level Public Folders. For more information, see How do I select to migrate all my Public Folders from the root level down?
    Note: If targeting specific Source folders for migration, contact BitTitan Support to add those specific folders to the project instead of the top-level Root folder.
  4. Run Verify Credentials. For specific steps, see How do I verify credentials?
  5. If you have more than 1000 folders total, you will need to work with BitTitan Support to split the migration up so that the project runs more efficiently.
    • First step: run this PowerShell command against your Source environment:
      Get-PublicFolder -Recurse -Resultsize Unlimited | select Identity | Export-Csv -Encoding Unicode C:\folders.csv
    • This will generate a file called folders.csv. Once you have that CSV, follow these steps:
      • Open the CSV and remove the names of any folders that will not be included in the migration.
        Notes:
        • Only folders included in the CSV will be included in the migration. For suggestions on working within this restriction, see Public Folder Migration Best Practices.
        • Any new folders created after the Public Folder Split is initiated will not be included in the scope for the migration. For suggestions on working within this restriction, see Public Folder Migration Best Practices.
      • Open a ticket with BitTitan Support by following the instructions in this article How do I get support for your products?
        Note: If you already have a ticket open with BitTitan Support, this information can be added to the open ticket.
      • The subject of the ticket should be “Public Folder Split”.
        Note: Once the MigrationWiz split process is complete, a new project will be created with “_SPLIT” in the title. You must run the migration from the new project.
  6. Purchase Public Folder licenses. See How do I purchase licenses?
    Note: To obtain an estimate of the number of Public Folder migration licenses required for your migration project, follow the directions in How do I estimate the number of Public Folder migration licenses required?
  7. Set Project Advanced Options. For more information, see What project Advanced Options are available?
  8. Set first pass Project Advanced Options. See Should I follow a Pre-Stage or Big Bang strategy when migrating Public Folders?
    • Under Support Options add:
      • MaintainWatermarkCompletionState=1
    • Set Date Filter to migrate items older than 6 months. For more information see How do I set a Date Range filter?
  9. Perform first pass for items older than 6 months by running a Full Migration. Refer to How do I start a migration?
  10. Set second pass Project Advanced Options.
    • Under Support Options:
      • Remove MaintainWatermarkCompletionState=1
      • Add SkipImportFolderWhenPublicFolderExists=1
  11. Set the Date Filter to migrate items newer than 6 months. For more information see How do I set a Date Range filter?
  12. Perform a second pass for items newer than 6 months by running a Full migration.
  13. Set Advanced Options for Security Group Permissions Pass.
    Note: This pass can be skipped if the source is Exchange 2007 as permissions are not supported.
    • Under Support Options:
      • Remove SkipImportFolderWhenPublicFolderExists=1
      • Add AllowAllMailboxTypesForPFPermissions=1
  14. Perform a Security Group Permissions pass by running a Full Migration. If you do not run this pass, none of the Security Group Permissions will migrate. For more information on Security Group permissions, see How do I allow Security Groups to be migrated during a Public Folder migration project?
  15. If you have multiple SMTP email addresses assigned to the mail-enabled Public Folders on the source and want to migrate them to the destination, use the instructions in this article: Migrating mail-enabled Public Folder email addresses.
  16. Request the migration statistics. Click the bar chart icon on the MigrationWiz dashboard to receive an email containing all the project migration statistics. For more information, see How do I request statistics for my migration project?

 

Was this article helpful?
0 out of 0 found this helpful