Moving from MYOB Exo to MYOB Acumatica: What Changes and When

Moving from MYOB Exo to MYOB Acumatica takes 12 to 20 weeks. Exo Business’s on-premise SQL Server database becomes a cloud tenant, the Exo branch and sub account structure maps to MYOB Acumatica subaccounts, and payroll moves from Exo Payroll to MYOB Acumatica Payroll. Go live at a quarter boundary for the BAS, cut payroll over at a pay-period start, and report the BMS ID change to the ATO.

At a glance

• Who it is for: Australian businesses on MYOB Exo Business, with or without Exo Payroll (Exo Employer Services), that have had MYOB’s notice about Exo Payroll compliance updates ending
• Problem it solves: A migration planned backwards from the two dates that cannot move, the last Exo Payroll pay run and the first MYOB Acumatica Business Activity Statement (BAS)
• Platforms: MYOB Exo Business and Exo Employer Services to MYOB Acumatica and MYOB Acumatica Payroll (called MYOB Advanced until 2024, so older Exo-to-Advanced material describes the same destination)
• Typical cost: MYOB prices MYOB Acumatica per named user and quotes through partners; indicative implementation ranges by scope, AUD ex GST, are in our MYOB Acumatica cost guide
• Typical timeline: 12 to 20 weeks from discovery to go-live depending on whether job costing, CRM and payroll are in scope
• Last verified: 20 October 2026 against MYOB’s Exo product page, the Exo Employer Services version history, MYOB Acumatica’s migration mode help and the ATO’s changing your payroll solution page

Most Exo sites we meet have run the same database for ten years or more. The GL is tidy, the stock file is not, and payroll runs on a server one person logs into. The move takes as long as that database says it does.

Is MYOB Exo being discontinued?

Treat the two products separately, because MYOB does. MYOB’s Exo product page still lists Exo Business as “flexible, on-premise business management software” and points visitors on to MYOB Acumatica, and the Exo Business version history lists a 2026.1 release. As at 20 October 2026 we could not find a MYOB page giving Exo Business an end date, so if someone says the ERP side has a deadline, ask to see MYOB’s wording.

Exo Payroll is different. MYOB has told Exo customers that compliance updates for Exo Payroll are ending; check the date MYOB gave your site in its notice, because the partner blogs disagree and none links a MYOB page. MYOB’s own Exo Employer Services version history shows, as at 20 October 2026, 2024.02 as the latest Australian release, with an STP security certificate described as valid until 7 August 2026. Ask MYOB what that means before you plan around a date you read online.

What is MYOB Exo, and what is different in MYOB Acumatica?

MYOB Exo Business is a Windows client over a Microsoft SQL Server database. MYOB’s system requirements guidelines (updated 15 September 2025) list SQL Server 2017, 2019 and 2022 and Windows Server 2016 to 2025. The modules are Exo Business Core, Exo Finance, Exo Job Costing, Exo CRM, Exo Fixed Assets, Exo POS and Exo OnTheGo, with Clarity for reporting. Exo Employer Services is a separate install; MYOB’s 2021.01 release notes list its applications as Exo Payroll, Exo Employee Information and Exo Time and Attendance.

MYOB Acumatica is the ANZ edition of Acumatica, described on MYOB’s product page as a cloud ERP for mid-sized businesses. The browser is the client and MYOB applies releases to your tenant. Licensing is per named user. Payroll is a module of the same platform rather than a second product, so the payroll journal lands in the general ledger on the pay date.

One row has a hard constraint: MYOB’s valuation help states an item’s method can only be changed when its on-hand quantity is zero, so that decision is made before opening stock is loaded.

What data migrates from MYOB Exo to MYOB Acumatica?

Less than you expect, and that is the point. Master data and open items move, closed history is reported from, and the depth of history you load is a decision with a cost attached.

• Chart of accounts and opening balances. The trial balance at the cutover date is loaded as a GL journal per account and subaccount. Prior-period balances go in as monthly net movements if you want comparatives, or stay in a read-only Exo database if you do not.
• Customers, suppliers and items. Exo debtors, creditors and stock items are exported, cleaned and imported with MYOB’s import scenarios. Cleaning is the real work: duplicate debtors, suppliers with no ABN and items with no movement in three years do not deserve a row.
• Open AR and AP. MYOB Acumatica’s migration mode, switched on in the receivables or payables subledger, loads each open invoice or bill with its original amount, open balance and document date. Released migrated documents “update customer or vendor balances but do not update the general ledger”, so the control account comes from the opening trial balance and the two are reconciled before migration mode is switched off.
• Stock on hand. Quantities and unit costs by warehouse at cutover, after a physical count. Lot and serial numbers come across only for items that will be tracked that way.
• Open jobs, fixed assets and open orders. Open jobs with cost to date and remaining budget, fixed assets with cost and accumulated depreciation, and open sales and purchase orders keyed in go-live week after the last Exo despatch.
• History depth. Two years of GL movements and twelve months of sales history is a common choice. Full history is possible, but it stretches every rehearsal and rarely gets used.

The sequence is the one we use when a business is moving from Xero or AccountRight to an ERP: rehearse the full load at least twice on a copy, reconcile to Exo each time, and only then load live.

“The Exo sites that go live cleanly are the ones that decided early what they were not bringing. Every rehearsal we have seen run long was carrying history nobody had asked for. Load what you will act on, keep Exo readable for what you will only look up.”

