Nobody switches accounting software because they are excited about switching accounting software. They switch when staying costs more than moving — and then they stall on one question: how much of the last decade comes with them?
.qbw file. Not Kantivo, not Xero, not Sage, and not QuickBooks Online.
Migration is always export-then-import. The only real variable is how much of that
export the receiving software understands well enough to be useful.
The closed format, and what it implies
QuickBooks Desktop stores a company’s books in a .qbw file. Intuit
has never released a specification for it. There is no public schema, no reader
library, and no lawful path to building one.
You can see the consequence in Intuit’s own product line. Converting a customer from QuickBooks Desktop to QuickBooks Online means moving between two Intuit products, using Intuit’s format knowledge and Intuit’s engineers — and it still runs as an export and a conversion, and still leaves things behind. When the author of a format has to export from it, that settles the question for everyone else.
Keep that in mind next time a competitor implies they will simply read your QuickBooks file. They will read an export of it. That is not a criticism — it is the only thing anyone can do — but it is worth knowing before you weigh anybody’s promises, including ours.
What travels with you
Rather than describe this in adjectives, here is the inventory.
| Record | Detail preserved |
|---|---|
| Chart of accounts | Numbering, account types, descriptions and the full sub-account nesting rather than a flattened list |
| Customer & vendor records | Names and contact details, including entries that only ever appeared inside a transaction |
| Invoices | Numbers, dates, individual lines and their income accounts, so receivables aging is right on day one |
| Bills | Numbers, dates, lines and expense-account postings, producing correct payables aging |
| Settlements | Customer payments and bill payments still linked to the invoice or bill they cleared |
| Item List | Service, inventory, non-inventory, group, discount-percentage and assembly items alike |
| Class List | Complete with parent and sub-class structure, mapped onto the built-in Class dimension |
| Line-level class & item tags | Re-applied as each journal line lands, so class-segmented reporting keeps working |
Pay attention to the final row. Importing a chart of accounts is table stakes and almost everyone manages it. Re-attaching your classes and items to individual transaction lines is the step most tools skip — and skipping it leaves you with a decade of history that reports as a single undifferentiated mass and has to be re-tagged by hand before any departmental or project report means anything.
What stays behind
A migration that loses nothing does not exist. These are the real omissions, stated plainly rather than discovered later:
- Payroll tax history. Bound to the QuickBooks payroll module. Mid-year movers should close out the year on their existing payroll records.
- Attached documents. Receipts and scans pinned to transactions sit in a separate QuickBooks store that no export reaches.
- Reconciliation detail. Reconciled balances arrive as balances; the mapping of statement to cleared line does not survive.
- The QuickBooks audit log. Not exportable at all. Your new audit trail begins at import.
- Memorized reports and bespoke form layouts. Both are QuickBooks-native objects and need rebuilding — normally quick, and normally an opportunity to abandon the ones nobody opened.
Worth saying clearly: none of this is particular to leaving for Kantivo. Every item above is equally lost when Intuit converts a customer to QuickBooks Online. We have catalogued Intuit’s own published list of exclusions elsewhere, and it runs considerably longer.
The sequence, end to end
- Pull the lists out. Inside QuickBooks go to File › Utilities › Export › Lists to IIF Files and select Accounts, Customers, Vendors, Item List and Class List.
- Pull the transactions out. Run a Transaction Detail report across your entire history, switch on the Class and Item columns under Customize Report, and export as CSV or Excel.
- Load them in order. The wizard works in phases and lists go first, so that classes and items already exist when the transactions referencing them arrive.
- Rehearse before you commit. Import into a throwaway company first and reconcile a couple of reports against QuickBooks. Anything that lands unmatched can be repointed en masse with Resolve Import Suspense, and an entire import batch can be reversed if you would rather start again.
Where that leaves you
An exact replica of your QuickBooks file is not on offer anywhere, because the format that would allow one has stayed shut for thirty years. What is on offer is your accounts, your contacts, your settled and outstanding receivables and payables, your items, your classes and your transaction history for as long as it runs — with the tagging intact, so the reports you rely on still produce the same shape of answer.
That is the line between migrating a business and restarting one. And the only part with a clock on it is the first: while QuickBooks still opens, get the export out.
Test the import before you decide anything
Run your QuickBooks export into a scratch company and see what lands. Thirty days, every feature, no card required. If it falls short of what this page describes, you have spent an afternoon and learned something worth knowing.
Start your free trialWorking with a file that will not open any more, or decades of history you are not sure about? Describe your setup to us — we would much rather see the real thing than speculate.
What people ask us before they move
Does Kantivo read my QuickBooks .qbw company file?
It does not, and no competing product does either. Intuit has kept the .qbw specification closed for its entire life, which is why even a move from QuickBooks Desktop to QuickBooks Online runs through an export and conversion rather than opening the file. The workflow is that QuickBooks produces an export and Kantivo reads it — IIF, CSV, Excel, QIF, QFX or QBO.
Which parts of my books survive the move?
The chart of accounts keeps its numbering, types and sub-account nesting. Customers and vendors arrive with contact details. Invoices and bills come across with their individual lines and the accounts each line was posted to, and the payments that settled them stay matched to them, so receivables and payables aging is correct immediately. Your Item List and Class List transfer with their hierarchies intact, and both get re-applied to individual transaction lines during the import.
What is left behind?
Payroll tax filings and history, files attached to transactions, the record of which bank statement cleared which line, the QuickBooks audit log, and any memorized reports or customised form templates. Some of that is sealed inside the .qbw and some has no counterpart outside QuickBooks. Treat any vendor promising a perfect one-to-one migration with suspicion.
Is there a limit on how old my transactions can be?
No. A Kantivo user moved books that began in 1997 without hitting a floor. In practice the constraint is the date range you asked QuickBooks to include when you ran the export report, not the software reading it.
My copy of QuickBooks is several years old — is it too late?
Desktop Pro, Premier, Mac and Enterprise going back to the 2013 releases export cleanly, and frequently older ones do too, because the IIF format has hardly moved in two decades. The real deadline is different: QuickBooks Desktop 2023 went out of support on 31 May 2026 and 2024 follows on 30 September 2027, and reinstalling a retired release on new hardware often fails because activation is no longer answered. If it opens now, export now.