What Happens to Your Accounting Records When QuickBooks Desktop Sunsets

Intuit's lifecycle policy gives each Desktop version roughly three years of support from its release date. After that, connected services — payroll, bank feeds, payments, security updates — are turned off. The software still opens. It just becomes an isolated tool.

Here's where things stand:

What about Enterprise?

QuickBooks Desktop Enterprise is the only edition Intuit continues to actively sell. It is not being discontinued as a product line. However, individual Enterprise version-years follow the same three-year rule — Enterprise 22.0 sunset in May 2025, Enterprise 23.0 sunsets in May 2026, and so on. Enterprise also costs significantly more than the Plus subscriptions, with annual prices in the $1,800 to $5,000+ range per user depending on tier.

So "we're on Enterprise" doesn't fully answer the timeline question. The right question is: which Enterprise version year, and when does it sunset?

Sources for these dates

Dates above come from Intuit's own announcement and from the contemporaneous coverage in publications like Insightful Accountant. They are not in dispute. They have not been extended. Treat them as fixed.

This is the part nobody is leading with, and it is the part that should be making the timeline feel urgent right now.

Historical payroll data does not migrate from QuickBooks Desktop to QuickBooks Online. None of it. Not the paychecks, not the YTD totals, not the per-employee history. The QBO migration tool moves your chart of accounts, your customer and vendor lists, your products and services, and up to two years of general transactions — but the payroll detail stays behind in the Desktop file.

This is confirmed by Intuit's own support staff on Intuit's own community forums, repeatedly. The official guidance, when users ask how to access historical payroll data after migrating to QBO, is: maintain an active QuickBooks Desktop subscription, plus an active Desktop Payroll subscription, indefinitely. That is the access mechanism Intuit will sell you.

Now layer that on top of the sunset timeline:

• Your Desktop subscription must remain active to access the file in full mode.
• Your Desktop Payroll subscription must remain active to generate historical payroll reports the way you remember generating them.
• When the version-year you're on hits its sunset date, payroll services shut off even if you've been paying for them.
• Once Desktop 2024 hits its end-of-support date in September 2027, every non-Enterprise customer is on unsupported software with frozen payroll. There is no "next version" to renew into.

And the workarounds that float around the community forums — using a Desktop Enterprise trial license, repeatedly reinstalling trials, or paying for an Enterprise subscription you don't otherwise need just to read old files — are exactly that: workarounds. They are not strategies for keeping records you might be required to produce three, five, or seven years from now.

The good news Intuit's guidance doesn't mention

The official Intuit answer — maintain an active Desktop subscription plus an active Desktop Payroll subscription, indefinitely — is the answer for users who want to keep using QuickBooks' built-in payroll reports. It's not the only answer, and the framing obscures what's actually happening.

Here is what specifically goes away when the payroll subscription lapses:

• The pre-built payroll reports. Payroll Summary, Payroll Detail, Employee Earnings Summary — these are queries QuickBooks runs against the payroll service. Once the subscription stops, the reports stop generating, even though the underlying data is still in your file.
• The structured paycheck-as-an-object view. In the API, a Paycheck is a single record with payroll-item breakdowns (regular wages, overtime, federal withholding, FICA, 401(k), etc.). That structured object is gated behind the payroll subscription. Query it without an active subscription and you get empty or invalid responses.
• Some payroll-service-side artifacts. E-filing receipts, electronically-submitted forms that Intuit retained on their servers but didn't write back into your file — those are subject to Intuit's data-retention policies, not yours. They can disappear.

Here is what does not go away:

Every paycheck QuickBooks ever produced also posted to the general ledger as a set of journal entries. The lines hit the specific accounts each payroll item maps to — wage expense accounts (debits), tax-withholding liability accounts (credits), employer tax expense accounts, 401(k) and benefits liability accounts, and cash (credit for net pay). The dollar amounts are identical to what the pre-built reports show. The employee is tagged on each line. The date is on every line. The doc number is the paycheck number.

The financial substance of every paycheck — gross wages by employee by period, individual tax withholdings, employer-side taxes, deductions, net pay — is preserved in the general ledger. It's just stored as journal-line detail rather than as a pre-built report.

What that means concretely: if the GL is captured into a portable, queryable format while the subscription is still active, the payroll-equivalent detail can be reconstructed from it indefinitely, by anyone, without QuickBooks or Intuit involved. A SQL query against the archive — filtering journal lines by employee, grouping by paycheck date and document number, classifying by account type — produces the same numbers a Payroll Summary report would have produced, sourced from the actual underlying transactions rather than from a service that no longer exists.

That reconstruction is exactly what a sealed archive is designed to support. The archive is a SQLite database with a published, open schema; anyone with SQL access — your CPA, an auditor, an attorney, you — can write the queries.

So the trap is real, but it's narrower than the Intuit-forum framing makes it sound. It's a reports trap, not a data trap, provided the GL gets captured in a form that doesn't depend on QuickBooks to read.

The implication is simple. Whatever migration path you choose, the time to extract a clean, complete, durable copy of your historical GL — including the payroll detail it contains — is while the subscription that lets you do it is still active. Not after sunset. Before.

That extraction is exactly what a sealed archive captures. More on that below.

Most coverage of the sunset frames the choice as "migrate to QBO or upgrade to Enterprise." That's two options. There are four, and the framing matters because the right answer depends on what you actually need going forward — not just which Intuit product you end up on.

Path 1 — Migrate to QuickBooks Online

