The IPUP process is much like the OnBase application itself: easy to configure and highly customizable. The first step will always be to upgrade the database. The last step will always consist of verifying functionality and then cleaning up the old software, and possibly claiming old virtual machines (VMs) or hardware.
The order of what happens between the database upgrade and cleanup depends first upon the needs of the solution, and the wishes of the upgrade project manager and administrators second. The needs of the solution must come first during planning. That is why this document should always be consulted prior to planning an Incremental Parallel Upgrade.
The exact same IPUP plan that was used for OnBase 16 may not simply be repeated for OnBase Foundation 22.1. A seasoned PM or administrator will take a previous IPUP plan as a framework from which to plan a future upgrade, but will check the most recent version of this document to make sure there are no major changes or caveats that would force them to retool the plan.
An Incremental Parallel Upgrade is not meant to be a shortcut or other means of making OnBase upgrades move more quickly or seamlessly from an administrative standpoint. An Incremental Parallel Upgrade will require more planning, testing and time than a traditional upgrade; however, the benefits of mitigating the risk involved in synchronous upgrades outweigh the cost of planning, testing and time.