The harder decisions arrive much earlier – when systems are still functioning, users remain productive and there is no obvious crisis demanding immediate action. The ERP platform continues to support day-to-day operations, reports are being produced, transactions are being processed and the business appears to be running normally. On the surface, there may be little reason to question whether the technology remains fit for purpose.

What often changes first is not the system, but the business around it.

We see this most clearly when organisations experience significant change. An acquisition introduces new entities, processes and reporting structures. A divestment requires data, systems and responsibilities to be separated. Manufacturing footprints evolve, distribution networks are redesigned and businesses find themselves operating across increasingly complex tax, duty and regulatory environments. In many cases, the ERP platform itself continues to perform exactly as it was designed to. The challenge is that the organisation it supports no longer looks the same as the one it was originally configured for.

This distinction matters because ERP systems rarely become strategic constraints simply because they are old. More often, they become constraints when the business begins asking them to support activities, structures and requirements that did not exist when they were first implemented.

When the business moves faster than the system

Many ERP discussions still focus heavily on age. Systems are judged according to how long they have been in place, where they sit on a vendor roadmap or how close they may be to support deadlines. While those considerations are perfectly valid, they rarely tell the whole story.

A well-managed platform that has supported a relatively stable business for twenty years may present very little risk. Conversely, a much newer system can quickly become difficult to manage if the organisation experiences rapid growth, multiple acquisitions or significant operational change.

The issue is rarely the age of the technology itself; it is whether the assumptions built into the system still reflect the realities of the business.

Consider a manufacturing organisation that consolidates production across several sites. A transfer pricing model designed around one operating structure may no longer support the new one. Intercompany transactions that were once relatively straightforward can become significantly more complex following an acquisition. Reporting processes that worked perfectly well when products moved through a small number of entities may become difficult to sustain when the supply chain spans multiple countries, legal structures and regulatory regimes.

Nothing has necessarily broken. The challenge is that the business has evolved while the underlying system logic has largely remained the same.

This is precisely the type of complexity we see organisations grappling with across supply chain finance, indirect tax and regulatory compliance. The commercial and operational implications can be significant, yet the root cause is often not a technology failure; it is a growing gap between how the business operates today and how its systems were designed to support it.

Why “is it old?” is the wrong question

One of the reasons ERP decisions can become difficult is that organisations often start by asking whether the system is too old.

Age is easy to measure, but it is not always the most useful indicator.

A more valuable question is whether the current environment can support where the business is heading next. Can a newly acquired entity be integrated efficiently? Can changing compliance requirements be accommodated without significant manual effort? Can the business maintain visibility across increasingly complex operating structures? Can reporting evolve as quickly as organisational requirements change?

Questions like these tend to reveal the real pressure points long before concerns around system age become relevant.

Viewed through this lens, ERP strategy becomes less about technology lifecycles and more about business capability. The focus shifts from replacing systems because they are old to ensuring they remain aligned with the needs of the organisation.

Finding the right moment

Perhaps the most difficult aspect of all is timing.

Move too early and organisations risk committing significant investment, time and disruption before a clear business need exists. Move too late and complexity has a habit of accumulating quietly. Customisations multiply, manual workarounds become embedded in processes and the people who understand why particular decisions were made gradually move on.

Unfortunately, there is rarely a single moment that clearly signals the need for change.

The organisations that navigate these decisions most successfully are often those that recognise alignment as something that requires ongoing attention. Rather than waiting for a major technology issue to emerge, they regularly assess whether their systems continue to reflect the realities of the business they support.

That does not automatically lead to a transformation programme. Sometimes the answer lies in targeted improvements, process changes or architectural simplification. In other cases, broader modernisation may be justified. The important point is that the decision is driven by business change rather than technology age alone.

The question, ultimately, is not whether an ERP system is old enough to replace. It is whether it still reflects the business it is being asked to support. As organisations continue to respond to acquisitions, divestments, regulatory change and increasingly complex operating models, that alignment becomes harder to maintain and more expensive to get wrong.

The challenge is recognising when the business has changed enough that the assumptions built into existing systems no longer reflect reality.