Exchange Server 2016 Migration – Public Folder Migration

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Exchange Server 2016 Migration – Public Folder Migration

Willsondmello
If you are migrating public folders from Exchange 2013 to Exchange 2016, you can simply move the public folder mailboxes just as you would migrate any other mailbox. If you are migrating public folders from Exchange 2010 to Exchange 2016, then the process is more difficult. To migrate public folders from Exchange 2010, a procedure called a batch migration is performed. At a high level the process involves in public folder migration: Step1: Downloading the scripts from Microsoft Step 2: Generating CSV files (mailbox name) using the Microsoft Step3: Next creating the public folder mailboxes in Exchange server 2016. Step4: Start the migration option, and waiting for initial synchronization process to complete Step5: Locking the exchange public folders for final migration Step6: When using the public folders and then unlocking them for access by users. Above mention public folder migration process is one-way only. Once you’re start using the modern public folders, any new data or changes can’t be change back to the public folder databases. This means that if you’re facing encounter a problem you’ll lose new or changed data in the public folders. So this process risks management perspective. EdbMails Exchange Migration takes the most critical part of a server migration or Exchange upgrade – moving of one user’s mailboxes to other user’s mailboxes as well as public folders. EdbMails automatically performs a direct migration of the mailboxes you selected on the source and mapped to target server mailbox. You can migrate easily one exchange server public folder to other exchange server public folder without any data loss.