Exchange 2007 to 2013 Public folder migration question

I currently am in the middle of my Exchange 2007 to 2013 Public folder migration.  I have made it to the AutoSuspended state ready to go into the Lockdown stage.  However, my migration was disrupted due to business reasons and I had to put the rest of the Public Folder migration on hold for 2 weeks.   Now that the 2 weeks has nearly passed, I will be resuming the Public folder migration.   Since it's been 2 weeks, should I cancel the current migration by running -
Get-PublicFolderMigrationRequest | Remove-PublicFolderMigrationRequest  

And also should I delete the Public Folder Mailbox I created on Exchange 2013 and start from the beginning again?

Or is there a better way, as it's been 2 weeks since the Public Folder migration has been sitting at the AutoSuspended stage so if I resume the migration, there would be 2 weeks worth of new data that needs to be migrated that has not been accounted for?

D CAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

If you want you can run the resume command Resume-PublicFolderMigrationRequest \PublicFolderMigration for the changes to get replicated. But i believe you can cancel the migration request and start again. Also if you want you can delete the public folder mailbox.

Please check the article from technet

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Henry DawsonCommented:
Hi user...

Yes, R--R is right, it's better to cancel the earlier migration process but don't get panic, you can also resume the migration process

First of all remove the migration request by this command----
Get-PublicFolderMigrationRequest | Remove-PublicFolderMigrationRequest

& thereafter, resume the migration with these 2 commands----

Set-PublicFolderMigrationRequest –Identity \PublicFolderMigration -PreventCompletion:$false
Resume-PublicFolderMigrationRequest –Identity \PublicFolderMigration

Can take the help of this link for full migration process--
Austin RobCommented:
I hope the above suggested references clarifies your concern to get this job done.

Moreover, have a look on below given links that might helps you to get in more details.
Public folder migration is not an easy task when it comes to manually which contains lots of complexity. If you are following step by step procedure while doing migration It doesn't cause any error for more please visit this link:

For import/export the best way is use outlook. You can export your contacts/PFs to a .PST files and then Import the .PST file to the new server for detailed check out these articles.

Export or back up messages, calendar, tasks, and contacts:

Import Outlook items from an Outlook Data File (.pst)

Hope it helps you!
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

D CAuthor Commented:
Thanks for the advice, what I did was follow R--R 's advice and ran the PS command - Resume-PublicFolderMigrationRequest \PublicFolderMigration   which synchronized the changes made since the original synchronization which was 2 weeks ago.  

I then able to lock down the legacy Exchange 2007 server with the following PS Command:
Set-OrganizationConfig -PublicFoldersLockedForMigration:$true

My Public Folder are now migrated to the Exchange 2013 server.  Many thanks for your advice! :)
Vaibhav BaggaCommented:

I am sharing with you an article, have a look at
Might be it will help you to Migrate Exchange 2007 Public folder to Exchange sever 2013 edition.
Hi D C,

I am glad my suggestion helped you to fix the issue. Thank you for the points.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.