Exchange Server Forums

Exchange 2007 to 2013 PF migration issue HELP

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2013] >> Migration >> Exchange 2007 to 2013 PF migration issue HELP

Page: [1]

Message

<< Older Topic Newer Topic >>

Exchange 2007 to 2013 PF migration issue HELP - 24.Jun.2016 5:22:05 AM

rjaclark

Posts: 1
Joined: 24.Jun.2016
Status: offline

Background:
Inter Domain Exchange Migration
Exchange 2007 to 2013
All Mailboxes successfully migrated to Exchange 2013
Both Servers at the correct patch level for Batch public folder migration
Pubic Folder Migration:
Number of Public folders to be migrated = 1800
Exchange 2007 Public folder Database = 220 GB

Issue when using:
.\PublicFolderToMailboxMapGenerator.ps1
The number of Public Folders is too many, so it only puts in the first 1000 Folders.
We manually put all the mappings in a single file.
When running New-MigrationBatch it then returns with the error indicating that the batch needs to be split, as it exceeds the maximum of 1000.
We split the batch, but there is no method of running the second batch.

Limitations:
Reference: https://technet.microsoft.com/en-us/library/dn170437(v=exchg.150).aspx
Extracted text: indicating 1,000 row limit
Staged Exchange migrations
You have to use a CSV file to identify the group of users for a migration batch when you want to use a staged Exchange migration to migrate Exchange 2003 and Exchange 2007 on-premises mailboxes to Exchange Online. There isn't a limit for the number of mailboxes that you can migrate to the cloud using a staged Exchange migration. However, the CSV file for a migration batch can contain a maximum of 1,000 rows. To migrate more than 1,000 mailboxes, you have to create additional CSV files, and then use each one to create a new migration batch. For more information about staged Exchange migrations, see Migrate mailboxes to Exchange Online with a staged migration.

.\PublicFolderToMailboxMapGenerator.ps1 50000000000 C:\PFs\PFmapNameToSize.csv C:\PFs\PFmapFolderToMailbox.csv
New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase (Get-PublicFolderDatabase -Server Exchange-01S) -CSVData (Get-Content C:\PFs\PFmapFolderToMailbox.csv -Encoding Byte) -BadItemLimit $BadItemLimitCount

Request for Support:
1: Are there any updates that can be applied including updated scripts that remove the current limitations preventing this Public folder migration
2: Is there any workaround not including deleting live data from the source PF database

Have talked to a few third party vendors but none of them can do PF migrations if both servers are in the same domain.