In general, organizations should strive to complete the upgrade across the entire solution. This results in a more stable OnBase solution that is far easier to support, troubleshoot, and maintain. Occasionally, an organization may need to remain in a hybrid state for an extended period of time for a very specific business need, but this is generally not recommended.
To ensure that no client or process was left behind during the upgrade process, legacy versions of the software should be removed. A minimum software version can be defined in the Configuration module to ensure users cannot log in using an older client version. To set a minimum version, in the Configuration module, navigate to Utils | Version Compatibility. If a user logs in using a client older than the minimum version, they will receive a message indicating they cannot log in.
A hybrid solution is defined as a deployment that includes more than one version of OnBase running in a production environment for an extended period of time, as opposed to more than one version of OnBase running in a production environment for a limited upgrade window.
Extending the business solutions addressed by a hybrid solution is significantly more complex and requires additional design, implementation, testing, and support considerations. Troubleshooting issues in a hybrid solution is considerably more difficult because errors can occur due to design flaws, software anomalies, or environmental challenges that may stem from differences between software versions. Additionally, finding and applying a workaround can be difficult.
Hyland strongly recommends consulting with your solution provider and Technical Support prior to making the decision to move forward with a hybrid solution.