Free guide
How UK businesses with specialist VAT regimes can migrate from Sage 50, QuickBooks Desktop, and other legacy systems to cloud accounting without losing compliance, control, or sleep.
Last reviewed: 23 June 2026
The migration that everyone's been delaying — and why specialist-VAT businesses get stranded on legacy platforms
The five things that go wrong: VAT scheme mapping, stock book loss, PE history disappearance, mid-year migration, MTD digital link
How OneSixth makes the migration safer — without doing the migration itself
Why the ledger choice becomes a technology decision, not a tax decision
Three ways to engage if you want to take a closer look
The PDF downloads instantly — no email required. The form below is entirely optional.
Optional — we'll add you to product updates if you want to stay in touch. We don't share or sell email addresses.
Their scheme — margin, TOMS or partial exemption — is held together by spreadsheets, custom codes and historical workings that don't move cleanly, so fear of breaking compliance keeps them on Sage 50 or QuickBooks Desktop.
Provisional calculations, stock books and recovery percentages all rely on a continuous record; a mid-year move can break that continuity and leave the year-end adjustment without the history it needs.
It can — MTD for VAT requires an unbroken digital link to the return, and re-keying or copy-paste between systems can break it. The transfer needs to preserve digital links or use a compliant bridging step.
Stock books often live outside the ledger and don't migrate, so the purchase history each item's margin depends on can be lost or orphaned — one of the five things the guide flags as most likely to go wrong.
It shouldn't — your scheme is a tax position, not a software feature — but the platform you choose decides how much manual work it takes. The guide's point: with the right tooling, the ledger choice becomes a technology decision, not a tax one.