When you buy a business or set up a new company or site, don't start by moving everything onto your systems. Start by getting consolidated numbers your board, bank and leadership team can trust, then make the bigger decisions in order: whether the new entity keeps its own accounting file, how its chart of accounts maps to yours, which job, stock and payroll systems win, and what should be migrated now versus simply connected. Rushing a full migration in the first few months is how acquisitions end up with broken reporting, unhappy staff and a year of spreadsheets.
What it looks like the month after the deal
The paperwork is signed and the new business is yours. Then the questions start:
- Two sets of books. You run Xero, they run MYOB, or both run Xero with completely different account codes. Nobody can produce a group profit and loss without a long night in Excel.
- Two of everything operational. Two job, stock, payroll and CRM systems. The same customer exists in both with different names, terms and price lists.
- Intercompany charges in spreadsheets. Shared staff, management fees, stock moved between sites, and loans from the parent company are all tracked in a workbook that one person understands.
- Someone wants group numbers now. The bank wants covenant reporting, the board wants a consolidated view, and the owner wants to know whether the acquisition is performing as expected.
- Staff in the new business are nervous. They know their systems well and are waiting to hear what will change.
None of this means the deal was a mistake. It's what happens when two businesses that grew separately suddenly need to report as one.
Why this is a problem between systems, not inside one
It's tempting to think the answer is to pick one product and put everyone on it. Sometimes that's where you end up, but it's rarely where you should start. The real problems sit between the two businesses:
- The two charts of accounts don't line up, so numbers can't be added together.
- The same customer, supplier or product has different codes in each system.
- Money and stock move between the entities, and both sides need to record it the same way.
- Processes differ: how jobs are quoted, how stock is received, how timesheets are approved, who signs off what.
No single accounting or ERP product fixes those on its own. Someone has to decide how the two businesses map to each other, and that work comes first whether you later migrate, connect or consolidate. If you're not sure yet where the gaps are, our page on disconnected business systems is a good primer.
The decisions, in the order to make them
1. Get consolidated reporting working first
Before changing any system, give leadership one view of the group. Each entity keeps its current accounting file. A reporting layer pulls the data from each file, maps the accounts to one group structure, removes the intercompany transactions and shows a consolidated profit and loss, balance sheet and cash position.
This buys you time. The board and bank get their numbers, and you can make the bigger system decisions with real data instead of under pressure. We cover how this is built in multi-entity reporting with Xero or MYOB.
2. Decide: separate accounting files or one merged file
This is usually a legal and tax question before it's a systems question, so involve your accountant.
- Keep separate files if the new business remains its own company, has its own ABN and GST registration, or might be sold or restructured later. Most acquisitions start here.
- Merge into one file if the acquired business has been absorbed into an existing company (for example, you bought the assets and the trading now happens under your company). Then its history usually stays in its old file, and new transactions go into yours from an agreed date.
Separate files are not a failure to integrate. With good mapping and intercompany accounts, they report as one group perfectly well.
3. Map the chart of accounts
Each entity's accounts need to roll up to one group reporting structure. You don't have to rename every account in the acquired business's file on day one. A mapping table can say that their "Motor vehicle expenses" and your "Vehicle running costs" both report as one line.
If you plan to merge files or move to a multi-entity system later, align the charts properly at a clean point such as the start of a financial year, and agree it with your accountant.
4. Set up intercompany properly
Use dedicated intercompany accounts in each file: one for amounts owed to each related entity, one for amounts owed by them, and separate accounts for management fees and recharges. Agree how each type of charge is raised, who raises it and when. Once both sides are coded the same way, the reporting layer can eliminate them automatically and flag any where the two sides disagree. Our Xero and MYOB multi-entity and intercompany work covers this in detail.
5. Decide which operational systems win
Staff care about this decision most. For job management, stock, payroll and CRM, ask:
- Which system handles the combined volume and the way the group wants to work?
- Which one would be hardest to leave (contracts, integrations, history, staff skill)?
- Do the two businesses actually work the same way, or are the differences real?
Sometimes the answer is that the acquired business's system is better, and you move onto theirs. Sometimes the businesses are different enough that two systems is the right answer for now, as long as they are connected and report the same way. Write down the processes in both businesses before deciding. If that hasn't been done, business process mapping is the place to start.
6. Decide what to migrate and what to connect
For each system, there are three realistic options:
- Migrate now. Move the data across and switch off the old system. Best when the old system is near its end of life, licences are expensive, or running both is creating daily double handling.
- Connect for now, migrate later. Leave both running and integrate them, so customers, stock or jobs flow between them and reporting is consistent. Best when the business is busy, the old system works and the team needs time.
- Leave separate. A specialist system used only by the acquired business may be fine, as long as its figures reach group reporting.
Payroll is often the one to plan most carefully. Year-to-date figures, leave balances, super and Single Touch Payroll reporting all have to be right on the switchover date. Choose a clean cut-over point such as a new financial year where you can.
Accounting migrations bring opening balances, open invoices and history; our accounting data migration service covers the detail.
When a built-in feature or an off-the-shelf tool is enough
Not every acquisition needs a custom project. Be honest about the size of the problem:
- A marketplace consolidation app may be enough if both entities are on Xero or both on MYOB, your intercompany arrangements are simple and you only need monthly finance reporting. Tools such as Fathom, Spotlight Reporting or Joiin connect to several files and produce consolidated statements for a monthly subscription.
- A multi-entity system may be the long-term answer if the companies share stock, staff and customers so heavily that separate files create daily double handling. Products such as MYOB Advanced or NetSuite handle several entities and intercompany transactions in one system. That's a bigger project and is covered on our multi-entity ERP consolidation page.
A custom reporting layer or integration makes sense when you have a mix of systems (Xero in one entity, MYOB in another, different job or stock systems), when you need operational figures alongside the finance numbers, or when the intercompany flows are more complicated than an off-the-shelf tool can handle.
A sensible first ninety days
For example, a practical sequence after an acquisition might be:
- Agree the file structure with your accountant and set up intercompany accounts.
- Map both charts of accounts and get a consolidated report running.
- Document the key processes and list every system in both businesses, who uses it and when its contract renews.
- Make the "which system wins" decisions with the people who use them, then plan moves around clean cut-over dates, not the deal date.
If you want an independent view before committing, our $5,000 Process & Systems Audit is a paid diagnostic. It maps the processes and systems across both businesses and gives you a written report on the options. For the wider picture on moving and connecting accounting systems, see our Xero and MYOB integration and migration guide.
Frequently asked questions
Should an acquired business keep its own Xero or MYOB file?
Usually yes, at least to begin with, if it remains a separate company with its own ABN. Separate files keep the legal and tax picture clean, and a reporting layer can still show the group as one. Your accountant should confirm the right structure.
Can we consolidate a Xero entity and a MYOB entity?
Yes. Both have APIs, so data from each file can be pulled into one reporting database and mapped to a group chart of accounts. It doesn't matter which accounting system each entity uses.
How soon should we move the acquired business onto our systems?
There's no fixed answer, but rushing is the most common mistake. Get consolidated reporting working first, then plan each system move around a clean cut-over date and the team's capacity. Some systems may never need to move.
What about payroll and staff entitlements?
Plan payroll carefully and get advice on employment and entitlement obligations. Leave balances, year-to-date figures, super and Single Touch Payroll reporting must carry across correctly. A new financial year is often the cleanest switchover point.
What will it cost to integrate an acquired business?
Costs vary widely depending on the size of the business, how many systems are involved and how much needs to be custom-built, so we scope every project first and give you a fixed quote after a free initial chat.
If you've just bought a business or set up a new entity and the numbers are living in spreadsheets, book a free initial chat. Tell us what both businesses run on, and we'll help you work out what to do first.