Chart of accounts
Every account, sub-account and account number — preserved one-to-one. UK VAT codes carry across; you continue filing under MTD from YionStack’s HMRC connection on the same VAT registration.
Move from QuickBooks
Your accounts, customers and invoices — in one place that runs.
Connect QuickBooks Online once, and the chart of accounts, customers, vendors, invoices, bills and journal entries land inside your YionStack business — with the UK VAT scheme and MTD submission history 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
- QuickBooks
- How
- OAuth (no password)
- Records
- 7 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.
Customers and vendors
Both sides of the contact ledger collapse into the unified contacts table. Default tax treatment, payment terms, and addresses all come across; duplicate detection runs on email and company name.
Sales invoices
Open, paid, partially paid — with line items, line VAT, customer messages and PDF attachments where the source export carries them.
Bills and bill payments
Vendor bills, credit memos and the bill payments that cleared them — linked to the right purchase accounts in the imported chart.
Bank transactions
Reconciled bank lines from the last 12 months come across as historical context. Live bank feeds reconnect through GoCardless or Open Banking, so the new feed is owned by your YionStack business.
Journal entries and classes
Manual journals are preserved with full line-level detail. Classes map to YionStack tags so departmental and project-based reports continue to work after the migration.
MTD VAT submission history
Past MTD VAT returns and HMRC submission receipts come across as historical filings. New returns are filed from YionStack’s accounting module under the same VAT registration.
How it works
Three steps. Reversible at any point.
- 1
Connect
Authorise YionStack from your company using QuickBooks Online’s OAuth handshake. We never see your password and the connection is revocable at any time.
- 2
Review the mapping
YionStack reads your accounts, customers, vendors 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.
- —Live bank feed connections — re-authorised in YionStack through GoCardless or directly with your bank, so the new feed is owned by your YionStack business under your own Open Banking consent.
- —Payroll runs and employees — 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, projects and HR modules too.
- —Time tracking and timesheets — handled by the YionStack attendance and projects modules. Any historical time entries you need to keep export as CSV and arrive via the Import surface.
- —Third-party app data (receipt-capture apps, expense apps) — exported from the source app and brought across via the Import surface so the receipts attach to the right expenses.
Common questions
Straight answers.
Does this work for both QuickBooks Online and QuickBooks Desktop?
QuickBooks Online is supported through the live OAuth connection above. For QuickBooks Desktop, export your file to the .IIF format from the Desktop app, then drop it into the Import surface — YionStack auto-detects the format and runs the same mapping flow.
What happens to my Making Tax Digital connection?
Your VAT registration is unchanged — HMRC holds the registration, not your old software. The historical MTD submission receipts come across as records. Once your books are in YionStack, the next VAT return is prepared and submitted from YionStack’s accounting module under the same registration.
What about CIS deductions on subcontractor bills?
CIS deductions on imported bills are preserved on the line. New bills entered in YionStack inherit the CIS scheme from the vendor’s default, and the YionStack accounting module files the monthly CIS300 return when you’re ready.
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.
What if classes were used heavily for departments or projects?
Classes map to YionStack tags one-to-one. If the same classes also exist as projects in your operation, you can elevate a tag into a YionStack project after the migration so the same dimension drives project P&L, time tracking and resourcing.
Ready to run your business smarter?
Join thousands of UK businesses already running on YionStack.
- No credit card
- 14-day free trial
- Cancel anytime