Moving from MYOB Exo to MYOB Acumatica
MYOB Acumatica is the cloud product in the MYOB range for organisations at the size Exo typically serves.
That makes some things easier and it does not make the migration itself easier. The work is the same work: your data has to move, your customisations have to be assessed, your reporting has to be rebuilt, and your team has to learn a different system. What it does change is that the commercial conversation is a roadmap conversation rather than a displacement one.
If you are on Exo and wondering what the path looks like, this page covers what genuinely moves, what does not, and what tends to surprise people.
For anything about the Exo product roadmap specifically, MYOB is the authoritative source. Ask them or your partner directly.
Is MYOB Exo end of life?
Half of it is. End of life is not one event, and Exo is not one product. Two products carry two very different statuses, and confusing them leads people to either panic or relax when neither is warranted.
- MYOB announced the end-of-life process in January 2024
- Reached end of life on 30 November 2025 and has been decommissioned
- No further updates to tax rates or thresholds, so it is no longer compliant
- Read-only access retained for historical and reporting purposes
- Pay runs can no longer be processed
- MyStaffInfo, the employee self-service portal, was shut down in November 2025
This came directly from MYOB to licence holders and partners. The dates were fixed, and they have now passed.
- No end-of-life date has been announced
- Runs on a Microsoft SQL database and remains supported
- Partners continue to support it for existing customers
- Still receiving compliance updates and bug fixes
- No published public product roadmap, and new development is going into MYOB Acumatica
The industry term for this position is mature lifecycle. It is an honest description: the platform will not break this week, and the gap between what it does and what modern cloud ERP does will widen quietly from here.
Nothing is forcing your hand on the ERP. Something already forced it on payroll.
That distinction is worth holding onto. If a supplier tells you Exo Business is end of life, they are either mistaken or hoping you will not check. If one tells you nothing has changed, they are ignoring that a major module has already been decommissioned and development has visibly moved elsewhere.
Where Exo sits
Exo has been a capable mid-market system for a long time, and a lot of New Zealand businesses run it well. Most organisations that start looking at alternatives are not doing so because Exo stopped working. They are doing so because something around it changed.
Payroll already went
Exo Employer Services was decommissioned in November 2025. Organisations that had to solve payroll then are now asking the same question about the ERP.
The deployment model
Exo installations are typically on your own infrastructure. When a server refresh comes due, the deployment question and the ERP question arrive together.
Access away from a desk
Field staff, site teams and warehouse people increasingly need to interact with the system from where the work happens.
Reporting that migrated into Excel
Where the numbers that matter get assembled outside the system every month, the organisation is effectively running a second, unlicensed system.
Accumulated customisation
Ten years of small changes, each sensible on the day, and no complete picture of what they now amount to.
None of these force a decision on their own
Two or three together usually start one.
What actually moves, and what does not
What holds generally, whatever your specific setup:
Modern systems handle layout, fields and personalisation differently enough that a faithful reproduction of an old screen is normally the wrong instinct and an expensive one.
Assume this from the start and budget for it. The useful exercise is working out which reports are still read, because organisations routinely find a meaningful proportion are produced and ignored.
Anything reading or writing straight into the Exo database, including reporting tools pointed at the back end, does not survive in any form because the underlying structure is different. These always need redesigning, and they are frequently built by IT rather than by the ERP partner, which is why they are the last thing anyone thinks to look for.
These are not integrations. Someone does that by hand, on a schedule. They rarely appear on any inventory because no software was ever bought, and most turn out to be an improvement rather than migration scope.
Payroll has already moved. What that tells you about the rest.
If you were running Exo Employer Services, you have already been through this. Payroll had a fixed date, the date has passed, and you made a decision one way or another.
That matters for the ERP conversation in a way most people have not thought about.
You have already done the hardest part of an ERP migration once.
Payroll is the least forgiving system in any business. The data is personal, the errors are visible to every employee, the deadlines do not move, and there is no version of getting it slightly wrong that nobody notices. If your team moved payroll and came out the other side, they now know what a migration actually involves, and the fear of the unknown is largely gone.
Where that leaves you now
Three situations, and the ERP question looks different in each.
You already run MYOB Acumatica alongside Exo Business. The ERP question is not really a migration question any more, it is a consolidation question: whether to keep operating two systems and the join between them, or bring the rest across to where payroll already lives.
You now maintain an integration between two vendors that were never designed to work together, and somebody owns that. Worth counting what it costs to run and what happens when either end changes.
If pay is being processed manually, on a spreadsheet, or on something temporary, that is the urgent item and it outranks any ERP decision. Sort it first.
What it does not tell you
Payroll reaching end of life says nothing about Exo Business, which has no announced end-of-life date and remains supported. Do not let a supplier use one to imply the other. What it does tell you is where MYOB's investment is going, and that is a slower signal, but it is a real one.
You choose how much comes across
The choice affects both cost and performance. Most organisations migrate balances plus a defined period of transaction detail, then either archive the remainder or retain read-only access to Exo for a period.
Audit, tax and warranty obligations usually drive the retention requirement, and those are not negotiable, so establish them before you plan anything else.
Agree the retention arrangement and its cost before you give notice on your current licensing. Access terms are rarely better once you have announced you are leaving.
Open transactions are missed more often than balances
Open sales orders, purchase orders, part-received goods and unbilled work all need identifying and agreeing. They are the items most likely to cause a reconciliation argument after go-live.
What your own team has to do
The heaviest load falls at two points, and both land on finance.
Somebody in finance has to put their name to the opening position. That work cannot be delegated to a supplier, because the supplier cannot know whether the numbers are right.
Your people run this. Testing done by consultants finds nothing, because consultants do not know what normal looks like in your business.
Any supplier should give you an estimate in days by role and by phase before you sign anything. If they cannot, that is worth knowing early.
Where to start
Two things you can do without involving a supplier.
Customisations, integrations and reports, with who uses each and whether anyone still understands it. The volume of customisation is the single largest variable in what a migration costs, and quotes given against a real inventory are sharper than quotes given against an unknown.
Licence, maintenance, infrastructure, external IT, upgrade projects annualised, and the staff time going into manual work and spreadsheet reporting. It is usually a larger number than people expect, and it is the one missing from most ERP business cases.
Both are free tools in our ERP Migration Toolkit, and you can complete them without involving anyone.
Avanza Solutions is a MYOB Acumatica implementation partner based in New Zealand and part of Verde Group. The tools in our migration toolkit are written to be useful whichever system you select, and MYOB is the authoritative source on the roadmap for its own products.
The ones people ask first
Half of it. MYOB Exo Employer Services, the payroll product, went through a formal end-of-life process announced in January 2024 and was decommissioned on 30 November 2025. It no longer receives tax rate and threshold updates, it cannot process pay runs, and read-only access is retained for historical and reporting purposes only. MyStaffInfo, the employee self-service portal, was shut down at the same time.
MYOB Exo Business, the ERP system, has no announced end-of-life date. It runs on a Microsoft SQL database, remains supported, and still receives compliance updates and bug fixes. What has changed is that new development is going into MYOB Acumatica rather than Exo. The accurate description is mature lifecycle rather than end of life.
MYOB announced the end-of-life process in January 2024 and Exo Employer Services was decommissioned on 30 November 2025. Organisations running it had to move payroll to another solution before that date. MYOB positions MYOB Acumatica Payroll as the replacement for the ANZ mid-market, though other options exist and it is reasonable to have considered more than one.
If you are still processing pay manually or on a temporary arrangement, that is more urgent than any ERP decision and should be resolved first.
No. Exo Business has no announced end-of-life date and is still supported, so nothing is forcing your hand.
What is worth examining is the position you are now in. If payroll went to MYOB Acumatica, you already run both systems and the question is really about consolidation rather than migration. If payroll went elsewhere, you now maintain an integration between two vendors and somebody owns the cost of that. Either way you have already been through a migration once, which usually makes the next conversation a more informed one.
MYOB Acumatica is the cloud product in the MYOB range for organisations at the size Exo typically serves. It is not an upgrade of Exo, it is a different product, so moving is a migration rather than a version upgrade.
Reports are generally rebuilt rather than ported, so budget for that from the start. Customisations sort into four groups: retired, replaced by standard functionality, redesigned because the implementation method cannot survive the move, and rebuilt where they encode something genuinely specific to your business.
Anything connecting directly to the Exo database always needs redesigning.
As much as you are willing to pay for and carry, though most organisations migrate balances plus a defined period of detail and archive the rest. Establish your audit, tax and warranty retention obligations first, since those are not negotiable, then decide the rest on cost.