Free white paper
ERP Implementation: 9 steps to success
The 9 proven steps you should follow when implementing ERP
Although it is very fashionable to write about ERP systems needing to be replaced every ten years or so, the selling of that notion to a business’s C-level is not nearly so fashionable. Clearly, there is a vested interest for software vendors to generate the perception of replacement need among customers; otherwise, growth becomes very difficult. But many of the arguments that convinced leadership to invest heavily in IT infrastructure – doing away with old, unconnected, band aided legacy systems written in COBOL; elevating security and financial controls to comply with financial auditing best practices; a consistent and consolidated look at business information across the enterprise – cannot be made when the issue is changing an ERP system. A worst case scenario is that your sales pitch is based on the replacement ERP platform simply doing more “stuff”.
Existing white papers seem to blur the lines somewhat as to whether a release version upgrade from your existing ERP vendor constitutes “ERP replacement”. It seems like a stretch to include this as a definition of replacement; systematic and routine upgrades were part of the original justification for ERP. The fact that religiously applying all of the patches, service packs, and small development releases is very difficult – in fact, it is often much easier to live with what you have than to have the discipline to continually test, fix, and install vendor updates – does not remove your original commitment to do so as part of your IT strategy.
Assuming, though, that you really do want to rip out your old ERP system and replace it with a different vendor’s package because you need different or additional functionality, what is available for financial payback that was not promised as part of your original conversion to ERP?
Unfortunately, one of the few avenues left to explore to financially justify replacing your ERP system is to move to Cloud ERP computing at replacement, essentially sacrificing your internal IT organization as a cost-reduction offering. The word “unfortunately” is used because many companies view IT as a cost center instead of a strategic asset (to that point, many companies do not have a strategy to utilize the rich business information of an ERP system). Trading away a strategic asset for marginally improved software is a poor exchange.
The bottom line is that if your ERP software does not have the functionality to handle your business competently ten years after an implementation, one of two things is true: (1) Your business model has changed so much that everyone in the organization – from the CEO to the shipping clerk – understands that the need for new software is inevitable, or (2) a fundamentally bad choice of ERP software was made ten years ago. If it is the latter case, it may be better for the organization to be brutally self honest - with the benefit of hindsight - rather than try to create the illusion of a financial justification.
Get your comprehensive guide to the cost of ERP softwareDownload
Calculate your new ERP's financial benefits with this comprehensive guideDownload
Get the definitive guide to converting your business from Quickbooks to ERPDownload
An analysis of ERP change management needs and processes
Discover the secrets to pitching an ERP software upgrade to your management or C-level executives.
A process-focused approach to calculating an ERP budget for new software