10 Critical Upgrade Mistakes
Common upgrade mistakes
If your company is considering launching the New Year with shiny, upgraded Sage 300CRE software (formerly Timberline Office) —now is the time to start for a successful deployment!
And to support that position, TechRepublic’s list of “10 critical ERP upgrade mistakes” is a fine blueprint for most software upgrades, not just ERP solutions (FYI, Sage 300 CRE software is considered a “light” ERP implementation.)
The TechRepublic Top 10:
- Not explaining what a new system means to users before starting the project
- Not load testing the system with scripts and end users
- Not performing a mock Go Live
- Not taking change management and testing seriously
- Assigning an internal resource as the only project manager
- Not communicating changes before they happen
- Delivering Training 1.0 in a Training 2.0 World
- Not moving proprietary components to open business standards
- Not addressing security and archiving before upgrading
- Assuming your internal tech people can pick up 15 years of experience in a couple of weeks
These seem logical enough at the top level; however if you want more in-depth explanations, you can find the full article here. (One can imagine that said ‘Guest Contributor’ has suffered most or all ten of these upgrade blunders to have composed such a succinct list. We do hope he/she is on a tropical island, sipping a rum-laced beverage!)
LAI consultants’ further recommendations
NOT READING THE RELEASE NOTES
Sage does a good job here detailing any changes in file or database structures. However, we have clients that just blindly install the upgrade without perusing any critical issues outlined in the Release Notes, and put their company data at risk. We cannot emphasize how important this is!!
NOT ALLOWING ADEQUATE TIME FOR TROUBLESHOOTING HELP
Many companies assign a resource to manage the upgrade, but don’t plan extra time for support calls or help research. This escalates the overall stress level within the organization and may result in extra costs for rush consulting. Put some “padding” in your upgrade implementation!
NOT CONSIDERING USING A CERTIFIED CONSULTANT
Would you rather pay a few hundred up front for a trained consultant to install an upgrade correctly, or pay thousands of dollars later to find the problem and apply a fix to it? It’s the ‘penny wise, pound foolish’ strategy that you can easily avoid.