QuickBooks Desktop Discontinued: Full Sunset Timeline Through 2027

QuickBooks Desktop is being discontinued in phases, not all at once. Intuit stopped selling new subscriptions for QuickBooks Desktop Pro Plus, Premier Plus, Mac Plus, and Enhanced Payroll to U.S. customers after September 30, 2024. QuickBooks Desktop 2024 is the final version — there will be no 2025, 2026, or 2027 releases. Support for Desktop 2024 runs through September 30, 2027. After that date, every non-Enterprise Desktop user will be on unsupported software with frozen payroll tables, dead bank feeds, and zero security patches.

QuickBooks Enterprise is not being discontinued. It continues to be sold and supported with no announced end-of-life date.

If your finance team runs on Desktop today, the real question is not whether the app opens tomorrow. It is whether payroll, bank feeds, payments, support, and security updates keep working long enough for you to control the migration instead of being forced into one at quarter-end. This guide covers the exact dates, what stops working, the real limitations of migrating to QuickBooks Online, and what to do if your business has outgrown the QuickBooks ecosystem entirely.

QuickBooks Desktop Discontinued: The 2024–2027 Sunset Timeline

Two terms get mixed together in most search results: stop-sell means Intuit no longer sells new subscriptions for a product, while service discontinuation means the version loses live support, connected services, and security updates. Those are separate events, and planning gets messy when teams treat them as the same deadline. (quickbooks.intuit.com)

Intuit follows a rolling support window for Desktop versions. When a version falls outside that window, it loses access to connected services. Because no new versions will be released after 2024, the rollout has a hard end.

Date	What Happens	Who It Affects
May 31, 2024	Support ended for QBDT 2021 (Pro, Premier, Enterprise 21.0, Mac)	Teams still on 2021
September 30, 2024	Intuit stopped selling new U.S. subscriptions for Pro Plus, Premier Plus, Mac Plus, and Enhanced Payroll. Existing subscribers can still renew. Enterprise was excluded.	New U.S. buyers
May 31, 2025	Support ended for QBDT 2022 (including Enterprise 22.0) — no updates, payroll, bank feeds, or live technical support	Teams still on 2022
May 31, 2026	Support ends for QBDT 2023 (including Enterprise 23.0) — same consequences	Teams still on 2023
September 30, 2027	Support ends for QBDT 2024 — the final non-Enterprise Desktop version	Teams on 2024

This timeline is sourced from Intuit's rolling discontinuation schedule.

One nuance on the 2024 end date: Intuit's public materials are clearer on "last annual platform release" and "supported through 2027" than on the exact final date. Official community replies and current industry sources consistently point to September 30, 2027. For planning, treat that as the deadline. (quickbooks.intuit.com)

How to check your version: Open QuickBooks Desktop, press F2 (or Ctrl+1), and check the Product Information window. Your version year and release number appear at the top.

What Happens After the Sunset Date? (The Risks of Doing Nothing)

The software doesn't brick. You can still open your company file, enter transactions manually, and run reports. But everything that talks to the outside world shuts off. Here is exactly what breaks:

• Payroll stops updating. Tax tables freeze at whatever rates were current when support ended. Withholding calculations use outdated rates. If you run payroll through Desktop, your W-2s and quarterly 941 filings will have wrong numbers. This is a compliance problem, not just a software annoyance.
• Bank feeds disconnect. Automatic transaction imports from your bank stop entirely. Open Banking APIs and direct connect services require active security certificates that Intuit revokes on the sunset date. Your accounting team will be forced to manually download and import QBO/CSV files from your bank for reconciliation.
• Payment processing ends. Credit card processing, ACH payments, and online invoice payments all require active Intuit service connections. If customers pay you through QuickBooks, that channel closes.
• Security patches stop. Your financial data sits on software that won't get patched against new vulnerabilities. For businesses handling customer payment information or storing sensitive financial records, this creates real compliance exposure.
• Technical support ends. If your company file corrupts or you hit a data error, Intuit won't help.
• Reinstallation may fail. Intuit will not allow new activations or license validations for discontinued versions. If you try to reinstall QuickBooks Desktop on a new computer after support ends, you may encounter difficulties registering it.

On the IT side, QuickBooks Desktop 2024 requires a 64-bit Windows install, supported Windows editions, and TLS 1.2 for connected services. Intuit does not support Linux, emulators, or virtual environments. (quickbooks.intuit.com) If the strategy is to keep an old server alive one more year, that strategy carries its own operating risk.

