For years, moving clients off QuickBooks Desktop was a someday project. The someday has arrived. Support for QuickBooks Desktop 2023 ended on May 31, 2026. Intuit stopped selling new Pro Plus, Premier Plus, and Mac Plus subscriptions back on September 30, 2024, and Desktop 2024 is the final version of those products, with its support ending September 30, 2027. Only Desktop Enterprise continues beyond that. The full schedule is on Intuit's service discontinuation page. If you have clients still running Desktop, the question is no longer whether to move them. It is whether you run the migration on your schedule or on a deadline.
What actually breaks when support ends
The software does not stop opening on the discontinuation date, which is exactly why clients underestimate the problem. What stops is everything connected to it. Per Intuit's policy, discontinued versions lose access to Desktop Payroll, so tax tables stop updating and payroll quietly goes stale. Online bank feeds stop, so every transaction goes back to manual entry. Desktop Payments stops processing. Live support ends. And most important for a firm: critical security updates stop shipping. The client sees a program that still launches. You see an unpatched system that is slowly drifting out of compliance and accuracy.
Why waiting compounds the risk
An unsupported accounting system is not just an inconvenience. For an accounting firm it is a compliance problem. A Desktop file holds taxpayer data, and a machine running software that no longer receives security patches is a known, documented weakness. The FTC Safeguards Rule treats tax and accounting firms as financial institutions and expects a written program that addresses exactly this kind of risk, and IRS Publication 4557 says the same to tax professionals directly. Keeping unpatched software on data like that is hard to defend in a WISP and harder to defend after an incident. Waiting also compounds the practical cost: every month on Desktop adds transactions to convert, and the closer you drift toward tax season, the fewer safe windows remain to do the work.
A migration plan that actually works
A clean migration is a project, not a button. The sequence matters. Clean up first. Reconcile every account, clear old undeposited funds, write off dead receivables, and condense or archive what does not need to come across. Migrating a messy file gives you a messy file in a new place. Migrate off-season. Pick a quiet month and a natural cutover point, ideally just after a period close. Never run a conversion during tax season. Validate before you trust it. Compare balance sheet, P&L, A/R and A/P aging between the two systems as of the cutover date, and keep the Desktop file as a read-only archive. Reconnect what does not convert. Bank feeds, payroll setup, recurring templates, and user access need to be rebuilt in QuickBooks Online, so schedule that work rather than discovering it. Intuit documents the conversion process and its limits in its guide to moving a Desktop company file to QuickBooks Online, which is worth reading before you promise a client a date.
How to have the conversation with clients
Most clients will not move because Intuit published a date. They move because their accountant frames the decision around their risk. A few talking points that work:
Lead with what stops working for them. "Your payroll tax tables and your bank feeds stop updating when support ends. That means manual entry and payroll risk, not just an old program." Concrete losses land harder than version numbers.
Name the security issue plainly. "This software no longer receives security fixes, and it holds your financial data. We are not comfortable being responsible for your books on an unpatched system." That sentence does most of the persuading.
Set a deadline, not an open question. Do not ask if they want to migrate someday. Tell them the window you have reserved: "We are converting our Desktop clients between June and November. Which month works for you?"
Offer to run it. The client's real fear is the disruption, not the destination. Take that off their plate: you handle the cleanup, the conversion, the validation, and their training on the new workflow.
Protect tax season. Be explicit that nothing moves between January and April. It reassures the client and it protects your team from a conversion landing on top of filing deadlines.
Where to start
List every client still on Desktop, note their version and their payroll and bank feed dependence, and rank them by risk. Then book the conversions into real calendar slots before the off-season fills up. If the project feels bigger than your team's spare capacity, this is exactly the kind of work we run for firms: migrations are part of how the Tech Guru Platform keeps a firm moving forward, and for the legacy Windows apps that genuinely cannot move, like Drake and UltraTax, we host them in a fast, secure cloud instead. Book a discovery call and we will help you plan the off-ramp before the deadline plans it for you.
