A final consistency report should be generated at this point. If the report shows that there are still unsynchronized deltas, a repeat of step #12 should be made to converge all the data. Repeat as many times as necessary.
If after several hours or days the consistency report continues to show deltas, it most likely means that either a user or application is still creating data in the source public folders. Efforts should be made to track down the originator(s) of these deltas and changes made to update those actions to target the new public folders.
Once the consistency report shows that all source data has been synchronized and no new deltas are being shown, the source environment can then be targeted for any further actions such as deprecation, tear down, isolation, or whatever action may be destined. Such actions, including remove and uninstallation of exchange, are out-of-scope actions with regards to support from Priasoft.
New management policies created earlier in the project should be started for items like mailbox and folder sizes as well as backups and other possible infrastructure maintenance routines.
Priasoft tools and related access accounts can be removed and there are no elements from Priasoft that must remain after the migration completes. Priasoft does recommend the use of the Public Folder Analysis Toolbox (PFAnalyzer) to help monitor, review, and remediation large folders after the migration is completed.
