Dear all,

usually when migrating public folders to Exchange 2013 I followed instructions as per http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/migrating-public-folders-exchange-2013-part1.html to migrate that.

As you can see there is some addition about export of the old PF hierarchie and they explicitely tell you that you must make use of -resultsize unlimited on the source side, while there is no such option to use on the New-PublicFolderMigrationRequest cmdlet.

But if you ever add more than 1,000 rows, that will fail and a message "your CSV file contains more than 1,000 rows" appeared. So you can create some portions of folders to migrate.

Now I have more than 500,000 public  folders having more than 2TB of data. I know there is a "supported" limit of 250,000 while there is no technical restriction. How can I make that 500 x 1,000 portions run in parallel? I can see you can only run one request per time, so migrating that amount of data would take months. Is there any possibility to run more than one migration request?

How do you handle a large count  of folders?

Please advice.

Martin

Hi,

Based on my understanding, you need to use ResultSize Unlimited if you have more than 1000 PFs when you try to run the following commands, instead of the New-PublicFolderMigrationRequest cmdlet.

The first cmdlet takes a snapshot of the original PF structure:

Get-PublicFolder -Recurse | Export-CSV C:\PFs\2010_PFStructure.csv -NoTypeInformation

The second cmdlet takes a snapshot of the PF statistics such as item count, size, owner, etc.:

Get-PublicFolder -Recurse | Get-PublicFolderStatistics | Export-CSV C:\PFs\2010_PFStatistics.csv -NoTypeInformation

Finally the third cmdlet takes a snapshot of all the PF permissions:

Get-PublicFolder -GetChildren | Get-PublicFolderClientPermission | Select Identity, User -ExpandProperty AccessRights | Export-CSV C:\PFs\2010_PFPerms.csv -NoTypeInformation

In your case, you have more than 500,000 public folders, so you need to add the -ResultSize Unlimited when you use one of the cmdlets above.

Best regards,

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

Hope, the above suggestion would help you to understand the PF migration concern in depth.

However, I would also like to refer you on this another informative blog that explains some good points by covering all the required aspects and helps to migrate public folders in more easier way : http://exchangeservermigration.blogspot.in/2014/07/preparing-public-folder-migration-to-exchange-2013.html

Hi Belinda,

thanks for your reply.

Please see the Blog-article mentioned before - I already created the CSV file using the -Resulsize unlimited.

The statement you referred are used only to create the CSV files, while you still need to start migration. You usually do that by running a statement like

new-migratepublicfolderrequest -sourcedatabase (get-publicfolderdatabase mysrcpfsrv) -csvdata (get-content myPFcsvfile.csv -encoding byte)

and that is the statement that returned "your CSV file contains more than 1,000 rows".

Any idea how to handle that?

Regards,
Martin