Export or back up the relevant data first. Do not delete, void, unreconcile, or adjust historical transactions unless you understand the accounting impact.
Menu names can change. We link current first-party instructions so you can confirm product behavior before acting.
QuickBooks Desktop remains a locally installed, company-file accounting system, but product availability and connected-service support depend on edition and subscription status. Treat Enterprise as a separate current-sales path, verify the exact year and license in Product Information, keep tested backups outside the workstation, and decide on upgrades or migration from workflow evidence—not fear of a deadline.
Best for: current Desktop users, buyers evaluating Enterprise, and teams planning an upgrade, hosted environment, or Online migration
What this guide covers—and what it does not
The page owns one search intent: understanding and managing QuickBooks Desktop as a product. Related jobs have their own canonical guides so you can move between them without mixing product selection, setup, troubleshooting, and migration advice.
- This hub owns the broad QuickBooks Desktop product intent; individual error codes stay in Hotfixes.
- Enterprise selection, remote hosting, upgrades, backups, and Desktop-to-Online migration each have deeper canonical guides.
- It does not provide license keys, downloads, activation workarounds, or unofficial support phone numbers.
Evidence-first workflow
Inventory the installation before choosing a path
A Desktop decision is only as reliable as the version, license, file, users, integrations, and connected services recorded at the start.
- 1
Identify
Record edition, release, license type, host computer, company-file path, and active users.
Evidence: Product Information and a file-location record agree.
- 2
Protect
Create a verified backup and preserve installation media, credentials, templates, and integration settings.
Evidence: A test restore opens outside the live file location.
- 3
Evaluate
Compare staying, upgrading, Enterprise, hosting, and Online against required workflows.
Evidence: A written scorecard includes blockers and total operating cost.
- 4
Validate
Test the chosen path on a copy and compare financial and operational reports.
Evidence: Owner-approved totals and workflows pass before cutover.
Decision control
Choose from evidence, not a feature list
Use the same four gates for understanding and managing QuickBooks Desktop as a product: define the job, surface constraints, choose the smallest workable option, then verify the records.
Which QuickBooks Desktop path fits?
Start from operating requirements and support facts. A familiar interface is useful, but it does not outweigh an unsupported service or a workflow the edition cannot control.
| Your situation | Direction | Why |
|---|---|---|
| Existing supported installation meets every need | Stabilize and document | Avoid unnecessary conversion while improving backups, access control, and close procedures. |
| Advanced inventory, pricing, permissions, or scale is required | Evaluate Enterprise | Enterprise is positioned separately from Pro, Premier, and Mac and must be tested against the exact workflow. |
| Remote access is required but Desktop workflows must remain | Evaluate authorized hosting | Hosting changes access and infrastructure; it does not turn Desktop into QuickBooks Online. |
| Browser access and connected collaboration matter most | Pilot QuickBooks Online | Online is a different product, so feature and report parity must be proven before migration. |
Separate edition, release year, license, and support status
“QuickBooks Desktop” is an umbrella term. Pro, Premier, Mac Plus, and Enterprise do not share the same feature set, licensing path, or current sales status. Open Product Information in the installed application and record the full product line and release before using any upgrade or support instruction.
Intuit stopped selling new US subscriptions for several non-Enterprise Desktop products after September 30, 2024, while Enterprise remains separately available. Existing-user rights and connected-service availability can vary, so verify the current first-party policy for the exact subscription rather than inferring that every Desktop installation has stopped working.
- Product and release shown in Product Information
- Subscription or perpetual-license evidence
- Payroll, payments, bank feeds, and other connected services in use
- Windows version, server role, and multi-user topology
Treat the company file as a controlled accounting database
The QBW file, its supporting network configuration, and attached documents are operational records—not ordinary office documents. Keep the live file in a supported local or server location, restrict folder permissions, avoid consumer sync folders for the open file, and document which computer hosts multi-user access.
A backup is useful only after a restore test. Retain dated copies outside the production workstation, record the last successful verification, and include attachments and external documents that are not necessarily contained in the company backup.
Do not rename network descriptor files, rebuild data, condense history, or move a live file until a verified backup and rollback point exist.
Use a weighted scorecard for stay, upgrade, host, or migrate
List the transactions, reports, custom forms, inventory methods, payroll dependencies, user roles, add-ons, and close controls that must survive. Weight each requirement by business impact, then run the same test cases in every candidate environment.
Include downtime, training, parallel operation, backup responsibility, integration replacement, and historical-data access in the cost. The lowest subscription quote can be the most expensive option if it removes a critical workflow or creates a manual reconciliation every month.
- Must-pass workflow scripts with named owners
- Report comparison at the same dates and accounting basis
- Integration input, output, failure, and duplicate tests
- Cutover, rollback, retention, and post-launch support plan
Use the narrow guide for the job
For a version change, use the Desktop upgrade guide. For remote infrastructure, use the hosting guide. For file protection, use the offsite-backup guide. For a browser-product move, use the Desktop-to-Online migration guide. Error-code and network symptoms belong in Hotfixes because their diagnostic evidence differs from product selection.
This separation prevents conflicting instructions and makes it clear which page is responsible for keeping time-sensitive product facts current.
Completion checklist
Do not call the decision or setup complete until someone independent of the initial change can verify these items.
Frequently asked questions
Is QuickBooks Desktop discontinued?
That statement is too broad. Intuit stopped new US sales of several non-Enterprise Desktop subscriptions after September 30, 2024, while Enterprise remained separately offered. Existing installations, renewal eligibility, and connected services depend on the specific product and status.
Does QuickBooks Desktop require internet access?
Core Desktop work is locally installed, but activation, updates, payroll, payments, bank services, remote hosting, and some integrations can require internet access. Document which connected services your company actually relies on.
Should every Desktop company move to QuickBooks Online?
No. The products differ. A move is justified when the target passes required transaction, reporting, user, inventory, payroll, and integration tests and the collaboration benefit outweighs conversion effort and lost features.
Still comparing adjacent tasks? Use the complete guide library to find the one page that owns your intent.
Optional free utilities
Tools that support this workflow
These run in your browser and can help prepare or inspect files. They do not replace reconciliation, source-document review, or an accountant’s approval.
Sources checked
First-party product documentation used to verify the workflow and risk notes in this guide.