Upgrade guide
MYOB Exo replacement: your options in 2026
MYOB retired Exo Employer Services in November 2025 and its cloud investment is in Acumatica. A practical guide to the real replacement paths for NZ and AU Exo sites, including the one MYOB will not pitch you.
Keep and extend
Keep the accounting system that works. Map the stock, order and warehouse records that need to cross the boundary, and agree ownership and reconciliation.
Replace and consolidate
Evaluate replacement when the existing system cannot meet core requirements. Include data migration, finance continuity, training and integration changes in the decision.
The decision in context.
MYOB Exo Business still runs, but the direction of travel is hard to miss. MYOB retired Exo Employer Services, the payroll companion most Exo sites run beside it, on 30 November 2025, and the company’s cloud investment is squarely in MYOB Acumatica. Exo is a twenty-year-old on-premise SQL Server product in a vendor portfolio whose future is being built elsewhere. Nothing is on fire. But most Exo sites are now planning their next move on a clock measured in years, not decades, and the consultant pool that knows their customisations gets shallower every year.
The replacement market splits into two shapes. The full-suite swaps first: MYOB Acumatica is the vendor's official upgrade path and the path of least resistance for finance-led teams, your existing MYOB partner can quote it, the commercial relationship carries over, and the migration is their problem. Microsoft Dynamics 365 Business Central and NetSuite are the credible suite alternatives outside the MYOB ecosystem, and Odoo is the open-source option for teams with technical appetite. All four replace everything at once, ledger and operations together, which is exactly what makes them slow, expensive, and a big-bang cutover risk.
There is a fifth option that splits the problem the way Exo's own architecture did. Exo was always two systems in one box: a general ledger and an operations engine for stock, orders, and dispatch. The ledger half moves to MYOB Business or MYOB AccountRight without drama, same vendor, and your accountant already knows it. The operations half is what actually made Exo hard to leave, and that is the half OpsUI replaces: warehouse, orders, and dispatch as individually priced modules, synced to your MYOB ledger through a bidirectional connector wired against your tenant during rollout. This page lays out all five paths honestly, including the ones where we lose.
Editorial context from the original analysis. Confirm current vendor-specific details against the applicable proposal.
Like-for-like requirements
Work through the requirements.
OpsUI + MYOB Business/AccountRight
- OpsUI approach
- NetSuite is listed as live; Xero, MYOB, Abel and SAP are built on rollout. NZ Couriers is listed as live; other carrier connections are scoped per account.
- MYOB Exo: considerations to verify
- Best for Exo sites whose pain is operational, who want to migrate one workflow at a time instead of big-bang, and who are happy keeping MYOB for finance.
Vendor-specific scope and limitations are not independently verified here.
MYOB Acumatica
- OpsUI approach
- NetSuite is listed as live; Xero, MYOB, Abel and SAP are built on rollout. NZ Couriers is listed as live; other carrier connections are scoped per account.
- MYOB Exo: considerations to verify
- Best for finance-led mid-market teams who want to stay inside the MYOB ecosystem, need full-suite depth, and have budget approved for a partner-led implementation.
Vendor-specific scope and limitations are not independently verified here.
Microsoft Dynamics 365 Business Central
- OpsUI approach
- Microsoft-ecosystem SMB suite, partner-implemented, integrated with Power BI, Outlook, and Teams.
- MYOB Exo: considerations to verify
- Best for operators standardised on Microsoft 365 who want a suite replacement from a vendor outside the MYOB orbit.
Vendor-specific scope and limitations are not independently verified here.
Oracle NetSuite
- OpsUI approach
- Global cloud ERP suite, sales-led licensing, partner or direct implementation.
- MYOB Exo: considerations to verify
- Best for multi-entity, multi-country groups that need consolidated financials in one ledger and can absorb Tier 1 licence and implementation costs.
Vendor-specific scope and limitations are not independently verified here.
Odoo
- OpsUI approach
- Open-source global ERP, free Community edition self-hosted, paid Enterprise on Odoo Online or self-hosted.
- MYOB Exo: considerations to verify
- Best for technically capable teams who want maximum flexibility and will own the configuration, hosting, and ANZ localisation work themselves.
Vendor-specific scope and limitations are not independently verified here.
Staying on Exo for now
- OpsUI approach
- Exo Business keeps running and remains supported, but the payroll companion is retired and MYOB’s roadmap investment is in Acumatica.
- MYOB Exo: considerations to verify
- A reasonable bridge while you choose a destination. Plan the destination now, while the partner pool that knows your customisations is still deep.
Vendor-specific scope and limitations are not independently verified here.
Commercial structure
Keep the assumptions visible.
Compare subscriptions, user allowances, integration work and implementation responsibilities. Preserve the currency and billing period of each offer.
Essential
NZ$499per month
2 users included
2 operational modules
Control
NZ$1,499per month
5 users included
5 operational modules
Command
NZ$2,999per month
15 users included
11 operational modules
Apex
NZ$11,990per month
Unlimited users
20 operational modules
Published monthly subscriptions in NZD. Existing annual pricing and package allowances apply. Additional seats are NZ$99 per month beyond the applicable allowance; integration connectors are separate add-ons.
Review the full packages and configure pricing →Where each approach may fit.
When MYOB Acumatica, the official upgrade path, is the right call
Confirm current subscription, allowances and implementation costs against an itemised proposal; the commercial structure is explained below.
Your manufacturing needs include MRP, finite-capacity scheduling, and shop-floor data collection. Exo plus add-ons was doing this for you, and that depth has to survive the migration. OpsUI's manufacturing scope is lighter, and we will tell you so on the scoping call.
Your long-standing Exo partner is also a MYOB Acumatica partner. They know your data, your customisations, and your workarounds. That knowledge materially de-risks a migration, and it is worth real money.
You want one suite to replace both halves of Exo at once, with a partner contractually owning the project rather than your own team sequencing it.
Confirm current subscription, allowances and implementation costs against an itemised proposal; the commercial structure is explained below.
When keeping MYOB for the ledger and replacing Exo's operations with OpsUI wins
Exo's value to you was in operations, stock control, sales orders, picking, dispatch, and the general ledger half can move to MYOB Business or AccountRight without ceremony.
Confirm current subscription, allowances and implementation costs against an itemised proposal; the commercial structure is explained below. No partner quote, no sales process to discover the number.
You want to migrate in stages, warehouse first, then orders, then dispatch, with Exo still running beside it, rather than betting the company on one cutover weekend.
Scope the required modules, users, data preparation and integrations before comparing delivery time or total cost.
Confirm production, backup and log locations for the proposed deployment. Regional domains or billing currencies do not establish data residency.
You do not need full-suite depth, MRP, finite-capacity scheduling, multi-entity consolidation. If you do, read the section above; we mean it.
Implementation and local context.
Exo began life as Exonet, built in New Zealand before MYOB acquired it, and its installed base is almost entirely NZ and AU wholesale, distribution, and manufacturing, exactly the profile OpsUI is built for. NZ and AU GST are native, NZ Couriers runs as a live carrier API today with Australia Post, StarTrack and other AU carriers configured against your accounts during rollout, support runs in ANZ business hours, and NZ data stays in NZ while AU data stays in AU. The honest counterweight: OpsUI launched in January 2026 and is founder-led with no public customer logos yet, so an Exo site trading a twenty-year-old product for it is trading institutional tenure for a modern product, public pricing, and direct access to the people who build it.
Agree data preparation, configuration, training, cutover and recovery responsibilities. Confirm the relevant accounting and carrier connections, rather than assuming they are included in the licence.
Questions buyers ask.
Is MYOB Exo end of life?
Exo Business itself has not been given an end-of-life date, it keeps running and remains supported. What has changed: MYOB retired Exo Employer Services, the payroll companion, on 30 November 2025, and MYOB’s product investment is focused on MYOB Acumatica. In practice that means Exo sites get to plan a replacement on their own schedule rather than being forced, which is the best position to evaluate from: no emergency, but a clear direction of travel.
Can I keep MYOB for accounting and just replace the Exo operations side?
Yes, that is exactly the split OpsUI is built for. Confirm current subscription, allowances and implementation costs against an itemised proposal; the commercial structure is explained below. The sync is event-driven, updates flow in seconds, not a nightly batch, works against both the AccountRight and MYOB Business APIs, and is wired against your tenant during rollout rather than installed from an app marketplace.
How do I migrate data out of MYOB Exo?
Exo Business runs on a Microsoft SQL Server database, so your data is fully accessible, item masters, customers, suppliers, stock on hand, and open orders all export cleanly. OpsUI imports those during onboarding, and because the rollout is module by module you move one workflow at a time (warehouse first is typical) instead of converting everything in a single cutover. Historical transactions can stay in a read-only Exo archive for reference; you rarely need to drag years of history into the new system.
What does the official upgrade path to MYOB Acumatica cost?
Compare the required modules, users, order allowances, integration work and implementation responsibilities before comparing prices. OpsUI’s current package structure is shown on this page. Current competitor prices and terms need confirmation with the vendor; historical estimates are not a current quote.
Is OpsUI a like-for-like Exo replacement?
No, and we will not pretend it is. Exo bundled a general ledger and an operations engine in one system, with payroll handled in the companion Exo Employer Services product. OpsUI replaces the operations half, orders, inventory, warehouse, dispatch, shipping, and pairs with MYOB Business or AccountRight for the ledger and payroll. Customer and pipeline tracking is handled as CRM-light inside Order Management, not a separate CRM module. If you need full-suite depth like MRP, finite-capacity scheduling, or multi-entity consolidation, MYOB Acumatica or Dynamics 365 Business Central are the honest answers.
Sources and verification scope.
Checked facts apply only to the scope described next to each source. Other vendor details in the editorial analysis remain unverified for a current purchase decision. Confirm them with the vendor and record the applicable plan, version and proposal date.
Current primary-source verification of this vendor’s detailed capabilities and prices is pending. An unknown is not a missing feature.
Further reading: MYOB / Acumatica, neutral guide
OpsUI integration delivery and scope · Security review information · Published OpsUI packages
Related comparisons and guides.
Your next step
Evaluate the fit against your operation.
Bring the workflows and dependencies that will decide the choice. We’ll review what OpsUI covers and what needs further confirmation.