Xero to MYOB Migration: The Steps and Where It Gets Complicated
The steps of a Xero to MYOB migration, and where it gets complicated: choosing the MYOB product, chart of accounts, tax codes, tracking, apps and payroll.
The steps of a Xero to MYOB migration, and where it gets complicated: choosing the MYOB product, chart of accounts, tax codes, tracking, apps and payroll.
Who this is for
Business owners, bookkeepers and finance managers planning to move from Xero to MYOB Business or MYOB AccountRight.
Question this answers
What are the steps of a Xero to MYOB migration, and where does it usually go wrong?
What you'll leave with
A Xero to MYOB migration follows the same path every time: choose the MYOB product and the conversion date, tidy Xero, design the MYOB accounts list and map Xero to it, map the tax rates, decide how much history to bring, move the balances and open items, then check MYOB against Xero before you switch. The move itself is the quick part. The time goes into the decisions and the checking.
Most migrations in this direction go smoothly. The ones that do not usually fail in the same few places: an accounts list copied from Xero without headers or linked accounts, tax rates that do not land on the right BAS labels, tracking categories forced into the wrong MYOB feature, apps that have no MYOB connection, or payroll moved mid-year. This guide walks through each of them so you know where to look.
Most moves go the other way, from MYOB to Xero. The businesses that move back to MYOB usually have a specific reason, and it is worth being clear about yours, because it decides which MYOB product you need.
If your reason is one specific feature, check that the MYOB plan you are looking at includes it before you start. It is much easier to change plans before the move than after it.
Here is the order a Xero to MYOB migration has to follow. Skipping ahead, for example connecting the bank feeds before the accounts are mapped, creates rework later.
The chart of accounts is the backbone of the move, and going from Xero to MYOB is not simply the reverse of going the other way. Xero is loose about structure. MYOB is strict. The structure has to be added, and somebody has to decide what it is.
Here is what getting it wrong looks like. A business copies its Xero accounts into MYOB in alphabetical order and lets the numbers fall where they may. Freight income lands in the expenses range, and a loan from the director lands under current liabilities when it should not. The trial balance still adds up, so nobody notices. Three months later the bank asks for a profit and loss and a balance sheet, and both are wrong in ways that take an afternoon to explain.
Tax mapping is the part of a migration most likely to be wrong without anybody seeing it. A wrongly mapped code raises no error. The invoices look fine. The BAS is simply wrong, every quarter, until somebody checks.
Standard rates. Xero's GST on Income, GST on Expenses, GST Free, GST on Capital, Input Taxed and BAS Excluded rates all have MYOB equivalents, but they are named and coded differently. Each one has to report to the same BAS labels it did in Xero. Check that capital purchases still land in G10, that GST-free sales still go to G3, and that input-taxed sales still sit outside GST.
Rates somebody created. Many Xero organisations carry extra rates added over the years: one for imports, one for a private-use split, one created by an app. Each needs a decision: map it to a standard MYOB code, create a matching code in MYOB, or retire it.
Accounts and items carry default tax codes. In MYOB, accounts and items can carry a default tax code that is filled in on every new transaction. If those defaults are wrong after the move, every new invoice and bill is wrong from day one, even if the history came across perfectly.
Xero lets you tag transactions with up to two active tracking categories, such as region and department. MYOB does not work the same way. It has two separate features, and they behave differently.
A Xero tracking category for a site, project or contract usually fits MYOB jobs. One for a branch or division may fit categories, but only if every transaction really belongs to a single branch. A business using both Xero tracking categories at once has to decide which one becomes which, and whether the second still earns its place.
Xero Projects is a separate feature again, with its own time entries, costs and quotes. That detail does not have a direct equivalent to land in, so decide which projects are still open, what the MYOB job needs to show for them, and where the time records will be kept.
Xero businesses often run several apps alongside it: payroll, inventory, job management, point of sale, ecommerce, expense claims, receipt capture, debtor follow-up and reporting. Every one of them needs an answer before the move.
The timing matters as much as the list. An app left connected to Xero after the conversion date keeps posting sales there, and an app connected to MYOB too early posts the same sales twice. Each one has to be switched over on the conversion date, and its first sync checked. Where an app has no MYOB connection and nothing replaces it, a MYOB integration may be the answer.
Payroll is the part of the move with the most direct effect on people. Year to date earnings, tax withheld, super and leave balances all have to carry across exactly, and every pay item in Xero has to be set up in MYOB to report to the same Single Touch Payroll (STP) categories.
STP reports to the ATO from each payroll system separately. When the software changes mid-year, the ATO sees a new source of reports. Unless the year to date amounts carry across correctly, employees can see two income statements for the same year, one from Xero and one from MYOB, and the totals may not add up.
If you can, change payroll at 1 July. If you cannot, plan the first MYOB pay run as part of the migration: check every employee's year to date figures before it is lodged, and decide what happens to Xero's payroll records for the part of the year already reported.
Xero works on one organisation per entity, and many businesses have several: a trading company, a property trust, a second company for a new venture. Each normally becomes its own MYOB company file, because each has its own ABN and its own BAS.
If you report across the group, plan how that will work in MYOB before the move. Each company file reports on its own, so consolidated reports need a separate reporting tool or a reporting dashboard.
They have to be redesigned as MYOB jobs or categories, not copied.
Each one needs reconnecting, replacing or retiring on the conversion date.
Year to date balances and Single Touch Payroll reporting have to be right.
Each becomes its own MYOB file, and loans between them must still agree.
Every one has to land on the same BAS labels in MYOB.
The MYOB plan has to support it, and the values have to agree on day one.
If any of these apply, our Xero to MYOB migration service covers the planning and the move at a fixed price, quoted before work starts. For ongoing MYOB setup and support, see our MYOB services, and if you are weighing up the opposite move, the MYOB to Xero migration page covers it. We work with businesses across Australia, from Perth to Sydney, Melbourne, Brisbane and Adelaide.
A single, tidy Xero organisation with no payroll can be moved in days. Most businesses take two to six weeks from the first look at the data to the first month closed in MYOB, because the time goes into decisions and checking rather than the move itself. Payroll, several Xero organisations, inventory, projects, foreign currency or a long list of connected apps each add time.
It depends on what you need MYOB to do. Smaller businesses usually suit MYOB Business (the Lite or Pro plans). Businesses that want payroll included, deeper inventory and job features, or the Windows desktop software look at AccountRight Plus or Premier. Foreign currency and stock in more than one location need AccountRight Premier. Much larger businesses with many staff look at MYOB Acumatica, which was called MYOB Advanced until 2024 and is a different system altogether. Check the current plan features with MYOB before you decide.
The start of a financial year (1 July) is cleanest, because the year end is closed in Xero and MYOB starts fresh. The start of a BAS quarter is the next best, because each activity statement then comes from one system. Moving mid-quarter works, but the first BAS has to be put together from both.
It can, but you choose how much. The options are opening balances only, balances plus open invoices and bills, or several years of transactions. MYOB offers a conversion through a partner that covers the current and previous financial year. Anything older is usually best kept in Xero, on a read only subscription, or exported and stored, rather than brought across.
They have to be redesigned rather than copied. MYOB has jobs, which are chosen line by line, and categories, which apply to a whole transaction. A Xero tracking category for a project or site usually becomes a job. One for a branch or division may become a category, but only if every transaction belongs to a single branch. Decide this before any history comes across, because it cannot easily be changed afterwards.
Yes, but it is the part to be most careful with. Year to date pay, tax, super and leave balances have to carry across exactly. Because the payroll software changes, the ATO sees a new source of Single Touch Payroll reports, so you either carry the year to date amounts across correctly or finalise employees in both systems. Otherwise employees can see two income statements for one year. If you can, change payroll at 1 July.
No. We are based in Perth and move Xero organisations to MYOB for businesses in Sydney, Melbourne, Brisbane, Adelaide, Canberra, Hobart, Darwin and regional Australia. The work is done remotely, by our own team in Australia.
Meet the person
This guide comes from real projects. If it raises a question about your own system, you can ask the founder directly.
Hello, I am Kasun, the founder of HELLO PEOPLE. My first career was in accounting, so a migration starts for me where it starts for you: with whether the numbers agree.
I have run HELLO PEOPLE from Perth since 2007. Over 100 projects sit behind it, from accounting migrations and system integrations to custom software for small and medium businesses.
I have a solid accounting and IT background, with over 20 years of business experience covering every process a business runs on: sales, marketing, service delivery, inventory and warehousing, and compliance, across many industries. I hold accounting and IT professional qualifications and an MBA in Oil and Gas, and I am currently reading for a PhD in AI at Curtin University in Western Australia, focused on retrieval-augmented generation (RAG).
Small and boutique. The person who scopes your migration is the person who moves your data, and the same person is there on cutover weekend.
No ticket queue and no account manager in between. You hear back within one business day, usually sooner.
The migration is the start, not the end. When you need the next system, integration or report, you call the same person, who already knows your business.
Ask the author
Ask it here and it comes straight to Kasun, who wrote this. No sales call, no obligation, and a real answer even if the answer is that you do not need us.
Kasun Wijayamanna
Founder, replies within one business day
Tell us what you are comparing, replacing, or trying to improve. We will come back with a practical recommendation and realistic scope.
Built here. Your data stays here.
Thanks for reaching out. We will get back to you within one business day.
See what else we do