Skip to content
YionStack
HelpMigration

Import from Xero

Connect Xero through OAuth, review the suggested mapping, and run a one-way import into your YionStack business. UK VAT codes, tracking categories and original invoice numbers are preserved.

In this guide

Migration
Steps
5
Prereqs
3
Pitfalls
3 common ones
Related
3 guides

Walkthrough only — no setup wizard. The flow is exactly what you do inside YionStack today.

Before you start

  • Admin or Adviser access on the Xero organisation you are importing from.
  • Owner role on the destination YionStack business.
  • No open migration job already running on the destination business (the migration queue is one-at-a-time).

Steps

  1. 1

    Open the migration workspace

    Go to Migration → New migration. Pick Xero from the live-connector list. YionStack opens the Xero OAuth flow under your Xero login.

  2. 2

    Authorise the connection

    Approve the YionStack app inside Xero. Only the scopes needed for the import are requested (read chart of accounts, contacts, invoices, bills, bank transactions). The connection is revocable from Xero or YionStack at any time.

  3. 3

    Review the suggested mapping

    YionStack reads your Xero organisation and suggests where each account, contact and tax code lands in YionStack. The mapping page shows source-side and destination-side names side by side; adjust any line before continuing.

  4. 4

    Run the import

    Run the job. The migration dashboard shows live progress — Extracting → Transforming → Validating → Importing → Completed — with a per-entity row count and any flagged rows surfaced for review.

  5. 5

    Verify and start posting

    Once the job completes, open Accounting → Trial balance and check the totals against Xero’s trial balance for the same date. They should match to the penny. Resolve any flagged rows from the migration summary, then start posting new transactions in YionStack.

Common pitfalls

Multi-organisation Xero accounts

If your Xero login has access to multiple organisations, the OAuth flow asks you to pick which one. Picking the wrong organisation imports the wrong books — re-run from a fresh OAuth handshake if so.

Open invoices vs paid invoices

Every invoice comes across regardless of status. Paid invoices preserve the payment link to the bank transaction; open invoices keep their balance for ongoing dunning. If a Xero invoice has been part-paid, the partial allocation is preserved.

Tracking categories vs projects

Xero tracking categories come across as YionStack tags. If a tracking category is really a project (a customer-funded engagement with billable time), promote it to a YionStack project after the migration so project P&L works.

Need a hand with this one?

If a step is missing or unclear, tell us — every guide is a working document we improve as customers ask.