QuickBooks Desktop Discontinued: What to Do Now

The end dates are fixed and public, so start with them rather than the commentary.

Two things follow that most coverage buries.

Your real deadline depends on your version, and the two dates are sixteen months apart. Check your version number before you plan anything.

Your real deadline is earlier than the support date anyway, because migrating during your busy season or against a hard cutoff is how migrations go badly.

The short answer

Check your version, check your file size, then pick a quiet month at least two quarters before your support date. Those three facts determine everything else. The migration is manageable when planned and genuinely disruptive when rushed, and the only variable you control is when you do it.

What "support ends" actually means

The software does not stop working. This is the most common misunderstanding and it causes people to either panic early or relax too much.

What you keep:

• The application opens.
• Your historical data is intact and viewable.
• You can enter transactions locally.

What stops at your version's discontinuation date:

• Payroll. Tax tables stop updating, so calculations become wrong rather than merely old. For anyone running payroll in QuickBooks, this is the hard deadline.
• Bank feeds. Reconciliation becomes fully manual.
• Security updates. An unpatched financial application holding banking details, on a networked machine, is a real exposure rather than a theoretical one.
• Payments processing and other connected services.
• Live support.

Check your file size before anything else

This is the step that changes the entire plan and almost nobody does it first.

Company files exceeding roughly 750,000 targets cannot be converted to QuickBooks Online. Above that threshold, migration is not a conversion at all. You export lists and balances, start fresh in the new system, and keep the Desktop file as a read-only historical archive.

That is a fundamentally different project:

If you are over the limit, the start of a financial year stops being a nice-to-have and becomes close to essential, because you are drawing a line and beginning fresh. That may mean the sensible plan is to wait for the next year start rather than migrate mid-year, which is a scheduling decision you can only make if you check the file size now.

The three destinations

Intuit's migration path assumes QuickBooks Online. That is one option of three, and the default is not always right.

QuickBooks Online. The path of least resistance. Familiar concepts, your accountant already knows it, integrations are plentiful, and the conversion tooling exists. The trade-offs are real: it is a genuinely different product rather than Desktop in a browser, some Desktop features have no direct equivalent, and pricing rose sharply for 2026, with Plus moving from around $90 to $115 a month. Detail in the QuickBooks 2026 price increase.

A different accounting product. Xero and FreshBooks are the usual general-purpose comparisons, with Wave suiting very small operations. Worth evaluating properly, since you are paying the migration cost regardless, and this is the one moment where the switching cost that normally locks you in is being incurred anyway.

A field service or operations platform. This is the one contractors most often should consider and least often do. Jobber, Housecall Pro and ServiceTitan are built around scheduling, dispatch, job costing and invoicing, and they connect to accounting rather than replacing it. If your actual constraint is knowing which jobs made money and which technician is where, an accounting product will not solve it at any tier. We compare these honestly in QuickBooks alternatives for contractors.

The question that sorts these: what is actually slow or painful today? If the answer is bookkeeping, pick an accounting product. If the answer is scheduling, job profitability or chasing quotes, the accounting product was never the bottleneck and moving to a different one will not feel like progress.

The sequence that works

Ordered so that the expensive discoveries happen early rather than late.

Weeks 1 to 2: decide and prepare. Confirm your version and support date. Check the target count. Choose the destination based on what is actually painful. Back up the company file to somewhere independent of the machine it lives on. List every integration touching QuickBooks, including payroll, payments, time tracking, CRM and bank connections, because each one is a separate reconnection task.

Weeks 3 to 4: clean up. This is the step people skip and regret. Merge duplicate customers and vendors, close inactive accounts, standardise naming, resolve outstanding reconciliation items, and clear anything sitting in undeposited funds. Migrating a messy file produces a messy file in a new system, plus a fortnight of confusion about whether the mess was there before.

Week 5: migrate. Run the conversion. Do it at a period end if possible, and never during your busy season. Keep the Desktop file untouched afterwards as the reference copy.

Weeks 6 to 7: validate. Compare trial balance, accounts receivable and accounts payable ageing, bank balances and prior period reports against the Desktop file line by line. Reconnect bank feeds. Test payroll on a single employee before running the full cycle. Rebuild integrations one at a time and verify each.

