There is no one-size-fits-all upgrade process or approach that is the best strategy for every installation due to the wide variety of solutions, custom integrations, personnel availability, budget, and many other factors that differ from solution to solution. Thoughtful processes for managing system changes and upgrades may be complex and will require time and concentrated effort to test and execute.
An Incremental Parallel Upgrade begins with updating the database, and concludes with removal of the legacy software components and clients. Between these events, there is a lot of flexibility with how and when to accomplish upgrade increments, establish training, reduce risk, and otherwise manage the upgrade as strategically as needed.
After upgrading the database, you may decide to first upgrade all processing components, verify they are working as expected, then move to upgrade client machines, or vice versa. On the end user side, potential increment strategies include upgrading by module, department, business process, and by region or office location. The amount of customization needed for an IPUP may seem overwhelming, but it is beneficial in requiring administrators to inventory their OnBase system and customize the upgrade based on the needs of the organization.