Common symptoms
- You use QuickBooks Desktop Pro Plus, Premier Plus, Mac Plus, or Enterprise 23.0
- Payroll, payments, bank feeds, email, or other connected services stopped working
- You need more time before upgrading or migrating
Before you begin
- Confirm the exact QuickBooks product, year, edition, and license status
- List every connected service and third-party integration the business depends on
- Create and verify a current company-file backup before changing software or computers
Back up your data before changing company-file components, services, firewall rules, or permissions. Never delete the .QBW company file as a troubleshooting step.
1. Understand what ended
Intuit ended support for QuickBooks Desktop 2023 after May 31, 2026. The affected products include Pro Plus 2023, Premier Plus 2023, Mac Plus 2023, Enterprise Solutions 23.0, and the related Accountant editions.
An unsupported installation may still open and perform local accounting tasks, but that does not mean the product is fully functional or secure. Intuit says discontinued versions lose live support, critical security updates, and access to specified connected services.
No firewall rule, antivirus product, or network design can replace security fixes that the software vendor no longer provides.
2. Inventory the services at risk
The practical impact depends on how your business uses QuickBooks. Document the workflows that cross the boundary between the local company file and an Intuit or third-party online service.
- Check whether payroll calculations, forms, filings, or Workforce access depend on QuickBooks Desktop Payroll.
- Identify payment processing, recurring payments, eInvoice, and merchant deposit workflows.
- Record every bank-feed, online banking, accountant-copy transfer, email, shipping, and exchange-rate workflow.
- List add-ons, imports, exports, and integrations that require a particular QuickBooks release.
Confirm service status and migration requirements before relying on an unsupported version for time-sensitive financial activity.
3. Choose a supported destination
The safest long-term answer is a supported product on a supported operating system. The right destination depends on file complexity, multi-user needs, integrations, licensing, and the amount of workflow change the business can absorb.
- Ask Intuit or your license provider which supported Desktop options are available to your account.
- Evaluate QuickBooks Desktop Enterprise and QuickBooks Online against the features you actually use.
- Test a copy of the company file and critical reports before committing to a migration.
- Confirm that payroll, payments, banking, email, and third-party integrations work in the destination environment.
Do not upgrade the only copy of a company file. Test with a protected copy and document the rollback path first.
4. Reduce exposure during a short transition
If the business must temporarily keep QuickBooks Desktop 2023, treat it as a transition state with documented risk—not a permanent secure configuration.
- Run it only on a Windows edition that still receives security updates; avoid an unsupported operating system.
- Apply Windows, browser, endpoint-security, and hardware-firmware updates promptly.
- Use standard user accounts for daily work and reserve administrator access for approved maintenance.
- Allow only the network shares and QuickBooks services that are required; never expose QuickBooks ports or Windows file sharing directly to the internet.
- Keep the QuickBooks host away from routine email and web browsing, and use a properly secured VPN for authorized remote administration.
- Remove unused integrations and internet-facing services after confirming they are not required.
Isolation can reduce opportunities for attack, but it cannot correct vulnerabilities inside unsupported QuickBooks software.
5. Build a recoverable backup plan
Reliable backups are the safety net for software failure, ransomware, file corruption, and a migration that does not go as planned.
- Create scheduled QuickBooks backups and retain multiple recovery points.
- Keep at least one protected copy offline or in storage that ordinary workstation accounts cannot overwrite.
- Verify backups regularly by restoring a copy in a safe test location and opening it.
- Preserve license records, installation media, update files, configuration notes, and a list of connected services.
- Write down who is responsible for checking backup results and responding to failures.
6. Turn the findings into a dated transition plan
Record the current risks, the selected destination, compatibility tests, owners, and a target completion date. A short transition with controls is materially different from leaving unsupported accounting software in place indefinitely.
- Set a decision date and migration or upgrade window.
- Schedule a test conversion and compare key financial reports before and after.
- Plan user training and a fallback window.
- Retire or isolate the old installation after the supported system is verified.
Verify the result
Leave with a documented, recoverable plan.
- Confirm the exact QuickBooks release and operating-system support status.
- Verify that every payroll, payment, banking, email, and integration dependency has an owner and destination.
- Restore a recent backup in a safe test location and confirm the company file opens.
- Record the transition deadline, responsible person, and rollback plan.
Sources and review notes
This guide is independently written and reviewed against the official references below. Product behavior can vary by version and network environment.
Want an expert to take over?
We’ll diagnose, repair, and verify it remotely.
Tell us what you are seeing. We’ll start with the work you have already completed and explain any changes before making them.