When is your ERP due for replacement? 4 financial signals

You know the conversation. The month-end close runs late again. A report misses the management meeting. A key user emails that the system “still cannot” do something. Someone says: “we need a new ERP.” Three months later there is a selection programme on the table. In the meantime no one stopped to ask whether it was actually needed.

We see this pattern often. The question of whether an ERP is due for replacement is rarely backed up financially. It is felt, and then decided. That is where the room for proper enquiry disappears. The business case is then written afterwards to justify the outcome.

In this article we turn the question around. What we care about is not which new system fits you. That is the second question. The first question is which financial signals justify replacement at all. At ERP Company more than 260 specialists work on ERP projects across the Netherlands and Belgium. From that work we have isolated four signals. Only when three of them occur simultaneously and persistently is replacement defensible. In every other situation, optimising within the current system is the smarter financial route.

The difference between discomfort and the need to replace

Concluding that an ERP is due for replacement is not a light decision. An ERP is not a consumer product you swap as soon as a newer model appears. It is infrastructure into which you have poured years of configuration, integrations and user knowledge. Replacement essentially writes that investment off.

An ERP is only due for replacement when three financial signals occur at the same time, and persistently. One symptom is not a signal. Individual pain points usually trace back to configuration, support or working processes, not to the platform itself. What feels like an “outdated ERP” is, in nine out of ten cases, an outdated configuration in a platform that can technically still run for years.

The distinction you have to draw as a director or CFO is the one between discomfort and necessity. Discomfort is part of every working system and you address it within the existing platform. Necessity arises only when the financial, operational or risk impact of the current system is greater than the cost and risk of replacing it.

Below are the four signals on which to base that judgement. No single signal is enough on its own. The combination is.

Signal 1: Operating costs rise structurally above your growth

The first signal is measurable in your own books. Add up your annual spend on licences, support, ongoing development, integrations, hosting and internal hours around the ERP. Compare the growth of that total against your growth in revenue and transaction volume over the same period.

If those ERP costs rise year on year faster than your business grows, the system is becoming less efficient as you scale. Outdated architecture or poorly configured modules demand disproportionately more support as the load increases. The curve no longer rises linearly. It diverges.

A CFO recently told us: “I do not want to be surprised by hidden costs.” The honest answer is: these costs are not hidden. They are simply scattered. They sit in the package fees and in temporary contractor hires. In incidents that pull IT into extra hours. In workarounds that your operations team keeps running. And in end users who default to Excel just to be safe.

What you are looking for is a trend line over at least three years. One expensive year is an outlier, not a signal. Only when you see ERP costs rising faster than your business for three consecutive years does this signal count. To support that kind of analysis, our note on the cost structure of an ERP project helps you map the right cost lines.

Signal 2: Reporting cycle blocks decision-making at quarterly level

The second signal touches the CFO and the executive team directly. If your reporting cycle takes longer than your decision cycle, you have a real problem. You are steering on numbers that are already out of date by the time you read them.

A healthy management cycle calls for reports within five working days of month-end. Some organisations live with ten. If your lead time sits structurally above that ten, and you cannot pull it back through process improvement, your ERP has become a steering blocker.

We do not state this signal neutrally. In our engagements it consistently turns out to be the most underestimated of the four. A reporting cycle that no longer matches your quarterly tempo costs you decisions you do not take. Opportunities you do not see. Risks you spot too late. There is no invoice for that. The opportunity cost is real all the same.

The test is concrete. How long does your month-end close take? How long until you have an actual revenue-against-budget read at quarterly level? Can you raise an ad-hoc question with your controllers on Friday evening and have a substantive answer Monday morning, or does it take a week? “Too long” three times in a row means this signal is at work. For those who want to widen the lens to wider steering, our Business and IT strategy is the frame in which we place this kind of question.

Signal 3: Integration costs mount without visible return

The third signal looks at your integration architecture. An ERP rarely stands alone. Around it sit CRM, WMS, e-commerce, a BI platform, an HR system and sector-specific applications. In that constellation the ERP is the hub everything hangs on or runs through.

If you spend more on connections year after year, and the effect of those connections does not show up in daily operations, your integration architecture no longer fits your reality. That tends to happen when an ERP becomes too old for modern API standards. Or when the system has become so specific that every new connection requires custom work.

The test runs in two steps. First inventory the annual integration costs over three years: build, maintenance and incident handling. Then ask your end users which connections they notice every day in better lead times or better data. If spend is rising and the user experience is not improving, you are paying for an architecture that no longer delivers on its promise.

This signal is not the same as “we don’t have an iPaaS”. An organisation can run perfectly well on point-to-point connections, provided they are few and stable. The signal kicks in when the number of connections keeps growing while the value does not. We often see that pattern emerge at the moment a platform is technically running into its shelf life.

Signal 4: Compliance and audit risk is no longer manageable

The fourth signal is risk-driven. It plays hardest in sectors with strict regulation. Think of manufacturers under the CSRD reporting obligation, service providers under the Wkb, organisations with international tax consolidation, or sectors where GxP, GDP or other certifications apply.

