"QuickBooks" isn't one product — and that single fact quietly breaks more HubSpot integration attempts than anything else. QuickBooks Online (QBO) and QuickBooks Desktop (QBDT) share a name and not much else under the hood. If you pick a HubSpot integration built for one while running the other, it won't half-work. It won't work at all.
First: Which One Are You Running?
This is easy to check and worth confirming before you evaluate anything else.
You're on QuickBooks Online if:
- You log in through a web browser at
qbo.intuit.com - There's nothing to install locally — it just works from any computer
- Your billing is a recurring subscription charged automatically
You're on QuickBooks Desktop if:
- You open a QuickBooks icon on a specific Windows computer to use it
- Your company file (
.QBW) lives on that machine or a local server - Someone in your office would describe it as "the QuickBooks computer"
A lot of companies that started on Desktop years ago are still on it — migrating a mature company file to Online is disruptive enough that many finance teams simply haven't done it, especially in construction, distribution, and other industries with complex job-costing or inventory needs that Desktop still handles better.
Why the Difference Matters for HubSpot
QuickBooks Online exposes a modern REST API over the internet. Any integration platform — Zapier, Make, a native HubSpot app — can call it directly, from anywhere, with an API key. That's why almost every "QuickBooks + HubSpot integration" you find by searching is built for QBO. It's the easier build.
QuickBooks Desktop exposes data differently: through qbXML, a local XML-based protocol that only runs on the same network as the QuickBooks installation, mediated by a small Windows utility called the QuickBooks Web Connector (QBWC). Nothing reaches into Desktop's data from the outside — a piece of software has to be installed next to QuickBooks, and QuickBooks has to explicitly poll out to sync, not the other way around. We cover exactly how that mechanism works in our QuickBooks Web Connector guide.
That architecture difference has real consequences:
| QuickBooks Online | QuickBooks Desktop | |
|---|---|---|
| API access | Cloud REST API | Local qbXML via Web Connector |
| Zapier / Make support | Yes | No |
| Most HubSpot Marketplace apps | Yes | Rare |
| Requires local install | No | Yes (the sync connector) |
| Data location | Intuit's servers | Your own computer/network |
(If markdown tables don't render cleanly in your reader: Online = cloud API, broadly supported. Desktop = local protocol, narrowly supported, requires an installed connector.)
The Practical Result
If you're on QuickBooks Online, you have real breadth of choice — general automation tools like Zapier work fine for lighter needs, and there's a wider field of purpose-built integrations to evaluate.
If you're on QuickBooks Desktop, your options narrow considerably. This is exactly the gap ARBridge for QuickBooks was built for: a read-only sync that talks to Desktop through the standard Web Connector protocol, so B2B companies who haven't (or won't) migrate to Online still get customer, invoice, and payment data — with AR aging and credit-status computed automatically — inside HubSpot. See our full guide to connecting QuickBooks to HubSpot for how that compares to the other options on the table.
One More Wrinkle: QuickBooks Enterprise
If your invoice says "QuickBooks Enterprise," you're still on the Desktop architecture described above — Enterprise is a higher tier of Desktop (more users, more capacity, industry editions) rather than a separate product. Everything in this article about Desktop applies to Enterprise too.
Bottom Line
Before you evaluate a single HubSpot integration option, confirm your QuickBooks edition. It's a five-second check that determines whether you're choosing from twenty tools or three — and picking a QBO-only tool while running Desktop is the single most common reason these integration projects stall before they start.