How to Choose Tax Software Hosting for Your Accounting Firm

Quick Summary

Choosing tax software hosting should start with your firm’s actual workload, not price or uptime claims. Identify your busiest tax-season week, number of users, applications, and workflow requirements first.

Check compatibility: Confirm that your tax software, QuickBooks, printers, scanners, and other applications work with the hosting environment.
Evaluate infrastructure: Look at resource isolation, server capacity, storage, and performance under real multi-user workloads.
Test recovery: Do not judge backups only by retention periods. Verify how quickly the provider can restore systems and data after an outage.
Review security: Check MFA, access controls, backups, monitoring, and the provider’s responsibilities for protecting client information.
Test support: Make sure the provider can handle both hosting problems and issues involving your tax software environment during peak season.
Compare total cost: Include licenses, private-server fees, backup upgrades, security features, migration, support, and additional users—not just the advertised monthly price.
Plan your exit: Confirm data ownership, export options, termination terms, fees, and how the provider handles data deletion when you leave.

Bottom line: The best hosting provider is not necessarily the cheapest or the one with the highest advertised uptime. Choose the environment that can reliably support your firm’s real tax-season workload, recovery requirements, security needs, and long-term exit plan.

How to Choose Tax Software Hosting for Your CPA Firm

Most accounting firms compare tax software hosting in the wrong order. They start with provider websites, ask for per-user pricing and then compare uptime percentages, backup retention and security badges. By the time somebody asks whether the firm’s actual tax applications, printers, scanners and QuickBooks workflow will work properly, the shortlist has already been built.

I would reverse that process. Start with the busiest week your firm expects to have next tax season. Count the preparers, list every application they will run, identify the tasks that already feel slow and decide how much downtime or lost work the firm could realistically tolerate. Only then does it make sense to compare hosting providers.

A five-person Drake practice and a 40-person firm running UltraTax CS, QuickBooks Enterprise, Practice CS, Microsoft Office and document-management tools are both CPA firms. Their hosting requirements are not remotely the same.

Start With the Applications, Not the Server

Write down everything employees actually use during a normal tax-season day. Include the obvious tax program, but also QuickBooks Desktop, Microsoft Excel, Outlook, Adobe, scanning software, document management, tax research tools, client portals and any small utility the staff relies on to get work out the door.

The reason is simple: tax applications have real technical requirements. Drake Tax’s April 2026 system requirements support Windows Server 2019, 2022 and 2025, recommend SSD storage and 16 GB of RAM for better performance, and specifically say Drake can be networked using a dedicated server, which Drake recommends, or a peer-to-peer network. Drake also states that installation to a NAS device is not supported.

UltraTax CS has its own requirements. Thomson Reuters supports current Windows Server versions, recommends multi-core processors and adequate memory, and warns that unsupported NAS configurations can cause file-locking, performance or even data-corruption problems. That is why “we host accounting software” is not a meaningful technical answer. The provider needs to understand the applications your firm actually uses.

Licensing Should Be Checked Before Migration Starts

This is one of the least exciting parts of a hosting project, and one of the easiest places to create a problem.

If your firm uses a terminal-server or Remote Desktop Services environment, confirm the licensing requirements for each application before the server is built. Thomson Reuters publishes separate terminal-server guidance for CS Professional Suite applications, while Microsoft licensing can introduce Remote Desktop Services Client Access Licenses depending on the deployment. Intuit similarly notes that QuickBooks Desktop Enterprise hosted for multiple users can require RDS licensing.

QuickBooks adds another consideration. Intuit maintains an official list of providers authorized through its QuickBooks Desktop hosting program and says those authorized providers can host Desktop Pro, Premier, Accountant and Enterprise. Intuit is careful to say authorization does not mean it endorses or guarantees the quality of the hosting company.

