Nominal codes
The full nominal ledger structure preserved one-to-one. Each code carries its category, VAT default and reporting position so trial-balance reports continue to read the same after the move.
Move from Sage
Your nominal codes, customers and invoices — without the upgrade pain.
Export from Sage 50 or Sage Business Cloud Accounting, upload to YionStack, and the AI-assisted Import surface maps every record into the right table — nominal codes, customers, suppliers, invoices, bills, VAT history and departments. UK VAT scheme preserved. See every supported source →
File-based — you upload an export from your old system, we map it. No connection to your old account.
At a glance
accounting- From
- Sage
- How
- Upload an export
- 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 suppliers
Both ledgers collapse into the unified contacts table. Email addresses, phone numbers, addresses, default tax codes, payment terms and credit limits all come across.
Sales and purchase invoices
Open, paid and credit-noted invoices on both sides — with line items, line VAT, original references and attachments where the export carries them.
Departments and projects
Department analysis carries across as YionStack tags. Project costing maps into the projects module so departmental and project P&L reports continue to work.
Bank account history
Reconciled bank lines come across as historical context. Live bank feeds reconnect through GoCardless or Open Banking, so the new feed is owned by your YionStack business.
VAT return history
Past VAT returns and their reconciliation come across as records. New returns are prepared and filed under MTD from YionStack’s accounting module on the same VAT registration.
Company details
Trading name, registered address, company number, VAT registration number and PAYE reference all come across so the business profile is complete from day one.
How it works
Three steps. Reversible at any point.
- 1
Export from your current system
From Sage 50 use the standard XML or CSV export; from Sage Business Cloud Accounting use Settings → Export. The Import surface auto-detects the format — no template selection needed.
- 2
Review the mapping
YionStack’s AI-assisted mapper reads the column headers and suggests where each record 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 surface 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 feeds — re-authorised in YionStack through GoCardless or Open Banking, so the new feed is owned by your YionStack business under your own consent.
- —Sage Payroll — if you ran payroll in your old books, the payroll history moves separately through the YionStack Payroll onboarding so the year-to-date figures stay HMRC-correct.
- —Final Accounts Production — statutory accounts are produced from YionStack’s reporting layer once the chart of accounts and year-end journals are in. The PDF outputs from the old system stay with you as records.
- —Fixed asset register — handled by the YionStack accounting module’s fixed-assets register. Existing assets can be re-keyed or brought across by CSV.
- —CIS subcontractor data — preserved on imported supplier bills. New CIS300 returns are filed monthly from YionStack’s accounting module under the same CIS scheme.
Common questions
Straight answers.
Does this support Sage 50 Desktop and Sage Business Cloud Accounting?
Both. Sage 50 exports as XML or CSV (Tools → File Maintenance → Export); Sage Business Cloud Accounting exports as CSV from Settings → Export. The Import surface auto-detects either format. A live OAuth connection to Sage Business Cloud Accounting is coming on the migration roadmap.
Will my nominal code structure stay the same?
Yes. The nominal codes are preserved one-to-one, including the standard Sage default codes (4000s for sales, 5000s for purchases, etc.) and any custom codes you’ve added. You can reorganise the chart later inside YionStack without losing the originals as the external reference.
What about the audit trail?
Every imported transaction keeps its original Sage reference number as the external reference, so the audit trail is intact and any auditor’s review reads the same. New transactions in YionStack continue the sequence from the highest imported number.
Do my year-end journals come across?
Yes. Manual journals — including year-end depreciation, accruals, prepayments and tax provisions — come across with full line-level detail and the original posting date. Year-end-locked periods stay locked in YionStack.
What about departments and cost centres?
Department analysis maps to YionStack tags one-to-one. If a department is also a real project (a job number, a customer-funded engagement), you can elevate the tag into a YionStack project after the import so the same dimension drives project P&L and time tracking.
Ready to run your business smarter?
Join thousands of UK businesses already running on YionStack.
- No credit card
- 14-day free trial
- Cancel anytime