For a deeper look at financial data risks during any accounting system move, see our Accounting Data Migration Checklist.

Is QuickBooks Enterprise Being Discontinued?

No. Desktop Enterprise remains fully supported with no announced end date. Enterprise is the most powerful edition in the QuickBooks Desktop family and the only Desktop version Intuit still sells to new customers.

But saying "we're on Enterprise" does not fully answer the timeline question. Enterprise version-year sunsets still apply. Enterprise Solutions 22.0 was included in the May 2025 discontinuation, and Enterprise Solutions 23.0 is included in the May 2026 discontinuation. You need the exact version number, not just "Enterprise." (quickbooks.intuit.com)

Staying on Enterprise comes with rising costs. Annual subscription pricing for QuickBooks Desktop Pro Plus and Mac Plus rose from $999 to $1,149 for single-user licenses, with multi-user pricing climbing from $200 per seat to $230 per seat. Enterprise pricing starts at approximately $1,740/year for a single-user Silver plan and climbs from there — $1,873–$5,364+/year (and rising) depending on tier and user count. Based on 2023–2025 changes, subscription increases have been in the 10–15% range per year.

Do not choose Enterprise unless you specifically need advanced inventory with multi-location tracking, barcode scanning, more than 25 concurrent users, sales orders with backorder management, or ODBC connectivity. If you don't need any of these, Enterprise is an expensive way to stay in familiar territory.

As of early 2026, the trajectory is clear — Intuit's revenue is shifting to cloud, Desktop pricing keeps climbing, and Enterprise is the last product standing in a deprecated category.

QuickBooks Desktop to Online Migration: The Technical Limitations

Intuit positions QuickBooks Online (QBO) as the default upgrade path. The native migration tool is free. But the tool has hard constraints that break real-world migrations, especially for companies with years of transaction history.

The target limit

"Targets" are QuickBooks' internal unit of measurement — every transaction, customer, vendor, account, and line item counts as a target. Intuit's current documentation states the governing import limit for current Desktop variants is 4,000,000 targets, and the Accountant Batch Migration Tool requires files 5 GB or smaller. File size in megabytes does not gate the standard import — it is the target count that matters. (quickbooks.intuit.com)

A mid-market company with 10+ years of transaction history can still exceed the target ceiling. If your file exceeds QuickBooks' size limits, you must use the Condense Data Utility in Desktop or start fresh in QuickBooks Online by importing only your lists. "Starting fresh" means losing your historical transaction detail.

If you try to squeeze under the limit by condensing the file, do it on a copy. Intuit warns that reports may not match after condensing. That makes condense a tactical workaround, not a casual cleanup step on your only copy of the books. (quickbooks.intuit.com)

The 60-day import window

You have 60 days after creating a QBO account to import Desktop data — miss that window and you'll need to start over. This is a frequently overlooked constraint that catches teams who set up QBO early but delay the actual data transfer. Do not create the QBO company until you are ready to import.

Features that don't survive the move

QBO and QuickBooks Desktop are built on different platforms. Several Desktop workflows have no direct equivalent in QBO:

• Inventory assemblies: Multi-level assembly items (bill of materials) don't transfer correctly. QBO supports only basic "bundle" items. Intuit's own docs confirm that assemblies become single inventory items on sales transactions, and item hierarchies preserve only up to five levels. QBO also allows only one default A/R and one default A/P account. (quickbooks.intuit.com)
• Inventory costing method: If you track inventory in QuickBooks Desktop using Average Cost method, you'll be switched to FIFO (First In, First Out) once you migrate to QuickBooks Online. This change can affect your cost of goods sold and may have tax implications.
• Sales orders: Intuit has recently added native sales order functionality to QBO Plus and Advanced plans, and open/closed sales order transactions do move during migration. (quickbooks.intuit.com) However, you can only convert an estimate into an invoice and turn a sales order into the latter item — QBO's sales order workflow does not match Desktop's full estimate-to-sales-order-to-invoice pipeline.
• Backorder tracking: Desktop Premier (Manufacturing & Wholesale edition) and Enterprise support partial fulfillment and backorder columns. QBO does not.
• Payroll history detail: Historical paychecks convert to regular checks. The detailed breakdown (item, rate, deduction) is lost. You must rely on your QBDT records for this history. Payroll is its own separate migration workstream — Intuit documents a separate IIF-based flow for payroll data with a 180-day import window. (quickbooks.intuit.com)
• Budgets, units of measure, bank feed setup: Do not transfer. (quickbooks.intuit.com)
• Custom and memorized reports: Need to be rebuilt manually in QBO. The Audit Trail does not move either.
• Multiple company files: QBO requires separate subscriptions for each company file. If you run five entities in Desktop, that's five QBO subscriptions.
• Cash-basis reporting: Intuit says accrual-basis reports should match Desktop, while cash-basis reports may not. Controllers should use accrual as the first post-migration truth test. (quickbooks.intuit.com)

