A lot of ageing systems get blamed for problems that are actually process problems. So before we talk a client into replacing anything, we look for signals that are structural rather than cosmetic. Here are the seven that come up again and again.
1. The vendor has stopped supporting your version. Not “support is expensive.” Stopped. No security patches, no bug fixes, and every year that passes makes the eventual migration harder because the gap between your version and the current one keeps widening.
2. Reports get exported to spreadsheets before anyone trusts them. If your finance team’s real workflow is “export, then fix in Excel,” the system isn’t producing decision-ready numbers. It’s producing raw material for a manual process that happens to look like a report.
3. Integrations are manual file transfers. Someone exports a CSV from one system and imports it into another, on a schedule, by hand. That’s not an integration, it’s a chore with a deadline, and it fails silently the day that person is on leave.
4. Nobody will authorise an upgrade. This is the quiet one. When a business has customised its ERP so heavily that upgrading feels too risky to attempt, the system has effectively frozen in time, and every year that passes makes it more fragile, not less.
5. Multiple systems hold their own version of the same customer or item. If sales, warehouse and finance each have a slightly different record for the same customer, the business is running on three approximations of the truth instead of one.
6. Month-end takes days because numbers need reconciling first, not just reviewing. A closing process should be a check. If it’s actually a reconstruction, that’s the system telling you it isn’t doing its job.
7. New hires take weeks to become productive because the system doesn’t match how the work actually happens. People building workarounds and passing them down as tribal knowledge is a sign the software and the business have drifted apart.
Not every old system is a bad system
Age on its own isn’t the problem. A ten-year-old ERP that’s still vendor-supported, still integrates cleanly, and produces trustworthy numbers on time isn’t a candidate for replacement just because it isn’t new. The signals above are what actually separate “old but fine” from “quietly costing you every month.”
If two or three of these sound familiar, it’s worth getting an honest read on whether the fix is replacement, or something smaller. Our ERP Consulting and Advisory engagement is built to answer that question on real numbers rather than a sales pitch.