Outgrowing MYOB AccountRight: When to Move to MYOB Acumatica

You have outgrown MYOB AccountRight when you tick most of five boxes: more than one entity consolidated in a spreadsheet, stock that needs serial, batch or multi-warehouse control, a growing user list with no approval step, reporting and audit history kept outside the file, and integrations hitting the API’s rate limits. The move to MYOB Acumatica takes 12 weeks on FastStart and typically 12 to 20 weeks when scoped wider.

At a glance

• Who it is for: Australian businesses on AccountRight Plus or Premier whose finance team now works around the product rather than in it
• Problem it solves: Deciding from MYOB’s own documentation whether the pain is AccountRight’s design limit or your setup, and what a move takes in weeks
• Platforms: MYOB AccountRight Plus and Premier (the source) and MYOB Acumatica, which MYOB sold as MYOB Advanced until 2024 (the destination)
• Typical cost: MYOB Acumatica licensing is quoted per named user through partners and is not published; implementation ranges are in our MYOB Acumatica cost guide
• Typical timeline: 12 weeks for a single-entity wholesale distributor on MYOB FastStart for wholesale distribution; scoped builds with multiple entities, payroll or integrations run longer
• Last verified: 20 October 2026 against MYOB’s AccountRight locations help, AccountRight roles help, companies and branches guide and MYOB Acumatica licensing

Most calls we take about outgrowing MYOB start the same way: the file is slow, month end takes a week, and someone has said the word ERP. Half the time the answer is a cleanup inside AccountRight. The other half, the business has hit something AccountRight was never built to do. Below are the five signals that separate the two, what moving from MYOB to an ERP takes in weeks, and what comes across. This is not a feature comparison; our MYOB Acumatica vs AccountRight comparison does that job.

How do you know you have outgrown MYOB AccountRight?

Where MYOB’s help pages state the boundary, we link them. Where they are silent, we say so.

Signal 1: you run more than one entity and consolidate in a spreadsheet

AccountRight is one company file per business. MYOB’s pricing page lists “add another business” as a Premier feature, which gives you a second file, not a group; the group result gets built in Excel. MYOB’s own comparison page assigns reporting that “supports cross-functional and multi-entity requirements” to MYOB Acumatica, not AccountRight.

In MYOB Acumatica, several companies share one tenant once the Multicompany Support feature is enabled, with branches on the Companies (CS101500) and Branches (CS102000) forms, per the companies and branches guide. The multi-branch models guide describes a consolidating branch that receives no transactions, and branches on separate ledgers for which “balancing interbranch transactions will be generated automatically”. Two or more ABNs plus a monthly consolidation workbook, and you are past this one.

Signal 2: stock needs serial numbers, batches or more than one warehouse

AccountRight’s inventory is average cost only. Its inventory method help says “your inventory’s monetary value is tracked using the average costing method”; FIFO appears only as a method other systems use. Multiple locations exist, but the locations help states they apply to “AccountRight Premier 2019.2 and later”, so Plus users have one. Neither page mentions serial or batch numbers, and we have not found an AccountRight help page that does.

MYOB Acumatica’s inventory overview lists the features you switch on: Multiple Warehouses and Multiple Warehouse Locations, Lot and Serial Tracking to “track stock items by lot or serial numbers and by expiration dates”, and multiple valuation methods. Our MYOB inventory management guide walks the three MYOB tiers. The test is a recall question: if a supplier rang about a faulty batch, could you name the customers who received it from the file alone?

Signal 3: more people need access, and nobody can approve anything

User count is not the problem. The pricing page lists unlimited user profiles on AccountRight Plus, and the roles help describes default roles (Administrator, Accountant/Bookkeeper, Sales, Field) you can copy and edit per window, plus a read-only override per user. What the roles page never describes is an approval step. A user can record a purchase or cannot; nothing waits for a second person.

MYOB Acumatica keeps access and approval apart. The licensing page lists named user licence types including Full user, Warehouse, Finance and External bookkeeper, with the edition deciding which are available. Separately, the Approval Workflow feature routes purchase orders, bills, payments, sales orders, expense claims and journals through approval maps, per the approval configuration guide. If “who signed off on this” is answered by searching email, that is box three.

Signal 4: reporting and the audit trail live outside the file

AccountRight does keep an audit record. Its security audits page describes the Journal Security Audit, which lists transactions as Added, Edited, Deleted, Reversed or System, and the Session Security Audit, which lists sign-ins. That is transaction level. It will not tell you who changed a supplier’s bank account number.

MYOB Acumatica’s field-level auditing guide describes switching auditing on per form at Audit (SM205510) and reading the history on Audit History by Screen (SM205530), filterable by user, table and date. For reporting, a generic inquiry (SM208000) pulls any data in the database onto a form that feeds dashboards and pivot tables. Count the spreadsheets that exist only because a report does not. More than three is a design limit, not a training gap.

Signal 5: your integrations are hitting the API’s limits

AccountRight has an API and an established partner ecosystem. The limits show up at volume. MYOB’s API error reference lists two 403 responses, “API key has exceeded the per-second rate limit” and “API key has exceeded the daily rate limit”, without publishing the numbers behind them. An ecommerce platform syncing stock every few minutes plus a warehouse scanning app on one key will find them.

