Have you ever had something that’s due for replacement, but for some reason you just keep it around? Maybe it’s a laptop that’s so loud it sounds like a jet engine, or a phone with so many cracks in the screen, you can hardly read your texts. Does that say “Let’s eat, Susie” or “Let’s eat Susie”?
Sooner or later, you reach a point where the costs simply outweigh the benefits and you’re running out of both excuses and duct tape. When the age of your OnBase solution is preventing you from using new functionality that could support more positive, impactful changes to your business processes, even if technically, it still works, maybe it’s time to move on and upgrade.
Not only does upgrading bring you a slew of new features that can save you even more time and money; it simplifies support and helps to promote data security. Here’s four ways to make sure your upgrade is a piece of cake:
Step 1: Give your current solution a check-up
Before you start making arrangements for an upgrade, you’ve got to figure out exactly how well your current system is functioning. Ensure your database is successfully, regularly backing up and check for any orphaned items or other issues within your workflows. Run a Diagnostic Console for web services to identify any associated errors, and assess DIP, COLD, and scanning functionalities. By reviewing all these areas, you’ll know ahead of time what sort of adjustments you’ll need to make as you proceed with a newer version.
Step 2: Review all custom code and APIs
After an overall evaluation of your solution is done, it’s time to take a closer look at any sections that required customization. This is important for two reasons. First, you’ll identify any code that may need to be adjusted in order to function properly after the upgrade and any legacy APIs that will have to be converted to ones that are supported. Second and more excitingly, you may find that you can eliminate past customization thanks to new tools and features. Knowing in advance what your upgrade will involve will unload loads of stress later on and eliminate any surprises.
Step 3: Evaluate Your Environments
Before you upgrade, make sure the current OS and database versions of each of your servers is supported with the OnBase version you’re upgrading to. If not, you’ll need to update those too, which could affect your upgrade schedule.
Step 4: Test
You can’t know how well your new system actually works before you use it, and immediately after it launches is a terrible time to find out something was overlooked. Hence, testing. Not only does testing allow you to make tweaks without affecting production, it lets users preview the new environment and decide how well they like it ahead of time.
Don’t forget to perform a full backup of your database before putting the upgrade in motion, and you’ll be on your way to a new and improved OnBase chock full of new possibilities!
With so many new features showing up in OnBase, now is the perfect time to start planning your upgrade, and these steps will help you to be better prepared as you make way for more efficient processes. For more information, download our free case study below to see how the Kansas City Board of Public Utilities implemented efficient invoice processing with OnBase.
