Outgrowing MYOB or Xero: Moving to Business Central, NetSuite or Odoo

Signs you have outgrown MYOB or Xero, how Business Central, NetSuite and Odoo differ, and where an ERP move gets complicated: entities, stock, GST, payroll.

Best for: Business owners, finance managers, financial controllers Written by the founder, an accountant first, who has moved Australian businesses between accounting systems since 2007.

Who this is for

Owners and finance managers of growing Australian businesses on MYOB or Xero who are considering Microsoft Dynamics 365 Business Central, Oracle NetSuite or Odoo.

Question this answers

When is it time to leave MYOB or Xero for an ERP, and where does that move usually go wrong?

What you'll leave with

  • The signs that a business has outgrown MYOB or Xero
  • How Business Central, NetSuite and Odoo differ, in plain terms
  • Why the chart of accounts has to be redesigned, not copied
  • What changes for entities, stock, GST, payroll and connected apps

The short answer

Moving from MYOB or Xero to an ERP (enterprise resource planning system, one system that runs accounting, stock, purchasing and operations together) is a redesign, not a copy. You choose the conversion date, redesign the chart of accounts and the way you report, set up each entity, decide how much history to bring, bring across balances, open items and stock, then check the ERP against MYOB or Xero before you switch.

The data itself is rarely the hard part. The hard part is the decisions: how the accounts and reporting dimensions are laid out, how entities trade with each other, how stock is costed, how GST lands on the BAS, and what happens to payroll and every app that used to connect to MYOB or Xero. This guide walks through each so you know what to ask before you sign anything.

Signs you have outgrown MYOB or Xero

MYOB and Xero are very good at what they are built for. A business outgrows them when the work around them starts to cost more than the systems themselves. These are the signs we see most.

  • Several entities and a consolidation spreadsheet. A trading company, a property trust and maybe an overseas subsidiary, each in its own file. Every month somebody exports the numbers and builds group reports by hand, and intercompany loans never quite agree.
  • Stock in more than one place. Warehouses, vans, branches or consignment stock, with transfers between them tracked outside the accounting system.
  • Manufacturing or assembly. Bills of materials, work in progress and labour costs that the accounting system cannot hold, so the cost of goods sold is an estimate.
  • Approvals by email. Purchase orders, bills and expenses approved by somebody replying to an email, with no record in the system of who approved what.
  • Too many connected apps. Inventory in one app, job costing in another, approvals in a third, reporting in a fourth. Each sync is a place where data goes missing or doubles up.
  • Reporting that needs more than two tracking categories. You want to report by branch, by product line, by project and by salesperson at once, and Xero allows two active tracking categories.

One of these on its own can often be solved with an app. When three or four turn up together, the business is usually ready for an ERP.

Business Central, NetSuite and Odoo in plain terms

These are the three ERPs Australian businesses leaving MYOB or Xero most often consider. All three can run accounting, stock, purchasing and sales in one place, and all three have an Australian setup with GST and BAS reporting. They differ mainly in how they are sold, how they are hosted and how they handle groups of companies.

How the three ERPs differ

Criterion Business Central NetSuite Odoo
Who makes it Microsoft (Dynamics 365 Business Central) Oracle Odoo, a Belgian software company
How it is usually bought Through a Microsoft partner, who also sets it up From Oracle NetSuite or a NetSuite partner From Odoo or an Odoo partner
Feels familiar to Teams already working in Microsoft 365 and Excel Groups with several entities, including overseas Businesses that want to add modules one at a time
Reporting splits Dimensions (two global, more as shortcut dimensions) Department, class, location and custom segments Analytic accounts and analytic plans
Several entities Several companies, with intercompany and consolidation features Subsidiaries in the OneWorld edition, with consolidation and eliminations Several companies, with intercompany rules and consolidation
Australian payroll Not included as standard. A separate payroll product is usual Built-in payroll is for the United States. A separate product is usual Has an Australian payroll module. Check it fits your awards

Features and editions change with each release. Confirm the current position with the vendor or partner for your own requirements before choosing.

None of them is the right answer for every business. The better question is which one fits your entities, your stock and your processes, and who will support you after go live. A strong local partner often matters more than the brand.

Six decisions to make before anything moves

  1. The conversion date. The start of a financial year is cleanest. The start of a BAS quarter is the next best. Mid-quarter works, but the first BAS then comes from two systems.
  2. The entity structure. Which companies, trusts and partnerships go into the ERP, and which, if any, stay where they are.
  3. The chart of accounts and the reporting dimensions. What the accounts are, and what moves out of the accounts into dimensions or segments.
  4. How much history. Opening balances only, balances plus open items, monthly totals for comparison, or full transactions.
  5. The stock costing method. How each type of stock will be valued in the ERP, and whether that matches what MYOB or Xero and your inventory app did.
  6. What happens to payroll and the connected apps. Which stay, which are replaced by the ERP, and how each one will connect.

