QuickBooks Desktop is being sunset. If you have twenty clients on it, you have twenty migrations.

Two dates matter. QuickBooks Desktop 2023 lost all support on May 31, 2026 — that one has already passed. Desktop 2024 loses support on September 30, 2027, and it is the final version; there will be no 2025, 2026 or 2027 release for Pro Plus, Premier Plus or Mac Plus.

Enterprise is carved out. Intuit still sells it, still supports it, and has announced no end date.

Most coverage of this stops at the dates and addresses a single business owner deciding what to do about a single company file. If you run a firm, that isn’t your problem. Your problem is that some portion of your client base is on Desktop, they’re on different versions with different deadlines, and every one of them is a separate conversion with separate payroll history and separate things that won’t come across. Fourteen months sounds like a lot until you divide it by the number of files.

This is the version written for that.

What are the actual QuickBooks Desktop end-of-support dates?

Intuit operates a rolling three-year discontinuation schedule, which is why different clients face different deadlines. A client on 2023 is already past theirs. A client on 2024 has until September 2027 — and after that there is no newer version to upgrade to.

One caveat on the 2024 date. Intuit’s public materials are clearer on “last annual release” and “supported through 2027” than on the precise day. Community replies and industry sources consistently give September 30, 2027. Treat that as the deadline; if it slips, you gain time you weren’t counting on.

How do I find out which version each client is on?

Open the file and press F2 (or Ctrl+1). The Product Information window shows the version year and release number at the top.

For a firm, do this as a documented audit rather than ad hoc. You want a single sheet with a row per client:

That sheet is the migration plan. Everything below is how to fill in the last column and put the rows in order.

If you’d rather not run it yourself, this is exactly the shape of how we onboard a client base.

What actually stops working when support ends?

The software does not shut off. This is the most widely misunderstood part, and it cuts both ways — clients panic when they don’t need to, then get complacent about the things that genuinely break.

What keeps working: the application opens, the company file opens, transactions can be entered manually, reports run, historical data is intact.

What stops:

Two of those are more serious than the rest.

No security patches on a financial database is a real risk. These files sit on local servers and shared drives holding years of financial records, banking credentials, vendor details and payroll data. Accounting systems are a known target precisely because of what’s in them. An unpatched one accumulates exposure every month it stays in service.

What are the actual options?

Four, not two. Most coverage presents this as “QBO or die,” which isn’t accurate and doesn’t serve clients whose workflow genuinely suits Desktop.

What doesn’t convert from Desktop to Online?

This is the part clients discover after the fact, and it’s where a firm earns its fee by knowing in advance.

Payroll is the worst of it. Desktop and QBO are separate platforms and the payroll data model doesn’t map cleanly:

• Paychecks convert as regular checks — the financial effect is preserved, the payroll detail isn’t
• Payroll item breakdowns don’t convert
• Prior-year employee year-to-date figures don’t convert
• Employee addresses and current YTD balances need manual re-entry
• Liability refunds, payroll adjustments and anything affecting opening balances convert to general journal entries

A firm on an Intuit Community thread described being told everything would transition, migrating, and finding payroll hadn’t come across at all. That is the predictable outcome, not bad luck. Any client with payroll history needs that history exported and preserved separately before the conversion runs, and needs to understand they’re re-establishing payroll rather than moving it.

Also affected:

Hard constraints worth knowing before you start:

• File size ceiling — 750,000 targets. Above it, the standard path is closed and you’re into third-party conversion or splitting the file. What a migration should actually cost covers what changes when you’re outside the free route.
• 60-day import window. After creating the QBO account you have 60 days to import Desktop data. Miss it and you start over with a fresh account.
• Not available on Self-Employed. Simple Start or higher.
• Admin access required on both sides.
• File must be local and single-user. A company file on a network drive or open in multi-user mode will fail the export.

How should a firm sequence twenty migrations?

Nothing in the top ten search results answers this, because they’re all written for someone with one file. Sequencing is the actual work.

Order by risk, not by convenience.

Tier 1 — move now. Clients on Desktop 2023 or earlier who run payroll. Their tax tables are already frozen and every pay run is producing numbers nobody has verified. This is a live compliance problem, not a 2027 problem.

Tier 2 — move this quarter. Clients on 2023 or earlier without payroll. Unsupported, unpatched, no bank feeds. Less urgent than Tier 1, still overdue.

Tier 3 — schedule across the next twelve months. Clients on 2024. Real runway, but they cannot all move in September 2027 and you should not want them to.

Tier 4 — assess separately. Enterprise clients. No deadline, but worth a conversation about direction — including whether QuickBooks is still the right platform at all, which is a different question from where on the QuickBooks ladder they sit.

Then sequence Tier 3 deliberately:

• Simplest files first. You want your first three conversions to be the easy ones, so the team learns the process on low-stakes files.
• Never mid-year with payroll. Convert at a period boundary, ideally year-end, so payroll YTD reconstruction is minimal.
• Never during that client’s busy season. A retailer in November and a tax client in March are both wrong answers.
• Cap concurrency. Two or three at a time. A proper conversion takes two to three weeks — hours for the data transfer, the rest for pre-cleanup, validation and reconnecting bank feeds.
• Leave buffer. Aim to finish by June 2027, not September. Something will slip.

Twenty clients at three at a time, three weeks each, is roughly five months of elapsed time if nothing goes wrong. Starting in mid-2027 doesn’t work.

What does a clean migration actually involve?

Data transfer is a small part of it. The work sits either side.

Before:

After:

One thing to settle before any of this starts: who holds the file and the subscription. A migration is the worst possible moment to discover that question hasn’t been answered.

Keep the Desktop file. Don’t uninstall. It remains your reference for anything the conversion dropped, and the software still opens after end of support. Several practitioners recommend keeping Desktop for historical access and converting only recent years — a legitimate strategy for a long-tenured file.

The short version

• Desktop 2023 support already ended — May 31, 2026.
• Desktop 2024 ends September 30, 2027 and is the final version.
• Enterprise is exempt, still sold and supported, no announced end date.
• The software keeps opening. Payroll tax tables, bank feeds, payments and security patches stop.
• Clients on unsupported versions running payroll are a live compliance exposure, not a future problem.
• Payroll history largely doesn’t convert. Export it before you migrate.
• 60-day import window. 750,000-target file ceiling. Single-user, local file, admin on both sides.
• Two to three weeks per client done properly. Twenty clients is a five-month program, not a September 2027 scramble.

Frequently asked questions