Should we replace or modernise the ERP?

Most ERP conversations start with the wrong question. Before choosing a platform, decide whether the current system has a structural problem or an operating problem. The answer changes the scope, the cost and the risk of everything that follows.

The signals that matter

Replacement is justified when the platform can no longer represent how the business actually works: the data model fights your processes, integrations are brittle, and every change needs a specialist. Modernisation is the better route when the platform is sound but the configuration, data quality or adoption has drifted.

• Process fit: can standard configuration express your core flows without heavy custom code?
• Control gaps: are approvals, audit trails and segregation of duties enforced by the system or by people?
• Data quality: is master data trusted, or reconciled in spreadsheets before anyone acts on it?
• Integration load: how many point-to-point connections break when one system changes?

Total cost, not licence cost

The licence line is the smallest part of the decision. Weigh the cost of carrying an unfit platform: manual reconciliation, delayed close, failed audits and the opportunity cost of decisions made on stale data. A modernisation that removes those carrying costs often pays back faster than a replacement that resets them to zero but restarts the adoption curve.

Choosing the route

Run a short, evidence-based assessment before committing budget. Map the core processes to standard capability, score the four signals, and model the two paths against the same outcome. The goal is not to defend a preferred answer, it is to make the constraint visible so the decision is defensible.

If you want a structured version of this, our team runs it as a fixed-scope discovery. You leave with a scored readiness view and a costed recommendation, not a sales pitch.