The migration steps, in order

An ERP project has more moving parts than a move between two small business systems, but the data migration inside it follows the same broad path.

  1. Review what you have. Every MYOB or Xero file, every entity, the tracking categories and jobs in use, the tax codes, the stock, and every app that sends data in or takes it out.
  2. Tidy the source files up to the conversion date. Reconcile every bank and card account, clear invoices and bills that are not really owed, and agree intercompany balances between entities.
  3. Design the ERP chart of accounts and dimensions. Map every MYOB or Xero account and tracking category to its new home.
  4. Set up tax. Each old tax code mapped to an ERP tax setting that reports to the same BAS labels.
  5. Prepare the master data. Customers, suppliers, items, locations and price lists, deduplicated and on one consistent list.
  6. Bring across balances, open items and stock. Opening balances per entity, open invoices and bills, stock quantities and values per location, and any history you chose to keep.
  7. Reconcile the ERP to MYOB or Xero. Trial balance per entity, aged receivables and payables, bank balances, stock value against the balance sheet, and GST for the same period.
  8. Test with real work. Run a sample of real orders, bills, receipts and stock movements through the ERP before go live.
  9. Cut over at the period end, then close the first month in the ERP. Treat the first month end and the first BAS as part of the project.

Where it gets complicated: redesigning the chart of accounts

In MYOB and Xero, many businesses report by creating more accounts. Sales Perth, Sales Sydney, Sales Online. Wages Perth, Wages Sydney. Over the years the chart of accounts grows to hundreds of lines because it is doing two jobs: holding the accounts and holding the reporting splits.

An ERP separates those jobs. The chart of accounts holds what the money is, such as sales, wages or rent. Dimensions in Business Central, segments such as department, class and location in NetSuite, and analytic accounts in Odoo hold where it belongs, such as branch, product line or project. One Sales account tagged by branch replaces three Sales accounts.

  • Tracking categories become dimensions or segments. Xero tracking categories and MYOB categories and jobs each need a decision: become a dimension, become a project, or be retired.
  • Split accounts have to be folded together. Sales Perth and Sales Sydney become one account with a branch tag, and the opening balances and any history have to be tagged the same way.
  • Every entity should share one chart. Group reporting is far simpler when each entity uses the same accounts. Entities that drifted apart in MYOB or Xero have to be brought onto one list.
  • Required tags have to be decided. If every expense must carry a branch, the ERP can enforce it, but history brought across without a branch will then fail or sit in a blank bucket.

Here is what getting it wrong looks like. A business copies its Xero chart of accounts into the ERP as it is, with all the branch accounts, and also sets up a branch dimension. Six months in, half the team codes sales to Sales Perth and the other half codes them to Sales with the Perth tag. The branch report now shows Perth at half its real size, and the board pack has to be rebuilt by hand, which is exactly what the ERP was meant to stop.

Where it gets complicated: several entities and intercompany

Many businesses move to an ERP because they run several entities. All three ERPs can hold several companies and produce group reports, but the setup decides whether that works.

  • Each entity keeps its own ABN and its own BAS. Group reporting in the ERP does not merge the GST of separate entities. Each one still lodges as it does now, unless the group is registered for GST as a GST group.
  • Intercompany balances must agree before the move. A loan of one amount in the company and a different amount in the trust will not eliminate in consolidation. Agree every intercompany balance at the conversion date first.
  • Intercompany trading needs rules. When one entity sells to another, the ERP can create the matching bill on the other side, but the accounts, tax treatment and pricing for that have to be decided.
  • Overseas entities add currency. A New Zealand or Singapore subsidiary reports in its own currency and is translated for group reports. The exchange rate approach has to be agreed with your accountant.

Where it gets complicated: opening balances and how much history

An ERP is stricter than MYOB or Xero. Every transaction usually carries more required information, such as dimensions, locations and posting rules, so history brought across has to carry it too.

For that reason, most businesses bring less detail than they expect: opening balances at the conversion date, every open invoice and bill, and monthly totals for the last one or two years so reports can compare this year with last. The detailed transactions stay in MYOB or Xero, kept read only for the records and for the auditor. If you do want full transaction history, every year brought across must reconcile, entity by entity, and the effort grows quickly.

Where it gets complicated: inventory and costing methods

