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 hosting runs the Desktop application and company file on remotely accessed infrastructure; it is not QuickBooks Online. Verify product and user licensing, hosting authorization, provider responsibilities, identity security, backup and restore tests, application and integration support, measured latency, incident response, total cost, data export, and exit before moving the live file.
Best for: teams that need remote access while retaining Desktop or Enterprise workflows
What this guide covers—and what it does not
The page owns one search intent: evaluating remote hosting for QuickBooks Desktop. Related jobs have their own canonical guides so you can move between them without mixing product selection, setup, troubleshooting, and migration advice.
- This page owns hosted Desktop evaluation and control.
- Enterprise product selection belongs to the Enterprise guide.
- Local network errors and RDS setup have dedicated technical guides and Hotfixes.
Evidence-first workflow
Pilot the hosted environment with a restored copy
Test business workflows, infrastructure controls, and provider response before cutover.
- 1
Design
Define users, locations, devices, edition, apps, printers, scanning, files, security, and service levels.
Evidence: Responsibility matrix names customer, host, Intuit, bank, and app duties.
- 2
Restore
Place a verified recent backup in the proposed environment without moving the live file.
Evidence: File integrity, permissions, attachments, and paths are confirmed.
- 3
Test
Run peak multi-user work, reports, printing, exports, integrations, backup, and recovery.
Evidence: Timing and failure results meet written thresholds.
- 4
Cut over
Freeze the source, move the approved file, validate totals, and monitor access and performance.
Evidence: Rollback and provider escalation contacts are active.
Decision control
Choose from evidence, not a feature list
Use the same four gates for evaluating remote hosting for QuickBooks Desktop: define the job, surface constraints, choose the smallest workable option, then verify the records.
Hosted Desktop, local Desktop, or Online?
The applications, support boundaries, and control models are different.
| Your situation | Direction | Why |
|---|---|---|
| Desktop-only workflow is required across locations | Evaluate hosting | Remote delivery can preserve the Desktop application while centralizing infrastructure. |
| Single office has stable local operations | Compare managed local infrastructure | Hosting cost and complexity may not add enough value. |
| Browser and mobile collaboration are primary | Pilot QuickBooks Online | Native cloud behavior may fit better, subject to feature and report parity. |
| Poor connectivity is common | Stress-test or retain contingency | Hosted work depends heavily on reliable network access and latency. |
Write a provider responsibility and licensing matrix
Identify who supplies and supports QuickBooks licenses, Windows, hosting, Microsoft applications, printers, scanners, integrations, backups, security monitoring, user administration, updates, file repair, and incident response. Confirm the host supports the exact QuickBooks product and release.
Ask where data is stored, which staff or subprocessors can access it, and how customer administrators control users. Retain the service agreement, data-processing terms, recovery targets, and escalation path.
Test identity, backup, restore, and incident controls
Require individual identities, multi-factor authentication, least privilege, timely departure removal, encrypted transport, monitored administration, patching, logging, and a documented breach-notification process.
Record backup frequency, retention, location separation, included files, recovery point, recovery time, test cadence, and customer export rights. Witness a restore that opens the company file and includes required attachments and integration data.
A provider statement that backups are included is not evidence that your complete company environment can be restored within the required time.
Measure peak performance and design the exit
Test from every real location and device during representative load. Time file opening, common forms, large reports, list search, imports, printing, scanning, integration jobs, backup, and re-login after interruption.
Model user, application, storage, support, onboarding, data transfer, Microsoft licensing, peripheral, integration, and overage costs. Define how quickly a current backup, attachments, reports, credentials, and configuration can be exported at exit.
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 hosted QuickBooks Desktop the same as QuickBooks Online?
No. Hosting remotely delivers the Desktop application and company file. QuickBooks Online is a different browser-native product with different features, data structures, updates, and integrations.
Can I host QuickBooks Desktop myself?
Technical possibility is not the only issue. Confirm licensing, supported architecture, security, backup, remote-access, multi-user, and administration requirements for the exact product and environment.
What should a QuickBooks hosting provider back up?
At minimum define the company file, related configuration, attachments, templates, and any dependent data needed for recovery. The contract should state frequency, retention, restore testing, recovery targets, and export rights.
Still comparing adjacent tasks? Use the complete guide library to find the one page that owns your intent.
Sources checked
First-party product documentation used to verify the workflow and risk notes in this guide.