An Odoo implementation in Australia typically runs 8 to 20 weeks for small businesses and 4 to 9 months for mid-market operators. The range depends on module scope, data quality in your current system (Xero, MYOB, Reckon), and whether the go-live needs to land around a BAS quarter, STP Phase 2 year-end, or 30 June.
We’re a Perth-based Odoo consultancy and we’ve moved enough Australian businesses off Xero, MYOB and older platforms to know the week-by-week shape of this work. Below is the phase breakdown we actually use on projects, with the Australian compliance dates that bend the schedule — and the three things that stretch timelines more than anything else.
How long an Odoo implementation takes in Australia
The honest answer: it depends on how many modules you switch on, how clean your data is, and whether you’re replacing a single system or stitching together five. But after running these projects for small businesses in Perth, Melbourne and Sydney, the ranges settle into three buckets.
Small business rollouts (5 to 50 users)
Plan for 8 to 20 weeks. That covers 3 to 5 modules — typically accounting with BAS and STP Phase 2, inventory, sales, purchase and basic CRM. If you’re coming from Xero and your chart of accounts is tidy, you’re at the 8-week end. If you’ve got 12,000 SKUs in spreadsheets and three sales channels, you’re at 20.
Mid-market rollouts (50 to 500 users)
Plan for 4 to 9 months. Payroll moves onto Odoo or stays on Employment Hero; manufacturing brings MRP routings and work centres; multi-entity brings intercompany journals and consolidation. Nine months isn’t slow — it’s the time a 250-person business needs to train, test, and parallel-run without dropping customer service.
Manufacturing and multi-entity
Plan for 6 to 12 months. A Perth steel fabricator we implemented for had 40 years of legacy costing assumptions baked into JIM2. Rebuilding bills of materials, work centre capacity and routing logic in Odoo took four months on its own — and that was before we touched the ERP cutover.
Phases of an Odoo implementation
Odoo collapses the classic seven ERP stages into five, because the design happens inside the product rather than in a 200-page specification document. You’re configuring a working tenant from day one, not drafting requirements that get implemented later.
Phase 1 — Discovery and scope (2 to 3 weeks)
Workshops with each functional area, a data audit of your current platform, and a scope document listing every module, integration and custom report. This is where Xero’s bank feeds, Starshipit for carrier labels, and any Shopify or WooCommerce storefront get mapped. Get this phase wrong and you pay for it at UAT.
Phase 2 — Configuration and build (3 to 8 weeks)
Chart of accounts, tax codes (GST, GST-free, export, input-taxed), BAS report configuration, product master, warehouses and routing rules, user roles. Any custom development — usually less than 15% of scope when we do it properly — happens here. We build on a sandbox tenant so you can see and challenge everything before it’s committed.
Phase 3 — Data migration and reconciliation (2 to 4 weeks)
Export from Xero or MYOB, transform to Odoo’s import format, load into the sandbox, reconcile opening trial balance to the cent. For the full step-by-step, see our Xero to Odoo migration playbook or MYOB to Odoo migration playbook. Opening AR/AP balances and stock-on-hand are the two reconciliations that catch out DIY migrations.
Phase 4 — User acceptance testing and parallel run (2 to 4 weeks)
End-users run real transactions in the sandbox: raise a quote, turn it into a sales order, pick and pack, invoice, receive payment via ANZ or CBA bank feed, reconcile. Payroll runs in parallel on both systems for at least one pay cycle before cutover. Every bug found here costs one-tenth of what it costs after go-live.
Phase 5 — Cutover and hypercare (1 to 4 weeks)
Final data load, DNS and URL switch, email signatures updated, first BAS on Odoo, first pay run on Odoo. Hypercare is two to four weeks of daily check-ins where we’re on Slack and Teams inside 15 minutes. After that you move to a standard support retainer — or if you’d rather, see our implementation method for how we hand you the keys cleanly.
What affects the timeline
Three things move the schedule more than anything else, and only one of them is Odoo.
Data quality in your current system
Clean Xero data with three years of bank reconciliations in order migrates in a fortnight. MYOB AccountRight files with 800 duplicate contacts, unreconciled bank accounts and negative inventory cost you an extra month. We’ve seen projects stall because the discovery phase uncovered two years of bank feeds that were never reconciled — the client’s old bookkeeper was papering over it with journals.
Scope creep during build
“Can we also add the field service module?” in week six is the single most expensive sentence in an ERP project. If field service is in scope, it’s in scope at week one — see our recurring service jobs playbook for how we scope that properly. If it isn’t, it goes in a phase two backlog and we talk about it after go-live.
Integration complexity
One Xero-to-Odoo swap on a clean tenant: 10 weeks. The same business plus Shopify, Starshipit, an ANZ direct-debit feed and a custom commission report: 18 weeks. Every integration adds an API, a failure mode, and a test case.
Small business vs mid-market timelines
The shape of the project changes as headcount grows, not just the length.
| Profile | Users | Modules | Typical timeline | Cutover window |
|---|---|---|---|---|
| Small services firm | 5–20 | Accounting, CRM, Sales, Purchase | 8–12 weeks | BAS quarter end |
| Trades / services | 10–40 | Above + field service, inventory | 12–16 weeks | 1 April or 1 October |
| Wholesale / distribution | 20–80 | Above + multi-warehouse, Peppol | 16–22 weeks | 1 July |
| Manufacturer | 40–150 | Above + MRP, quality, maintenance | 6–9 months | 1 July or 1 January |
| Mid-market multi-entity | 100–500 | All + payroll, consolidation | 6–12 months | 1 July |
Small businesses get stuck on data; mid-market gets stuck on change management. We build training into every project from week one for that reason.
BAS cycle and cutover windows
The ATO’s BAS cycle pins your cutover window whether you like it or not. Most Australian SMEs report GST quarterly — April, July, October, January. The cleanest cutover lands on the first day of a new BAS period, so your final BAS on the old system closes cleanly and the first BAS on Odoo starts from zero.
Cutover mid-quarter is doable but painful. You’ll need to either combine the partial periods in a single BAS (and explain the split to your accountant) or run a dual-BAS for one cycle. We’ve done both and the dual-BAS is cleaner for audit — but it costs the bookkeeper an extra day.
If your BAS agent files on your behalf, book them in the month before cutover. Most agents need two weeks’ lead time to learn the new report layout, and the first Odoo BAS always takes twice as long as the steady-state version.
STP Phase 2 parallel run and 1 July timing
Single Touch Payroll Phase 2 is the compliance event that dictates mid-year payroll cutovers. Moving payroll onto Odoo mid-financial-year means you’ll file STP from two systems in the same YTD window — the ATO accepts it, but your payroll officer has to stitch year-to-date totals together manually at 30 June.
The cleaner option is a 1 July cutover. You close the prior year on the old platform (Xero Payroll, MYOB or Employment Hero), finalise STP, then start the new year fresh on Odoo. That gives you a clean year-to-date and avoids the stitch.
If you can’t wait until 1 July, run payroll in parallel on both systems for at least two full pay cycles before cutover. We also register the new ABN-linked software ID with the ATO before the first live pay run — that single step catches out about a third of DIY implementations we’ve been called in to rescue.
EOFY and Peppol registration lead times
Two long-lead items shape the calendar more than most businesses realise. The first is End of Financial Year itself. A 30 June go-live means discovery starts no later than mid-February for a small business, or October the previous year for a mid-market rollout. Every year we turn away a handful of businesses in May wanting a 1 July go-live — the maths just doesn’t work.
The second is Peppol e-invoicing registration. The ATO’s access point network takes two to four weeks to register a new participant; if you’re switching access points (say, from a Xero-bundled provider to a standalone one), factor in four to six weeks. Odoo ships native Peppol BIS Billing 3.0, but registration is still an external dependency — see our Peppol e-invoicing registration article for the sequence.
If Peppol is a must-have at go-live, we start the registration during phase 1. If it’s nice-to-have, it goes in a phase two backlog for the month after cutover.
Award interpretation and Fair Work testing windows
If payroll is in scope, Fair Work award interpretation is where timelines quietly blow out. Australian modern awards — the Clerks Award, the Building and Construction General On-site Award, the Manufacturing and Associated Industries Award — encode penalty rates, overtime tiers, and allowance rules that need to be translated into Odoo’s payroll rules one by one.
Two pay cycles of parallel run is the floor. We run at least three if the workforce includes shift workers, casuals on multiple award classifications, or anyone on an enterprise agreement. Each parallel cycle catches a different class of edge case: public holiday loadings, saved RDO accruals, annual leave loading on termination.
Build a Fair Work testing window into the project plan and treat it as non-negotiable. The cost of a single incorrect pay run — back-pay, super, interest, and the time to explain it to affected staff — is larger than the cost of the extra parallel cycle every time.
If you’re scoping an Odoo rollout for an Australian business and want a realistic phase plan tied to your BAS cycle, payroll calendar and integration list, book a scoping conversation. We’ll walk you through the timeline for your specific module mix and tell you — honestly — whether the window you want to hit is achievable or whether you’re better off waiting one quarter.
Frequently asked.
How long does Odoo Implementation take?
For an Australian small business on 3–5 modules (accounting, inventory, sales, purchase, CRM) the realistic range is 8 to 20 weeks from kickoff to go-live. Mid-market rollouts with payroll, manufacturing or multi-entity typically take 4 to 9 months. Anything advertised as 'Odoo in 2 weeks' is either a trial configuration or will need redoing.
What is the Implementation lifecycle of Odoo?
Discovery and scope, configuration and build, data migration, user acceptance testing with a parallel run, cutover, and hypercare. Each phase produces an artefact you can sign off: a scope document, a configured tenant, a reconciled opening trial balance, a signed-off UAT log, and a cutover runbook. Skip the artefacts and you'll pay for the gap later.
What are the 7 stages of Implementation of ERP?
The classic seven stages are discovery, planning, design, configuration, data migration, testing, and deployment with post-go-live support. Odoo compresses them into five because the configuration and design happen in the product itself rather than in separate specification documents. The work is the same; the artefacts change.
Is Odoo a Chinese company?
No. Odoo is headquartered in Ramillies, Belgium, with regional offices including one in Sydney servicing the Australian market. The company was founded in 2005 by Fabien Pinckaers. Australian businesses deal with Odoo's Sydney team for direct licensing and with local partners for implementation and ongoing support.
What is the timeline for implementation?
Plan for 3 to 5 months for a typical Australian SME rollout covering accounting with BAS and STP Phase 2, inventory, sales and purchase. Add 2 to 4 months if payroll, manufacturing, or Peppol e-invoicing are in scope. Tie the cutover to a BAS quarter end or 1 July to simplify opening balances and payroll year boundaries.