If you named your job anything other than PFMigration you will need to change that here. To start the actual data copy run the following command. C:\> New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase (Get-PublicFolderDatabase -Server EX10) -CSVData (Get-ContentĬ:\PFScripts\FolderToMailbox.csv -Encoding Byte) -NotificationEmails Status Type TotalCount NotificationEmails specifies where to email the batch migration report.
We had called this FolderToMailbox.csv and saved it to C:\PFScripts. CSVData specifies the path to our map file we created in part one of our series. SourcePublicFolderDatabase (-Server) specifies the 2010 server hosting the public folder database. Name specifies a display name to help identify the batch.
C:\> New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase (Get-PublicFolderDatabase -Server EX10) -CSVData (Get-Content C:\PFScripts\FolderToMailbox.csv -Encoding Byte) -NotificationEmails our example: From the Exchange 2016 server issue the following command. We will also finalize the migration process. In this second and final part of our series, we will copy the data from the legacy public folder databases into our newly created modern public folders. Then we ran all the necessary scripts to size and create the new public folder mailbox hierarchy. In part one of public folder migration, we prepared our environment. PREVIOUS: Exchange 2016: Public Folder migration Part 1