If your ERP can no longer guarantee the auditability of financial, operational or compliance data without structural workarounds, that is a hard signal. Compliance requirements shift every year. A platform that was compliant five years ago is not automatically compliant today. An audit that overruns again and again because data has to be merged manually from three systems is not a comfortable position. It is a slow-burning fuse.

The test for this signal asks three honest questions. Has your auditor flagged the auditability of your ERP data in either of the last two annual reports? Have you had to build workarounds in the last two years because the system does not support a new compliance requirement? Is there a realistic scenario in which a regulator asks for your data within 24 hours and you cannot meet that window without emergency hours?

Three times yes means this signal does not just count, it has its own priority. Compliance failure costs more than an ERP implementation, even when the implementation underperforms.

When you stay anyway: three improvement paths within the current system

Suppose that after this test you recognise one or two signals, but not three. What then? In most cases you are in the territory where optimising is financially smarter than replacing. Replacement, in practice, means a programme of twelve to eighteen months. You only carry the implementation cost once per cycle. And the productivity dip touches your entire operation. Optimising is cheaper, faster to result and less disruptive.

The first improvement path is targeted reconfiguration of pain processes. In most organisations, seventy per cent of the discomfort sits in twenty per cent of the processes. An audit of your core processes, followed by reconfiguration within the existing platform, removes the bulk of the symptoms. The whole system does not need to be torn out.

The second improvement path is reporting modernisation separate from the ERP. Many organisations are unhappy with the standard reporting in their ERP and conclude that the system has to be replaced. More often, a modern BI platform on top of the existing ERP is the faster and cheaper route. You get the same steering information out, without the migration risk.

The third improvement path is strengthening functional support. A large share of the pain around ERP systems comes from support being under-resourced or set up without enough strategic intent. A functional support lead who steers ongoing development proactively prevents a working system from quietly falling behind. We work that out further in our note on management, support and ongoing development.

Our experience is that organisations who genuinely follow these three paths keep their ERP productive for another three to five years. That gives you time to take a replacement decision when the signals do come together, instead of under reactive pressure.

How to reach a well-grounded decision

Replacement is an investment, not an upgrade. Treat it that way. In practice that means: walk three steps consistently before you open a selection programme.

The first step is diagnosis, not diagnosis-confirmation. Have an independent party look at your situation that has no interest in the call to replace or to stay. An implementation partner has, by definition, an interest in replacement. So does a software vendor. Independent advice means the adviser is just as comfortable saying “stay where you are” as saying “you need to replace”.

The second step is a business case grounded in the four signals, not in a feature comparison. A feature comparison between a new and your current ERP almost always lands in favour of the new system. That is not an independent outcome. That is a property of the comparison. A business case grounded in signals is harder, more honest and more defensible.

The third step is review in a management decision with engineered challenge. Replacement decisions often get stuck in confirmation bias. The CFO wants control, the IT manager wants modern, the operations manager wants calm. Everyone has a reason to say “yes”. Not always the same reason. A well-structured decision process appoints someone whose explicit job is to make “no” defensible. Only when that “no” can no longer hold up is “yes” a tenable outcome.

For those who want to structure these steps, our complete guide to ERP selection is a natural follow-up. For the wider package and partner selection, our page on ERP package and partner selection is the starting point.

Frequently asked questions

How do I know if my ERP is due for replacement?

Your ERP is due for replacement when three of the four financial signals coincide persistently: operating costs rise faster than your growth, the reporting cycle blocks quarterly decisions, integration costs mount without value impact, and compliance risk is no longer manageable. One or two signals usually point at configuration or support issues you can solve within the current system.

What are the risks of replacing too early?

Replacing too early means writing off two to five years of configuration, integrations and user knowledge for an improvement you could have realised within the existing system. On top of that you take a productivity dip of six to twelve months during the implementation. If the signals are not persistent, that price weighs more than the claimed benefits of the new platform.

How many signals must coincide for a replacement decision?

Three signals that occur persistently for at least two to three years. One signal is almost always solvable within the current system. Two signals justify a deeper analysis, not replacement. Three signals that do not disappear under optimisation make a well-grounded business case for replacement realistic. Four signals at the same time are rare and usually point to a platform technically reaching its end of life.

Which improvement paths are available within the current system?

Three paths deliver, in our experience, the highest return for the lowest cost. Targeted reconfiguration of pain processes addresses seventy per cent of the discomfort in twenty per cent of the processes. A modern BI platform on top of the existing ERP solves reporting shortcomings without migration. Strengthened functional support prevents a working system from quietly falling behind. Together, these paths typically extend the productive life of an ERP by three to five years.

To close: the replacement decision is a board decision

Whether an ERP is due for replacement is not an IT-department question. It belongs in the boardroom, with the same care given to other investment decisions. What we often see: organisations that take this decision based on the four signals rarely regret the outcome. Organisations that take it based on symptoms or vendor pressure too often do.

Would you like your situation tested independently against these four signals? We are happy to spar without a commercial agenda and without trying to sell you a new system. Sometimes “stay where you are” is the most useful advice an adviser can give. You may also want to read our article on outsourcing or running an ERP implementation in-house for the next step once the call does fall on replacement. Or our note on why organisations choose independent ERP advice for the wider context of our role.