Buying guide - Cost
Understanding what an ERP project in Australia actually costs.
ERP budgets are dominated by two things that have nothing to do with the software price: the scope of modules you attempt at once, and the condition of your master data. This guide sets out the full cost structure, the variables that move it, a phasing framework that contains risk, and the questions that separate a realistic proposal from an optimistic one.
At a glance
- Who this is for
- Owners, CFOs and operations leaders preparing an ERP business case.
- What this is not
- A published price list. Figures without your scope and data condition are guesses.
- Related
- Timeline, migration and platform comparison guides cover the adjacent decisions.
Cost structure
Six lines in a complete ERP budget.
If a proposal does not address all six, the missing ones have not disappeared.
Licensing or subscription
Per-user or per-application pricing, sometimes with edition tiers that unlock specific modules. Hosting choice can shift this cost between subscription and infrastructure.
Infrastructure and hosting
Cloud hosting, backups, environments and, if self-managed, the operational capability to run them. Not applicable to every option, but never zero when it is.
Implementation services
Process design, configuration, integration, testing, training and cutover. In ERP this is consistently the largest line, typically a multiple of first-year licensing.
Data migration
Products, partners, stock, open transactions and opening balances, with rehearsals and reconciliation. Highly sensitive to how well the current system was maintained.
Internal effort and backfill
The most underestimated line in ERP. Key operational people are needed for design, testing and cutover, and the day job still has to be covered.
Post-go-live support and upgrades
Post go-live support, ongoing support, and the periodic cost of staying current - which rises with every customisation you carry.
Variables
What moves an ERP number.
Module scope and master data condition explain most of the difference between two superficially similar businesses.
| Driver | Effect on cost |
|---|---|
| Module scope | Finance and inventory is a contained programme. Adding manufacturing, quality, projects, field service or payroll in the same phase multiplies design, testing and training effort. |
| Inventory and product complexity | Multi-location stock, batch or serial traceability, landed cost, variants and units of measure each add configuration, migration and testing. |
| Master data condition | Undocumented bills of materials, inaccurate stock and inconsistent product data can outweigh every other variable in the estimate. |
| Customisation depth | Standard flows are cheap to build and cheap to upgrade. Each deviation adds build cost, testing scope and a permanent upgrade obligation. |
| Integration landscape | Ecommerce, EDI, freight, banking, payroll and specialist tools each require design, build, error handling and testing. |
| Number of sites and entities | Multiple warehouses, legal entities or currencies add configuration, reconciliation and cutover complexity beyond simple duplication. |
| Regulatory and reporting needs | GST and BAS handling is standard; industry-specific traceability, certification or statutory reporting is not, and is priced separately. |
| Change management ambition | Replacing the system while keeping every existing habit is expensive. Adopting standard processes reduces both build and training cost. |
Framework
Building an ERP budget you can defend.
- 01
Assess data readiness first
A short profiling exercise on stock accuracy, product data and BOMs. This single input reshapes most ERP budgets, usually downward in scope and upward in preparation.
- 02
Define the minimum viable core
Finance, inventory and purchasing running accurately is a legitimate phase one. Everything else is a candidate for later.
- 03
Price phase one properly, range the rest
Detailed pricing on the core, indicative ranges beyond it, revisited with real knowledge once the core is live.
- 04
Treat migration as its own budget
Separate line, separate contingency, separate acceptance criteria based on reconciliation rather than completion.
- 05
Fund the internal side
Backfill, overtime or temporary capacity for the operational people the project depends on. Unfunded internal effort is how timelines slip.
- 06
Model three-year total cost
Licensing, hosting, support, enhancement and upgrade. Compare options on this basis rather than on implementation price.
Design choices
Decisions that move total cost more than platform choice.
Lowers total cost
Standard-first
- Adopt native process flows where tolerable
- Phase modules rather than a big-bang scope
- Cleanse master data before configuration
- Use configuration in place of custom code
- Keep an internal admin capability
Raises total cost
Legacy-preserving
- Rebuilding old system behaviour in the new one
- All modules live on one date
- Migrating years of history into the live system
- Bespoke development for edge cases
- Full dependence on an external partner for change
Rather work through your own numbers?
A consultation covers the same ground against your systems, volumes and timeline instead of a general range.
Risk
Five common sources of ERP overrun.
- 01
Stock was not accurate at cutover
Every downstream number - valuation, availability, margin - inherits the error, and the remediation effort lands after go-live when it is most expensive.
- 02
Bills of materials had to be built during the project
A data creation exercise disguised as a migration task. It belongs in the plan and the budget from the start.
- 03
Integration scope discovered late
A freight portal, a bank feed or a customer EDI requirement that surfaces during UAT changes both cost and date.
- 04
Parallel running extended
Running old and new systems in parallel is a legitimate risk control, and an expensive one. Its duration and exit criteria should be decided in advance.
- 05
Training deferred to save money
The saving is nominal and the cost appears immediately after go-live as errors, workarounds and support load.
ERP cost questions buyers ask
- Why is ERP so much more expensive than CRM?
- Because it touches money and physical goods. An ERP project carries valuation, tax, stock accuracy and cutover risk that a CRM project does not, which means more testing, more reconciliation and a more controlled go-live. The software may be comparably priced; the delivery discipline required is not.
- Is open-source ERP cheaper?
- Licensing can be lower, and that is genuinely part of the equation. Implementation, integration, data and change effort are broadly driven by your complexity rather than by the licence model, so licence savings rarely dominate a three-year total. Hosting and support responsibility also shift with the model.
- Can we phase an ERP rollout to spread the cost?
- Usually yes, and often you should. Finance, inventory and purchasing first, then manufacturing or projects, is a common and lower-risk sequence. The caveat is that phasing adds some temporary integration or manual bridging between phases, which should be budgeted rather than discovered.
- How much internal time will an ERP project take?
- More than most businesses plan for, concentrated in design, UAT and cutover, and drawn from your most operationally valuable people. That is the cost most often omitted from comparisons between proposals.
- What is a realistic ongoing cost after go-live?
- Subscription or hosting, a support arrangement, and a modest budget for continuing improvement. The variable is customisation: each deviation from standard adds to future upgrade and support cost, which is why we document every one.
Where to go next
Related buying guides
Related architecture and services
Recommended for your industry
Test your ERP budget before you commit to it.
A short data readiness assessment usually tells you more about likely cost than another round of vendor demonstrations.