QuickBooks Desktop Discontinued? The 2027 Reversal

Is QuickBooks Desktop being discontinued? For new customers, yes. For existing Desktop 2024 subscribers, not any more. In August 2026 Intuit reversed the plan that most articles on this topic are still built around, and its own help article now reads: "QuickBooks Desktop 2024, Pro Plus, Premier Plus, and Enterprise Solutions, won't be discontinued in May 2027." It adds: "There's no sunset deadline for this release."

That changes the advice. The fixed deadline that forced a migration is gone for anyone on 2024. The fixed facts that remain are these.

Two things follow. Your version matters more than ever, because 2023 and older are unsupported while 2024 has no end date. And Desktop is now a closed club: it keeps working for people already inside it, but no new Pro or Premier customer can join, which is the real long-term pressure. If you are still deciding between the two products, our QuickBooks Online vs Desktop comparison weighs them with the new policy in mind.

The short answer

Check your version first. On 2023 or older, you are unsupported and should upgrade to 2024 or migrate now. On 2024, you can stay: Intuit says it will keep version 24.0 current with security patches, tax compliance updates and fixes delivered through periodic in-product updates. Staying is now a legitimate choice rather than a delay, but it should still be a written decision, because the policy that set May 2027 was changed once and can be changed again.

To check, press F2 inside QuickBooks Desktop or open Help, then About QuickBooks. The year appears at the top of the product information window.

What changed in August 2026

Intuit historically retired each Desktop version about three years after release, almost always on 31 May. Desktop 2021 lost support in May 2024, 2022 in May 2025 and 2023 in May 2026. Under that rule, Desktop 2024 would have gone in May 2027, which is why so much of the coverage you will find, and the earlier version of this page, gave a 2027 end date.

Intuit's release process article, updated 5 August 2026, states that "QuickBooks Desktop Plus 2024 and QuickBooks Desktop Enterprise 24.0 were our last annual platform releases," with new features and security updates arriving through the year instead. The Desktop 2024 article, updated 18 September 2026, spells out the consequence: no discontinuation in May 2027 and no sunset deadline.

Three details are worth reading closely:

• The named products are Pro Plus, Premier Plus and Enterprise Solutions. The statement does not mention Mac Plus. If you run QuickBooks on a Mac, confirm your position with Intuit directly.
• It covers version 2024 only. Nothing was extended for 2023 or older.
• It is a policy, not a contract. The same page could carry a new date next year. Plan as if staying is safe for now and keep a migration plan on file.

Is QuickBooks Desktop being discontinued in Canada?

No, not for existing subscribers. Intuit Canada stopped selling QuickBooks Desktop Pro, Premier and Desktop Payroll to new subscribers: the Canadian Desktop page states that "as of April 15, 2025, QuickBooks Desktop Pro, Premier, and associated Payroll services are no longer available for new subscribers." Enterprise remains on sale, and current subscribers can keep using their version while their subscription is active.

The support timeline matches the US. Intuit's Canadian discontinuation policy says Desktop 2023 was discontinued after 31 May 2026 and that existing Plus and Enterprise subscribers are entitled to version 2024 at no additional cost. Intuit's Canadian Desktop 2024 article repeats the US wording: 2024 won't be discontinued in May 2027 and has no sunset deadline.

What is different in Canada is the cost of staying on an unsupported version. Payroll in Desktop depends on tax table updates, and CPP, EI and income tax deduction rates change every year, so a frozen 2023 install drifts away from what the CRA expects. If you run Canadian payroll in Desktop 2023 or older, upgrading to 2024 or moving payroll out is urgent.

What Desktop users on Reddit are saying

The confusion is real, and Intuit's own sales calls add to it. A Canadian subscriber on r/QuickBooks asked whether 2024 Pro would be cut off in mid 2027, saying they phoned Intuit and "basically got no answers," were pushed toward Online, and "was quoted for the Enterprise option at over $500 per month without payroll." The reply in that thread pointed to the same Intuit line quoted above and gave the practical advice: keep what you have, and Intuit will email you if a forced move ever comes.