That distinction is worth understanding. Authorization answers a licensing and hosting-program question. It does not tell you which provider has the fastest server, strongest support or best recovery process. Before moving data, get the application’s hosting and licensing position confirmed in writing. Discovering a licensing problem after fifty users have been scheduled for cutover is avoidable.

I Prefer Dedicated Infrastructure for Heavier CPA Workloads—but With a Qualification

For a firm running several desktop tax and accounting applications, I generally prefer a private dedicated server or a clearly isolated environment over an aggressively shared platform. The reason is not that “dedicated” sounds better. It is that tax-season workloads can be bursty, and resource contention is much easier to diagnose when you know what CPU, RAM and storage actually belong to your firm.

Thomson Reuters’ own virtualization guidance explains why this matters. A virtual machine only shows its own resource use; the underlying host may be consuming far more CPU or memory than the guest environment reveals. Thomson Reuters gives the example of a host using 80% of system resources while the virtual environment reports only 20%.

That does not make virtualization bad. Nearly every modern hosting environment uses virtualization somewhere. The point is that a CPA firm should understand what is shared.

I would ask the provider: What CPU, RAM and storage resources are assigned to our firm, what is shared with other customers, and how do you determine when we need more? A poorly sized dedicated server can still be slow. Dedicated infrastructure gives you isolation; proper sizing gives you performance.

Never Judge Performance From a Login Demo

A provider can make almost any environment look fast when one user opens a clean desktop during a sales call. That is not how your firm will use it in March.

I would ask for a pilot and reproduce real work. Open a large prior-year return. Recalculate a complex return. Generate a PDF. Print to the office printer. Scan a document. Open QuickBooks at the same time. Move files between applications and have several preparers repeat those tasks together.

Printing deserves more attention than many cloud projects give it. Thomson Reuters still publishes specific printing and scanning requirements for UltraTax CS because tax preparation remains a document-heavy workflow. Then test session reconnects, multiple monitors and remote users working from ordinary home internet connections. A hosting environment is successful only if the employees doing the work stop thinking about the hosting.

Ask Recovery Questions, Not Backup Questions

Almost every provider advertises backups. That is not enough information to evaluate resilience. You need to know how frequently recoverable copies are created, how long they are retained, where they are stored and how they are protected from the same event that damages production. More importantly, ask how long it takes to restore one deleted client file and how long it takes to recover the entire hosted environment.

Those are two different problems. The first relates partly to your recovery point objective: how much recent work the firm could lose. The second relates to recovery time: how long the business can operate without the system.

A provider offering 180 days of retention is not automatically better than one offering 90 days if a serious restore takes dramatically longer. Backup depth and recovery speed need to be evaluated separately.

During vendor discussions, I would ask for the recovery process in ordinary language: A preparer accidentally deletes a client folder at 2 p.m. What exactly happens next, and when should we expect the file back? You learn more from that answer than from “enterprise-grade backups included.”

Security Is Shared Responsibility

A cloud provider can improve a firm’s security considerably, but outsourcing the server does not outsource responsibility for taxpayer information. The FTC Safeguards Rule requires covered financial institutions to maintain safeguards and to take steps to ensure that relevant service providers also protect customer information. The IRS likewise reminded tax professionals in 2026 that they need a Written Information Security Plan tailored to the firm’s size, complexity and data environment.

Ask hosting providers about MFA, privileged administrator access, encryption, endpoint protection, patching, logging, vulnerability management, network controls and incident response. If they provide an independent audit or SOC report, understand what systems and controls that report actually covers.

Then ask the more important question: Which controls are still our responsibility? Employee laptops, phishing, Microsoft 365 accounts, internal permissions and offboarding often remain partly or entirely with the firm. A professionally secured data center cannot protect an old employee account nobody disabled.

Test Support Before Tax Season Tests It for You

“24/7 support” appears on almost every hosting website, so it tells me very little by itself. Give the provider a realistic scenario. It is 9:15 p.m. on March 14. Fifteen preparers can sign into Windows, but UltraTax or Drake will not launch. What happens next?

