QuickBooks Desktop
Desktop is going away.
Your integration
doesn't go with it.
Intuit is retiring QuickBooks Desktop on a rolling schedule. If you run a custom sync against it — a field system, a delivery app, a CRM, anything that writes into your books without a person re-typing it — then that sync does not come across to QuickBooks Online. It gets rebuilt. Most people find this out at the worst possible moment, which is the reason this page exists.
Where it stands
The dates, and
how much to trust them.
I am keeping these in one place rather than sprinkling them through the page, because they move. Intuit has already pushed one of them back. Last checked 23 October 2026.
| Edition | Status | Detail |
|---|---|---|
| New Desktop subscriptions — Pro Plus, Premier Plus, Mac Plus | No longer sold to new US customers | Since 2024. Existing subscribers were not cut off at that point. |
| Desktop 2023 | Support ended | 31 May 2026. When support ends, connected services go with it — bank feeds, Desktop Payroll, Desktop Payments, online payments. |
| Desktop 2024 | Contested | Sources disagree, and Intuit has moved this one once already. Treat any specific date you read as provisional until you have seen it on Intuit's own site. |
| Desktop Enterprise | Still sold, no announced end date | The one edition still available to new customers. That is not a promise about 2030. |
Before you act on any date above, check it against Intuit's own Desktop page. If you find it has moved again, tell me and I will correct this page.
The part that costs money
It's a rebuild,
not a setting.
Desktop and Online are different pieces of engineering. Desktop is reached through the Desktop SDK, exchanging qbXML through the Web Connector — a Windows application running on a machine you own. Online is a REST API over OAuth, reached across the internet, with a different data model on the other side.
Nothing carries over. Not the connection, not the field mapping, not the logic that decides which record is which. Intuit's own guidance to software vendors is to build a separate Online integration and move customers onto it, with each customer re-authorising the connection.
So the accounting migration and the integration migration are two projects, and only one of them shows up in most quotes. If somebody is moving your books and has not mentioned the sync, that is the question to ask today.
Find yourself
What it means
for you specifically.
- You run Desktop Pro, Premier or Mac with a custom integration
- Your integration has a shelf life, and it is shorter than the software's. Plan the rebuild while it is a project rather than an emergency.
- You run Desktop Enterprise with a custom integration
- Nothing is forcing your hand this year. The rebuild still applies the day you move, so it belongs in the plan rather than in a drawer.
- You are already on QuickBooks Online
- This page is not about you. Your integration is on the modern API and is not going anywhere.
- You are thinking about moving to Online
- Budget for the integration separately from the accounting migration. They are two different jobs, and the one nobody budgets for is this one.
What you'd be buying
What the rebuild
actually involves.
Five steps, in this order. Most of the cost is in the first two, which is the opposite of what people expect — the writing of the code is rarely the slow part.
- 01
Work out what the old one actually did
Usually nobody has written this down, and the person who set it up has moved on. This is archaeology — reading the existing sync to find every rule hiding in it, including the ones added at 11pm during a busy month.
- 02
Agree the mapping again, in writing
Online's data model is not Desktop's. Accounts, items, customers and tax all need re-deciding rather than copying, and that is a conversation with whoever owns your books.
- 03
Build against Online, with both running
The new sync gets built and tested while Desktop is still live, so you are comparing its output against something known-good instead of hoping.
- 04
Cut over on a date you choose
Month end is the wrong moment and everyone picks it anyway. The cutover gets scheduled somewhere quiet, with the old system still there for a fortnight.
- 05
Watch it for a month
The failures that matter are the quiet ones. Anything I build reports its own problems, and I stay on it through the first full monthly cycle.
What to do now
Three things,
none of them urgent yet.
- Find out which edition and year you are on. It is in QuickBooks under Product Information. That one fact decides whether this is a this-year problem or a someday problem.
- Write down what currently writes into your books. Not how it works — just what it is and who set it up. Most businesses have more connections than they remember, and the forgotten ones are the ones that break loudly.
- Get the rebuild costed before you are forced into it. A planned rebuild is an ordinary project. The same work done in the fortnight after something stops is the expensive version of itself.
I have spent twenty years on the side of this that bites. If you just want to know whether you have a problem, ring me and I will tell you, whether or not it turns into work.