A spreadsheet to Xero restaurant migration goes wrong when it’s treated as a data-copying exercise. It’s really a chart-of-accounts design exercise with a cut-off date. Plan the structure, migrate opening balances only, rebuild the monthly rhythm from day one.

When spreadsheets stop working

Most hospitality businesses start on spreadsheets. For a single-location cafe pulling AED 30-60k or AUD 25-50k per month in revenue, spreadsheets are genuinely fine. Volume is low, channels are few, one operator can keep the whole picture in their head.

Somewhere between outlet #2 and the first delivery platform, spreadsheets stop working. Not with a bang. With a slow increase in the time it takes to answer simple questions, and a growing feeling that the numbers aren’t quite right anymore.

We’ve onboarded enough spreadsheet-to-cloud migrations to have an unpopular opinion: most operators wait six months too long to migrate. The transition gets harder, not easier, the longer spreadsheets stay authoritative. By the time you’re Googling “excel to quickbooks cafe” or “spreadsheet to xero restaurant,” the migration has usually been needed for months.

This guide is the migration playbook: how to plan the move, what to migrate, what to leave behind, and the first-month rhythm that prevents the new software from ending up as a more expensive spreadsheet.

Before you pick the software

Do not start the migration by picking the software. That’s backwards. The platform decision matters, but it sits behind two more important decisions:

  1. Chart of accounts design. What structure actually fits the business today and the business it’s becoming?
  2. Cut-off date. When does the old spreadsheet stop being the source of truth and the new software start?

With those two locked, the platform question is easier. Xero, QuickBooks, Zoho, or MYOB, picked for fit with the geography, the POS, and the bookkeeper. See Xero vs QuickBooks for restaurants for how to pick between the two dominant options.

Step 1: decide what the new structure should actually look like

This is where most restaurant bookkeeping migration efforts quietly go wrong. The chart of accounts from the spreadsheet gets copy-pasted into the new software, and all the limitations of the old structure come with it.

Before touching any accounting software, design the chart of accounts the business needs going forward. For hospitality, that means:

  • Revenue split by channel. Not a single “Sales” line. Dine-in, takeaway, each delivery platform, catering, retail all separated.
  • COGS split food / beverage / packaging. So food cost % and beverage cost % are separately visible.
  • Labour split BOH / FOH / management. And gratuity / long service leave as an accrual, not a when-paid expense.
  • Platform commission as its own section. So contribution margin per platform is calculable.
  • Clearing accounts per platform. Talabat receivable, Deliveroo receivable, each as a separate asset.
  • Location tagging if multi-outlet. Either sub-accounts or tracking categories.

Full walkthrough: Restaurant chart of accounts: a practical starting point.

This is the single highest-impact step in any migration. The COA is the lens; everything else is just data flowing through it.

Step 2: pick the cut-off date

The cut-off is the line where the spreadsheet stops being authoritative and the new software starts. Two options work, a third usually doesn’t:

  • Start of a new financial year. Cleanest cut-off. The prior year stays in the spreadsheet as historical reference; new year starts in the new software. Tax filings tie back to whichever source covered which period.
  • Start of a new VAT / GST period (quarterly). Second cleanest. Current period goes in the new software; prior period stays in the spreadsheet. The new software’s first filing is an easy mechanical sum.
  • Mid-period (e.g. 15 April). Don’t do this. The current period ends up split across two sources and the filing becomes an archaeological exercise.

For most operators, aligning the cut-off to the financial year-end is worth waiting for even if it means 2-3 months of spreadsheet patience. The cleanup effort saved is significant.

Step 3: migrate opening balances, not historical transactions

The biggest upgrade bookkeeping software hospitality migration mistake: trying to bring every historical transaction into the new software “for completeness.”

Don’t. The opening balances are what the new software actually needs:

  • Bank balances at the cut-off date
  • Accounts receivable balances per customer (usually light in cash-heavy hospitality)
  • Accounts payable balances per supplier
  • Inventory value at cut-off
  • Fixed assets on the balance sheet with accumulated depreciation
  • Loan balances with current principal
  • Accrued liabilities (gratuity, long service leave, unpaid bonuses)
  • Equity / retained earnings as the plug