Ongoing: run parallel briefly. For one cycle, enough to trust the numbers. Not indefinitely, because dual entry produces divergence and nobody maintains it past a few weeks.

Where Desktop and Online genuinely differ

Worth setting expectations, because the most common post-migration complaint is not that Online is worse but that it is different in ways nobody flagged in advance.

Speed feels different. Desktop is a local application operating on a local file. Online is a web application. Experienced Desktop users who navigate by keyboard and muscle memory notice this immediately, and it reads as the software being slow when it is mostly the interaction model changing. It fades in a few weeks; it is very loud in week one.

Some reports do not have direct equivalents. Particularly customised Desktop reports built up over years. Identify the five reports you genuinely run every month, and confirm before migrating that each can be reproduced. Discovering this afterwards is the single most common source of migration regret.

Multi-user works differently. Desktop licenses seats against a file; Online charges per user with role-based access. For some businesses this is cheaper and for others considerably more expensive, and it is worth pricing at your actual headcount rather than assuming.

Inventory handling is not equivalent. If you carry meaningful stock, this needs specific evaluation rather than a general assumption that it will be fine.

Batch entry and keyboard workflows change. Anyone doing high-volume data entry will feel this most. It is a training and process question rather than a blocker, but budget for it.

None of these are reasons to avoid migrating, since the end date is fixed regardless. They are reasons to test with your real workflow during the trial rather than clicking through a demo, and to have the person who does the daily entry present when you do.

A note on your accountant

Involve them at the decision stage rather than after the migration, for three practical reasons.

They may have a preference with real weight behind it. An accountant fluent in one system and unfamiliar with another is a genuine cost or saving depending on which way you go.

They can do the cleanup faster than you can. Reconciliation items, undeposited funds and chart of accounts tidying are their normal work, and the cleanup step is where migrations succeed or fail.

They need to validate the result. Someone has to confirm the opening balances and trial balance match, and that someone should not be the person who ran the migration.

Book their time early. The months approaching each support deadline are exactly when their capacity disappears, and being in the queue ahead of the rush is worth more than any tooling decision on this page.

Mistakes that make this expensive

Waiting for the deadline. Every accountant and consultant in the country is handling the same migrations in the same months. Availability drops and rates rise. Going early is cheaper for reasons unrelated to the software.

Migrating during busy season. A fortnight of uncertain numbers is survivable in a quiet month and genuinely damaging in a peak one. For seasonal trades this dominates the timing decision, which is the same logic as the advertising calendar in the best time of year to advertise HVAC.

Skipping the cleanup. The single largest source of post-migration pain, and the one part entirely within your control.

Assuming integrations reconnect themselves. They do not. Each is a separate task, and the CRM connection in particular deserves care, because a first sync into a fresh file is exactly where duplicate customers get created at scale. The failure modes are in QuickBooks CRM sync problems.

Forgetting the archive. Keep a working Desktop installation and a copy of the file for historical reference and any audit that reaches back. It costs nothing and you cannot recreate it later.

Treating it as purely technical. The people entering data need to know the new workflow before go-live, not during it. Most failed migrations are adoption failures with a technical postmortem.

If you decide to stay until 2027

A legitimate choice on Desktop 2024, provided it is a decision rather than a delay. Conditions:

• You are on 2024, not 2023. The 2023 date is close.
• You have a written date in the calendar for starting the migration, with the same two-to-three-week plan, well before September 2027.
• You are not running payroll on an older version.
• You have a current backup stored off the machine.
• You are not buying new integrations that depend on the Desktop connector, since you would be building on a platform with a fixed end date. That constraint also applies to choosing a CRM, which is why it appears in the best CRM that integrates with QuickBooks.

Staying is fine. Drifting is not, and the difference is whether the date is written down.

The step-by-step version of the migration itself, including the validation checks worth running, is in migrating off QuickBooks. If you are weighing Online against staying on Desktop for the remaining window, QuickBooks Online versus Desktop in 2026 compares them with the end date factored in.