Xero to Odoo migration for Australian organisations

A Xero to Odoo programme may be driven by purchasing controls, inventory, projects, multi-entity reporting or a need to connect finance with operations. Those reasons should be tested individually rather than converted into a product ranking. Some connected applications may remain, some may be replaced and others may be retired after their records and controls have been accounted for.

Start with the Australian entities, GST registrations, actual BAS notices, transaction samples and future process owners. Document what must be operational in Odoo on the cutover date and what can remain in a readable archive. The target baseline is the proposed Odoo 19 build, validated with representative data rather than inferred from a generic feature list.

Reviewed 6 November 2026. General implementation guidance only; it is not tax, payroll, employment or legal advice. Confirm your obligations with a qualified Australian specialist. This is a migration decision guide, not tax advice or a claim that one product suits every organisation.

Map each Xero tax code to its actual use and evidence before choosing an Odoo tax and report mapping. GST is 10% on taxable supplies, but taxable, GST-free, input-taxed and out-of-scope treatments are not interchangeable. Eligible purchases used to make GST-free sales may qualify for GST credits, while purchases used to make input-taxed sales generally do not qualify. Out-of-scope and not-reportable labels require separate review. A legacy code's label cannot make that decision automatically.

The ATO's A$82.50 including GST threshold concerns tax-invoice documentation in context, not automatic credit eligibility. Include taxable, GST-free with credits, input-taxed without general credits, out-of-scope, credit-note and missing-document samples. Imports and offshore purchases receive separate review because conditional reverse charge is not deferred GST.

Odoo 19's Australian localisation provides GST grids, BAS and TPAR outputs for configuration and accountant review. It does not provide direct BAS lodgement in the reviewed documentation, and deferred-GST balances use a manual process. Reconcile source and target workings to the actual statement, cycle and agent concessions.

For each Xero bank account, record the last reconciled statement position, uncleared items, historical statement source and intended feed-start behaviour. Basiq and Consumer Data Right connectivity is opt-in and provider-, institution- and account-specific. Available history and non-real-time limits are validated per account through the Basiq documentation, with statement import as a controlled fallback.

Prevent duplicate lines where historical imports and feed retrieval overlap. Reconcile the target statement balance and investigate missing, pending or duplicated transactions before accepting the account. The general bank synchronisation guide does not establish coverage for a particular Australian institution.

Where supplier payments use ABA files, file generation and upload are not payment proof. Bank approval, account debit, settlement and reconciliation require separate artefacts. Keep provider fees and rejected payments distinct from the invoice allocation.

Role acceptance covers Australian finance reviewers, receivables, payables, inventory, payroll, integration operators and read-only auditors. Test that users can complete their own work and cannot cross entity, approval or payroll boundaries unintentionally. Preserve the source-access and retention decisions for people who must investigate historical transactions after cutover.

The cutover runbook names the final Xero export, transaction freeze, delta handling, integration switch, repeating-transaction activation, reconciliation and fallback authority. Connected apps are disabled or redirected in a defined order so old and new paths cannot both create the same financial record. Late customer or supplier corrections receive a controlled route.

Acceptance applies to the named Odoo version and deployed build; later versions require separate assessment. The release uses the named build and provider versions tested in the second rehearsal, with any later change reassessed rather than treated as equivalent.

The decision pack includes source inventories, approved scope, mapping rules, tax and payroll review status, two reconciliation packs, provider evidence, open exceptions and operating responsibilities. It explains which Xero functions or apps remain, which Odoo processes replace them and which requirements need custom work. It does not rank Xero against Odoo for every Australian organisation.

Fixed-fee discovery can establish these inputs before implementation phases are quoted in AUD where commercially agreed. Subscriptions, connected-app and provider charges, archive products, specialist review, hardware, infrastructure and client internal effort are separately identified. No implementation duration, saving or statutory outcome is inferred from the migration design.

Continue with the AUD reconciliation guide, GST and BAS readiness guide and POS checklist where those workstreams form part of the future operating model.