Moving from QuickBooks to Odoo in Australia follows seven steps. For a small business already on QuickBooks Online, a clean accounting migration takes four to eight weeks. The work isn’t leaving QuickBooks — that part is straightforward. It’s configuring Odoo’s Australian localisation so GST, BAS and payroll behave correctly from day one.
- Export your QuickBooks Online data.
- Pick a cutover date aligned to your BAS cycle.
- Configure Odoo’s Australian localisation — GST, BAS, Peppol, ABA.
- Import contacts, then open invoices and bills.
- Post opening balances from the trial balance.
- Hand off payroll and switch bank feeds.
- Parallel-check for three to five days, then go live.
This is the playbook we use. It assumes you’ve already decided Odoo is the right next step. If you’re still weighing that up, the short test is whether QuickBooks has become the bottleneck — stock, jobs, manufacturing, multi-entity — rather than just the accounts engine.
When not to migrate from QuickBooks
Not every QuickBooks business should move, and we’ve talked several Perth operators out of it in the last year. The pattern is consistent. You probably shouldn’t migrate if any of the following describe you.
You have a handful of users and your only complaint is that QuickBooks “feels basic.” It is basic — but you haven’t hit a real ceiling yet, and a tidier chart of accounts plus one good add-on will cost a fraction of a migration. If straight accounting is all you need, the honest answer is often Xero rather than Odoo; see our Odoo vs Xero comparison before you spend a dollar.
Your books are a mess. A migration surfaces every reconciliation shortcut and dangling balance your team has papered over. Clean QuickBooks first, migrate second; do both at once and neither goes well. The same applies if you’re inside six months of a sale or raise, or if nobody in finance has four to eight weeks of attention to give the cutover. A rushed migration is worse than a delayed one.
Why businesses outgrow QuickBooks
QuickBooks Online is a capable accounting product. It is not an ERP, and at roughly 20 to 50 staff most Australian businesses hit the same wall: three or four bolt-ons patched around it — Cin7 or DEAR for stock, ServiceM8 for jobs, Employment Hero for payroll, and a spreadsheet for the gaps. Each tool charges its own per-user fee, breaks on its own schedule, and reconciles against a single source of truth that doesn’t exist.
We worked with a Fremantle homewares importer running QuickBooks Online Plus alongside a separate inventory app and a manual reorder spreadsheet. By the time they called us they were paying around $1,050 a month across five tools and losing the better part of two days a month reconciling stock-on-hand against the general ledger. Folding the whole stack into Odoo took their monthly software bill to roughly $560 for 14 users and cut the reconciliation to about an hour. That’s the typical shape. The migration isn’t really about leaving QuickBooks; it’s about retiring the four tools bolted to it.
The second trigger is control. Once you’re running manufacturing, multi-warehouse logistics or field service, you need to model rules — reorder points, routing, job costing, award interpretation — that a pure accounting product can’t see. Odoo puts those rules into one database the accounts team and the operations team both read from.
How QuickBooks and Odoo differ
The mistake most QuickBooks businesses make is assuming Odoo is “QuickBooks with more buttons.” It isn’t. QuickBooks is an accounting application you sign up for; Odoo is a connected suite you configure. That difference shapes every part of the migration.
QuickBooks Online tops out at 25 users on its highest plan and treats inventory, projects and reporting as light extensions of the ledger. Odoo treats the ledger as one app among forty — sales, purchasing, inventory, manufacturing, CRM, projects, field service and payroll all post to the same accounts automatically. You stop exporting CSVs between systems because there’s only one system.
The trade-off is honest: Odoo asks for configuration that QuickBooks doesn’t. Tax codes, BAS tags, payment terms, warehouses and approval rules all need setting up deliberately. Done well, that’s the point — your business rules live in software rather than in someone’s head. Done badly, the breadth becomes complexity, which is the main reason we steer most Australian businesses away from a DIY Odoo install.
The migration, step by step
The accounting migration itself is rarely the bottleneck. The Australian configuration and the operational modelling are. Here’s how the work actually breaks down once you’ve picked Odoo.
Export your QuickBooks Online data
QuickBooks Online exports cleanly enough through Reports and the list screens. You’ll pull the chart of accounts, the customer and supplier lists, open invoices (Reports → Accounts Receivable Ageing Detail), open bills, a trial balance at your cutover date, general ledger detail per financial year, and your product and service items. Bank transaction history exports as CSV per account.
Three things QuickBooks won’t hand you cleanly: attachments (receipts and bills live behind the API, not the UI), recurring transaction templates (no export path at all), and the audit log. Note each before you start so nothing gets discovered on the first day after go-live.
Set up Odoo’s Australian accounting
This is where generic migration guides lose the plot. Odoo ships an Australian localisation pack that installs the AU chart of accounts, GST tax codes and the BAS report generator — but installing the pack is the first ten per cent. Map every QuickBooks account to an Odoo account before you import a single transaction; QuickBooks “Classes” and “Locations” become Odoo analytic accounts or tags, and that mapping decision shapes your reporting for years. Configure the GST tax groups so each code carries the right BAS tag (G1, 1A, 1B, W1, W2), set up a GST clearing account, and enable Peppol e-invoicing and ABA batch payments if you need them. Our full BAS and GST setup guide covers the tag configuration in detail.
Import contacts, then open transactions
Order matters. Load customers and suppliers first because invoices and bills reference them. Dedupe by ABN, standardise state codes (WA, not Western Australia), and keep the QuickBooks contact ID in a reference field for tracing later. Then import only open invoices and bills as live documents — everything historical can sit as opening-balance journals or stay read-only in QuickBooks for audit. The ATO accepts the QuickBooks archive as source records, so there’s rarely a case for rehydrating seven years of line-item detail.
Post opening balances
Opening balances come from the trial balance at cutover. Post one journal debiting every asset, crediting every liability and equity, with the offset to an Opening Balance Equity account. If your books are clean, it balances to zero. If it doesn’t, you’ve found a QuickBooks reconciliation problem — fix it there, don’t migrate it.
Bank feeds and ABA payments
Connect Odoo’s bank feed from day one, not after go-live. ANZ, NAB, CBA and Westpac all feed in via statement import or CDR open banking, and each bank wants its own user ID and APCA number in the ABA file header. Pull those from your corporate banking portal rather than from QuickBooks’ stored copy, which is often stale.
QuickBooks-specific data gotchas at cutover
Every accounting system has quirks that don’t round-trip through its own export, and QuickBooks has a handful that catch migrations inherited from other partners. Plan for these before you load anything.
Undeposited Funds
QuickBooks parks received payments in an Undeposited Funds account until you “make a deposit.” If you migrate mid-process, those payments sit in limbo and your bank reconciliation won’t tie out. Clear Undeposited Funds to zero in QuickBooks before cutover, or map the balance deliberately to an Odoo suspense account and reconcile it in the first week.
Classes and Locations
QuickBooks Classes and Locations are its only dimensional reporting, and they don’t export as a clean column on every transaction. Run the Profit and Loss by Class and by Location reports to capture the full picture, then decide whether each becomes an Odoo analytic account, an analytic tag, a warehouse or a cost centre. Pick one convention and apply it consistently.
Recurring transactions and multicurrency
QuickBooks recurring templates have no export path; list every one and rebuild it in Odoo’s recurring-invoice or subscription engine before the relevant period rolls over. If you trade in multiple currencies, check that QuickBooks’ stored exchange rates and realised gains match Odoo’s revaluation method — mismatches here create small, persistent variances that are miserable to chase after go-live.
BAS and GST cutover timing
The single most important date in the project is the cutover date, and for an Australian business it should be the first day of a new BAS period. For most small businesses that’s 1 October, 1 January, 1 April or 1 July; for monthly lodgers it’s the first of any month. Finish the current period in QuickBooks and lodge it from there, then start the next period in Odoo. Splitting one BAS quarter across two systems means reconciling one consolidated statement by hand — avoidable pain.
End of financial year on 1 July is the cleanest cutover. Your opening balances come straight from the trial balance, depreciation restarts, and the payroll year rolls over so STP reporting doesn’t span two platforms. The catch is that every bookkeeper in the country wants the same window, so partner capacity tightens through June; book early, or take a 1 January cutover instead. Whichever you pick, confirm your GST codes map to the right BAS labels in a test database first, because a mistagged tax code is the quiet kind of error that only surfaces when the ATO flags a variance.
Payroll and STP Phase 2 handoff
If you’re running QuickBooks Payroll, you’re moving payroll too, and this is the part businesses underestimate. Odoo’s Australian payroll handles STP Phase 2 and SuperStream, and many implementations pair it with Employment Hero or KeyPay for award interpretation, syncing back to Odoo for the general ledger postings — we cover the options in our Australian payroll guide.
Cut payroll over on the first day of a pay period, never mid-pay. Splitting a single pay run across two systems creates STP reconciliation headaches the ATO doesn’t forgive, and it confuses staff who see two payslips. Validate every super fund’s USI against the ATO Fund Validation Service before the first SuperStream batch, because one wrong identifier fails the whole batch. The cleanest approach is to align the payroll cutover with the start of a new financial year so year-to-date STP figures begin fresh in Odoo rather than carrying mid-year totals across.
Validation, parallel run and go-live
The week before go-live, run parallel entries for three to five days — enter the same transactions in both systems and reconcile daily. You’re not chasing a cent-perfect match; you’re confirming every variance has a known cause. The usual suspects are rounding (fine), bank-feed timing (fine) and tax-code mapping (fix immediately).
Reconcile the open accounts-receivable and accounts-payable ageing between QuickBooks and Odoo before you flip the switch. Any gap is almost always a payment-allocation issue, and the fix belongs in QuickBooks followed by a re-export, never a patch in Odoo after the fact. Then run a hypercare fortnight: a named consultant on call, daily check-ins, and a freeze on non-essential configuration. The golden rule is don’t start customising Odoo until finance has closed one clean month in it.
What it costs and how long it takes
A straightforward QuickBooks-to-Odoo migration for a 10-to-25-user business runs four to eight weeks and costs $20,000 to $45,000 in partner fees, plus Odoo licensing from about $34 AUD per user per month for all apps, billed annually. For comparison, QuickBooks Online Plus sits near $70 a month for a single file with limited users, so the licence gap narrows fast once you count the bolt-ons Odoo retires. Businesses with real inventory, manufacturing or field service sit in the $45,000 to $90,000 range and take two to three months, because the work is modelling the operational side, not the accounts. Our implementation cost breakdown walks through three anonymised scenarios in detail.
The approach mirrors the one we use moving businesses off Xero — same discipline, different export quirks. You can also see our implementation method for how we phase the work, or the migration paths we support if you’re coming from somewhere other than QuickBooks.
If you’re weighing up a QuickBooks-to-Odoo move, we run free discovery calls for Australian businesses — we’ll map your current stack, the triggers pushing you off QuickBooks, and what a realistic cutover looks like against your BAS cycle. Arrange a discovery call and we’ll give you an honest assessment before you commit a dollar.
Frequently asked.
Is QuickBooks Desktop going away in 2026?
In Australia, QuickBooks has been online-only for years — Intuit withdrew the desktop product locally after its split with Reckon in 2014, and Reckon kept the desktop line. Globally, Intuit is winding down QuickBooks Desktop subscriptions through 2025 and 2026. Either way, most Australian businesses we migrate are already on QuickBooks Online.
Does Odoo replace QuickBooks?
Yes. Odoo replaces QuickBooks Online's accounting entirely — invoicing, bills, bank reconciliation, GST and BAS — and adds inventory, manufacturing, CRM, projects and field service in one database. Most businesses move because they've outgrown accounting on its own, not because QuickBooks broke.
What is the disadvantage of using Odoo?
Odoo is broader and more configurable than QuickBooks, so it needs proper setup rather than a sign-up. Done badly, that breadth becomes complexity. The Australian payroll and BAS configuration in particular rewards a partner over a DIY install. Budget for the implementation, not just the licence.
Does QuickBooks integrate with Odoo?
There's no official Intuit-to-Odoo connector. You can sync data through middleware like Zapier or a custom API bridge, but for a migration you export from QuickBooks and import into Odoo rather than run both live. Permanent two-way sync is rarely worth the reconciliation cost.
Why don't accountants like QuickBooks?
Many Australian accountants prefer Xero's bank reconciliation and local support, and QuickBooks Online holds a smaller market share here. The frustration is rarely the ledger itself — it's the limited inventory, job costing and reporting once a business grows beyond simple accounting.
What's replacing QuickBooks?
For straight accounting, most Australian businesses move to Xero. For those needing inventory, manufacturing, projects or field service in one system, Odoo is the common destination. The trigger is usually growth — when the bolt-ons around QuickBooks cost more than consolidating into one platform.