When to Replace Your ERP and How to Build the Business Case

Replacing an ERP is one of the most expensive and disruptive decisions a mid-market company makes. It is also sometimes the right one. The difficulty is telling the difference between an ERP that has reached the end of its useful life and an ERP that is being blamed for problems that live somewhere else.

Signs it may really be time

The vendor has announced the end of support or the product is no longer being developed. The system cannot support a process the business now depends on, and the workarounds around it keep multiplying. Every integration is a custom project and every upgrade is a crisis. You cannot find or keep people who know the system. Or the cost of keeping it running, in licenses, hosting and people, is rising faster than the value you get from it.

Signs the ERP is not the problem

Before you commit to a replacement, check whether the real problem is something a new system would simply inherit. Low adoption is not an ERP problem, and we cover it in what to do when your ERP goes live and nobody uses it. Wrong numbers usually come from process and master data, as described in why your ERP data is wrong. Heavy customization can often be unwound into configuration, as in ERP customization versus configuration. And reporting frustration is usually a reporting-layer problem, covered in why built-in ERP reports are not enough.

If those are your issues, a replacement will cost a great deal and you will have the same problems on the new platform.

Options short of replacement

A re-implementation of the current system, with clean data and processes designed properly this time, can cost far less than a new platform. A separate reporting database can fix most reporting complaints without touching the ERP. A clean-up of customizations can restore upgradeability. These are not consolation prizes. For many companies they are the better answer.

What goes into the business case

Be complete on the cost side. Software or subscription, implementation partner, data migration, integrations, training, hardware or hosting, and your own people's time, which is usually the largest number left out. Add parallel running and the cost of the productivity dip around go-live. Then add a contingency, because every ERP project needs one.

Be careful on the benefit side. Count what you can defend: labor currently spent on workarounds, errors that cost real money, capabilities you cannot get today that have a clear value. Do not count vague efficiency gains. Ask someone in finance who was not involved in the project to challenge every assumption.

Include the cost of doing nothing

The baseline is not free. Put a number on what staying costs over the same period: the rising maintenance, the workarounds, the risk of an unsupported system. A business case that compares a new system against an imaginary perfect status quo is not a real comparison.

Then scope it properly

If the case holds, the next risk is scope. Our guides on how to scope an ERP implementation and an ERP go-live checklist cover the points that most often decide how it goes.

If you are weighing a replacement and want an outside view on whether the case holds up, reach out. We would rather tell you not to replace it than sell you a project you do not need.