Public Folder migration can be challenging in Exchange 2013 and 2016, when you’re migrating from older versions like Exchange 2003. Firstly, there is no public folder database in the latest versions, and secondly there is no direct native method to do so. If you still go by the native solution, then you’ve to first migrate the Exchange 2003 public folders to newer Exchange version (2007 or 2010) and then again to Exchange 2013/2016. Kernel for Exchange Migrator provides an effortless way to migrate your public folders from one Exchange version to another and without worrying about its large size.
Kernel Migrator for Exchange is designed to smoothly migrate your public folders on all cross-forest Exchange environments (including Exchange 2003/ 2007/ 2010/ 2013/2016). It helps you to avoid the complex public folder infrastructure and focus on the migration better, without worrying about its sprawling size.
Migrate your public folders from one Office 365 platform to another without a double hop migration. The solution also provides hassle-free PF migration from on-premises Exchange Server (any version) to Office 365 platform.
With Rollback feature, you can immediately undo a wrong/mistaken migration task (in few clicks) without losing your head. It helps to keep up your migration pace as smooth as possible, as if nothing wrong has happened.
This helps you to maintain co-existence between the migrated and non-migrated mailboxes. While carrying out the migration, the solution lets you to still synchronize your mailboxes from source to target, target to source or even both ways, which eventually eliminates the data integrity issues.
The solution lets you execute your migration according your convenience based on resource availability and other factors. The Scheduler allows you to create and execute a job automatically at your suitable time. You can even define the blackout duration where you want to halt the migration, and it will resume again after the blackout duration.
Specify what you want to carry in the public folders migration based on the defined date range, include/exclude criteria, message class(es). You can also apply filters on the migration jobs to migrate the data that matters to you.