What it does well: If your business is operationally simple and going to keep operating, QBO is the path of least resistance. The migration tool is built-in, the data transfer takes hours, and you keep a familiar interface and reporting.

What it doesn't do: Move historical payroll. Move more than ~2 years of detailed transaction history in some cases. Replicate certain Desktop-only features cleanly — multi-level inventory assemblies flatten, FIFO inventory costing falls away in favor of average cost, and some industry-specific reports don't exist. Most of all: QBO is a subscription. If you ever lapse, your data is held by Intuit and re-access requires reactivation. After a year of inactivity, the data is deleted.

When this is the right choice: Active, ongoing business; standard accounting needs; you want to keep operating in the Intuit ecosystem; historical payroll preservation isn't a priority (or you're handling it separately).

Path 2 — Migrate to a different platform

What it does well: Xero, Sage, NetSuite, and others can be a better fit if QBO's specific feature gaps matter to your business — particularly inventory-heavy operations or industries QBO doesn't serve well.

What it doesn't do: Make the historical-records problem any easier. Cross-platform migrations carry the same data-loss risks as QBO migrations, often more, because there isn't a vendor-supplied tool. Anything you carry forward gets re-mapped through a third-party tool or manual export-import, and history below a couple of years often doesn't survive the trip.

When this is the right choice: Specific feature requirements QBO can't meet; willingness to invest in a proper data migration project; ongoing business with no need to preserve QB Desktop history in its original form.

Path 3 — Keep using Desktop offline

What it does well: Nothing about the strategy is officially endorsed, but the software does still open after sunset. You can still enter transactions manually, run reports, and access your data on the local machine.

What it doesn't do: Handle payroll correctly (frozen tax tables = wrong filings). Provide bank feeds or payment processing. Receive security updates. Survive a hard drive failure gracefully — there's no live support, no online backup, no professional recovery path. And it doesn't answer the verifiability question at all: any QBB or QBW file can be opened, edited, and re-saved by anyone with the software. There is no way for a future auditor to verify that what they're looking at is what was originally there.

When this is the right choice: Honestly — rarely, and only as a short-term bridge. The risks compound year over year.

Path 4 — Seal the historical record, then start fresh on the new platform

What it does: Captures the complete current state of your QuickBooks Desktop data — every transaction, every balance, every payroll record, the full history — into a cryptographically sealed archive that does not depend on QuickBooks (or any subscription) to read. Then you migrate forward to whatever platform makes sense for the live business, carrying only what you need to keep operating. The historical record is preserved as a verifiable, court-defensible artifact; the live file is freshly cut and clean.

When this is the right choice: When the historical record matters and the cost of losing access to it is high. That includes businesses that are selling (due diligence), winding down (records survive the entity), undergoing transitions in bookkeeping or ownership, in industries with elevated audit risk, or simply that have been on QB Desktop long enough that ten or fifteen years of history matter.

Path 4 isn't an alternative to Paths 1 or 2. It's something you do alongside them. The seal preserves the past; the migration sets up the future. They solve different problems.

A sealed accounting archive does three things a backup file cannot:

1. Captures complete history, not just current state. Every transaction, every balance, every payroll record, every reconciliation, the full audit trail — pulled out of QuickBooks while it's still readable, into a portable, standards-based format that doesn't require QuickBooks to open.
2. Cryptographically proves nothing has changed since capture. The archive is sealed with a SHA-256 cryptographic hash, then time-stamped by an independent authority using the open RFC 3161 standard. Anyone can verify, decades later, that the file is exactly what it was at the moment of capture — using free tools like openssl and standard timestamp verifiers.
3. Stays accessible without depending on any vendor. No subscription. No proprietary software to open it. The archive uses standard SQLite for the data and JSON for the metadata. Any auditor, attorney, or developer can query it directly.

The methodology behind this — called SALT (Sealed Accounting Ledger Technology) — is published openly, so reviewers can understand exactly what the seal proves and what it doesn't. The verification procedure is a plain-language guide written for auditors and attorneys without an engineering background. And the custody model is non-custodial: you hold the only copy of the sealed archive. The provider that produces it doesn't retain a copy, doesn't have ongoing access, and can't be subpoenaed for what they don't have.

That last property matters more than people realize. The buyer of a business, the auditor reviewing returns, the attorney handling a dispute — none of them want a vendor in the middle of the chain of custody. A sealed archive delivered directly to the business owner, with no third party holding a copy, is the cleanest possible answer to "where did these records come from and who has had access to them?"

Regardless of which path you take, do these things now while the subscriptions and services are still active:

1. Confirm your version. Open QuickBooks Desktop, press F2 (or Ctrl+1), and check the Product Information window. The version year is the key date. If you're on 2023, your sunset is May 31, 2026 — weeks from now.
2. Export every payroll report you might need. Year-by-year payroll summaries, employee-by-employee earnings histories, payroll tax payments, W-2 data, 941 filings. Export to Excel and PDF. Save outside the QuickBooks file.
3. Reconcile every bank account through the most recent statement. An unreconciled file is harder to migrate, harder to seal, and harder to defend.
4. Make a fresh backup. A backup file isn't a defensible archive (see above), but it is the starting point for one.
5. Decide your live-books destination. QBO, another platform, or "we're not moving the live books because we're closing the business." This decision drives everything else.
6. Decide whether the historical record matters. If yes — by the framework above — start the conversation about a sealed archive now, while the data is still extractable in clean form.

The thing you cannot do later is extract clean payroll history once your Desktop Payroll subscription is gone. Everything else is harder after sunset, but possible. That one is genuinely time-bounded.