Moving to Enterprise to escape the uncertainty has its own cost. In a thread about Desktop payroll support, one owner who switched said "the layout is almost identical" but "the renewal was over $2300 a year now and it was 1300 when we switched." Another commenter, a bookkeeper, warned against the default escape route: "You should not migrate to QBO payroll, it is a terrible product."

The pattern: people are being sold a deadline that no longer exists. Check your version, read Intuit's help article yourself, and make the decision on your own timeline. If price is what is pushing you, the numbers are in the QuickBooks 2026 price increase.

What "support ends" actually means

This still matters for anyone on 2023 or older, and for 2024 if Intuit ever sets a new date. The software does not stop working. What stops, per Intuit's 2023 policy:

• Payroll. Tax tables and forms stop updating, so calculations become wrong rather than merely old. For anyone running payroll in QuickBooks, this is the hard deadline.
• Bank feeds and online banking. Reconciliation becomes fully manual.
• Security updates. An unpatched financial application holding banking details, on a networked machine, is a real exposure rather than a theoretical one.
• Desktop Payments and other connected services, including emailing forms and accountant copy transfers.
• Live support.

If you stay on Desktop 2024

Now a genuinely reasonable choice. Conditions that keep it that way:

• You are on 2024, confirmed with F2, and accepting the in-product updates when they appear.
• You have a current backup stored off the machine.
• You have a written trigger for leaving: a price rise past a set number, a key integration dropping Desktop, or Intuit announcing a new date.
• You are not buying new integrations that only work through a Desktop connector. Most new tools build for Online first, which is the slow squeeze on Desktop now that nobody new can join. That constraint also applies to choosing a CRM, which is why it appears in the best CRM for QuickBooks.
• You know who else touches the file. A new bookkeeper or accountant is increasingly likely to work only in Online.

If you are a contractor weighing the Desktop Contractor edition specifically, QuickBooks Desktop Contractor edition alternatives covers what replaces its job costing reports.

Check your file size before any move

This is the step that changes the entire plan and almost nobody does it first.

Company files exceeding roughly 750,000 targets cannot be converted to QuickBooks Online. Above that threshold, migration is not a conversion at all. You export lists and balances, start fresh in the new system, and keep the Desktop file as a read-only historical archive.

If you are over the limit, the start of a financial year becomes close to essential, because you are drawing a line and beginning fresh. With the 2027 deadline gone, you can now choose that year start freely rather than migrating mid-year under pressure.

The three destinations

Intuit's migration path assumes QuickBooks Online. That is one option of three, and the default is not always right.

QuickBooks Online. The path of least resistance. Familiar concepts, your accountant already knows it, integrations are plentiful, and the conversion tooling exists. The trade-offs are real: it is a genuinely different product rather than Desktop in a browser, some Desktop features have no direct equivalent, and pricing keeps rising, with another round of US increases applying to renewals from 1 August 2026, per Intuit's price change notice. If cancelling a Desktop or Online plan is part of the move, how to cancel a QuickBooks subscription covers what happens to your data.

A different accounting product. Xero and FreshBooks are the usual general-purpose comparisons, with Wave suiting very small operations. Worth evaluating properly, since you are paying the migration cost regardless, and this is the one moment where the switching cost that normally locks you in is being incurred anyway.

A field service or operations platform. This is the one contractors most often should consider and least often do. Jobber, Housecall Pro and ServiceTitan are built around scheduling, dispatch, job costing and invoicing, and they connect to accounting rather than replacing it. If your actual constraint is knowing which jobs made money and which technician is where, an accounting product will not solve it at any tier. We compare these honestly in QuickBooks alternatives for contractors.

The question that sorts these: what is actually slow or painful today? If the answer is bookkeeping, pick an accounting product. If the answer is scheduling, job profitability or chasing quotes, the accounting product was never the bottleneck and moving to a different one will not feel like progress.

The sequence that works

Ordered so that the expensive discoveries happen early rather than late.

Weeks 1 to 2: decide and prepare. Confirm your version and whether it is still supported. Check the target count. Choose the destination based on what is actually painful. Back up the company file to somewhere independent of the machine it lives on. List every integration touching QuickBooks, including payroll, payments, time tracking, CRM and bank connections, because each one is a separate reconnection task.

