How much does ERP implementation and customisation cost in Australia?

What are the five buckets of ERP cost?

An ERP budget has five parts, and the licence is usually not the largest. Price each one separately, because each is driven by different things and each goes wrong in a different way.

Bucket	What it covers	What drives it
1. Licences	Per user or per resource subscription fees	Number of full users, light users, modules
2. Implementation	Partner or vendor consultants configuring the system	Modules, entities, locations, process complexity
3. Customisation and integration	Code the vendor does not provide; links to ecommerce, CRM, warehouse, banks	How far your processes differ from the standard, number of systems
4. Data migration	Moving masters, open transactions and history	Data quality, number of source systems, how much history you keep
5. Training and change	Teaching staff, rewriting procedures, parallel running	Headcount, how different the new way of working is

Indicative first year totals for 20 to 50 users run from $80,000 to $250,000 (AUD, ex GST) on Business Central or Acumatica with light customisation, $150,000 to $500,000 on NetSuite with manufacturing and ecommerce integration, and $120,000 to $600,000 or more for custom ERP modules around an accounting system. Expeed’s published band for enterprise systems, including ERP, is $150,000 to $500,000 or more. These are market ranges, not our prices.

What do ERP licences cost in Australia?

Licence models differ more than the headline prices suggest: some charge per user, one charges by applications and resources, and one does not publish prices at all. These are list prices at the time of writing (November 2026).

Platform	Pricing model	Listed price
Dynamics 365 Business Central	Per user a month, paid yearly	Essentials AU$119.70; Premium AU$164.60 (adds service management and manufacturing); Team Members AU$12.00
Odoo	Per user a month, all apps	Standard about US$31 and Custom about US$61 a user a month on yearly billing; one app free for unlimited users
Acumatica	Unlimited users; priced mainly by applications, plus transaction resources and licence type	By quote
NetSuite	Not published on its Australian site when we checked	By quote

Odoo displayed US dollar prices to us, and both Odoo and Acumatica change prices with promotions, so confirm current AUD figures with the vendor or a partner. The Business Central Team Members licence matters for budgeting: Microsoft describes it as limited access to read data, approve workflows and update select information, so staff who only approve or look up records do not need a full seat.

What does partner implementation cost?

Implementation is priced in consultant days, so ask every partner for a day rate, a day count by module and the assumptions behind it. Partners set their own rates and rarely publish them. As an anchor, Re:Sourced’s July 2026 guide puts senior software contractors in Sydney at $800 to $1,100 a day ex GST, with principal and specialist rates to $1,300. Firms charge more than an individual contractor because the rate includes project management and support.

Odoo is unusual in publishing its own services. Its Success Packs for new customers range from US$3,060 for 25 consultant hours to US$21,250 for 200 hours, after a 15% first pack discount. Odoo says companies under 50 employees usually work with it directly and larger ones usually use a local partner.

When comparing partner quotes, line them up on:

• days per module and per integration, not a single total;
• who does data cleansing and who loads it;
• how many rounds of user testing are included;
• what happens to the price if a requirement changes;
• post go live support days included.

Our guide to comparing software quotes has a template.

Where do ERP budgets blow out?

Customisation and integration are where most ERP budgets grow, because they are estimated before anyone has mapped the real process. The common causes:

1. Replicating the old system. Asking the new ERP to behave like the one you are leaving turns configuration into custom code.
2. Unowned integrations. Ecommerce, warehouse, CRM and bank feeds each need someone to own the mapping and the error handling.
3. Custom reports. Fifty bespoke reports cost far more than ten good dashboards and an export.
4. Upgrades. Every customisation is retested at each platform update. That cost repeats.
5. Late decisions. Policy questions (approval limits, costing method, numbering) left open until build cause rework.

The rule that saves most money: configure first, extend with supported apps or APIs second, and write custom code last.

What does an ERP cost over three years? A worked example

A hypothetical distributor with 20 full users and 10 approvers on Business Central would spend about $189,000 in year one and about $297,000 over three years under these assumptions. It is illustrative arithmetic, not a quote. Services are priced at an assumed $1,300 a day, inside an assumed $1,100 to $1,500 range.

Line	Arithmetic	Amount (AUD, ex GST)
Licences a year	(20 × AU$119.70 + 10 × AU$12.00) × 12	$30,168
Implementation	70 days × $1,300	$91,000
Customisation and integrations	30 days × $1,300 (ecommerce, warehouse scanning, bank feed)	$39,000
Data migration	12 days × $1,300	$15,600
Training and change	10 days × $1,300	$13,000
Year one total	Services $158,600 + licences $30,168	$188,768
Years two and three	Licences $30,168 + assumed partner support $24,000, each year	$108,336
Three year total		$297,104

Notice that services are more than five times the first year licence cost. That ratio is why the scope of customisation, not the licence choice, decides most ERP budgets.

Do data migration and parallel running need their own budget?

Yes. Treat migration as its own workstream with its own owner, and decide early how much history to bring. Bringing open transactions and balances is usually enough; years of closed history can stay in a read only archive. Parallel running, where staff use both systems for a period, doubles workload, so keep it short and focused on the processes with the most risk, such as payroll or month end. Our guide to migrating off a legacy ERP and data migration plan cover the method.

Does the R&D Tax Incentive help with ERP costs?

Usually not for an ERP you implement for your own use. business.gov.au says developing, modifying or customising software for the dominant purpose of internal administration, by you or a connected or affiliated entity, cannot be a core R&D activity. Software you build to sell to other businesses is treated differently. This is general information, not tax advice; our R&D Tax Incentive guide for software explains the rules, and a registered R&D tax agent should assess your case.

When does a custom ERP beat a configured one?

A custom ERP wins on fit, not on price. It makes sense when:

• your core operation (for example job costing across unusual contracts, or production with rules no ERP models) is the business’s advantage;
• you are happy with Xero or MYOB for accounting and only need operational modules around it;
• per user fees at your headcount would exceed the cost of owning software over five or more years.

It does not make sense when your processes are standard distribution, manufacturing or services. In that case, configure a packaged ERP and spend the difference on data quality and training. Our enterprise software cost guide and build vs buy guide go further.

How do you stop scope creep in an ERP project?

Freeze a written scope with acceptance criteria before build starts, and route every change through a priced variation. Practical controls:

1. Map the current and future process for each module, and get sign off from the people who do the work.
2. Rank requirements as must have, should have and later; build only the first group in phase one.
3. Require a written impact on cost and timeline for every change request.
4. Hold a short weekly decisions meeting so policy questions do not stall the build.
5. Keep a single list of open decisions with an owner and a due date for each, visible to the whole project team.

How AWLabs approaches ERP work

Our starting point is fit, not a particular platform. In a 15 minute Development Consult we look at your current systems and whether configuring a packaged ERP, extending one, or building operational modules around your accounting software makes most sense. If we are a fit for the work, a paid Discovery Audit maps processes, integrations and data, with the fee credited in full against the build, followed by a fixed price Schedule of Work in three options: The Minimum, The Recommended and The Complete. Senior engineers lead every build. See our enterprise software service.