Bill Alvarez, Practice Manager, Auboros

How do you cut over payroll from Exo Payroll to MYOB Acumatica without breaking STP?

Payroll is its own project inside the project. Single Touch Payroll (STP) reports carry a BMS ID, which the ATO’s changing your payroll solution page (last updated 13 November 2023) describes as acting “like a serial number to tell us which payroll solution sent the STP report”. When MYOB Acumatica Payroll takes over, the ATO sees a new BMS ID, and the page gives three ways to keep income statements whole.

• Do not transfer year-to-date amounts. Finalise STP in Exo Payroll for every employee, then start MYOB Acumatica Payroll at zero. Each employee has more than one income statement for the year, each must be finalised, and the ATO says you can finalise the old one until 14 July if you still have access to Exo Payroll and authorisation for the ABN. Simplest if your cutover lands on 1 July.
• Zero out and transfer. Send an update event from Exo Payroll showing all year-to-date amounts as zero, then load the year-to-date figures into MYOB Acumatica Payroll and report them from there. Use it if Exo Payroll can still send that event.
• Replace the BMS ID. Load the year-to-date figures into MYOB Acumatica Payroll and send an update event carrying the previous BMS ID and payroll IDs. The Previous ID Update form (MPPP5027) does this: it reads the previous BMS ID from the Companies form (CS101500) and each employee’s previous payroll ID from Pay Details (MPPP2310), and submits the update event. Tick Include inactive employees for migrated terminated staff.

The ATO is blunt about getting this wrong: transfer year-to-date amounts without telling it and “your employees will see duplicate income statements”. Our MYOB Acumatica payroll guide covers what happens next: STP batches on Manage STP Submissions (MPPP5019), finalisation on STP Finalise (MPPP5023), and the super batch after every pay run that Payday Super has required since 1 July 2026.

The data that moves is employee masters, pay items mapped to STP Phase 2 categories, leave balances by type, year-to-date figures if you are transferring them, and award rules rebuilt as pay rules. Cut over at a pay-period start, after one full pay period run in parallel: the same timesheets in both systems, every employee’s gross, tax, super and net compared line by line. Then the last Exo pay is finalised or zeroed out, its super paid within the Payday Super 7 business day window, and the first MYOB Acumatica pay goes out the following period.

How long does an Exo to MYOB Acumatica migration take?

Plan it in weeks, anchored to a quarter end and a pay-period start. The ATO’s BAS due dates (updated 17 September 2026) fall on 28 October, 28 February, 28 April and 28 July for quarterly lodgers, so a go-live on the first day of a quarter means the last Exo BAS is lodged from a closed Exo database and the first MYOB Acumatica BAS covers a whole quarter.

• Weeks 1 to 3, discovery and design. Walk every Exo module in use, map the GL to accounts and subaccounts, pick valuation methods, decide history depth. Payroll discovery runs alongside: pay items, awards, leave types, the STP method.
• Weeks 4 to 9, build. Companies, branches, chart, subaccounts, item classes, warehouses, customer and vendor classes, projects, approval maps. Payroll build and data cleaning in Exo happen here.
• Weeks 8 to 12, migration rehearsals one and two. Full load on a test tenant, reconciled to Exo at the same date. Finance signs off the trial balance, aged ledgers and stock valuation after each. Training runs on the rehearsal data.
• Weeks 12 to 15, payroll parallel run and acceptance testing. One full pay period in both systems, compared employee by employee, and the main processes tested end to end on rehearsed data.
• Week 16, cutover. Last Exo despatch, physical count, final exports, live load over the quarter-end weekend, reconciliation Monday, first transactions Tuesday. Payroll cuts over at the first full pay period after go-live.
• Weeks 17 to 20, hypercare. The first month-end close with a consultant in the room, the first BAS prepared from MYOB Acumatica, and the Exo database set to read-only.

A finance-only move sits at the short end; job costing, CRM and payroll together push it to the long end. We are a MYOB Acumatica partner in Brisbane and most of the Exo moves we scope are the long version, because the sites that chose Exo chose it for job costing or stock, not for the ledger.

Where Exo to MYOB Acumatica migrations go wrong

• Rebuilding Exo in MYOB Acumatica. Every GL analysis code made a subaccount segment produces a system nobody can code a transaction in. Keep subaccounts to what finance will filter by.
• Loading history nobody asked for. Every extra year is another reconciliation per rehearsal. Decide depth in discovery and hold the line.
• Treating payroll as a data job. The ATO sets the sequence. Pick the STP method in week one, confirm Exo Payroll can still send whatever event the method needs, and keep the Exo Payroll server alive until 14 July of the following year.
• Going live mid-quarter. A split BAS and a stock valuation that reconciles to nothing. If the payroll notice forces an early cutover, move payroll first and the ERP at the next quarter end.
• Switching Exo off. Keep the database readable for a full financial year of lookups and the ATO’s finalisation window.

Goes well with

• MYOB Acumatica hidden costs: what the licence quote leaves out
• Payday Super is live: what to check in MYOB Acumatica Payroll now
• What is MYOB Acumatica? A plain-English guide for Australian businesses

Planning an Exo to MYOB Acumatica move around a payroll date?

We scope Exo Business and Exo Payroll migrations for businesses across Queensland, NSW and Victoria, starting with the two dates that cannot move and working back. If you want the plan tested against your Exo database and pay calendar, book a free consultation. We will tell you what moves, what stays, and whether payroll should go first.