MYOB Acumatica publishes its limits. The API licence page describes a free Full User API licence capped at 1,500 calls a day for one user, and a paid Full Access API licence with no daily cap across up to 100 named users. If any integration has been throttled or re-run by hand in the last quarter, that is your fifth box.

When is staying on AccountRight the right call?

One box: stay. A single entity with simple stock, one location and a bookkeeper who runs the file is what AccountRight is built for, and an ERP project will cost more than the problem. MYOB’s September 2025 mid-market survey found 36% of more than 500 mid-sized business leaders planned to upgrade or improve their ERP; the majority did not, and plenty of them are right to stay put.

Two boxes is worth a conversation. Three or more, and the work-arounds cost more than you think, because they live in people’s heads and leave when they do.

“I don’t ask what AccountRight cannot do. I ask what your finance manager does on a Saturday. If the answer is consolidation, stock reconciliation or rebuilding a report, the product has stopped doing its job and a person has started doing it instead.”

Bill Alvarez, Practice Manager, Auboros

How long does moving from MYOB AccountRight to MYOB Acumatica take?

Twelve weeks is the fixed answer for one profile, and a scoped answer for everyone else.

The fixed answer is MYOB FastStart for wholesale distribution: a pre-configured MYOB Acumatica implementation for a single legal entity and branch, under 10 users, under 50 staff and under $10m turnover, in wholesale distribution. Seven signed-off checkpoints run from finance setup to go-live, and the page budgets 95 hours of your team’s time across the 12 weeks, about 8 to 9 hours a week, 52.5 of them alongside a consultant, plus 14.5 hours of MYOB Academy training.

Outside that profile, the implementation is scoped after discovery. Our MYOB Acumatica vs AccountRight comparison puts a typical AccountRight-to-Acumatica project at 12 to 20 weeks, and our guide to moving from Xero or AccountRight to an ERP notes that cutover is usually a weekend at period end, with multiple entities, complex inventory and custom integrations as the things that lengthen the plan.

The phases do not change with scope, only their length.

• Discovery and scoping (weeks 1 to 2). Entity map, item master review, user list by role, integration inventory, history depth decision.
• Core configuration (weeks 2 to 6). Chart of accounts, tax codes and BAS mapping, bank feeds, customers, suppliers, items, pricing, order types, approval maps. FastStart compresses this because it is pre-built.
• Migration rehearsal (weeks 5 to 8). Export from AccountRight, clean, import into a test tenant, reconcile to the trial balance and aged lists. Expect two or three passes.
• User acceptance testing (weeks 7 to 10). Your people run a real month in the new system, including a pay run if payroll is in scope.
• Cutover and stabilisation (weeks 10 to 12 or later). Final balances loaded over a weekend at period end, then the first BAS with support.

What carries over when you replace MYOB with an ERP?

Data moves. Configuration is rebuilt.

Open transactions and balances. MYOB Acumatica’s document migration guide explains migration mode: it lets you “load documents without affecting the general ledger”, switched on for receivables, payables or both. Each migrated invoice or bill needs its open balance, original amount and document date; once released, these update customer and supplier balances while the GL is loaded separately from the trial balance. Per the data import guide, test each scenario on one record, then run it on Import by Scenario (SM206036).

History depth. The default is opening balances plus open transactions, with AccountRight kept as a read-only archive. That meets the ATO’s record-keeping rules, which require most records for five years and say “you need to be able to reconstruct your original data if your record-keeping system changes over time”. Full history is for businesses with a specific reason, such as warranty lookups.

Payroll and STP. The clean cutover is 1 July. If you move mid-year, the ATO’s guidance on changing payroll software gives two routes: zero out year-to-date amounts in AccountRight with an update event and load them into the new software, or load them and send an update event quoting your previous BMS ID (an update event only, never a pay event). Finalisation stays open until 14 July. On the MYOB Acumatica side, the Single Touch Payroll guide states that completing a pay run creates an STP batch submitted to the ATO after a declaration, with finalisation run from the STP Finalise form (MP.PP.50.23).

If three or more signals apply

Write them down with the evidence next to each: the consolidation workbook, the batch you could not trace, the approval that lives in email, the spreadsheets that replace reports, the integration that was throttled. Then settle the two questions that add the most weeks: how many legal entities go live on day one, and whether payroll moves with finance or later. We are a MYOB Acumatica partner in Brisbane, and those two answers decide the timeline more than anything in the item master does.

Goes well with

• MYOB Acumatica hidden costs: what the licence quote leaves out
• MYOB Acumatica for wholesale distribution: what the FastStart program gives you
• MYOB AccountRight to Odoo migration: what moves, what doesn’t, and when Acumatica is the better answer

Not sure whether you have outgrown AccountRight or just outgrown your setup?

We work with businesses across Queensland, NSW and Victoria weighing this call, and we say so when the answer is to stay on AccountRight. If you want the five signals scored against your file, book a free consultation. Thirty minutes, and you leave with a yes, a no, or a list of what to fix first.