Ask who answers, whether first-line support understands the tax application, when an engineer gets involved and who coordinates with the software vendor if the problem sits between the application and the server. That last point matters. Intuit’s own hosted QuickBooks guidance acknowledges that some support situations may require both the hosting company and the software vendor or IT administrator to participate.

Experienced CPA firms know how frustrating the alternative is: the host says the application is responsible, the software vendor says the network is responsible, and employees sit between them waiting. A strong provider takes ownership of the troubleshooting process even when another vendor ultimately has to fix the issue.

Compare the Full Three-Year Cost

Do not compare providers from one advertised per-user number. Build the configuration the firm actually needs and include private-server charges, Microsoft licensing, RDS licenses, storage, backup upgrades, MFA, security services, migration fees, support tiers and seasonal users.

Then calculate the same environment at expected year-three headcount. This is where apparently inexpensive hosting can become surprisingly expensive. It is also where a higher published price can become reasonable if it includes infrastructure or services competitors charge separately for. A hosting decision should survive three tax seasons, not one sales proposal.

Ask How You Get Out Before You Go In

Migration planning should include the possibility that the relationship eventually ends. Ask who owns the data, which format you will receive it in, how much notice you must provide, whether the provider charges an export or termination fee, and whether it will cooperate with your next hosting provider. Also ask when the old provider deletes remaining production and backup copies after termination.

This is not pessimism. It is normal vendor-risk management. The easiest time to negotiate an exit process is before you become dependent on the provider.

The Five Tests I Would Require Before Signing

I would not approve a tax-hosting provider until it passes five practical tests:

Compatibility: Every important tax, accounting and supporting application has been checked.
Concurrency: Several employees can perform real tax-season work at the same time without unacceptable slowdown.
Recovery: The firm understands how both individual files and the full environment are restored.
Support: There is a clear escalation path when the problem involves both infrastructure and the tax application.
Exit: The firm knows how its data comes back if it changes providers.

If a host cannot answer one of those areas clearly during the sales process, that uncertainty belongs in the buying decision.

A Practical Tax Hosting Provider Scorecard

Once I have narrowed the field to three or four providers, I stop comparing marketing pages and score each company against the same set of questions. That prevents one provider from winning simply because its salesperson gave the best presentation.

The weights below are how I would evaluate a typical CPA firm running professional tax software in a multi-user environment. They are not universal. A two-person practice may put more weight on price, while a 40-person firm running UltraTax CS, QuickBooks Enterprise and several supporting applications should probably care much more about performance, recovery and support.

Evaluation Area	Weight	What I Would Verify
Application & licensing compatibility	15%	Tax software, QuickBooks, Office, PDF tools, scanners, integrations and RDS/licensing requirements
Infrastructure & resource isolation	20%	Dedicated/private environment, CPU and RAM allocation, storage type, resource contention and scaling process
Real workflow performance	15%	Return calculations, PDFs, printing, scanning, QuickBooks use and several simultaneous preparers
Backup & recovery	15%	Backup frequency, retention, isolation, file restore, full-server recovery, RPO and RTO
Security & vendor oversight	15%	MFA, encryption, admin controls, logging, endpoint/security tooling, incident handling and independent assurance
Tax-season support	10%	24/7 availability, application knowledge, engineer escalation and vendor coordination
Migration & exit	5%	Migration testing, rollback, data ownership, export process and termination terms
Three-year cost	5%	Users, private-server fees, Microsoft/RDS licensing, storage, security, migration and seasonal seats
Total	100%

Dedicated infrastructure receives the highest individual weight for a reason. Drake recommends a dedicated server for network installations, while Thomson Reuters explains that virtual environments share the host’s CPU and memory resources, so conditions on the underlying host can affect performance.
That does not prove every dedicated server will outperform every shared environment, but it makes resource allocation worth examining carefully for heavier tax workloads.

