The question “should we replace our ERP?” rarely comes up at the right time. It surfaces at the end of a contract, after an acquisition, during a budget review, or when a department head sends an email that starts with “honestly, nobody really uses the system anyway.”
The problem is that the question never produces a clear answer on its own. Status quo advocates point to the cost and complexity of change. Replacement advocates cite current limitations. And the decision ends up being made by default: you stay because the timing is “never right.”
This guide offers seven measurable signals to move past opinion-based debate and structure a rational decision.
Signal 1: Maintenance Costs Exceed 20% of the Original Project Cost
How to Calculate Your TCO-to-ERP-Value Ratio
The total cost of ownership for ongoing operations includes three components: annual licences, application support (in-house or managed), and corrective updates. Expressed as a percentage of the original ERP project cost (hardware, licences, integration, training), this ratio measures the accumulated technical debt.
A ratio below 15% is typical for a well-maintained ERP under five years old. Beyond 20%, replacement becomes economically justifiable.
The 20% threshold is not a published industry standard — it is a reference benchmark used by IT transformation teams to qualify the alert signal. Treat it as a starting point, not an absolute truth.
What This Threshold Reveals About Technical Debt
A high maintenance cost ratio typically masks two distinct realities. First: system complexity has grown through successive projects (customisations, added connectors, bolted-on modules) without refactoring. Second: the vendor is reducing investment in the version you are running, which drives up the cost of each corrective patch.
In both cases, every pound or euro spent on maintenance is money not funding business value.
Signal 2: Your Team Works Around the ERP Rather Than With It
Symptoms of ERP Shadow IT
The most common workarounds are visible without a formal audit:
- Excel spreadsheets maintained in parallel to track orders, inventory, or budgets that the ERP is supposed to manage
- Manual weekly exports because built-in dashboards don’t match real business needs
- Data duplicated across the CRM, payroll, and ERP, with manual reconciliations at every month-end
These workarounds are not change management failures. They signal a structural misalignment between the system and the organisation’s actual processes.
How to Measure Actual Usage vs Licences Paid
An audit of active logins over the past twelve months lets you compare the number of users actually accessing the system against the number of named or concurrent licences being invoiced. A gap exceeding 30% is a clear signal: part of the organisation has already found other solutions.
For a detailed methodology on ERP licence reviews, see our article ERP Licence Audit 2026: Cut Costs and Improve Compliance.
Signal 3: Your Vendor Has Stopped Investing in Your Version
Announced End-of-Support: SAP ECC and Microsoft Dynamics NAV
Several major vendors have published mainstream end-of-support dates for their legacy versions:
- SAP ECC 6.0 loses mainstream support on 31 December 2027 (Rimini Street, SAP maintenance deadlines). A paid extension is available until 31 December 2030. Beyond that, standard SAP on-premise support ends completely for ECC versions.
- Microsoft Dynamics NAV 2018 ended mainstream support on 11 January 2023, with extended support running to 12 January 2028 (Microsoft Lifecycle). Earlier versions (NAV 2016 and before) have already passed their extended support deadlines.
Running a version past mainstream end-of-support means losing security patches and regulatory updates as compliance obligations evolve.
Release Cadence: The Signal of Gradual Abandonment
A vendor investing in its product ships regular releases: new features, performance fixes, regulatory adaptations. Fewer than two major releases per year for your version, combined with release notes that no longer address your use cases, indicates that the version has become secondary in the vendor’s roadmap.
Signal 4: You Are Locked on a Version More Than 3 Years Old
Security Risks From Unmaintained Versions
ERP versions that have not received recent security patches accumulate known vulnerabilities. The CVE (Common Vulnerabilities and Exposures) database regularly records ERP component flaws with CVSS scores above 7, classified as “high” or “critical.” These vulnerabilities remain open on unmaintained versions regardless of the organisation’s network posture.
The exposure surface is concrete: an ERP handles financial data, personal data (GDPR/UK GDPR), supplier access, and sometimes interfaces with industrial systems (MES, PLCs). A critical ERP flaw is a flaw across the entire perimeter.
Regulatory Compliance Becomes Impossible on Obsolete Modules
E-invoicing mandates are rolling out progressively across Europe and the UK, requiring ERP modules (accounts receivable, purchasing, accounting) to generate and receive compliant formats (Peppol, UBL, Factur-X). An obsolete module that no longer receives regulatory updates will not be certified for these exchanges.
Signal 5: Your ERP Can No Longer Talk to Your Application Ecosystem
Non-Existent or Obsolete APIs
An ERP designed before 2015 often relies on proprietary or SOAP integration protocols. Most modern SaaS applications (cloud CRM, BI tools, e-commerce platforms, treasury management solutions) expose REST APIs. Bridging these two worlds becomes a custom middleware exercise — fragile and expensive.
The problem is not just technical. It is economic: every custom connector must be retested and sometimes rewritten with each ERP or third-party application update.
The Cumulative Cost of Unmaintained Connectors
In practice, an SME or mid-market company running a ten-year-old ERP has typically accumulated dozens of interfaces: flat-file imports/exports, overnight sync scripts, direct database access. This invisible estate represents hidden technical debt that appears in no budget line, depreciates nothing, and breaks with every unanticipated update.
An inventory of existing interfaces is a standard component of any serious ERP audit.
Signal 6: Your Business Model Has Changed, Your ERP Hasn’t
New Models: Subscriptions, Multi-Currency, Multi-Entity
A single-entity, single-currency ERP designed for a company that sold B2B in one domestic market does not natively support:
- Subscription management with recurring billing and prorations
- Financial consolidation across multiple legal entities with automated intercompany
- Simultaneous management of multiple currencies with live exchange rates
These capabilities cannot be added through configuration alone. They require either a significant (costly and risky) rebuild, or a system change.
Acquiring a Subsidiary the ERP Cannot Absorb
An acquisition is a maturity test for any ERP. If integrating the subsidiary into the existing system requires creating a separate database, multiplying manual entity-to-entity synchronisations, or deploying a separate ERP instance without native consolidation — that is the signal that the ERP has reached its perimeter limit.
Signal 7: Your Implementation Partner No Longer Wants to Maintain Your ERP
What This Means: A Shrinking Skills Pool
System integrators manage their competency portfolios actively. When a vendor announces end-of-support or reduces certifications on a version, consultants retrain on newer releases. The result: fewer available experts, longer response times, and rising day rates.
This dynamic is mechanical on ageing stacks: consultants certified on an end-of-life ERP become scarce, which drives up their cost independently of the actual complexity of the work required.
When Your Partner Suggests Migration Themselves
A strong signal not to ignore: when your usual partner proactively raises the idea of exploring a replacement, it means they have already made their own calculation. They no longer have sufficient internal expertise on your version to guarantee quality of service, or they prefer to redirect their teams toward technologies where they can still recruit.
The 3 Decisions After Identifying the Signals
Option A: Stay and Modernise (Major Upgrade or Cloud Lift-and-Shift)
If one or two signals are present and the vendor maintains a clear roadmap, a major upgrade to the current version may be sufficient. Risk is manageable when the technical migration is well-governed and customisations are documented. Our 8-step guide to decommissioning a legacy ERP covers this type of transition in detail.
Option B: Full Replacement (Greenfield)
When three or more signals are active — particularly vendor end-of-support, obsolete APIs, and an uncovered business model — full replacement is often the only option that holds up economically over a five-year horizon. The 5-year comparative TCO across multiple vendors helps make this comparison objective.
Option C: Hybrid Approach (Keep the Core, Replace Failing Modules)
Some organisations have a solid ERP core (accounting, manufacturing) but suffer from an obsolete peripheral layer (CRM, e-commerce, payroll). In this case, a composable architecture — replacing failing modules with API-connected SaaS — can be a lower-risk alternative to full replacement.
Decision Matrix: 5 Common Profiles
| Situation | Active Signals | Recommendation |
|---|---|---|
| SME on 8-year ERP, stable maintenance costs, no acquisition | Signal 3 (vendor end-of-support in 18 months) | Plan migration now; budget for next fiscal year |
| Mid-market post-acquisition, subsidiary cannot be integrated | Signals 5, 6 | Full replacement; evaluate a native multi-entity ERP |
| Manufacturing on 12-year ERP, integrator reducing headcount | Signals 2, 4, 7 | Priority replacement; launch RFP within 3 months |
| Growing SME moving to multi-currency and subscriptions | Signal 6 | Targeted functional upgrade or module-by-module replacement |
| Mid-market on SAP ECC with significant customisations | Signals 3, 4 | Evaluate RISE with SAP (Private Edition) vs greenfield before end of 2026 |
Key Takeaways
The ERP replacement decision is not made in reaction to an incident. It is structured from objective, measurable criteria translated into financial impact.
A single signal warrants a review. Three simultaneous signals warrant a formal business case. Five signals or more means that maintaining the status quo represents an operational and regulatory risk that neither the CIO nor the CFO can defend in a board meeting.
The concrete next step: evaluate your ERP against these seven criteria and quantify the impact of each signal on your maintenance budget, regulatory exposure, and your ability to evolve your operating model.
Download our ERP evaluation scorecard — 30 criteria across 100 points to benchmark your current system and structure a replacement or status quo decision with hard numbers, not a spreadsheet of vendor promises.
