MYOB AccountRight to Odoo Migration: What Moves, What Doesn't, and When Acumatica Is the Better Answer

AccountRight has probably run your books for a decade or more. It’s familiar, your accountant knows it, and it still lodges your BAS every quarter. But somewhere along the way the business outgrew it: stock in two locations, a second entity, sales data in one system and financials in another, and a growing pile of spreadsheets doing the work the software can’t. If that’s where you are, this post walks through what a MYOB to Odoo migration actually involves, what comes across, what doesn’t, and the question most partners won’t put in writing: whether Odoo is even the right destination for you.

A quick note on why we’re placed to answer that last part. Auboros implements both Odoo and MYOB Acumatica. We don’t need to talk you out of the MYOB ecosystem to win the work, so you’ll get the honest version.

Why businesses are leaving AccountRight now

The push usually comes from growth more than dissatisfaction. AccountRight is accounting software with some inventory and payroll bolted on. It was never designed to run purchasing, warehousing, manufacturing, field service, and a customer pipeline. Businesses hit the ceiling when they need those functions to share one set of data, and MYOB’s own 2025 mid-market research found 36% of mid-sized Australian businesses were looking to upgrade their business management or ERP software.

There was also a hard deadline this year. MYOB decommissioned AccountRight Classic (v19 and earlier) on 28 February 2026. Classic files are now view-only, which forced every remaining desktop holdout to move somewhere. Plenty simply shifted to the current AccountRight, but for a lot of businesses the forced change became the moment to ask whether the next system should be an ERP instead of another accounting package. The decision framework is the same one we laid out for Xero users in when to upgrade from accounting software to ERP: if the pain lives in operations, not in the ledger, an accounting upgrade won’t fix it.

Two paths off AccountRight: Odoo or MYOB Acumatica

Before any migration talk, be clear about the destination. From AccountRight there are two credible ERP paths, and we implement both.

• MYOB Acumatica keeps you in the MYOB family. It’s a mid-market cloud ERP with deep ANZ payroll and compliance built in, and the upgrade path from AccountRight is well worn. If your headcount is climbing, payroll complexity is a big part of your world, and you want a platform where the vendor handles local compliance end to end, read our MYOB Acumatica vs AccountRight comparison before you decide anything.
• Odoo takes you out of the MYOB ecosystem to an open platform where accounting, inventory, CRM, eCommerce, manufacturing, and field service are modules of one system. It tends to win when the business wants operational breadth, per-module flexibility, and more control over how the system is shaped.

Neither is universally better. Acumatica usually suits payroll-heavy, finance-led mid-market businesses. Odoo usually suits operations-led businesses that want one platform across the whole workflow. The rest of this post covers the Odoo path, because that’s what people searching for this topic are planning.

What moves in a MYOB to Odoo migration

Data that comes across cleanly

AccountRight exports its lists and reports to Excel or CSV, and Odoo imports CSV and XLSX natively, with Odoo’s import tooling handling the mapping. In a typical migration we bring across:

• Chart of accounts. Odoo’s Australian localisation ships a default chart with GST tax codes and BAS-ready configuration, so the real work is mapping your AccountRight accounts onto it, not rebuilding from nothing.
• Customers and suppliers. Contact records, ABNs, and payment terms come across as a straight import.
• Open transactions. Unpaid invoices and bills are recreated so your receivables and payables start accurate on day one.
• Items and stock. AccountRight items become Odoo products, and opening stock is loaded as a counted adjustment at cutover.
• Opening balances. A trial balance as at your cutover date, entered once your accountant has reconciled it.

Data that needs a decision

Historical transactions are the big one. You can migrate opening balances only, bring the current financial year across, or attempt full history. We usually recommend the middle option at most. Rebuilding ten years of AccountRight journals inside Odoo costs real money and delivers very little, because the history you need lives happily in an archive. If you use jobs in AccountRight for project or cost-centre tracking, they map to analytic accounts in Odoo, and that mapping is worth redesigning rather than copying, since analytic accounts can do considerably more than jobs ever did.

What doesn’t move

Bank feeds don’t transfer; they’re re-established against your accounts in Odoo, and reconciliation works differently enough that it’s worth reading our guide to bank reconciliation in Odoo before cutover. Recurring transaction templates, memorised reports, and user permissions are all rebuilt rather than migrated. None of this is difficult, but it belongs in the project plan, not in the surprises column.

The payroll question, answered honestly

AccountRight includes Australian payroll with Single Touch Payroll (STP) reporting, and if you run payroll in it today, this is the part of the migration to slow down on. Odoo has an Australian payroll module, but payroll is the area where we’re most conservative with clients. Award interpretation, STP, and superannuation are unforgiving, and the local payroll ecosystem around Odoo is still maturing. For many AccountRight-sized teams, the right architecture is Odoo for operations and accounting with payroll scoped separately, which sometimes means a dedicated payroll product running alongside. Historical payroll records don’t migrate either way; they stay in your archive with the rest of the history.

We’d rather tell you that before you sign anything than have you discover it in week six. Payroll scoping is a standard part of how we run an Odoo implementation, and it’s the first question we ask AccountRight businesses.

When to cut over, and what to keep

Cut over at the start of a BAS quarter. Your old system owns the last complete BAS, your new system owns the next one, and nobody splits a quarter across two platforms. The next clean window is 1 October 2026, which gives a business starting now a realistic runway for scoping, data preparation, and testing. Cutting over mid-quarter is possible, but it buys you nothing except a messier first BAS.

Keep your AccountRight data after you leave. The ATO’s record-keeping rules require most business records to be kept for at least five years. Before the subscription ends, export general ledger detail, trial balances, BAS worksheets, payroll reports, and your customer and supplier ledgers to PDF and Excel, and archive them somewhere the accountant can reach. Exported archives are searchable, free, and don’t depend on anyone’s software subscription staying alive.

“The AccountRight conversations we have are rarely about the software being bad. It’s that the business has become three businesses and a warehouse since the file was set up. Our job is to work out whether that business belongs on Odoo or on Acumatica, and we don’t mind which answer comes out.”

Bill Alvarez, Practice Manager, Auboros

---

Thinking about moving off AccountRight?

Auboros is a Brisbane-based ERP consultancy and one of the few Australian partners implementing both Odoo and MYOB Acumatica, so the advice starts with which platform fits, not which one we sell. Our ERP migration page covers the wider move in detail.

If you’re weighing up a move from AccountRight, book a free consultation. Bring your questions and your messiest spreadsheet, and we’ll tell you what we’d actually do.