QuickBooks Desktop Enterprise is still sold and still supported, with no announced end date. The discontinuation that generated years of headlines applied to the Pro Plus, Premier Plus and Mac Plus product lines, which Intuit stopped selling to new US subscribers in September 2024. If you are an Enterprise customer, you are not facing a forced migration. What you are facing is a planning question, because the direction of travel for the Desktop family is clear even where the dates are not.
What has actually been announced
Three facts are worth separating from the noise.
New Pro Plus, Premier Plus and Mac Plus subscriptions stopped being sold to new US subscribers in September 2024. Existing subscribers on those products have been able to renew. Intuit’s own notice that QuickBooks Desktop is no longer sold to new US subscribers is the reference here rather than any third-party summary.
QuickBooks Desktop 2023 reached service discontinuation on May 31, 2026. Intuit sets out which connected services end and when in its Desktop service discontinuation policy. After a version’s discontinuation date, connected services stop working. That means payroll, Desktop Payments, bank feeds and security updates. The software continues to open and the data remains readable. What ends is anything that requires Intuit’s servers.
Enterprise is a separate product line and remains available. It is sold, supported and updated, and Intuit has not published an end date for it.
The practical implication for an Enterprise seller is that the urgency is lower than the marketing of every migration vendor suggests, and the planning horizon is still shorter than most Enterprise customers assume.
Why Enterprise sellers stayed on Desktop
Four capabilities kept them there, and none of them have gone away.
Inventory depth is the main one. Enterprise carries advanced inventory features, including multiple locations and lot or serial tracking, that sellers with real warehouse complexity depend on. Sellers who evaluated QuickBooks Online and went back to Enterprise usually did so over inventory.
User role granularity is the second. Enterprise permissions are more detailed, which matters once several people touch the books.
Performance on a large file is the third. An Enterprise file with years of transaction history and thousands of items performs in a way that a browser-based ledger does not always match.
Custom reporting built over years is the fourth, and it is the one that makes migrations painful. Reports built in Desktop rarely transfer.
The five questions worth answering now
1. Which version are you on, and when does it reach discontinuation?
This is the only question with a hard deadline attached. Check the version year against Intuit’s published service discontinuation policy. If a version reaches its date and the business depends on bank feeds or Desktop Payroll, that dependency ends on that date whether or not a plan exists.
2. Can you export a complete backup today?
Not a company file copy. An export of transaction detail, item lists with cost data, and the reports the business relies on, in formats that outlive the software. This is the cheapest risk reduction available and most Enterprise customers have never tested it.
The retention periods in the IRS recordkeeping guidance for small businesses run longer than most software licences, and the obligation to produce a supporting record years from now sits with the business.
3. What is actually connected to the file?
List every integration touching the Desktop file: marketplace sync tools, inventory systems, shipping platforms, payroll. Each one is a dependency with its own roadmap, and some vendors will stop supporting Desktop connections before Intuit does.
For a multi-marketplace seller this list is usually longer than expected, and the marketplace connection is the one that matters most. Amazon, Shopify, Walmart, TikTok Shop and eBay each report settlements differently, and whatever handles that decomposition today needs to keep handling it. Platforms built for this work connect marketplace channels into Enterprise directly, and ConnectBooks is one of them, syncing those channels into QuickBooks Online, QuickBooks Desktop Enterprise or Xero.
4. What would you lose by moving to QuickBooks Online?
Be concrete. For most Enterprise sellers the honest answer includes some inventory functionality, some permission granularity, and every custom report. That is a real loss, and pretending otherwise leads to a migration that gets abandoned halfway.
The counterweight is also real. QuickBooks Online beats Enterprise on accessibility, on the breadth of third-party integrations available, and on not requiring anyone to maintain a server or a hosting arrangement. For a business whose inventory complexity has actually decreased since it bought Enterprise, that trade may now favor Online.
5. Is inventory complexity growing or shrinking?
This is the question that decides the answer. A seller adding warehouses, lots and channels should stay on a system built for depth. A seller who consolidated to one fulfillment arrangement and simplified the catalogue may be paying for Enterprise capability nobody uses.
What a reasonable plan looks like
For an Enterprise seller, the plan is not a migration. It is four items.
Know your version’s discontinuation date and diarize it.
Test a full export this quarter and store it somewhere outside the accounting system. Repeat annually.
Ask every integration vendor, in writing, what their Desktop support commitment is. The answers will vary and some will be vague, which is itself useful information.
Re-examine the inventory complexity question once a year. The reason to stay on Enterprise is capability the business uses. When that stops being true, the calculus changes, and it will change quietly rather than with an announcement.
What not to do
Do not migrate on the strength of a vendor’s urgency. Enterprise has no announced end date and a rushed migration costs weeks of parallel running, a chart of accounts rework, and a month closed twice.
Do not assume a discontinued version is unusable. Discontinuation ends connected services, not the software.
Do not treat Intuit’s published dates as the only constraint. The integration that breaks first is more likely to force your hand than Intuit is.
Anyone weighing a change should confirm version-specific dates against Intuit’s own support documentation rather than a summary, and should involve their accountant before committing to a cutover date. Nothing here implies any relationship between ConnectBooks and Intuit.