An ERP project rarely fails on go-live day. It fails months earlier, in decisions that seemed small at the time: a requirement nobody wrote down, a partner chosen on price, a data migration left to the last week.
The real cost of a failed rollout
The partner's invoice is only the visible part. The bigger costs tend to be:
- Staff time spent on testing, workarounds and re-entering data.
- Running the old and new systems side by side for longer than planned.
- Wrong stock, receivable and payable balances that take months to untangle.
- Late or incorrect tax filings and audit adjustments.
- Management losing trust in the numbers and going back to spreadsheets.
- Paying a second time to fix, or re-implement, the system.
Six common reasons ERP projects go wrong
1. Requirements were never written down
If your processes, reports and approvals are not documented, nobody can test whether the system delivers them. Scope arguments start the moment something is missing.
2. The system was chosen on licence price or demo polish
A slick demo with sample data says little about how the system handles your pricing rules, your tax setup or your month-end close.
3. The partner proposal was not read closely
Who migrates the data? How much training is included? What exactly counts as out of scope? Many disputes come from questions nobody asked before signing.
4. Data migration was treated as an afterthought
Opening balances, open invoices and stock valuation decide whether your first months in the new system are usable. They need to be reconciled to the old books and signed off.
5. Nobody on the client side owned the project
The partner can configure the system, but someone inside the business has to make decisions, chase users and accept the work.
6. Too much customisation
Rebuilding the old way of working inside a new system adds cost, slows upgrades and often reproduces the problems you were trying to leave behind.
Warning signs your project is drifting
- Milestones keep slipping without a revised plan.
- Change requests are piling up and nobody is tracking their cost.
- Testing is being done only by the partner.
- Opening balances do not tie back to the old trial balance.
- Users are keeping spreadsheets on the side, just in case.
How to protect your project
- Document requirements before talking to vendors.
- Run scripted demos with your own data.
- Review the partner proposal line by line, especially scope, migration and support.
- Have someone accountable on your side tracking progress, cost and quality, whether that is an internal project owner or an independent project controller.
- Reconcile and sign off the data migration before go-live.
- Use a go-live checklist that includes the first month-end close.
Is your ERP project already off track? We can review where it stands and agree a recovery plan with you and your partner. Book a free ERP consultation.