What do OnBase upgrades and home renovations have in common?

After months of planning your OnBase upgrade project, requesting project funding, attending project meetings, making test plans, executing test plans, troubleshooting reported issues, and rolling out new clients – you’ve applied the final coats of paint, and you’re now enjoying your shiny, new version of OnBase!

*** Insert celebration dance here ***

A finished upgrade project is definitely a reason to celebrate, especially if you were using an older version. But don’t trade in your OnBase hard hat for a party hat for too long!

Record your recent OnBase upgrade project

Don’t let the dust settle on your OnBase upgrade project without documenting it. While it’s still fresh in everyone’s memory, record your planning and testing and keep it as a reference for your next upgrade.

The first thing to do is schedule an internal “lessons learned” retrospective for all the people who worked on the project. Include OnBase support, IT, business users, and stakeholders. Set an agenda to discuss what worked great and what you could have done better.

Next, carefully compile your test plan from all your individual test cases. Add or refine any scenarios you may have missed, so your testing continues to improve.

Plan your next upgrade window

I recommend upgrading your OnBase solution every two years. There are circumstances where this recommendation may not be feasible, but if possible, make it your goal.

Work with your internal stakeholders now to set an objective. Sticking to a schedule every two years allows you to actually budget for an upgrade, as you can earmark the next project for a predetermined fiscal period.

It also allows your team to form tribal knowledge around the upgrade since you do the project on a regular basis. Preparing and executing the project becomes much easier when your team is comfortable with the cadence.

Finally, upgrading regularly and as close as possible to the recommended two-year schedule ensures that server compatibility should remain between now and your next upgrade, lessening the need for added server migration projects.

OnBase is your home, upgrades are renovations

Technology moves fast. What is now modern quickly becomes dated. Technology from a decade ago can seem as old-fashioned as the pastel colors, chrome Formica tables, and linoleum flooring from the 1950s.

And tech from just a few years ago can be like the shag carpeting, wood paneling, and indoor ferns from the 1970s.

But old technologies don’t just look dated; many times, they are unable to keep up with the needs of modern solutions and are more vulnerable to security risks. Unlike in the world of home design, once a technology is dated, it’s never coming back. That’s why it’s so important to work with IT to ensure you’re always planning your OnBase servers and end-user workstation compatibility with the future in mind.

Remember, your OnBase system is a home, and upgrades are the renovations. To continue to build value in your investment and prepare for the future, improve your next upgrade by learning from your most recent one, leverage regular OnBase upgrades at least every two years, and keep OnBase in the conversation as you plan your IT strategy.OnBase 18

Editor’s note

Next week is OnBase 18 Week, where we’ll detail specific reasons why upgrading is so important. We’ll also highlight some significant improvements, including:

  • Why we continually enhance OnBase and why that’s important to you
  • Improvements for healthcare
  • Enhancements to reporting dashboards
  • Online training classes
  • Enhancements to revenue cycle management
  • FIPS 140-2 compliance
  • Important advancements in security

Make sure to check out OnBase 18 Week, starting on Monday!

This blog post was originally published on the DataBank Blog.

Mike Current started at Hyland in 2010 as a technical support rep and cloud engineer for Global Cloud Services. He is currently an Infrastructure Admin in Quality Assurance. Mike tests configuration, runs projects such as Release Candidate and the OnBase 16 Beta Program, manages the “Mitigating Risk in OnBase Upgrades” whitepaper and evangelizes synchronous and incremental parallel upgrades.

Outside of OnBase, Mike loves spending time with his family, working out and playing Xbox. He can often be found sipping a whisky and talking about geeky things while watching a Patriots football or Cleveland Cavaliers game.
Mike Current

Mike Current

Mike Current started at Hyland in 2010 as a technical support rep and cloud engineer for Global Cloud Services. He is currently an Infrastructure Admin in Quality Assurance. Mike tests... read more about: Mike Current