Why companies leave Xero
Xero is decent software. Most of the businesses we move off it aren’t leaving because it failed them. They leave over cost and consolidation.
The cost argument is arithmetic. Xero’s UK pricing has crept up year after year, with payroll and expenses each on their own meter. Run more than one entity and you pay per organisation. Zoho Books is included in Zoho One, so a business already paying for Zoho CRM often discovers that its accounting software is, in effect, already covered.
The consolidation argument matters more day to day. When your pipeline lives in Zoho CRM but your invoices live in Xero, the link between them is a sync that needs watching. We wrote up how that integration behaves, including where it tends to break, in our Zoho CRM and Xero integration guide. Move the books into Zoho and the quote and its invoice sit in the same database with nothing to sync. That pattern is the core of how we build a finance stack on Zoho.
One caveat before you commit: if your accountant is deeply wedded to Xero, raise it with them early. Plenty of UK practices now work happily in Zoho Books, but the pool is smaller and you want your accountant on side before cutover.
If you’re coming from QuickBooks rather than Xero, the mechanics are similar and our QuickBooks to Zoho Books migration guide covers the differences.
What maps to what
| In Xero | In Zoho Books | How it moves |
|---|---|---|
| Chart of accounts | Chart of accounts | CSV import. Account types need remapping because the two products categorise accounts differently. |
| Contacts | Customers and vendors | Xero keeps one contact list; Zoho Books separates customers from vendors. A contact who is both needs a record on each side. |
| Invoices | Invoices | CSV import with line-level detail. Sent and paid statuses map across; partially paid invoices need their payments imported too. |
| Bills | Bills | Same approach as invoices, from the supplier side. |
| Bank accounts | Bank accounts | Recreated, not imported. Feeds reconnect through open banking; balances come from your cutover trial balance. |
| VAT settings | Taxes | Rebuilt by hand: registration number, scheme, rates and the MTD connection to HMRC. |
| Fixed assets | Fixed assets | The register is rebuilt with accumulated depreciation entered as opening figures. Zoho Books then takes over the depreciation schedule. |
| Tracking categories | Reporting tags | The closest one-to-one mapping in the whole migration. Tag values import cleanly; apply them to transactions during import. |
The contact split catches people out most often. If a company both buys from you and sells to you, it becomes two records in Zoho Books, so settle a naming convention before the import. The other trap is the chart of accounts: Xero’s report codes and Zoho’s account types don’t line up automatically, so someone who understands your reporting needs to own that mapping.
The migration, step by step
- Reconcile and lock Xero. Get every bank account reconciled to the cutover date. Chase unreconciled lines now; they’re far harder to untangle once you have two systems. Lock the period so nobody posts behind you.
- Export everything. Xero’s export tools give you contacts, invoices, bills and the chart of accounts as CSV. Also run the reports you’ll check against later: trial balance at the cutover date, aged receivables, aged payables and the VAT report for the open period.
- Build the Zoho Books organisation. Base currency, financial year start, VAT registration details. Import the chart of accounts first because everything else hangs off it.
- Import masters. Contacts, split into customers and vendors, then items.
- Import transactions. Historic invoices and bills first, then credit notes and payments. How far back to go is a judgement call. Two full financial years is the usual compromise between completeness and effort; some businesses bring everything, some bring only open items.
- Post opening balances. Straight from the Xero trial balance at the cutover date. This is the step to get right, because every later reconciliation depends on it.
- Reconnect banking. Each account re-authorises through open banking inside Zoho Books. Bank rules don’t import, so rebuild them from screenshots of your Xero rules. If a feed misbehaves after connection, our guide to UK bank feeds not working in Zoho Books covers the common failures.
- Set up VAT and MTD. Covered properly in the next section.
- Check in parallel. Trial balance against trial balance. Aged ledgers against aged ledgers. Raise a handful of live invoices in both systems for the first week or two if you want extra confidence.
- Go live and archive. Downgrade Xero to its cheapest tier for read access or take a final full export. HMRC expects six years of records either way.
Rebuilding UK VAT and MTD
Nothing about your VAT configuration copies across. You rebuild it inside Zoho Books, which is HMRC-recognised for Making Tax Digital and files returns directly.
The rebuild covers four things. Your VAT registration number and reporting basis, accrual or cash. Your scheme, if you are on flat rate. Your tax rates, including any custom or reverse charge rates you created in Xero over the years. And the MTD connection itself, which is a fresh authorisation grant against HMRC; your old Xero authorisation means nothing here.
The first VAT return out of Zoho Books deserves real attention. Its figures pull only from transactions that exist in Zoho, so if your cutover landed mid-period, part of the return’s data still lives in Xero. You’d have to assemble it across two systems and adjust manually, which is exactly the kind of work that produces filing errors. We see enough of these that we wrote up the common Zoho Books VAT return errors with HMRC separately. Cutting over at a period boundary avoids the problem entirely.
What does not migrate cleanly
Be realistic about these before you start, because each one is a small project of its own.
Payroll history. Zoho Books has no UK payroll module. If you run payroll in Xero today you’ll need a separate payroll product, with its journals posted into Zoho Books each period. Historic payroll records stay in Xero or in an export; they have no destination in Zoho.
Repeating invoice templates. Xero’s repeating invoices don’t export in a usable form. List them before you lose access and recreate each one as a recurring invoice in Zoho Books. Tedious, but a one-off afternoon for most businesses.
Bank rules. Rebuilt manually, as noted above. The rules are usually undocumented institutional knowledge, so capture them while Xero is still open.
Transaction attachments. Receipts and PDFs attached to individual Xero transactions do not come across in any bulk import. If your audit posture depends on them, export the files and keep the archive somewhere your accountant can reach.
The audit trail. Xero’s history of who changed what stays in Xero. Zoho Books starts its own audit log from day one.
Timing the cutover
A VAT quarter end is the natural break. Your final Xero VAT return covers a complete period filed from Xero; your first Zoho Books return covers a complete period filed from Zoho. Clean handover, no manual adjustments, no split-period spreadsheet.
Your financial year end is better still, because opening balances become trivial and your accountant gets one tidy set of records per system per year. The trade-off is that year end comes once a year and is usually the busiest time to attempt anything. A quarter end is nearly as good and comes round four times as often.
The date to avoid is the impatient one: mid-period, because the new system is ready and waiting feels wasteful. Three weeks of waiting is cheaper than one split VAT return.
How long it takes
These ranges are based on migrations we’ve done:
- A single entity with light history and no multi-currency: one to two weeks.
- A typical UK SME with VAT, a few years of history and feeds across two or three bank accounts: two to four weeks.
- Multi-currency, multiple entities or a heavy fixed asset register: four to eight weeks.
Most of that is elapsed time. The work clusters at the start, in cleanup and export, then again at the end, in checking and go-live, with a quieter parallel-running stretch in the middle. Budget your own team’s availability accordingly: the bookkeeper who knows where the bodies are buried needs to be free in week one and again in the final week.
DIY or bring in a specialist
You can do this yourself. Xero’s exports are clean, Zoho’s import tools are competent and the steps above are the whole map. A small business with a confident bookkeeper and a quiet fortnight will manage.
Where DIY migrations go wrong, in our experience, is in three specific places: opening balances that never quite tie back to the Xero trial balance, VAT schemes left on defaults instead of what the business actually registered for and contact imports that made every customer a vendor. None of these is hard to avoid. All of them are miserable to fix three months later, usually discovered the week a VAT return is due. If you are already in that position, our emergency Zoho support puts a senior developer on it within 30 minutes during UK business hours.
If you’d rather hand the whole thing over, this is bread-and-butter work for us. Our Zoho Books work follows a fixed migration checklist. A developer is assigned to standard projects within 24 hours and our pricing is published, so you can see the cost before you speak to anyone. The conversation itself is free too: book a discovery consultation and we’ll tell you whether your migration is a DIY job or one worth paying for. If it’s the latter, you can hire a Zoho developer who already has a Books migration checklist in hand.