QuickBooks Desktop to Online: Why Year-End Is the Cheapest Time to Move
QuickBooks Desktop 2024 is the last non-Enterprise release. A 90-day migration plan you can start in October — and why a 1 January cutover costs less than a mid-year one.
There is a version of a software migration that goes fine, and a version that eats an entire quarter. The difference is rarely the tool. It is almost always the timing.
If your books still run on QuickBooks Desktop, the next few months are the best window you will get — and it closes on 31 December.
What is actually ending, and when
Intuit has been retiring the non-Enterprise Desktop line in stages rather than all at once, which is why the situation feels murkier than it is. Three things have happened so far.
New US customers stopped being able to buy Pro Plus, Premier Plus and Mac Plus subscriptions after September 2024. QuickBooks Desktop 2023 reached end of support on 31 May 2026. And Desktop 2024 is the last non-Enterprise release, supported through 30 September 2027.
QuickBooks Desktop Enterprise is carved out of all of this and continues to be sold and supported.
End of support does not mean the program stops opening. It means everything that talks to Intuit's servers stops: payroll updates, bank feeds, payment processing, security patches and live support. You keep an offline ledger you can read, and lose every service that made it a working system.
Before you plan anything, confirm your exact edition and year against Intuit's own service discontinuation policy — the dates differ by product, and the country you file in matters too.
Why year-end is the cheapest time to move
The expensive part of a migration is never the file transfer. It is proving that the numbers on the other side are right, and then explaining any difference to your accountant, your lender, or the IRS or CRA.
Move on 1 January and you have exactly one set of opening balances to prove, tied to a trial balance your accountant is reconciling anyway.
Move in June and you have a split year: two systems, two partial sets of books, and comparative reporting that has to be stitched together by hand every time someone asks how this year compares to last. That stitching does not go away after the migration. It follows you through every board pack and every loan renewal for the next eighteen months.
There is a scheduling argument too. January is when 1099s and W-2s are due. You do not want to be mid-cutover, with payroll history half-migrated, in the same three weeks you are trying to file information returns.
A 90-day migration plan you can start in October
Days 1–30: clean before you copy
A migration does not fix messy books. It carries them across and makes them harder to fix.
Reconcile every bank account, credit card and loan through the most recent statement. Clear out undeposited funds. Write off the receivables that are never coming and clean up stale payables. Trim a chart of accounts that has quietly grown to four hundred lines. Fix negative inventory if you carry stock.
Then take a full backup and export PDFs of your trial balance, balance sheet, profit and loss, and AR and AP aging as of your cutover date. Those PDFs are your evidence. If this stage is bigger than it sounds, that is what catch-up and clean-up bookkeeping is for.
Days 31–60: convert, then prove it
Run the conversion, then reconcile the new file against the PDFs you exported — line by line on the balance sheet, total by total on the P&L. Differences are normal at this stage. Undocumented differences are not.
Know what does not come across cleanly before you start, rather than discovering it afterwards: payroll history, reconciliation history, some inventory costing methods, custom report templates, and memorised transactions all have limits. Budget time for rebuilding them rather than assuming.
Rebuild your bank feeds and rules, your recurring transactions, and your user permissions — permissions in QuickBooks Online are structured differently, so this is a fresh decision rather than a copy.
Days 61–90: run both, then commit
For the final stretch, keep Desktop readable and run the new file in parallel for at least one full close. Do a month-end in the new system while you can still check it against the old one.
Sign off when a full close completes without surprises. Then set your Desktop file to read-only, keep the backups somewhere you will still find them in seven years, and stop.
What actually changes afterwards
The honest pitch for QuickBooks Online is not that it is a better ledger. It is that it is a connected one — bank feeds, apps, and multi-user access from anywhere, with your accountant in the same file rather than emailing accountant's copies back and forth.
The honest warning is that some Desktop workflows have no direct equivalent, particularly around inventory, job costing and batch entry. If those are central to how you operate, test them specifically before you commit, and look at whether Enterprise or a purpose-built reporting layer alongside QBO is the better answer.
For a lot of businesses the migration is also the moment to ask a different question: not which software, but who is actually keeping the books in it. A clean new file with nobody maintaining it is a clean new file for about two months.
If you want the clean-up, the conversion and the first close run by people who do this repeatedly, that is the work we do — for businesses and for CPA firms moving a block of clients at once.
Product names, editions and discontinuation dates belong to Intuit and change. Confirm your specific edition against Intuit's current service discontinuation policy before planning a migration.
