Migrating to Xero is not a software install. It is a financial-data migration that touches your chart of accounts, opening balances, payroll history, GST treatment and bank reconciliation. Done badly, it leaves a year-end mess that takes months to undo and a first-BAS-after-cutover that lands with errors the ATO eventually finds.
The cleanest path is staged: cutover at a logical date (BAS quarter-end or financial year-end), with a defined parallel-run period and a close-out checklist. This article walks through the week-by-week timeline we use with clients moving from MYOB, QuickBooks Desktop, Reckon or spreadsheet bookkeeping.
Pick the cutover date — and respect the consequences
Three options, in order of preference:
- 1 July (start of financial year). The cleanest break. Annual return, fringe benefits year, depreciation pools and most balance-sheet substantiation align with the cutover. Recommended for any business that can plan ahead.
- 1 January (start of calendar year). A natural break for businesses with a strong end-of-year activity pause. Mid-financial-year cutovers mean STP YTD figures need to migrate carefully, and the cutover BAS quarter (Oct–Dec) needs special treatment.
- 1st of a BAS quarter (1 Oct, 1 Apr). Acceptable. Easier than mid-quarter cutover because the prior period closes cleanly under the old system and the new period opens cleanly in Xero.
Avoid mid-quarter or mid-month cutovers if at all possible. Splitting a BAS period across two systems is the single most common source of post-migration errors.
The staged migration — what happens, in order
Step 1: Build the chart of accounts in Xero
Map each old account to its new home. Resist the temptation to add 200 new accounts — Xero's reporting works better with fewer, better-named ones. A typical SME chart of accounts has 50–80 active accounts; 200+ is a sign that accounts were created for one-off transactions and never retired.
Use the migration as the opportunity to clean up:
- Merge near-duplicate accounts (you don't need separate accounts for “Office supplies” and “Stationery”).
- Archive accounts that haven't been used in 12+ months.
- Standardise the account naming convention so reports read cleanly.
- Decide on cost-of-goods-sold vs operating-expense classifications. Inconsistent COGS allocations are the most common cause of incorrect gross margin reporting.
Step 2: Migrate opening balances
Trial balance as at the cutover date, including:
- Bank accounts — the closing balance from the old system, ready to reconcile against the first feed in Xero.
- Accounts receivable — open customer invoices migrated as individual transactions (not lump sums), with original invoice dates so aging works correctly.
- Accounts payable — open supplier bills migrated similarly.
- GST control account — the balance carried over from the last BAS lodged on the old system.
- Payroll liabilities — accrued super, PAYG withheld, leave provisions. These are the most commonly missed items in MYOB → Xero migrations.
- Fixed assets and accumulated depreciation — asset register with original cost, depreciation method, accumulated depreciation, and remaining effective life.
- Director loan accounts and equity items — capital contributions, retained earnings carried forward, current-year movement.
Step 3: Connect bank feeds and verify the opening balance
Connect every bank account, credit card, and loan account to its Xero feed. Verify that:
- The first feed arrives correctly (test with a small recent transaction).
- The opening balance in Xero matches the closing balance on the day before the cutover.
- No transactions are missing in the gap between when the feed was set up and the cutover date.
This is where most migrations stumble. A 1 July cutover with a feed connected on 28 June can miss the 29 and 30 June transactions if the feed isn't set to backfill correctly.
Step 4: Set up payroll
Employee details, leave balances, YTD figures (for mid-year cutovers), super fund details, STP2 enabled. From 1 July 2026, Xero's Payday Super workflow needs to be configured before the first pay run.
Test pay run before going live: run a parallel pay for one employee on both old and new systems, compare the outputs, and verify that net pay, PAYG withheld, super amount and STP report match to the cent.
Once Payday Super is live, our Payday Super impact calculator can help you re-model the cash flow timing — particularly important if you're moving from MYOB's quarterly super workflow to per-payday.
Step 5: Parallel run for 1–2 pay cycles
Run both old and new systems in parallel for at least one full BAS period (or one full pay cycle for payroll-heavy businesses). Compare outputs. The new system is only ready to take over when reports tie out exactly.
What to compare:
- P&L for the parallel period — every line item should match within rounding.
- Balance Sheet at the parallel period's end — bank balances, AR, AP, GST control, payroll liabilities.
- BAS calculation — net GST, PAYG withheld, PAYG instalment.
- Aged debtors and creditors reports.
Step 6: Close out the old system
Final BAS lodged from the old system. Final reports exported and archived. Subscription downgraded to the cheapest read-only tier and retained for the ATO's 5-year record-keeping requirement (or longer for payroll records).
Do not cancel the old subscription too early. You may need to re-open old data for an ATO query, an audit, or a missed reconciliation. Xero, MYOB and QuickBooks all revoke access to old data once the subscription lapses; restoration is expensive (or impossible) once that happens.
The seven things that go wrong
- Opening balances don't tie to the trial balance from the old system.Usually a missed account or a misclassified balance. The reconciliation between old and new is non-negotiable — you can't produce accurate reports from inaccurate openings.
- GST control account migrated to the wrong tax rate. Xero distinguishes between “GST on Income” and “GST on Expenses” control accounts; MYOB uses a single GST account. The mapping needs explicit attention.
- Bank feed missing transactions for the cutover period. Most common when the cutover date is more than a few days before the feed setup date. Always check transaction-by-transaction for the first week.
- Employee leave balances not migrated correctly. Annual leave, personal leave, long service leave all need to migrate at the right accrual rate. Get this wrong and an employee's final pay calculation is wrong.
- Year-to-date payroll figures missing for mid-year cutovers. If you cutover on 1 January, the YTD figures for the half-year already lodged via STP need to be migrated so the EOFY STP finalisation works correctly. Otherwise, every employee's payment summary is wrong.
- Old recurring transactions still firing in the legacy system. Direct debits, scheduled invoices, automatic bank transfers — all need to be migrated or cancelled before the old system is dormant.
- Subscription cancelled too early. You can't re-open old data after Xero starts billing (or after MYOB's lockout period). Keep the old subscription on the cheapest tier for at least 2 years after cutover.
The week-by-week timeline
- Week −8 — confirm cutover date, sign up to Xero, set up the company profile.
- Week −6 — build chart of accounts in Xero. Sample mapping done by hand for the most-used accounts.
- Week −4 — connect bank feeds (early — they take time to authenticate and stabilise). Configure GST rates, payment methods, tracking categories.
- Week −3 — set up payroll. Employee details, super funds, leave balances, STP2 enabled.
- Week −2 — migrate fixed asset register, contacts (customers + suppliers), recurring transactions. Run first test pay.
- Week −1 — final opening balance reconciliation. Sign off the trial balance match. Brief the team.
- Week 0 (cutover) — first transactions go in Xero. First pay run in Xero. Parallel run for first BAS quarter.
- Week +4 — verify first BAS prepared in Xero matches what the old system would have produced. Lodge if it ties out.
- Week +12 — close-out: final exports from old system, archive, downgrade subscription.
What we deliver on a Xero migration
Justyna is a Xero Certified Partner (and MYOB Partner, QuickBooks ProAdvisor) — Torch Corporate runs migrations for clients moving from MYOB, QuickBooks Desktop, Reckon and spreadsheet bookkeeping. The first conversation is always about whether the cutover date you've picked is the right one.
A typical engagement covers:
- Pre-migration assessment of the existing data quality (the cleaner the source, the smoother the migration).
- Chart of accounts design and approval.
- Opening balance migration with a reconciliation to the source trial balance.
- Bank feed setup and verification.
- Payroll setup, including Payday Super readiness from 1 July 2026.
- Parallel-run reconciliation for the first BAS period.
- First BAS lodged from Xero.
- Old system close-out and archive.
Where to start
If you're considering a migration, the discovery call is the right place. We'll walk through your current setup, identify the cutover date that minimises risk, and scope the migration before you commit to a Xero subscription you might not need yet (or might need urgently).
References: Xero migration guides (Xero Certified Partner training), ATO record-keeping requirements (5 years for tax records, 7 years for super), STP Phase 2 documentation. The 1 July 2026 Payday Super reform requires Payday Super-ready payroll configuration in Xero — see our Payday Superarticle for the broader reform context.
This information is general in nature and does not constitute personal financial or tax advice. Please contact us to discuss your individual circumstances. Tax laws are subject to change; information on this page reflects legislation in effect as of May 2026.