That’s usually fifteen to thirty numbers. They get entered as the opening balance journal in the new software on the cut-off date.

What you don’t migrate:

  • Individual transactions from before the cut-off
  • Historical P&L month-by-month (the totals exist in the spreadsheet; they don’t need to live in the software)
  • Every supplier invoice you’ve ever entered
  • Historical payroll detail

The temptation to migrate everything is emotional (“I want it to be complete”). The operational reality is that historical detail in the new system rarely gets used, adds weeks to the migration, and creates reconciliation errors that take more time to fix than the data was worth.

If you ever need historical detail, the spreadsheet is still there.

Step 4: set up the monthly rhythm from day one

The new software won’t keep itself current. The monthly bookkeeping rhythm is what makes it work, and it needs to be set up deliberately in the first month, not assumed.

On day one of the cut-off period:

  • Bank feeds connected for every operating account.
  • POS integration or daily sales import configured (not manual entry).
  • Delivery platform statements. Know how each one will be booked (direct integration where available, manual import where not).
  • Supplier invoice entry. Who enters them, how often, from where.
  • Payroll integration. Payroll software feeding the GL via journal or integration.
  • Reconciliation schedule. Weekly bank, weekly platforms, monthly suppliers, monthly close.

The rhythm this guide refers to is the same one any healthy hospitality business runs. See Month-end close checklist for hospitality businesses for the working cadence.

Without a named owner for each step and a calendar cadence, the new software is just a more expensive place to lose track.

Step 5: the first month reconciliation

End of month one post-migration is the most important reconciliation of the entire year. It’s where errors from the migration reveal themselves.

Things to check:

  • Bank balances match between the new software and the physical bank statement
  • Total revenue matches the POS (with channel split preserved)
  • Platform receivables match the platforms’ end-of-month outstanding balances
  • Supplier balances match the AP aging reports
  • Opening balances plus month 1 activity equals month-end closing balance, on every balance sheet account
  • P&L makes sense when compared to the spreadsheet’s historical monthly pattern (revenue shouldn’t be 40% off last month’s; if it is, something migrated wrong)

If the first month reconciles cleanly, the migration is done. If it doesn’t, investigating the variance at month one is trivial; waiting until month three to notice is a three-month cleanup.

Common migration mistakes

  • Treating it as data entry instead of structural design. The COA decision is the whole migration. Everything else is follow-through.
  • Migrating every historical transaction. Weeks of work, rarely useful, creates reconciliation errors.
  • Mid-period cut-off. Splits a tax period across two sources; the filing becomes a reconstruction.
  • Not setting up bank feeds before go-live. Manual bank entry turns the new software into a slow spreadsheet.
  • Running the spreadsheet and the software in parallel indefinitely. “Just a few more months in Excel while we get comfortable” is how some operators end up in both systems at once for a year. Pick a date. Cross it.
  • Skipping the month-1 reconciliation. Migration errors that would be a 20-minute fix at month one become a week-long cleanup at month three.
  • Picking the software based on starter pricing. Most hospitality businesses outgrow the starter tier in six months. Price the tier you’ll actually run on.

Migration checklist

  • Chart of accounts designed for current business + next 18 months
  • Cut-off date picked, aligned to financial year or quarter end
  • Platform picked based on geography, payroll fit, POS integration, bookkeeper preference
  • Opening balances prepared (bank, AR, AP, inventory, fixed assets, loans, accruals, equity)
  • Bank feeds configured for all operating accounts
  • POS-to-software integration or daily-sales import set up
  • Delivery platform data flow decided per platform
  • Payroll-to-GL integration in place
  • Monthly rhythm cadence documented with named owners
  • Month-1 reconciliation completed before month-2 begins
  • Spreadsheet archived (not deleted; kept as historical reference) once month-1 reconciles clean

Next step

If your business is on spreadsheets and you’re weighing the move to Xero or QuickBooks, the free books health check is the practical first step. We look at the current spreadsheet structure, design the right chart of accounts, and map the cut-off strategy for a clean migration, not a data dump.

Last updated: April 2026.