Xero and MYOB have carried a huge number of Australian businesses from their first invoice to their first warehouse.
They are very good at what they were built for: bookkeeping, BAS preparation, payroll and a clear view of cash. The trouble starts when a business grows in directions that accounting software was never designed to cover.
If your team spends more time copying numbers between systems than acting on them, you may be closer to an ERP project than you think. This guide looks at the common signs, then walks through what a move to an ERP such as Odoo really involves.
The Warning Signs Worth Paying Attention To
Most owners do not wake up one morning and decide they need an ERP. The pressure builds slowly, usually through workarounds that made sense at the time. A stock spreadsheet here, a job costing app there.
A few patterns tend to show up again and again:
- Stock levels in your accounting file rarely match what is physically in the warehouse.
- You run two or more companies and consolidate them by hand each month.
- Production costs are worked out after the fact instead of being tracked as jobs move through the floor.
- Add-on apps keep multiplying, each with its own subscription and its own version of the truth.
- Month-end close takes days because figures have to be reconciled across several tools.
None of these alone means you must switch. Two or three together usually mean the business is paying a quiet tax in staff hours and double handling.
What Changes When You Move to an ERP
An ERP puts sales, purchasing, inventory, manufacturing and accounting into one database. When a sales order is confirmed, stock is reserved, a purchase or manufacturing order can be triggered, and the accounting entries follow without anyone retyping them.
Odoo appeals to many small and mid-sized firms because it is modular. You can start with inventory, sales and accounting, then add manufacturing, quality or a customer portal later. It has an open-source core, with a paid Enterprise edition that adds more features.
For Australian businesses, the local setup matters as much as the software. One example is WilldooIT, an Odoo partner since 2009 with teams in Sydney and Melbourne, which lists migration from Xero or MYOB as part of its implementation work. The company also says it sets up Single Touch Payroll reporting in its Australian implementations, alongside Odoo’s GST and BAS reporting, which is exactly the part that overseas templates tend to miss.
Moving Your Data Without Losing Your History
Data migration is where good projects are won or lost. The first decision is how much history to bring across. Many businesses move opening balances, current customers, suppliers, products and open orders, then keep the old Xero or MYOB file in read-only mode for reference. Others want several years of transactions so reports compare like with like. More history means more cleaning and more testing.
Cleaning is the unglamorous part. Duplicate customers, inactive products and inconsistent units of measure all need sorting before import, not after. It is also a good moment to tidy your chart of accounts.
Plan for at least one full trial migration. Load the data into a test system, run a handful of real transactions from start to finish, and compare trial balances and stock values against the old system. Fix what breaks, then run the trial again.
Security deserves attention during the move as well. Exports of customer, payroll and supplier data often end up sitting in inboxes or shared drives long after they are needed. The Australian Cyber Security Centre publishes practical advice for small businesses on access control, backups and multi-factor authentication, and those basics apply to every migration file you create.
Inventory, Manufacturing and Multiple Entities
These three areas usually drive the move, so they deserve the most design time.
For inventory, decide early how you will track stock: by warehouse, by bin location, by lot or by serial number. Food distributors often need lot tracking and expiry dates. Equipment sellers may need serial numbers for warranty claims. Changing this after go-live is painful, so settle it during scoping.
Manufacturing brings bills of materials, work centres and routings into the picture. Start with accurate bills of materials for your best sellers rather than trying to model every product on day one. Once those are reliable, the system can calculate material needs and the real production cost of each job.
Multi-entity setups are where spreadsheets usually break down first. Odoo can run several companies in one database, each with its own ledger, and handle transactions between them. Joolca, a family-owned Australian engineering and design company, has said in a published testimonial that its project delivered a true multi-company, multi-location setup within a single Odoo instance.
Getting the Timing Right
An ERP project takes real effort from your own people, not just from the implementer. Try to avoid going live during your peak season or in the weeks before the end of the financial year. A quieter period gives staff time to learn the new screens and lets you run the old and new systems side by side for a short while if needed.
Set aside a realistic budget for training and for the first few months of support. Most frustration after go-live comes from small process gaps rather than software faults, and those settle quickly when someone local can answer questions in your time zone.
If the warning signs above sound familiar, start by mapping your current processes and writing down every workaround your team relies on. That list becomes the brief for any ERP conversation, and it will tell you fairly quickly whether you need a full system or simply better use of the tools you already have.

