If you still double-click the QuickBooks Desktop 2023 icon every morning, you have not been locked out. Your company file still opens. Your reports still run. But since May 31, 2026, every connected service that kept that file accurate, compliant, and safe quietly stopped — payroll tax tables froze on the last rate published that week, bank feeds went dark, direct deposit and e-filing shut off, and security patches ended for good.
That gap between "the software still opens" and "the software is still safe to run your business on" is where small businesses get hurt. A payroll check calculated on a stale table is not a minor inconvenience; it is a withholding error you will have to correct, penalty by penalty. A bank feed that no longer downloads is not just extra data entry; it is a reconciliation blind spot that grows every week. This guide lays out exactly what broke on May 31, what did not, and the checklist to get your books off frozen software without losing data.
What Actually Ended on May 31, 2026 (and What Did Not)
Intuit runs QuickBooks Desktop on a three-year lifecycle. Each version gets updates and assisted support for about three years after launch, then it is retired. QuickBooks Desktop 2021 support ended in May 2024, 2022 in May 2025, and 2023 on May 31, 2026. QuickBooks Desktop 2024 — the last Pro/Premier/Mac Plus release Intuit ever plans to ship — is expected to run through September 2027. After that, QuickBooks Desktop Enterprise is the only desktop accounting product Intuit will continue to sell.
What stopped for Desktop 2023 on June 1, 2026
According to Intuit's discontinuation policy, all of these services through Desktop 2023 were discontinued:
- Payroll tax tables and payroll services — Basic, Enhanced, and Assisted Payroll subscriptions are deactivated. Tax tables stop updating, paychecks no longer calculate taxes automatically, and you cannot send payroll to Intuit for processing, including direct deposits. Outstanding subscription balances are refunded for the unused term, but the service is gone.
- Desktop Payments — Credit card and ACH processing inside Desktop stops.
- Online bank feeds — No new transactions download, and existing connections cannot be refreshed or re-authorized.
- QuickBooks Workforce (formerly ViewMyPaycheck) — Employee access to pay stubs and W-2s through the connected portal stops.
- Online Backup and other hosted services — Automatic online backup through the Desktop integration ends.
- Live technical support — Phone and chat support for 2023 issues is no longer available.
- Critical security patches and updates — No new fixes for vulnerabilities discovered after May 31.
What still technically works
Intuit does not flip a kill switch on your local install. You can still:
- Open existing company files in Desktop 2023
- Enter bills, invoices, journal entries, and manual checks
- Run reports, memorize transactions, and print forms
- Access data in single-user or multi-user mode on your local network
That list is deliberately short. The program will run, but every workflow that relied on Intuit's servers is now a manual process you own — with the risk that comes with it.
Why Frozen Payroll Tables Are a Liability, Not an Inconvenience
This is the most urgent reason to migrate, especially if you run payroll in-house.
QuickBooks Desktop payroll does not hard-code tax rates. Each payroll update delivers new federal tables, state withholding tables, Social Security wage bases, unemployment rates, and form revisions. When support ends, your last downloaded table is the last one you will ever get. Every legislative change after that — a state bracket adjustment, a locality that tweaks its withholding, the annual Social Security wage base reset — will not reach your software.
Running a single payroll on a frozen table creates a real compliance exposure:
- Withholding is wrong from the first check. Even a 0.2% rate change across a dozen employees can create a material under-withholding over a quarter.
- E-filing and e-pay shut down. Desktop 2023 can no longer transmit 941s, 940s, or state returns through Intuit's e-file service, and assisted payroll customers lose automatic tax payments and filings.
- Direct deposit stops processing. Intuit will not process ACH payroll files for a discontinued version, so you would need to fund net pay by paper check or move to an outside provider mid-stream.
- W-2s and year-end forms require manual preparation. Without updated forms and tables, year-end filings will need to be completed in another system or by hand.
The IRS does not waive penalties because your software was out of support. Late or incorrect deposits still trigger failure-to-deposit penalties, and W-2 mismatches still generate notices. If you must run payroll before you migrate, pause Desktop payroll entirely and run it through a standalone provider or payroll service that is still receiving updates — then import the journal entries back into your accounting system.
Dead Bank Feeds and Disconnected Services: The Silent Breakage
Payroll gets the headlines, but bank feeds are where daily bookkeeping quietly breaks.
When live bank feeds stop, you lose:
- Automatic transaction downloads — Every deposit and charge must be hand-entered or imported via manual QBO/CSV files.
- Feed-based matching and rules — Bank rules that auto-categorized recurring vendors will not fire, because there is nothing to categorize.
- Re-feed on connection errors — If a bank connection was already flaky before May 31, you cannot re-authenticate it now to fix it.
Desktop Payments and Online Backup fail the same way. Payments processed through the Desktop integration are no longer authorized, and online backup jobs that depended on Intuit's service will show as failed. Any connected app that authenticated through Intuit's Desktop gateway — time tracking, inventory sync, bill pay — may also lose its link and need to be re-authorized through a different integration after you move.
The practical result is a slow drift between your bank and your books. One week of manual imports is manageable. Three months without a feed is a reconciliation project that takes a full weekend and still misses a fee or refund you would have caught automatically.
The Security Risk You Cannot Patch Yourself
No security updates means every vulnerability discovered after May 31, 2026 remains open on every workstation running Desktop 2023. That includes the Windows components QuickBooks touches — PDF generation, database manager, and network sharing.
If you keep Desktop 2023 on a networked machine that also browses the web or checks email, you are carrying unpatched financial software on an internet-connected box. The mitigations are blunt but effective:
- Move the install to an isolated, non-internet-facing workstation if you must keep it for historical lookup
- Restrict Windows user permissions so only accountants can launch the company file
- Take encrypted local backups to an external drive after every session — you no longer have a cloud safety net
- Plan to go offline entirely for that machine and do all banking on a separate computer
These are stopgaps, not fixes. The fix is to get your active books onto software that still receives patches.
Your Three Migration Paths (and How to Choose)
There is no single right answer, but there are only three viable paths. Pick based on how you work, not just what you already own.
Option 1: Move to QuickBooks Online
This is where Intuit is steering every Pro, Premier, and Mac Plus customer. It is the fastest migration path because Intuit built a direct export tool, and it restores every service that just broke — payroll tables, bank feeds, payments, and mobile access.
Best fit if: you have fewer than 100 employees, you want bank feeds and payroll in one place, and you can work in a browser instead of a desktop app. Trade-offs: subscription pricing is higher than old desktop licenses, and some advanced inventory and job-costing features in Premier and Enterprise do not translate one-for-one. Audit what you will lose before you move (more on that below).
Option 2: Upgrade to QuickBooks Desktop Enterprise
Enterprise is the only desktop product Intuit still sells to new customers after September 30, 2024. Existing Desktop 2023 customers can upgrade to Enterprise and keep a desktop workflow with continued support, payroll, and hosting options. Enterprise 2024 support is expected to run well beyond 2026, and Intuit typically extends Enterprise versions longer than Pro/Premier.
Best fit if: you need advanced inventory (FIFO lots, barcoding, bin locations), have 30+ simultaneous users, or run complex job costing and cannot rework those workflows for Online. Trade-offs: Enterprise is significantly more expensive and still a Windows desktop product — you retain local IT costs and backup responsibilities.
Option 3: Move to a Different Platform Entirely
If you are already bumping against QuickBooks limits — or you want version-controlled, plain-text books you fully own — the discontinuation is a natural moment to evaluate alternatives, from Xero to modern plain-text systems. This path takes more planning because there is no one-click export, but it gives you the most control over data and long-term cost.
Best fit if: you are a developer-friendly shop, you value text-based audit trails and git history, or you want to decouple bookkeeping from a single vendor's lifecycle. Whichever platform you pick, run the same pre-migration checklist below — the steps to protect data are identical.
Pre-Migration Checklist: What to Gather and Clean Before You Click Export
A clean source file migrates cleanly. A messy one carries years of uncleared reconciliations into your new system. Work through this before you export.
1. Pick your cutover date. The cleanest dates are a fiscal year-end, calendar year-end, or quarter-end. Avoid mid-pay-period if possible. If you are mid-year, plan to bring year-to-date transactions so comparative reports still work.
2. Get admin access in order. You need the QuickBooks Desktop Admin user and password, plus admin access to the target system (QBO company admin, Enterprise license manager, or new platform owner). Confirm you can sign in to both before migration day.
3. Run Verify and Rebuild. In Desktop 2023, go to File > Utilities > Verify Data. Fix any errors with Rebuild, then re-verify. A file that fails verification will fail migration.
4. Clean up the data you do not want to carry forward.
- Void or delete stale uncleared checks older than your retention policy
- Clear "uncategorized" bank feed leftovers
- Merge duplicate vendors, customers, and accounts
- Inactivate unused items, classes, and locations you do not want to recreate
- Resolve negative inventory quantities — these often block migration
5. Reconcile everything to a point. Reconcile every bank and credit card account to the last statement before your cutover date. Pay open bills or mark them clearly as unpaid so Accounts Payable transfers correctly. Do the same for open invoices and Accounts Receivable.
6. Snapshot payroll and tax. Run a payroll summary, payroll detail, and payroll liability balance report as of the cutover date. Export employee records, year-to-date wages, deductions, and tax payments made. If you use assisted payroll, request a final payroll register from Intuit before the service is fully deactivated.
7. Document what will not migrate. QuickBooks Online does not import everything. Common gaps include:
- Historical payroll checks as individual transactions (summarized journal entries instead)
- Custom reports and memorized report groups
- Certain inventory costing layers and advanced price rules
- Attached documents — reattach after migration
- Recurring transactions and bank rules — rebuild manually
Note each gap and assign someone to rebuild it.
8. Inventory and sales tax setup. Print your item list, quantity-on-hand valuation, and sales tax liability report. If you collect sales tax in multiple states, screenshot your tax agency setup and filing frequencies so you can recreate them exactly.
9. Back up twice, in two places. Create a local backup (File > Back Up Company > Create Local Backup) and a portable company file (File > Create Copy > Portable company file). Copy both to an external drive and to cloud storage you control. Verify you can restore the backup to a test folder before you proceed.
10. Check your integrations. List every app connected to Desktop — expense capture, time tracking, e-commerce, bill pay, CRM. For each, confirm whether it integrates with your target platform and whether the connection will need to be moved from a Desktop gateway to a cloud API.
Step-by-Step Migration: Desktop to Online Without Losing Data
If you choose QuickBooks Online, Intuit's built-in tool does most of the heavy lifting. The steps are similar whether you are on Pro Plus 2023, Premier Plus 2023, or Enterprise 2022+.
Step 1: Update Desktop to the latest release. Install the final updates available for your 2023 version (Help > Update QuickBooks Desktop). You want the last definitions before the service window closed.
Step 2: Prepare the target company. Create or identify the QuickBooks Online company you will move into. If it already has data, the import will overwrite it — use a fresh company unless you intend to replace everything.
Step 3: Start the export from inside Desktop. As the Admin, open your company file and go to Company > Migrate this company file to QuickBooks Online (Pro/Premier) or Company > Migrate to QuickBooks Online (Enterprise). Choose "Export Your Company File to QuickBooks Online" and sign in to your Intuit account when prompted.
Step 4: Choose what to move. Select the Online company to receive the data and confirm the move. The tool will warn you that existing Online data will be replaced and estimate how long the conversion will take — anywhere from minutes for a small file to hours for a large one with many years of history.
Step 5: Let the conversion run uninterrupted. Do not close either program, do not put the computer to sleep, and do not edit transactions in Desktop while the export runs. If the tool reports errors, note the error codes — they usually point to a specific list item or transaction with special characters or an inventory inconsistency.
Step 6: Validate totals immediately. Once Online reports the import is complete, compare these three reports side-by-side between Desktop and Online as of the cutover date:
- Trial Balance
- Profit and Loss (year-to-date and last fiscal year)
- Balance Sheet
If debits equal credits and retained earnings match, your core ledger moved intact. If not, the variance report will usually isolate the account.
Step 7: Reconnect and rebuild. Reconnect bank feeds in Online (these are new connections, not resurrected Desktop feeds), re-authorize payments, rebuild bank rules and recurring transactions, and reattach documents. Run a test payroll for one employee in the new system before your next real pay run.
Post-Migration Reconciliation Checklist
Do not declare victory after the import finishes. Reconciliation is the real migration.
- Bank and credit card accounts — Re-reconcile every account in Online to the same statement you reconciled in Desktop. Outstanding checks and deposits should match penny for penny.
- Accounts Receivable and Payable — Open the A/R and A/P aging reports and tie each open invoice and bill to a customer or vendor record. The total should equal the balance sheet control accounts.
- Inventory — If you carry inventory, compare quantity on hand and inventory asset value item by item. Online uses FIFO and may value the same quantities differently than Desktop's average cost — note the method change and adjust opening values with a journal entry if your accountant advises it.
- Payroll — Confirm employee year-to-date wages, taxes withheld, and employer taxes match your Desktop payroll summary. Verify that payroll liabilities in Online equal what you actually owe agencies, not just what the import calculated.
- Sales tax — Rebuild tax agencies, rates, and filing settings, then compare the Sales Tax Liability report to Desktop. File the next return from the new system only after the liability ties.
- Chart of accounts and classes — Review account types, detail types, and class/location tracking. Online has different required types for certain accounts (e.g., inventory and sales tax) — correct any type mismatches before you post new transactions.
- Users and permissions — Recreate user roles, set up two-factor authentication, and remove the old Desktop admin share if the machine will stay in service for lookups.
Run parallel for one cycle if you can: keep Desktop in read-only mode for 30 days while you post all new activity in Online, then compare the next month-end close. It is the cheapest insurance against a hidden mapping error.
If You Must Stay on Desktop 2023 for a While: Damage Control
Sometimes the calendar forces you to keep Desktop 2023 alive for a few more weeks — a prior-year audit, a CPA who needs a portable file, or a heavy inventory close that cannot move mid-count. If that is you, treat Desktop as a frozen archive, not an active general ledger.
- Stop running payroll inside Desktop. Use a standalone payroll provider that still receives live tax tables. Post payroll as summarized journal entries instead of individual paychecks.
- Switch bank feeds to manual imports. Download QBO or CSV files from your bank each week and import them through File > Utilities > Import > Bank Data. Reconcile to the statement every time — do not let imported transactions sit uncleared.
- Take full local backups after every session and store them offsite. Test a restore monthly. Without online backup, a single drive failure is a total loss.
- Isolate the machine. If possible, disconnect the Desktop 2023 workstation from the internet after you finish downloads, or block outbound traffic except for the brief windows where you manually import bank files. Use a separate, patched computer for email and web browsing.
- Set a hard stop date. Frozen software gets more expensive every month you keep posting to it. Put the migration on the calendar before the next quarterly payroll filing, not after.
Getting Your Books Ready for Whatever Comes Next
The Desktop 2023 discontinuation is not a sales event; it is a lifecycle event. Every desktop accounting version has an end-of-support date, and every connected service tied to that version ends with it. The businesses that handled May 31 well did two things: they cleaned their data before they moved it, and they verified every control total after.
If you are doing that verification, do it in a system where you can see the entire trail. Good bookkeeping after a migration is not about which logo is on the screen — it is about having a complete, auditable record you can diff, back up, and reconcile without asking a vendor whether the feature is still supported.
Beancount.io is built for that kind of ownership: plain-text, double-entry accounting under version control, where every transaction is a line of text you can review, search, and keep forever. It pairs with Fava for dashboards and reports, and it keeps your history in git so a discontinuation never takes your books with it. Whether you land on QuickBooks Online, Enterprise, or a plain-text ledger for part of your workflow, the same discipline applies — reconcile to the source, keep the backup you can restore, and do not run payroll on a table that stopped updating.
If May 31 caught you by surprise, treat this week as your migration sprint. Back up, verify, export, and re-reconcile. The software will still open tomorrow — but the parts that keep your payroll compliant and your bank feeds honest already closed. Move while your books are still clean.
Simplify Your Financial Management
As you move off discontinued software and rebuild bank feeds, payroll, and reports, it is the perfect time to tighten how you track money. Beancount.io gives you plain-text accounting that is transparent, version-controlled, and built to last beyond any vendor's support window — no black boxes, no forced upgrades. Get started for free and see why businesses that want full control over their financial data are switching to plain-text accounting.