QuickBooks Desktop end of life: what happens to your integrations.
QuickBooks Desktop's end of life gets written about as an accounting decision. For most companies the harder part is the software plugged into the company file, which stops working on a schedule nobody put in the calendar.
Guide Updated 5 min read 3 sources
On this page
The dates, from Intuit
Intuit has published two changes, and they are often confused.
- After September 30, 2024, Intuit stopped selling QuickBooks Desktop Pro Plus, Premier Plus, Mac Plus and Desktop Enhanced Payroll to new US subscribers. Existing subscribers can keep renewing, and QuickBooks Desktop Enterprise was not affected.
- QuickBooks Desktop 2023 was discontinued on May 31, 2026. That covers Pro Plus 2023, Premier Plus 2023, Mac Plus 2023 and Enterprise Solutions 23.0.
Discontinued means the software still opens, and the services around it stop. Intuit's policy lists what goes: live technical support, critical security updates, payroll (tax calculations, forms and filing data), online banking (downloading transactions and sending payments), payment processing, and several smaller services such as sending accountant's copies. Intuit discontinues each Desktop version on a published schedule, so check its discontinuation policy page for the version you run.
What happens to your integrations
Most businesses on Desktop have more plugged into the company file than they realize: a CRM that sends invoices, an e-commerce connector, a time-tracking tool, a payroll or inventory add-on, a reporting tool reading through ODBC, and often a script someone wrote years ago that runs through the Web Connector every night.
Those connections fail in three different ways:
- The integration depended on an Intuit service that has stopped. Anything that relied on bank feeds, payments or payroll data from Intuit stops working the day the service does.
- The vendor drops Desktop support. Add-on vendors follow Intuit's schedule, and many have already moved their development to QuickBooks Online.
- You move to QuickBooks Online and the integration can't come with you. Desktop integrations speak Intuit's Desktop SDK, usually through the Web Connector. QuickBooks Online has a different API, different authentication and a different data model. There is no switch that converts one into the other.
Intuit's migration tool moves the accounting data. Each integration then has to be reconnected or rebuilt, and that work is easy to leave out of the plan.
Four options, and who each one suits
| Option | Suits | What it means for integrations |
|---|---|---|
| Upgrade to a supported Desktop version | Companies that need Desktop-only features and want time | Integrations usually keep working, until that version's own discontinuation date |
| Move to QuickBooks Online | Most small and mid-sized companies | Every integration is replaced with a QuickBooks Online version or rebuilt on its API |
| Move to a larger system, such as NetSuite or Dynamics 365 Business Central | Companies that have outgrown QuickBooks, with several entities, heavy inventory or complex revenue rules | A migration project, with integrations rebuilt against the new system |
| Stay on an unsupported version | Nobody, for long | No security updates, no bank feeds, no payroll updates, and add-ons that stop one by one |
If you're moving to QuickBooks Online
Four things differ enough to plan for.
- Some Desktop features, such as sales orders and parts of Enterprise's advanced inventory, have no direct equivalent in QuickBooks Online. Map how each is used before you move, so the workaround is chosen deliberately.
- Desktop companies often lean on custom fields that integrations fill in. Check how each one maps to QuickBooks Online before you move, because they don't carry over one-to-one.
- Reading data now has a price. Since July 2025, apps connect to QuickBooks Online under Intuit's App Partner Program, which leaves data written into QuickBooks unmetered and meters data read out of it (queries, reports and the change feed) beyond each tier's allowance. An old Desktop sync that re-read everything every night becomes a running cost if it's rebuilt the same way on Online.
- QuickBooks Online connections use OAuth tokens that have to be refreshed. An integration that isn't monitored can lose its connection and stop syncing without anyone noticing.
A migration plan that doesn't lose a month-end
- Inventory every connection. List each app in the Web Connector, each add-on, each ODBC connection and each export someone runs by hand. For each one, write down who owns it, what it reads and writes, and whether a QuickBooks Online version exists.
- Decide per integration. Use the vendor's Online version where it exists and fits. Rebuild only what doesn't have one, or what the vendor version can't do.
- Migrate into a test company first. Move a copy of the data, connect the new integrations to it, and run a normal week of transactions through them.
- Run one month-end in parallel. Close the month in both systems and reconcile the totals. Differences found here are cheap; differences found by an auditor aren't.
- Cut over, then watch closely. Monitor every integration daily for the first month: failed syncs, duplicate records and totals that disagree.
Questions to ask each add-on vendor
Send every vendor whose product touches your company file the same five questions, and keep the answers with your migration plan:
- Does your product support QuickBooks Online, and is it the same product or a different one?
- Which fields and records does the Online version sync, and which ones from our Desktop setup does it drop?
- Can you move our history and settings, or do we start again?
- Until what date will you support the Desktop version we run?
- Does your Online version read from QuickBooks often, and will Intuit's App Partner Program fees be passed on to us?
The answers decide which integrations need rebuilding, and they often surface a cost that wasn't in anyone's budget.
Where we fit
We rebuild the integrations that don't have a ready-made replacement, and we build them for QuickBooks Online's current rules: writing more than reading, listening for changes instead of polling, and reconciling daily. Our QuickBooks integrations page covers how. If the move is really a sign you've outgrown QuickBooks, our NetSuite integrations page is the next step.
If you only need the accounting data moved and no integrations are involved, Intuit's own migration tool and your accountant are the right people for the job, and you don't need us.
Sources
- Intuit: QuickBooks Desktop to stop selling to new US subscribers
- Intuit: QuickBooks Desktop 2023 service discontinuation policy
- Intuit: API classification for the Intuit App Partner Program
The Automation Audit
One workflow you name, mapped end to end, with the arithmetic done before anyone writes code.
- Scope
- One workflow you choose, traced end to end, including the steps nobody documented.
- Duration
- Two weeks, fixed.
- Fee
- Fixed, and quoted in full before we start. No hourly drift.
- You get
- A written map: what can be automated, what it would save in hours, what building it would cost, and what we would leave alone.
- You keep it
- The map is yours whether or not you hire us to build anything.
And if the audit shows the automation will not pay for itself inside twelve months, we will tell you, and we will not quote the build.