Weeks 3 to 4: clean up. This is the step people skip and regret. Merge duplicate customers and vendors, close inactive accounts, standardise naming, resolve outstanding reconciliation items, and clear anything sitting in undeposited funds. Migrating a messy file produces a messy file in a new system, plus a fortnight of confusion about whether the mess was there before.

Week 5: migrate. Run the conversion. Do it at a period end if possible, and never during your busy season. Keep the Desktop file untouched afterwards as the reference copy.

Weeks 6 to 7: validate. Compare trial balance, accounts receivable and accounts payable ageing, bank balances and prior period reports against the Desktop file line by line. Reconnect bank feeds. Test payroll on a single employee before running the full cycle. Rebuild integrations one at a time and verify each.

Ongoing: run parallel briefly. For one cycle, enough to trust the numbers. Not indefinitely, because dual entry produces divergence and nobody maintains it past a few weeks.

Where Desktop and Online genuinely differ

Worth setting expectations, because the most common post-migration complaint is not that Online is worse but that it is different in ways nobody flagged in advance.

Speed feels different. Desktop is a local application operating on a local file. Online is a web application. Experienced Desktop users who navigate by keyboard and muscle memory notice this immediately, and it reads as the software being slow when it is mostly the interaction model changing. It fades in a few weeks; it is very loud in week one.

Some reports do not have direct equivalents. Particularly customised Desktop reports built up over years. Identify the five reports you genuinely run every month, and confirm before migrating that each can be reproduced. Discovering this afterwards is the single most common source of migration regret.

Multi-user works differently. Desktop licenses seats against a file; Online charges per user with role-based access. For some businesses this is cheaper and for others considerably more expensive, and it is worth pricing at your actual headcount rather than assuming.

Inventory handling is not equivalent. If you carry meaningful stock, this needs specific evaluation rather than a general assumption that it will be fine.

Batch entry and keyboard workflows change. Anyone doing high-volume data entry will feel this most. It is a training and process question rather than a blocker, but budget for it.

None of these are reasons to avoid migrating, since the end date is fixed regardless. They are reasons to test with your real workflow during the trial rather than clicking through a demo, and to have the person who does the daily entry present when you do.

A note on your accountant

Involve them at the decision stage rather than after the migration, for three practical reasons.

They may have a preference with real weight behind it. An accountant fluent in one system and unfamiliar with another is a genuine cost or saving depending on which way you go.

They can do the cleanup faster than you can. Reconciliation items, undeposited funds and chart of accounts tidying are their normal work, and the cleanup step is where migrations succeed or fail.

They need to validate the result. Someone has to confirm the opening balances and trial balance match, and that someone should not be the person who ran the migration.

Book their time early. Year end and tax season are exactly when their capacity disappears, and being in the queue ahead of the rush is worth more than any tooling decision on this page.

Mistakes that make this expensive

Waiting for Intuit to force it. If a new end date is ever announced for 2024, every accountant and consultant will be handling the same migrations in the same months. Availability drops and rates rise. Moving on your own schedule is cheaper for reasons unrelated to the software.

Migrating during busy season. A fortnight of uncertain numbers is survivable in a quiet month and genuinely damaging in a peak one. For seasonal trades this dominates the timing decision, which is the same logic as the advertising calendar in the best time of year to advertise HVAC.

Skipping the cleanup. The single largest source of post-migration pain, and the one part entirely within your control.

Assuming integrations reconnect themselves. They do not. Each is a separate task, and the CRM connection in particular deserves care, because a first sync into a fresh file is exactly where duplicate customers get created at scale. The failure modes are in QuickBooks CRM sync problems.

Forgetting the archive. Keep a working Desktop installation and a copy of the file for historical reference and any audit that reaches back. It costs nothing and you cannot recreate it later.

Treating it as purely technical. The people entering data need to know the new workflow before go-live, not during it. Most failed migrations are adoption failures with a technical postmortem.

The step-by-step version of the migration itself, including the validation checks worth running, is in migrating off QuickBooks. Everything else we have written on Intuit's products, from sync problems to job costing, is collected in the QuickBooks topic hub.