Chart of accounts
Full account hierarchy, account codes and class codes — preserved one-to-one, with the UK VAT scheme attached to each account where it applied.
Move from Xero
Your accounts, contacts and invoices — where they belong.
Connect Xero once, and the chart of accounts, contacts, invoices, bills and bank transactions land inside your YionStack business — mapped to the right places, with UK VAT codes preserved. See every supported source →
Connects through the same OAuth flow most accountants already trust. We never see your password.
At a glance
accounting- From
- Xero
- How
- OAuth (no password)
- Records
- 6 types come across
- Steps
- 3-step migration
- Stays put
- 5 items intentionally
- Residency
- UK (europe-west2)
What lands in your business
The records you depend on, in their right places.
Contacts
Customers and suppliers land in the unified contacts table. Email addresses, phone numbers, addresses and default tax treatment all come across.
Sales invoices
Drafts, awaiting payment, paid — with line items, line tax, and the original invoice number kept as the external reference for audit.
Purchase bills
Bills, credit notes and supplier statements — including attachments where the original export carried them.
Bank transactions
The last 90 days of reconciled bank lines come across as historical context. New bank feeds reconnect through GoCardless or your bank directly.
Tracking categories
Tracking categories map to YionStack tags. Reports that grouped by tracking category continue to work after the migration.
How it works
Three steps. Reversible at any point.
- 1
Connect
Authorise YionStack from your organisation using the same OAuth flow Xero uses for accountants. We never see your password and the connection is revocable at any time.
- 2
Review the mapping
YionStack reads your accounts, contacts and tax codes and suggests where each one lands. You approve or adjust before any data is written.
- 3
Run the import
The job runs in the migration dashboard. Progress is live; any rows that need attention are surfaced as the job finishes, not buried in a log.
What stays where it is
We are honest about scope.
A migration is not the same as a clone. The records below are intentionally out of scope — either because they belong with the system that produced them, or because their meaning changes once they live inside an operating system instead of a point-tool. You can still reference the originals while you run YionStack alongside.
- —Bank feed connections themselves — re-authorised in YionStack through GoCardless or directly with your bank, so the new feed is owned by your YionStack business.
- —Payroll runs — if you ran payroll inside your old books, the payroll history moves separately through the YionStack Payroll onboarding so the year-to-date figures stay HMRC-correct.
- —Saved reports and budgets — re-authored once inside the YionStack reporting layer, where they can pull from the live CRM and projects modules too.
- —Third-party bolt-on app data (Hubdoc, expense capture apps) — exported on the source side and brought across via the Import surface.
- —Inventory items — handled by the inventory module migration, scheduled separately so it can take stock counts into account.
Common questions
Straight answers.
Does this support UK regional VAT and CIS codes?
Yes. YionStack reads the country code from your organisation and applies the UK VAT scheme to imported accounts, including the reduced and zero-rated codes and the domestic reverse charge. CIS deductions on subcontractor bills are preserved.
What happens to my old invoice numbers?
Every imported invoice keeps its original number as the external reference, so the audit trail is intact. New invoices issued from YionStack continue the sequence from the highest imported number — you do not get a number collision.
Can I run both side by side while we test?
Yes. The migration is a one-time copy by default. Your old books continue to operate normally; YionStack does not write anything back. Most teams run both for a month, agree the cutover date, then stop posting to the old books.
How long does it take?
A typical UK SME — five years of history, around ten thousand invoices — completes in fifteen to twenty minutes. The job runs in the background; you do not need to keep the tab open.
What if something fails mid-way?
Each entity is imported in a transaction-safe order (accounts before contacts before invoices). If a row fails validation, that row is surfaced for review and the rest continue. You can re-run the migration after fixing the source, and YionStack deduplicates on the external reference so nothing imports twice.
Ready to run your business smarter?
Join thousands of UK businesses already running on YionStack.
- No credit card
- 14-day free trial
- Cancel anytime