An ERP system that was designed for your business five years ago may now be a drag on the business you are trying to run. The signs are consistent.
The Signs Your ERP Is Creating More Work Than It Saves
The most reliable signal that an ERP has become a liability is the number of spreadsheets running alongside it. When finance teams maintain separate Excel models to reconcile ERP reports, when operations teams track exceptions in shared drives because the ERP cannot handle their process variations, and when month-end close requires manual data corrections — the ERP is no longer your system of truth. These workarounds represent process debt that compounds over time.
Customisation Debt
ERP systems accumulate customisations during implementation to fit specific business processes — and those customisations create upgrade risk. Each new vendor release must be tested against every customisation before upgrade, delaying upgrades and leaving organisations on older versions with security vulnerabilities. Companies that took 'vanilla' ERP implementations with minimal customisation are running current versions; companies that customised heavily in 2015-2018 are often two major versions behind. Customisation debt is the ERP equivalent of technical debt in software development.
The Re-Implementation vs Replace Decision
When the ERP is clearly misaligned, the options are: re-implement on the same platform (clean up the data model, remove obsolete customisations, redesign workflows), migrate to a new platform (SaaS ERP like NetSuite, Dynamics 365 Business Central, or Acumatica), or invest in integration middleware to connect the ERP to more modern tools for the functions where it fails. The re-implement option is underutilised — many companies underestimate how much a clean re-implementation on a platform they know can deliver, without the risk of a full platform migration.
The Data Quality Problem Nobody Admits
ERP migration projects routinely find that source data quality is worse than anyone expected. Duplicate customer records, products with inconsistent units of measure, partially converted historical transactions, supplier records with missing compliance data — these problems exist in almost every ERP that has been live for five or more years. Data remediation before a migration typically adds 60-90 days to the project timeline and 20-30% to the budget. Companies that admit this and budget for it upfront avoid the most common ERP project failure mode.
- Spreadsheets running alongside the ERP are the most reliable signal that the system has become a liability
- Customisation debt delays upgrades and creates security risk — vanilla implementations are easier to maintain
- Re-implementation on the same platform is an underused option — it is faster and lower risk than a full platform migration
- Data quality remediation adds 60-90 days to migration projects — budget for it explicitly, not as a contingency