Stock is often the reason for the move, and it is where the numbers most often fail to agree on day one.

  • Costing methods differ. Business Central offers FIFO (first in, first out), LIFO, average, standard and specific costing. Odoo offers standard, average and FIFO, set by product category. NetSuite has its own set of costing methods. MYOB and many Xero inventory apps use average cost. Changing method changes the value of the same stock.
  • Stock has to be counted into each location. Quantities by warehouse, van or branch, with values that add up to the stock figure on the balance sheet at the conversion date.
  • Units of measure and item codes need tidying. The same item bought by the carton and sold by the unit, or listed twice under slightly different codes, has to be sorted out before it reaches the ERP.
  • Manufacturing adds bills of materials and work in progress. Half-finished jobs at the conversion date need a decision: finish them in the old system, or bring them across with their costs so far.

Where it gets complicated: GST and BAS in the new system

All three ERPs can report GST for an Australian BAS. Business Central has an Australian version with GST posting setup and BAS reporting. NetSuite provides Australian tax reporting, including the BAS, through its Australia and New Zealand localisation. Odoo has an Australian localisation with a BAS report and GST rates mapped to the BAS labels.

The catch is that the tax setup is new. In MYOB or Xero you picked a tax code on each line. In an ERP, GST often comes from a combination of settings on the customer or supplier, the item and the account. A wrong combination raises no error. It quietly sends a sale to the wrong BAS label, every period.

  • Standard treatments. Taxable sales, GST-free sales, exports (G2), capital purchases (G10) and input-taxed items each have to land on the same labels as before.
  • Special codes. Custom codes from MYOB or Xero, and industry taxes such as Wine Equalisation Tax, luxury car tax or fuel tax credits, need their own decision in the ERP.
  • GST groups and branches. If your entities are a GST group or report GST by branch, the ERP has to be set up to report the same way.

Where it gets complicated: payroll usually stays separate

MYOB and Xero both run Australian payroll. Many businesses assume the ERP will too. Often it does not.

Business Central does not include Australian payroll as standard, and the payroll built into NetSuite is for the United States. Australian businesses on either one usually keep a separate payroll product, then post each pay run into the ERP as a journal. Odoo has an Australian payroll module, which Odoo says supports Single Touch Payroll Phase 2 from version 19, but test it against your awards, allowances and leave rules before relying on it.

If payroll stays separate, decide how wages, PAYG withholding, super and leave land in the ERP, including which dimensions each pay line carries. If payroll is moving too, the safest time is 1 July, so year to date figures do not have to be carried across mid-year.

Where it gets complicated: integrations to rebuild

Every app that talked to MYOB or Xero stops when you leave. Point of sale, ecommerce, job management, expense tools, payment gateways, bank feeds, and the reporting tools that read your data. Some will connect to the ERP, some will be replaced by it, and some will need a custom integration.

List every connection before the project starts, not in the last week. For each one decide whether it stays, goes, or is replaced, and when it switches over. Switch them all at the conversion date so nothing is posted twice or missed.

Implementation partner and data migration are two jobs

An ERP is usually set up by an implementation partner, who designs the processes, configures the system and trains your team. Moving the data from MYOB or Xero is a separate job, and partners vary in how much of it they take on.

Some partners handle the migration fully. Others set up the ERP and expect you to hand over clean, mapped data in their templates. Before you sign, ask who maps the chart of accounts, who cleans the master data, who brings across the stock and history, and who proves the trial balance agrees. If nobody owns the reconciliation, it tends to land on the finance manager in the week before go live.

Parallel running and cutover at a period end

Cut over at the end of a period, ideally a financial year or a BAS quarter. The old system closes cleanly on that date, the ERP starts fresh the next day, and each BAS comes from one system.

Some businesses run both systems side by side for a month to compare the results. It gives confidence, but it doubles the data entry, so keep it short and decide in advance what has to match for you to stop. Once you switch, lock MYOB or Xero as at the conversion date and keep it read only for the records.

Signs your move to an ERP needs a careful migration plan

  • You run more than one entity

    Intercompany balances, one shared chart of accounts and group reporting all need decisions.

  • Your chart of accounts holds your reporting splits

    Branch or product accounts have to become dimensions or segments, history included.

  • You carry stock in several places

    Quantities and values per location must agree with the balance sheet on day one.

  • You manufacture or assemble

    Bills of materials, work in progress and costing methods all change.

  • You expect payroll to move into the ERP

    Check first. Australian payroll often stays in a separate product.

  • Many apps connect to MYOB or Xero today

    Every one has to be kept, replaced or rebuilt, and switched on the same date.

  • Nobody has been named to prove the numbers agree

    The reconciliation needs an owner before the project starts.

