QuickBooks Desktop 2022 Hosting Options After Discontinuation
Learn how to keep QuickBooks Desktop 2022 running remotely after its May 2025 sunset. Compare third-party hosting, self-hosted servers, and local setups.
QuickBooks Desktop 2022 officially reached the end of its supported lifecycle on May 31, 2025. When Intuit sunsets a version, it means the discontinuation of add-on services, live technical support, and security updates—but it does not mean you have to stop using the software. If you want to keep your 2022 installation alive but need to move it off a local physical machine, you have a few viable hosting paths.
Why Move QuickBooks 2022 Off Your Local Hardware?
Relying on a local workstation for a discontinued product introduces a few headaches. The computer itself might be aging out, or you might have team members in different locations who need simultaneous access to the company file. Moving QuickBooks Desktop 2022 to a hosted environment centralizes the data, makes automatic backups easier to manage, and allows multiple users to access the exact same installation without relying on a fragile peer-to-peer network setup.
Third-Party QuickBooks Hosting
With this approach, an authorized commercial hosting provider installs your QuickBooks Desktop 2022 software and your company file onto a virtual server in a secure data center. You and your team access the software and data remotely via a remote desktop connection.
The primary advantage here is infrastructure offloading. The hosting provider handles server maintenance, operating system updates, and daily backups. For a discontinued version like 2022, this is often the safest route because the data center's physical security and firewall configurations protect your company file far better than a standard office network. The main tradeoff is cost: you will pay a recurring monthly subscription fee per user.
Self-Hosted Remote Desktop
If you want complete control over the environment and want to avoid monthly per-user hosting fees, you can build your own remote setup. This involves designating a dedicated computer or server in your office (or a virtual private server you rent) to act as the host.
You install QuickBooks Desktop 2022 on that central machine, move your company file to it, and configure Windows Remote Desktop Services. Users connect from their local laptops or tablets to the host machine to do their work.
The benefit is autonomy. The drawback is maintenance. You are entirely responsible for hardware failures, network uptime, and managing firewall ports so remote users can connect securely. Also, if your office loses power or internet, your entire accounting team is locked out until connectivity is restored.
Local Machine vs. Hosted Environments
Keeping QuickBooks 2022 on a single local machine is perfectly fine for a solo user. However, it creates a single point of failure. If that specific hard drive crashes, you lose your installation and potentially your data if backups are inadequate.
Moving to either a third-party hosted cloud or a self-hosted remote server isolates the QuickBooks installation from the user's physical device. If an employee spills coffee on their laptop, the QuickBooks installation and company file remain completely untouched on the server.
Managing Reinstallation and Activation
Whether you move to a third-party cloud or your own remote server, you will need to reinstall QuickBooks Desktop 2022 from scratch. The installation process itself is identical across recent QuickBooks versions.
The critical hurdle with a sunsetted version is activation. You must have your original license and product numbers. Because Intuit's activation servers occasionally flag older, discontinued versions when installed on new hardware, you need to ensure you have your original installation files and valid license keys ready before attempting the migration.
Preserving Your Company File
Moving your installation to a new hosted environment means moving your company file (.qbw) and your transaction log (.tlg) together. Always create a proper backup (.qbb) on the old machine and restore it on the new hosted server rather than simply dragging and dropping the working file. If the migration process results in data corruption or missing transactions, you may need to repair the damaged company file to restore your ledger's integrity.