How to Migrate from Xero to Zera Books
A step by step playbook for moving your books off Xero. Export, import, categorize, reconcile, run your first P&L the same day. Built for business owners and the accountants who serve them.
TL;DR
Migrating from Xero to Zera Books takes about 90 minutes. Export your COA, transactions, and trial balance from Xero, drop them into Zera Books, upload 12 months of bank statement PDFs, and let the AI categorize at 99.6% accuracy across 3.2M+ documents processed. You run a P&L the same day. Cost is $79 per month flat, no per user fees, with a 1 week trial and no credit card.
By Damin Mutti, founder of Zera Books. Last reviewed 2026-05-21.
Why switch from Xero
Three forces are pushing Xero customers to look elsewhere in 2026: the steady US price climb, the 1 user wall on expense claims and project tracking, and the AI gap. Xero Established (US) sits at $80 per month with strict per user caps on features that were previously bundled. The document workflow has also barely moved. Xero still cannot read a bank statement PDF on its own. You either re key transactions or pay for Hubdoc seats and add ons that drift the real price toward $150 to $300 per month.
Annual cost: typical Xero stack
- Xero Established (US) base
- $960
- Hubdoc additional users + add ons
- $420
- Expense seats (3 extra users)
- $360
- Bookkeeping cleanup hours
- $1,200
- Total
- $2,940 / year
Annual cost: Zera Books
- Flat subscription
- $948
- Document processing
- Included
- Categorization AI
- Included
- Cleanup time
- ~80% lower
- Annual savings
- $1,990+
Xero pricing pulled from Xero's official US pricing page on 2026-05-21.
Pre flight checklist
Gather these before you start. Allow 15 minutes for prep. The migration will not move forward if any of these are missing.
- Adviser or Standard plus reports role in Xero (must be able to export everything)
- A current chart of accounts CSV (Accounting → Chart of Accounts → Export)
- A trial balance as of your chosen cutover date
- The last reconciled bank and credit card statement for every connected account
- 12 months of bank statement PDFs downloaded from each bank portal
- Login credentials for any third party app you want to reconnect (Stripe, Gusto, Shopify, etc.)
- A list of repeating invoices and bills plus their schedules from Xero
- A Hubdoc export of all attached documents (Hubdoc → Settings → Export)
Step by step migration from Xero
Eight steps. Eighty to ninety minutes. Each step has an estimated time so you can pace the work between meetings.
Export your chart of accounts from Xero
5 minInside Xero open Accounting, Chart of Accounts, then Export. Save the CSV as zera-coa-import.csv. This becomes the seed file for your new ledger. If your COA has more than 200 lines, archive the inactive ones first. Old dormant accounts only slow categorization later.
Export 12 months of transactions plus the trial balance
10 minRun the Account Transactions report for the last fiscal year and a Trial Balance as of your chosen cutover date. Export each as CSV and PDF. The PDF is your audit copy. The CSV is what Zera will reconcile against.
Sign up for Zera Books and import the COA
2 minCreate a Zera Books account at zerabooks.com/auth. The first onboarding screen asks for your COA. Drop in the Xero export. Zera maps Xero account types to its 5 type model automatically. You will see the full new COA in under 30 seconds.
Upload bank statement PDFs
15 minSkip re exporting transactions out of Xero. Drag the original PDF bank statements (one file per account, last 12 months) into Zera. The AI extracts every transaction at 99.6% accuracy. No template setup. No CSV reformatting. Multi page and password protected statements both work.
Review and approve AI categorization
20 minZera batch categorizes against your imported COA. Approve the first batch one click at a time. By batch two the AI has learned your contact patterns and tracking categories. Roughly 95% of transactions auto match in batch two. This step scales with transaction volume more than any other.
Reconcile and verify trial balance
20 minOpen the reconciliation panel. Tie each account to the ending balance on its last bank statement. Then compare the Zera trial balance to your Xero trial balance. They should match to the cent if the prior books were clean. If a number is off, Zera shows a variance report that names the offending entry.
Set opening balances and lock prior periods
5 minApply the Xero trial balance as opening balances on the cutover date. Lock all periods before cutover. This freezes the historical numbers so nothing back dates into them by accident. Lock day is the only irreversible step in the entire process.
Keep Xero read only for 30 days, then cancel
5 minDo not cancel Xero on day one. Run parallel for 30 days. Reconcile the same month in both systems. Once three statements match cleanly, cancel Xero from Subscription and billing. The official Xero cancellation steps live on their help center.
Need the official Xero cancellation steps? See Xero's cancellation help article and the IRS recordkeeping guidance for your archive retention period.
Xero to Zera Books data mapping
Every Xero field has a home in Zera. Some map one to one. A few rebuild during cutover. This table is the reference your accountant will ask for.
| Xero | Zera Books equivalent |
|---|---|
| Chart of Accounts (CSV export) | COA import wizard, 5 type model |
| Account Types (Revenue, Direct Costs, Expense, etc.) | Asset, Liability, Equity, Income, Expense (mapped automatically) |
| Account Codes | Account codes preserved and editable |
| Contacts (Customers and Suppliers) | Customers and Vendors modules with vendor aliases for AI matching |
| Inventory Items | Items table, linked to invoices and bills |
| Sales Invoices | invoices and invoice_lines tables, AR aging native |
| Bills (Purchase Invoices) | bills and bill_lines tables, AP aging native |
| Bank Transactions | Uploaded statements, AI extracted, then posted |
| Manual Journals | journal_entries and journal_entry_lines (double entry enforced) |
| Trial Balance | Opening balances on the cutover date |
| Bank Reconciliations | Re reconciled in Zera (about 20 min per account) |
| Tracking Category 1 | Class tagging on every transaction |
| Tracking Category 2 | Departments table, Location tagging on entries |
| Repeating Invoices and Bills | Recurring engine, rebuild from Xero list (about 5 min each) |
| Attached Files | Bulk download from Xero, retain as archive; new PDFs stored in Zera |
| History and Notes | Full immutable audit log from cutover date forward |
| Payroll Journals (Gusto, ADP, Xero Payroll) | Push directly to Zera, same as Xero |
| Sales Tax (GST, VAT, US Sales Tax) | Sales tax tracking on invoices and bills |
| Bank Feeds (Yodlee, direct feeds) | Plaid integration, OAuth in 5 minutes per institution |
| Hubdoc Documents | Drag PDFs straight into Zera; AI extracts without Hubdoc |
| Reports (P&L, BS, Cash Summary) | Built in plus AI insight commentary on every report |
What carries over and what does not
Honest answer first. Most data migrates cleanly. A few items rebuild during cutover. None of it is destructive.
Carries over cleanly
- Chart of accounts (codes, types, structure)
- Trial balance as opening balances
- Contacts (customers and suppliers)
- Inventory items mapped to items
- Open invoices and bills (re entered at cutover date)
- Tracking categories mapped to class plus department
- Tax rates and codes (GST, VAT, US sales tax)
- Repeating invoice and bill schedules (rebuilt from list)
Rebuilds in Zera
- Historical bank reconciliations (about 20 min per account)
- Xero attached files (download via Files area, retain as archive)
- Xero history and notes log (Zera starts a fresh audit log)
- Third party app connections (OAuth reconnect, 5 min each)
- Bank feeds (Plaid reconnect, 5 min per institution)
- User roles and adviser access (re invite team to Zera)
Common pitfalls during Xero migration
Six things that trip Xero customers up. None of them are deal breakers, but each wastes 20 to 60 minutes if you hit it cold.
Tracking category sprawl
A long running Xero file often has 40+ tracking category options between Category 1 and Category 2. Audit them in Xero before exporting and archive anything unused. Zera will only map active categories.
Multi currency complications
If you have multi currency in Xero, lock exchange rates for the cutover date before exporting. Zera applies those rates to opening balances. Mismatched rates produce a foreign currency gain or loss that takes 15 minutes to chase down.
Hubdoc carryover
Hubdoc only mirrors documents into Xero, it does not retain originals after you cancel Xero. Bulk export from Hubdoc into a local folder before cutover. Zera ingests PDFs directly, so you will not need Hubdoc again.
Bank feed duplication
If you reconnect Plaid to Zera while Xero still has the same feed active, you get double counted transactions during the overlap. Disconnect Xero bank feeds on cutover day. The PDF upload covers prior history.
GST and VAT rate drift
If your jurisdiction changed GST or VAT rates between your last Xero filing and your cutover, re verify rates inside Zera before issuing new invoices. Most state and national revenue sites publish current rates monthly.
Forgetting expense claim history
Xero expense claims do not export through the standard COA path. Export expense claim reports separately if your accountant needs the historical detail. Zera tracks new claims via the purchases module from day one.
Reference: AICPA accounting software evaluation guidance recommends a 30 day parallel run after any general ledger migration.
What changes day to day after switching
You will notice four big workflow shifts in the first week. None of them require training. Most teams stop opening Xero entirely after week two.
Document upload replaces Hubdoc
Drop a PDF straight into Zera. The AI extracts and categorizes. Hubdoc is no longer in the loop, and no extra seat fee applies.
Batch reconciliation replaces line by line matching
You approve categorizations in batches of 50 to 200, not one transaction at a time on the Xero Reconcile screen.
One platform for accountants and owners
Your adviser sees the same data you see. No more Xero HQ separate from your file. One login, one ledger.
AI insight commentary on every report
P&L and balance sheet reports include a written AI narrative on what changed month over month. That alone has replaced the 30 minute prep call most advisers used to do before sending statements to clients.
“We ran Xero plus Hubdoc plus a bookkeeping retainer for four years. The Zera migration took two hours on a Sunday. By Tuesday I was reading a clean P&L for the first time without waiting on my bookkeeper. The 14 months of bank statements categorized faster than I could pour a coffee.”
Xero migration FAQ
- How long does it take to migrate from Xero to Zera Books?
- A single entity migration takes 60 to 90 minutes of active work. The Xero exports run in 5 minutes, the COA import takes 30 seconds, statement upload and AI categorization runs 20 to 40 minutes, and reconciliation takes about 20 minutes per bank account. A 25 client firm typically finishes in one working day.
- Will I lose any data when I move from Xero to Zera Books?
- No transaction data is lost if you follow the export checklist. Chart of accounts, contacts, manual journals, and trial balance all migrate cleanly. What does not import are Xero bank reconciliation flags, attached files, and the Xero history and notes log. Reconciliations get rebuilt in Zera in about 20 minutes per account.
- Do I need to cancel Xero before starting the migration?
- No. Keep Xero running for 30 days after cutover as a read only reference. Cancel only once you have confirmed three months of reconciliation match in Zera. Xero bills monthly, so timing the cancellation a day before your renewal avoids paying for an extra month you will not use.
- Can I migrate from Xero mid year, or do I have to wait for the new financial year?
- Mid year is fine. Pick the first day of any month as your cutover date. Apply the Xero trial balance as of that date as opening balances in Zera. Year to date data stays in Xero for the prior period and continues in Zera from the cutover forward. Most teams switch in May or October to dodge year end pressure.
- What happens to my Xero bank feeds and connected apps?
- You reconnect third party apps to Zera Books. Stripe, Shopify, and bank feeds reconnect via OAuth or Plaid in 5 minutes each. Payroll providers like Gusto and ADP push journal entries to Zera the same way they pushed to Xero. Specialty Xero only apps need a CSV bridge or a replacement.
- Is Zera Books cheaper than Xero over a year?
- Yes for almost every configuration. Zera Books is $79 per month flat, $948 per year. Xero Established (US) is $80 per month, $960 per year, and that price excludes Hubdoc beyond a 1 user limit, expense claims for more than 1 user, and project tracking for more than 1 user. A typical Xero stack runs $1,800 to $3,600 per year once Gusto, Hubdoc add ons, and per user expense seats are added.
- How does Zera Books handle my Xero tracking categories?
- Tracking categories map to Zera departments and class tagging on every transaction. The first category maps to Class. The second maps to Location or Department depending on how you used it. A short setup wizard walks you through the mapping. Reports that grouped by tracking category in Xero run natively in Zera after mapping.
- What about Xero attachments and the file library?
- Bulk download Xero attachments from the Files area before you cancel. Xero attachments do not migrate automatically. Zera stores new PDFs from day one alongside the extracted transactions. Keep the downloaded Xero archive as part of your year end binder.
- Can my accountant still work with me if I leave Xero?
- Yes. Zera Books exports to QBO, IIF, and clean CSV. If your accountant insists on Xero, they can import your Zera journal entries into a Xero file at year end. Most accountants prefer Zera once they see the AI pre categorization because it cuts cleanup hours roughly in half.
- Will my Xero VAT, GST, or sales tax data carry over?
- Tax codes and rates re map during cutover. Sales tax filings already submitted in Xero stay in Xero as your filing record. Open tax liabilities map to opening balances in Zera. New filings from cutover forward run through Zera. Refer to the IRS recordkeeping guidance for the standard 3 to 7 year retention period on prior records.
- What support do I get during the Xero migration?
- Founder support. Damin Mutti personally helps with migrations during the 1 week trial. Average reply time is 1 hour. Book a 30 minute migration walkthrough through the in app chat after you upload your first Xero COA.
- Will my year over year comparisons still work after migrating from Xero?
- Yes, with one extra step. Import the prior year P&L from Xero as a comparison budget in Zera. Once both years live in Zera, year over year reports run natively. Most teams backfill 13 months of prior data so the rolling comparison is clean from month one.
Related migration and comparison guides
If Xero is not the only platform you are evaluating, these guides cover the rest of the field. Start with the QuickBooks alternative pillar guide for the full landscape.
Start your Xero migration today
Sign up, upload your Xero COA, and watch the new ledger build itself. One week trial, no credit card. Migration done before your next coffee.