If any of these apply, our migration services cover the planning and the data move at a fixed price, quoted before work starts: MYOB to Business Central, MYOB to NetSuite, MYOB to Odoo, Xero to Business Central, Xero to NetSuite and Xero to Odoo. We work alongside your implementation partner, or on our own, for businesses across Australia, from Perth to Sydney, Melbourne, Brisbane and Adelaide. See all our migration services.

Questions about moving from MYOB or Xero to an ERP

How do I know we have outgrown MYOB or Xero?

The usual signs are several companies or trusts that need one set of group reports, stock held in more than one place, manufacturing or assembly, approvals that happen by email, and a long list of apps joined to the accounting system to fill the gaps. One sign on its own can often be solved with an app. Three or four together usually means the business needs an ERP, which stands for enterprise resource planning: one system that runs accounting, stock, purchasing and operations together.

Which is better for an Australian business: Business Central, NetSuite or Odoo?

None of them is better for every business. Business Central suits businesses already working in Microsoft 365 and is sold and supported through Microsoft partners. NetSuite is cloud only and is strong for groups with several entities, including overseas ones. Odoo is modular, so you add the apps you need, and it can be run in the cloud or hosted yourself. All three have Australian GST and BAS reporting. The right answer depends on your entities, your stock, your processes and who will support you after go live.

Can our payroll move into the ERP too?

Not always. Business Central does not include Australian payroll as standard, and the payroll built into NetSuite is for the United States, so Australian businesses on either one usually keep a separate payroll product and post the pay runs into the ERP. Odoo has an Australian payroll module that it says supports Single Touch Payroll Phase 2 from version 19, but check it against your awards and allowances before deciding. Many businesses keep their current payroll and change it at a later 1 July.

How much history should we bring into the ERP?

Less than most people expect. Many businesses bring opening balances at the conversion date, the open invoices and bills, and monthly totals for the last one or two years so reports can compare this year with last. Detailed transactions often stay in MYOB or Xero, kept read only for the records. Every extra year brought across has to reconcile in the new system, and an ERP is stricter about that than MYOB or Xero.

How long does a move from MYOB or Xero to an ERP take?

Longer than a move between two small business systems, because the ERP is being set up for the first time as well as receiving data. A single entity with simple stock might take a few months from the first decisions to the first month closed. A group with several entities, manufacturing or many integrations takes longer. The data migration is usually a smaller part of that time than the design decisions and the testing.

Our implementation partner says they will move the data. Do we need anyone else?

Sometimes not. Some partners are strong at data migration, and others focus on setting up the ERP and expect you to supply clean, mapped data. Ask your partner exactly what they will bring across, how they will prove it reconciles to MYOB or Xero, and who fixes it if the trial balance does not agree. If the answers are vague, it is worth having the migration handled separately.

Do you only help Perth businesses move to an ERP?

No. We are based in Perth and work with businesses in Sydney, Melbourne, Brisbane, Adelaide, Canberra, Hobart, Darwin and regional Australia. The work is done remotely, by our own team in Australia.

Key takeaways

  • Moving to an ERP is a redesign, not a copy. The chart of accounts, the entities and the stock all need decisions before any data moves.
  • Tracking categories in MYOB or Xero usually become dimensions or segments in the ERP. Getting that design right decides how useful every report will be.
  • All three ERPs have Australian GST and BAS reporting, but the tax setup is new and must be proven against your last lodged BAS.
  • Australian payroll often stays in a separate product. Plan the link from payroll to the ERP rather than assuming it will move.
  • Cut over at a period end, ideally a financial year or quarter, and check the ERP against MYOB or Xero before you switch.
MYOBXeroBusiness CentralNetSuiteOdooERPMigrationGST

Meet the person

Written by the person who does the work

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).

  • An old-fashioned service

    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.

  • Quick responses

    No ticket queue and no account manager in between. You hear back within one business day, usually sooner.

  • A long-term partner

    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

Question about moving from MYOB or Xero to an ERP?

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 Kasun Wijayamanna
Founder, replies within one business day

Get Started

Want help choosing the right next step?

Tell us what you are comparing, replacing, or trying to improve. We will come back with a practical recommendation and realistic scope.

Australian owned and operated

Built here. Your data stays here.

  • No offshore development. Everything is written by our own team in Australia. Nothing is subcontracted overseas.
  • Your data stays onshore. Hosted in Australia, on infrastructure you own, under Australian law.
  • Every state, not just ours. Perth, Melbourne, Sydney, Brisbane, Adelaide and everywhere between.