Security also deserves a meaningful score rather than a simple yes/no checkbox. The FTC requires covered firms to oversee service providers that handle customer information, including selecting capable vendors, setting contractual security expectations and periodically reassessing them. The IRS likewise says a tax professional’s WISP should reflect the size, complexity and sensitivity of the firm’s actual environment.

How to Score Each Provider

Give each provider a score from 1 to 10 in every category:

10: unusually strong, clearly documented and verified;
8–9: strong with only minor weaknesses;
6–7: acceptable but with meaningful limitations;
4–5: below what I would normally want for a production CPA environment;
1–3: serious weakness or requirement not met.

Multiply the score by the category weight to produce the final result.

For example, if Provider A earns 9/10 for infrastructure, its weighted infrastructure result is: 9 × 20% = 1.80 points

Do that for every category and add the results. The maximum final score is 10.00.

Example CPA-Firm Comparison

Imagine a 20-person CPA firm running UltraTax CS, QuickBooks Enterprise, Microsoft Office and document-management software.

Category	Weight	Provider A	Provider B	Provider C
Application compatibility	15%	9	10	8
Infrastructure	20%	10	7	8
Workflow performance	15%	9	8	8
Backup & recovery	15%	9	10	7
Security	15%	9	9	8
Tax-season support	10%	9	8	7
Migration & exit	5%	8	8	7
Three-year cost	5%	9	6	10
Weighted Score	100%	9.15/10	8.35/10	7.90/10

The numbers in that example are illustrative, not scores for actual hosting companies. The purpose is to show why the cheapest provider or the provider with the longest backup retention does not necessarily win the overall decision.

More importantly, I would add one rule that sits outside the mathematics:

A provider cannot compensate for a failed critical requirement with points somewhere else.

If your firm must run UltraTax CS and the provider cannot confirm support for that environment, eliminate it and If your firm requires a private dedicated server but the proposed plan uses shared infrastructure, eliminate it. If recovery expectations cannot meet the firm’s acceptable downtime, it is out.

Those are pass/fail requirements, not weighted preferences.

Questions I Would Put Beside the Scorecard

Before assigning a high score, I would want clear answers to these questions:

Are our CPU and RAM resources dedicated to our firm or shared with other customers?
Which of our tax and accounting applications have you hosted in environments similar to ours?
How do you size the server for our peak concurrent-user count?
Can we test several users performing real tax-season work before migration?
How frequently are backups created, how long are they retained and where are copies stored?
How long does a normal file restore take?
What is the process after a full-server failure?
Which accounts require MFA, including privileged administrators?
Who can access our server from your organization, and how is that activity logged?
Who answers when the tax application fails outside normal business hours?
What happens when the hosting provider and software vendor disagree about the cause of a problem?
What will our complete monthly bill look like with all required licenses and seasonal users?
What happens to our data if we leave?

A provider does not need to give the answer you hoped for every time. I am more concerned when the answer is vague. A clear limitation can be evaluated. An unclear architecture, unclear recovery process or unclear responsibility usually becomes more difficult after the contract is signed.

Final Verdict

The best tax software hosting provider is not necessarily the company advertising the highest uptime percentage or the longest feature list.

Start with your firm’s real workload. Count the users. Map every application. Verify licensing. Understand whether resources are dedicated or shared. Run a production-like test, restore something and make support explain what happens during a filing-season outage. Then compare the complete three-year cost and the exit terms.

When I evaluate hosting for a CPA firm, the question I keep coming back to is simple: Will this environment still make sense when everybody is busy, something breaks and nobody has time for the technology to become another tax-season problem? If the answer remains yes after those tests, the provider deserves to be on the shortlist.

Fact-Checking Note: We checked the technical requirements against 2026 documentation from Drake Software, Thomson Reuters, and Intuit. We also cross-checked security responsibilities with current FTC and IRS guidance. Because application requirements and licensing can change, firms should reconfirm these details directly with the relevant vendors before migration.

ReaThis