If your business still runs QuickBooks Desktop, this is a must-read. Intuit is retiring desktop support in stages — and the most important near-term milestone for many companies is May 31, 2026 (the date when support for QuickBooks Desktop 2023 ends). After those dates you’ll lose access to live support, security and tax updates, and in-product services such as payroll, payments and bank feeds.
Below I’ve broken down the timeline, what stops working, and a practical checklist so you (or your accountant) can confidently prepare and migrate before May 2026.
Quick timeline (what Intuit has announced)
-
Stop-sell / no new subscriptions for several Desktop SKUs: Intuit stopped allowing new U.S. subscriptions for some Desktop products (deadline extended to Sept 30, 2024). Existing subscribers could still renew, but new sales were curtailed.
-
Versioned end-of-support (rolling May 31 dates): QuickBooks Desktop versions follow a pattern: 2021 support ended May 31, 2024; 2022 ended May 31, 2025; 2023 ends May 31, 2026 (this is the key date for most users of the 2023 release). After each version’s cutoff you lose integrated services and official support.
-
Payroll & in-product services stop working: When a Desktop version is discontinued, payroll calculation/tax form filing, Online Banking (bank feeds), Payments/merchant features, and other connected services are affected or turned off for that version. Plan for payroll continuity.
What “end of support” actually means for your business
(Short version — what will break)
-
No more live technical support or product updates for that version.
-
No payroll tax updates / filings from in-product Payroll services for discontinued versions.
-
Bank feeds, merchant payments, and other online integrations may stop syncing.
-
No more security patches or critical updates — a potential compliance/security risk.
-
Some features (e.g., eInvoicing, accountant copy transfers or contributed reports) may stop working.
Priority checklist — actions to take now (and why)
Immediate (today — within 2 weeks)
-
Identify which QuickBooks Desktop version you run (Help → About QuickBooks) and record subscription/renewal dates.
-
Make full backups (company file
.qbw, the.nd/.tlgfiles, plus copy the QB backup to an external drive and cloud storage). Keep one immutable, date-stamped archive. -
Export key reports and lists (Chart of Accounts, Customer/Vendor lists, Payroll reports, General Ledger, prior-year tax reports, invoices, bills) to Excel/CSV/PDF for quick reference and for migration.
-
Snapshot integrations — list apps that connect to QuickBooks (payment processors, bank accounts, POS, inventory systems, CRM). You’ll need to reconnect or replace these later.
(Backups + exports keep you operational if a service or integration stops unexpectedly.)
Short term (30–90 days)
-
Decide on a long-term platform — QuickBooks Online (QBO), QuickBooks Enterprise (if still available for your use case), or an alternative accounting system (Sage Intacct, NetSuite, Business Central, Xero, etc.). If you prefer staying “desktop-like”, check whether Enterprise or accountant-grade offerings meet requirements.
-
Talk to your accountant / bookkeeper about migration implications (reports, closing periods, payroll continuity, sales tax history).
-
Test a conversion — use a copy of your company file to run a trial conversion to QBO or another target (most conversions can be tested). This helps spot data mapping issues (classes, inventory, custom fields).
-
Plan payroll fallback: If you use QuickBooks Desktop Payroll, decide whether you'll move payroll to QBO Payroll, a third-party payroll provider, or a payroll service bureau.
Medium term (3–9 months)
-
Execute migration on a test file and resolve discrepancies.
-
Train staff on the new workflow (invoicing, bank reconciliation, reporting).
-
Reconnect integrations and validate bank feeds, payment processing, recurring invoices and payroll runs on the new platform.
-
Run parallel accounting for a month (operate both systems in parallel to confirm numbers match).
Final deadline (by May 31, 2026 if you’re on 2023)
-
Complete migration/upgrade before your version’s end date so you do not lose payroll or bank feed functionality mid-fiscal year. (If you plan more time, begin sooner — conversions and clean-ups often take longer than expected.)
Migration options — pros & cons (short)
-
QuickBooks Online (QBO) — easiest path for many small businesses. Cloud access, regular updates, payroll integration (separate subscription). Conversions are well-supported but some desktop-specific features may not map perfectly.
-
QuickBooks Enterprise — closer to desktop functionality; better for advanced inventory and large file support. Check availability/pricing and whether Intuit continues to support purchases/renewals for Enterprise.
-
Third-party accounting systems — consider if you need strong multi-entity support or advanced ERP features. Migration can be heavier but better long-term fit for scale.
-
Keep Desktop (with mitigations) — some firms keep Desktop and accept reduced support, but this risks lost integrations and security updates over time.
Quick migration / audit checklist (copyable)
-
Version & subscription dates recorded
-
Full QB file backup saved offsite (date stamped)
-
Exported Chart of Accounts, Customers, Vendors, Items, Payroll reports, GL, A/R, A/P to CSV/PDF
-
Inventory valuation snapshot and supporting docs
-
List of third-party integrations with login details
-
Test migration completed on a copy of the file
-
Payroll run tested on new payroll provider before first pay date after migration
-
Staff trained and run parallel month completed
Common mistakes to avoid
-
Waiting until the last week before EOL — migrations and payroll transitions can require several weeks to validate.
-
Migrating without a test run — data mappings (inventory, classes, retentions) often require manual fixes.
-
Forgetting historical access — keep a read-only archival copy and exports for audit/tax reference.
Final notes & where to get help
If your business uses QuickBooks Desktop 2023, your actionable cutoff is May 31, 2026 — plan and execute migration steps well before that date to avoid disruptions to payroll, bank feeds, and support.

No comments:
Post a Comment