Intuit also flags a sales-tax edge case: migrated tax payments can apply to the wrong filings and should be deleted and recreated in QBO.

For a full breakdown of what goes wrong when financial data moves between systems, see 7 Costly Mistakes to Avoid When Migrating Financial Data.

Alternatives to QBO: When You've Outgrown QuickBooks

If your business has multi-entity structures, complex inventory, revenue recognition requirements, or more than 25 users, QBO may not be the right destination regardless of cost.

QuickBooks Online (when it fits)

QBO is genuinely the right move for businesses that:

• Have fewer than 25 users
• Don't rely on backorder tracking or assembly builds
• Use FIFO inventory costing (or don't track inventory at all)
• Need remote access and real-time collaboration
• Can tolerate rebuilding custom reports

For straightforward service businesses, professional firms, and small retailers, QBO works. Don't over-engineer the move if the shoe fits. Note that not every QBO plan has the same feature set — native sales orders are only in QBO Plus, QBO Advanced, or Intuit Enterprise Suite. (quickbooks.intuit.com)

Staying on Enterprise (buying time)

Upgrading to Enterprise buys you runway. You keep sales orders, assemblies, advanced inventory, and job costing. But you're paying a premium that's rising ~10–15% annually, and you're betting that Intuit won't deprecate Enterprise before you're ready to move.

Intuit Enterprise Suite

Intuit's newer cloud offering targets businesses that need multi-entity management, shared charts of accounts, intercompany allocations, and consolidated reporting while staying in the Intuit ecosystem. This is the clearest cloud step-up inside Intuit's current portfolio. (intuit.com)

Mid-market cloud ERPs

For companies that have truly outgrown QuickBooks:

• Sage Intacct — Strong for multi-entity consolidation, nonprofit accounting, and dimensional reporting (departments, locations, funds). Best fit for finance teams that need reporting flexibility without enterprise ERP overhead.
• Microsoft Dynamics 365 Business Central — Natural fit if you're already in the Microsoft stack. Handles manufacturing, distribution, and project accounting. Steeper learning curve but significantly more scalable than QBO. See our NetSuite to Business Central technical guide for a sense of the architecture.
• Oracle NetSuite — The incumbent cloud ERP for high-growth companies. Strongest in multi-subsidiary, multi-currency environments. Highest implementation cost of the three, and vendor lock-in is real.

Moving to an ERP introduces a major architectural shift: translating a segmented Chart of Accounts into a dimensional one. Instead of creating a new GL account for every combination of Department and Expense (e.g., 6000-Marketing-Software), modern ERPs use a base account (6000) tagged with dimensions (Marketing). This structural translation makes native export tools useless — you cannot push a Desktop .QBW file into an ERP without heavy data mapping and transformation.

The expensive mistake is doing a quick QBO move now and an ERP replatform a year later because the first target was undersized.

How to Migrate Historical Financial Data Without Loss

The hardest part of leaving QuickBooks Desktop isn't picking a destination — it's getting the data out intact. Financial data is relational. An invoice links to a customer, a payment, a GL entry, and potentially a job. Break those links and you get orphaned records, mismatched balances, and an audit trail that doesn't reconcile.

Why DIY CSV exports fail

The standard approach — export reports to Excel, clean them up, import into the new system — sounds reasonable until you try it at scale:

• Flattened relationships. CSV exports produce flat tables. The link between Invoice #4521, Customer "Acme Corp", Payment #8830, and GL account 4000 doesn't survive as a relational structure. The new system knows the customer owes $1,000 and paid $1,000, but it does not know which payment applies to which invoice. You get an aging summary full of unapplied credits and open balances.
• Truncated fields. QuickBooks Desktop memo fields, long descriptions, and custom field data frequently get truncated or dropped during Excel export.
• No audit trail. A stack of CSV files doesn't prove chain-of-custody from the old system to the new one. If your auditor asks "show me that the opening balance in the new system matches the closing balance in the old system, transaction by transaction," CSVs don't answer that question.
• Scale problems. A company with 15 years of history might have 200,000+ transactions across AR, AP, GL, payroll, and inventory. Manual reconciliation of CSV imports at that volume is a multi-week project that still produces errors.

For guidance on what to bring forward versus what to leave behind, see What Data Should You Actually Migrate to Your New ERP?

The tiered data strategy that works

1. Tier 1 — Active data (must migrate). Open invoices, unpaid bills, current customer/vendor records, active inventory items, open purchase orders, current-year payroll YTD totals. This data goes into the new system as live, transactable records.
2. Tier 2 — Reference data (archive with access). Closed transactions from the last 2–3 fiscal years. Needed for audit, tax prep, and dispute resolution. Archive in a queryable format — a read-only QuickBooks Desktop installation, a structured database export, or a reporting warehouse.
3. Tier 3 — Cold storage. Transactions older than 3–7 years (depending on your retention policy). Back up the original .QBW file and store it securely. You can reinstall an old Desktop version to open it — though license reactivation may be an issue post-sunset.

Extract via database, not CSV

QuickBooks Desktop runs on a Sybase SQL Anywhere database. Direct extraction from this database preserves the exact relational keys linking a payment to an invoice to a specific GL account — relationships that CSV exports destroy. This approach bypasses the native migration tool's target limits entirely.

Before loading data into the target system, map your legacy items to the new architecture. If moving to QBO, restructure assemblies and account for the FIFO costing switch. If moving to an ERP, map your segmented accounts to dimensions.

Review the common pitfalls in 7 Costly Mistakes to Avoid When Migrating Financial Data.

Planning a Zero-Downtime Migration Off QuickBooks Desktop

The window between "my version is still supported" and "everything is broken" is narrower than most teams expect. Here's the practical sequence:

1. Inventory your current state. Press F2 in QuickBooks Desktop. Note your version year, target count, file size, and which connected services (payroll, bank feeds, payments) you use. This determines your constraint profile. "Desktop" is not specific enough — 2023 vs. 2024 changes the timeline, and payroll or bank feeds change the cutover risk.

2. Pick a destination based on workflows, not features. Map your actual daily workflows — invoicing, purchase orders, payroll runs, bank reconciliation, reporting — against the target platform. Don't compare feature checklists; test whether your real processes survive the move.

3. Don't create QBO prematurely. The 60-day migration clock starts when the QBO company is created. Pick the target and scope the data first. If you need to condense or sync attachments, do it on archived copies before creating the target company.

4. Clean before you move. Remove inactive customers, vendors, and items. Write off stale receivables. Reconcile all bank accounts through the current period. The cleaner your Desktop file, the less painful the migration.

5. Run a trial migration. Export a copy of your data to the target system. Reconcile the accrual trial balance, AR aging, AP aging, inventory valuation, and sales-tax liability between old and new. Every dollar must match before you cut over. If payroll is in scope, add year-to-date payroll liabilities and sample paycheck tracing to the QA pack.

6. Cut over at a fiscal boundary. The cleanest migrations happen at month-end or quarter-end. Close the period in Desktop, migrate, and open the new period in the target system. This gives your auditor a clear demarcation point. If payroll is in scope, move before the unsupported version cuts off tax calculations — not after. (quickbooks.intuit.com)

7. Run parallel for 30 days. Keep Desktop accessible (read-only) for at least one full accounting cycle after go-live. Compare reports side by side. Only decommission Desktop after your team and your accountant are satisfied.

The point is not to rush into QBO or ERP blindly. The point is to move while you still control the shape of the data and the timing of the cutover.

At ClonePartner, we've completed 1,200+ data migrations across accounting, CRM, helpdesk, and ERP systems. For QuickBooks Desktop exits specifically, we use direct database extraction and API-based loading to bypass the native tool's target limits, preserve relational links between invoices, payments, and customers, and deliver a reconciled, audit-ready cutover. We handle complex data transformations — mapping multi-level assembly items, translating segmented accounts into ERP dimensions, and maintaining SOX-compliant audit trails. If you're staring down a sunset deadline and need the data moved right, we can help.

For a complete preparation plan, review our Accounting Data Migration Checklist: The 10-Point Plan.