Moving QuickBooks Desktop Off a Hosting Provider and Back On-Premises
A staged plan for moving a hosted QuickBooks Desktop company file, its attachments and licence details onto local hardware before the term ends.
A hosted QuickBooks Desktop environment is convenient until the term ends. Data is removed on the provider's schedule, not yours, and the company file is only one of several things living there. Attached documents sit in a separate folder, licence details sit inside the hosted session, and add-ons installed in that session do not travel. Our engineers treat this as a staged migration: extract and verify first, then cut over in one closed weekend.
Pick the window early
Begin weeks before the hosting term ends, not days. Avoid any window containing a payroll run, a sales tax filing, or a month-end close. Choose a weekend when nothing must post from Friday afternoon to Monday morning, and announce the cutoff to users in advance. If the first attempt fails, you want enough term left to try again.
Inventory everything the host holds
List before you extract. A typical hosted environment holds the live company file and the transaction log beside it. It also holds scheduled and manual backups, the attachments folder feeding the Document Center, and any third-party add-ons installed in the session. Ask the provider where backups and attachments live. Those two are the items most often left behind, and attachments are not stored inside the company file.
Extract while you still control the account
Open the Product Information screen in the hosted session and record the exact version and release, the licence and product numbers, and the file size. Keep the Admin password with that record. Then run a backup with verification enabled and download it, together with the live file, its transaction log, and the attachments folder. Compare downloaded sizes against the originals and open a few attachments to confirm they are intact. Finally, test-restore the backup on a local machine and run Verify. A backup that has never been restored is a hope, not a backup.
This phase is safe to repeat. Nothing has changed for users, and the host remains untouched.
Match the licence to the file
The local install must be the same version as the hosted one or newer. A company file restored from a newer release will not open on an older one, and the format upgrade is one-way. If your local licence cannot match the hosted release, decide now between upgrading locally or downgrading the company file to an earlier version. That decision belongs in planning, not on cutover night.
Prepare the on-premises server in advance
Install the database server manager on the machine that will hold the file. Create a shared folder for the company file set and grant the QuickBooks users full control of it. Copy the extracted test set to the share, scan the folder, and confirm the database service is running. Install matching QuickBooks on every workstation, and have each connect to the share by network name rather than a mapped drive letter. Everything here can be tested weeks early. The weekend should hold only data movement.
Run the weekend cutover
Friday: users finish entry by the announced cutoff and log off. Have the provider confirm no active sessions, then take the final verified backup and download it with a fresh copy of the live file, log, and attachments. If the final download fails or is incomplete, stop. Abandon the cutover, keep working on the host, and retry another weekend.
Saturday: restore the final backup over the pre-staged copy on the share and run Verify immediately. Open the file in multi-user mode. Compare a trial balance, receivables and payables aging, and the last bank reconciliation date against reports printed before the cutoff. Confirm attachments still open from the Document Center. From this point until Monday sign-off, the host remains your fallback; do not cancel the term.
Rebuild multi-user access
Each workstation opens the file from the server share with hosting active on the server. The File menu should offer to switch to single-user mode, which confirms the session is shared. If a workstation cannot connect, error H202 is the usual symptom: stale network descriptor files, a stopped database service, or a firewall. Delete the descriptor files beside the company file and rescan the folder so they rebuild with current server details. For deeper multi-user and H202 troubleshooting, the general knowledge base covers the common causes.
Is the fault in the data or in the setup?
Copy the file to a second machine with QuickBooks installed and open it there. The same error on both machines points to the data. A clean open on the second machine points to the local installation. A Verify failure that survives a Rebuild needs repair rather than another restore; our QuickBooks Verify and Rebuild repair service handles exactly that. Distinguish the two before you spend a weekend reinstalling software.
What does a clean outcome look like?
Two users work in the file at once from different machines. Attachments open from the Document Center. Verify completes without errors, and reports match the pre-move figures. After a full week of normal entry with no faults, cancel the hosting term. Archive the downloaded backup set and keep it; it is your last independent copy of the hosted years.