More recent versions of exchange servers like the 2013 and 2016 have moved the public folder to mailbox database, this is a significant change as in earlier exchange versions, the Public Folder used to be a separate database . While this is a step in right direction, in scenarios where you have to relocate from a legacy exchange server versions to newer ones like the 2013 or 2016, the whole process becomes a little more complicate . Here are a few pointers that you should keep in mind while attempting such a migration.
If your are running on rather old versions of exchange like for instance the 2003 version, then you should first migrate public folders to 2007/2010 as direct migrations to exchange 2013 or 2016 from 2003 is not possible.
Make sure you are on Service Pack 3 RU10 or later if you are working with a Exchange 2007 deployment.Similarly for Exchange 2010, you should have Service Pack 3 or later.
Both legacy mailboxes and new public folders cannot coexist.
Plan the migration so as to make the impact of inevitable downtime during the process minimal.
Users wont be able to get access to new public folders in Exchange 2013 or 2016 if they're are utilizing legacy mailboxes.
Since Microsoft doesn't support direct migration of public folder you'll have to depend on power shell scripts to get the job done. However using scripts is a tedious multi step process and might require you to even modify the script on your own to make it work properly.This is where EdbMails EDB to PST exchange recovery software comes to your rescue . EdbMails can perform quick and reliable public folder migration, Thanks to its easy to use and understand user interface, even a non technical person can easily make use of EdbMails for migration purposes.
Sign in to leave a comment.