MYOB to Odoo migration for Australian organisations

MYOB migration cannot start from a generic product logo. Identify the relevant MYOB product families and versions, desktop and online operation, the company files in use, where each file is hosted, which users maintain it and whether payroll, inventory or connected services form part of the operating record. A file that looks similar to another entity's file can still contain different fields, tax codes and historical practices.

Document why the organisation is changing its systems and test that reason in Odoo 19. Multi-entity controls, warehouse processes, project reporting or operational integration may justify a programme, but this guide does not rank MYOB against Odoo. It defines the evidence needed for a controlled Australian migration.

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. Product-version and export findings must be reconfirmed against the client's actual environment.

GST is 10% on taxable supplies only. Map taxable, GST-free, input-taxed and out-of-scope transactions from their actual MYOB use and supporting evidence, not from a code abbreviation alone. 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 and are not synonyms for either treatment.

Include sales and purchases, credit notes, bad-debt or adjustment scenarios, missing documents and mixed transactions in the review pack. The ATO's A$82.50 including GST tax-invoice threshold is conditional documentation context, not automatic credit entitlement. Imported goods and offshore purchases need a transaction-specific decision; conditional reverse charge is not deferred GST.

Use the Odoo 19 Australian localisation to configure and review GST grids, BAS and TPAR outputs. There is no direct BAS lodgement in the reviewed documentation, and deferred-GST balances remain manual. Reconcile against the issued statement, actual GST and PAYG cycles, instalment notices and any tax-agent concession rather than a generic due-date calendar.

For every account, identify the last reconciled MYOB statement, unpresented items, historical statements and target feed-start position. Basiq and Consumer Data Right access is opt-in and depends on the provider, institution and account. Test available history and non-real-time behaviour, and retain statement import as a controlled fallback where appropriate.

Use boundary-day tests to detect missing or duplicated statement lines when history and live feeds meet. Reconcile bank balances and uncleared items separately from the general ledger so one cannot conceal a problem in the other. The bank synchronisation reference is a product guide, not proof of account coverage.

ABA file generation or upload is not supplier-payment proof. Bank approval, debit, settlement and reconciliation require separate evidence, and rejected or corrected files need their own procedures. Tyro, Stripe or another payment path is validated only for the exact provider, merchant, device and production flow used by the business.

The runbook names the final company-file backup, locked-period decision, last transaction entry, final exports, delta handling, integration redirection and release authority. Users know when MYOB stops accepting new transactions and how late corrections are handled. Source files remain accessible under the agreed retention and read-only policy.

Acceptance covers the trial balance, open receivables and payables, applied payments, inventory, GST workings, bank positions, attachments and payroll scope. Finance, operations, payroll and data owners sign within their areas. Any residual has a reason and owner, and a failed critical control invokes the documented stop or fallback route.

Acceptance applies to the named Odoo version and deployed build; later versions require separate assessment. Changes to the deployed build, MYOB extraction route or provider behaviour after the second rehearsal trigger targeted revalidation rather than an assumption of equivalence.

A discovery proposal should identify the company files, product versions, objects, historical periods, reporting structures, attachments, integrations, payroll populations and acceptance reports examined. Implementation phases then state the mapping rules, rehearsal inputs, client responsibilities and provider dependencies. This is more useful than a universal MYOB-to-Odoo checklist or a product-ranking claim.

Oakland services can be quoted in AUD where commercially agreed. Odoo subscriptions, provider and bank charges, archive products, specialist tax or payroll review, hardware, infrastructure, optional travel and client internal effort remain separately identified. No fixed timeline, saving or statutory result follows from the migration scope alone.

Use the migration and AUD guide for reconciliation fields, the GST and BAS guide for transaction evidence and the payroll guide for YTD and role readiness.