How do I split migrations based on child Public Folder count?
If Source Public Folders have more than 1000 folders below the top-level folder, it is important to work with BitTitan Support so that the migration can be split up, based on migration points after every 1000 folders.
Here are the steps to follow:
- Create a Public Folder migration project.
- Select the Source endpoint and enter admin credentials.
- Select the Destination endpoint and enter admin credentials.
- Submit a ticket to BitTitan Support, by following the directions in KB004529. In the ticket description notes, add the name of the Public Folder migration project, and specify that the Source Public Folders have more than 1000 folders. The title of ticket should include the following text: "Request to split Public Folder migrations based on child Public Folder count." In addition, run the following PowerShell command in your Source Exchange Management Shell (EMS) or Source Office 365 PowerShell environment and include the results of the command, by providing the folders.csv file, generated from running the script, to the ticket:
Get-PublicFolder -Recurse -Resultsize Unlimited | select Identity | Export-Csv -Encoding Unicode C:\folders.csv
- BitTitan Support will then create a new MigrationWiz project on your behalf, and configure the new migration points as needed.
Further details on what the split process will do:
- It will create a new MigrationWiz project called (project)_SPLIT.
- It will create additional "migration points" in addition to the top-level folders already configured. These are created in Office 365. The extra migration points will assist with processing the migration expeditiously.
- It will count the number of subfolders from the root, and then create a new migration point after every 1000 folders from the top-level folder.
- It will also configure folder filters. These are used to start and stop the migration points.
- Any new folders created after the Public Folder split is initiated will not be in scope for the migration.
- The original project will not be affected or changed, and will remain in your list of MigrationWiz projects. However, do not continue the Public Folder migration project from the original project.
- Once the tool is complete, you should run the migration from the new project, and can then delete the original project.