Failed Projects, Contract Traps and Official Sources
Why ERP projects fail and how Australian SMEs can avoid it
The recurring patterns behind failed or troubled ERP projects, the warning signs at each stage, and the practical controls that small and mid-sized businesses can put in place.
ERP projects rarely fail because the software cannot work. They fail because the business bought the wrong scope, underestimated data and people effort, accepted a quote whose assumptions did not match reality, or signed a contract that made problems expensive to fix. Industry surveys frequently report that a large share of ERP projects run over budget or time, but published figures vary widely with how "failure" is defined, so treat any single statistic with caution. What is consistent is the pattern of causes, and most of them can be controlled before the contract is signed. This guide describes those patterns generically, with warning signs and controls.
The other guides in this category go deeper: budget overruns, contract traps and unfair contract terms, exit and data export, SLAs and support, privacy and data breaches and disputes and official sources.
Pattern 1: buying before defining the problem
A business sees a polished demo, signs, and only then works out what it needs. The implementation becomes the requirements exercise, paid at partner day rates.
Warning signs: no written requirements; the shortlist was one product; the decision was made by one person.
Controls: a ranked requirements list and scripted demos with your data, as in the ERP selection checklist.
Pattern 2: the scope keeps growing
Every workshop adds "just one more" report, approval rule or integration. Each one is small; together they double the build.
Warning signs: a growing change request log in the first month; no one has authority to say no; phase two items creeping into phase one.
Controls: a scope freeze for phase one, a change control process with costs shown before approval, and a list of phase-two items.
Pattern 3: data is worse than anyone admitted
Duplicate customers, obsolete stock items, wrong tax codes and unreconciled balances surface during trial loads. Cleansing takes weeks that were not in the plan.
Warning signs: the first trial load fails reconciliation; nobody owns data cleansing.
Controls: start cleansing in week one, assign named owners, limit migrated history, and budget your staff's time. See the implementation cost guide.
Pattern 4: customising instead of changing the process
The business insists the new system works exactly like the old one. Heavy customisation increases cost, slows the project and makes every upgrade harder, especially in cloud ERP where the vendor releases updates on its own schedule.
Warning signs: many custom scripts or fields to replicate old reports; partners warning about upgrade risk.
Controls: for each customisation, ask what business result it protects and what it will cost to maintain over five years.
Pattern 5: the people are not available
The project owner keeps their full day job. Key users skip testing because it is month-end. Training is cut to save money.
Warning signs: missed workshops, testing deferred, decisions waiting for one person.
Controls: release staff time in writing, backfill if needed, and treat training as non-negotiable.
Pattern 6: a fixed price that was not fixed
A low fixed price is won by narrow assumptions. When reality differs, change requests follow.
Warning signs: a long exclusions list; vague assumptions such as "standard configuration"; one data load; limited training.
Controls: price likely change requests when comparing quotes (quote comparison guide) and hold your own contingency.
Pattern 7: go-live at the wrong time or before it is ready
Going live in the weeks around 30 June, a BAS lodgment or a seasonal peak, or before payroll and balances reconcile, turns small issues into crises. Payroll errors are especially costly in 2026 because super must be paid each pay cycle under Payday Super.
Controls: go/no-go criteria, a test pay run, reconciled balances and a realistic timeline.
Pattern 8: contract terms that make problems expensive
Auto-renewal at a higher price, no data export rights, weak service levels, and liability limits that make the partner's failures your cost.
Controls: read the contract against the ERP buying checklist before signing, and get legal advice for a significant contract.
A simple health check during the project
| Question | Healthy answer |
|---|---|
| Is spend on track against the budget including contingency? | Within plan, with contingency largely untouched |
| Are key decisions being made within a week? | Yes |
| Has a trial data load reconciled? | Yes, by the planned date |
| Are change requests approved with costs shown? | Yes, and logged |
| Do users attend testing and training? | Yes |
| Is there a written go/no-go checklist? | Yes |
If several answers are "no", pause and reset scope or timeline before costs escalate. A short delay to fix fundamentals usually costs less than a troubled go-live.
When things go wrong
- Document issues, decisions and costs as they happen.
- Raise concerns formally with the partner under the contract's dispute or escalation clause.
- Consider an independent review of the project.
- For small business disputes, free or low-cost help is available from state small business commissioners and the Australian Small Business and Family Enterprise Ombudsman; see disputes and official sources.
Frequently asked questions
What percentage of ERP projects fail?
Published figures vary widely and depend on how failure is defined (over budget, late, abandoned or not delivering benefits). We do not quote a single figure. Plan as though overruns are likely and hold a contingency.
Is cloud ERP less likely to fail?
Cloud removes server and upgrade work, but the main failure causes (scope, data, people, contracts) are the same.
Should we hire an independent project manager?
For mid-sized projects it can help, particularly if your staff have not run an ERP project before. Make sure they work for you, not the vendor.
Can we stop a project halfway?
Check the contract for termination rights and what you must pay. Stopping can be the right decision if the fundamentals are wrong.
Sources
- Australian Small Business and Family Enterprise Ombudsman — dispute support and guidance for small businesses
- ACCC — unfair contract terms and consumer guarantees
- business.gov.au — managing suppliers and technology projects
- Australian Taxation Office — payroll and Payday Super obligations
