When should you upgrade business software or replace it?
In a world where "the only constant is change," we often delay making any change related to our business software.
It is easy to make the case that by delaying upgrades, or new software implementation, we can avoid retraining staff, organizational angst, potential upgrade costs and, possibly, the need to change processes. With that avoidance, however, we can miss out on new features that can increase productivity and business insights, and we can also increase security risk by foregoing patches released to address vulnerabilities.
If the following situations fit, it might be time to upgrade your software.
1. The software you are running is not a current version
A good software vendor will continue to develop new features and functions to meet the evolving needs of the marketplace.
In fact, assuring that the vendor has a product roadmap (scheduled product updates) for future releases is an important software selection criterion, as you will want to make sure your tools meet your business needs in the future.
In addition to launching new feature updates, vendors release patches to address user issues and bugs. Depending upon your application and vendor, there may be numerous patch releases between feature upgrades. These may address security vulnerabilities or enable the application to work properly with new browser and operating system versions.
A good rule of thumb for determining when you need to upgrade is to follow the plan to remain in the “current support path,” usually within two versions of the vendor’s current software release. Security patches and those that enable applications to work with new browser versions, should be applied as soon as practical to protect business data and assure the correct operation of applications interacting with browsers.
2. New features have been released that address business challenges
Assuming you are within the “current support path,” the upgrade to your application may be included in an annual support agreement.
These agreements usually do not include implementation services but do entitle you to the current software with all the new bells and whistles.
If the new features are a “no brainer” in terms of business value, then it is important to understand the product roadmap and the release schedule. You will want to make sure you time the upgrade such that you get the features you want and the greatest return from the investment you will make in terms of implementation services and staff training.
Don’t forget to factor in training for staff so they can get up to speed quickly and you can begin to realize the benefits of your technology investment. You will also want to factor in the seasonality of your business when timing the upgrade.
3. New releases permit integration between the software applications in use in your business
I can’t say enough about the importance of integrated applications. Applications that share data eliminate redundant work and reduce human errors. The time you will save, and the improved quality of the information in your system will offset upgrade costs.
So when is it better to consider changing your software than upgrading it?
1. Your business has grown or changed in such a way that you are manipulating or overextending software to meet current needs
The most common instance of this is businesses that find themselves running their entire operation and much of their accounting from a series of spreadsheets. Spreadsheets are a wonderful business tool, but as they become increasingly elaborate their complexity increases. With this complexity, fewer and fewer people have the ability to update and manage them.