QuickBooks CRM Integration: HubSpot, Salesforce, Zoho and Dynamics

Published: Oct 17, 2026 Author: Itexus Team Read 11 min
Have a project in mind? Let’s turn it into a working product
Discuss Your Project

Sales teams live in the CRM. Finance lives in QuickBooks. When the two don't talk, someone retypes customer details, rebuilds invoices from closed deals and chases payment status by email. A QuickBooks CRM integration closes that gap: customers, products and invoices move between the systems, and sales reps can see what a client owes without opening the accounting file.

This guide covers the four CRMs people most often connect to QuickBooks (HubSpot, Salesforce, Zoho CRM and Microsoft Dynamics), what each connection actually syncs, how QuickBooks Online and QuickBooks Desktop differ here, the usual setup path, the limits that catch teams out, and when a custom integration is worth building. For the wider picture across QuickBooks, Xero, NetSuite and Sage, see our accounting software integration guide.

What a QuickBooks CRM Integration Syncs

Most connectors work with the same small set of records. The names differ by CRM, but the pairs look like this:

CRM record QuickBooks record HubSpot app Zoho CRM native
Contact (or Account in Zoho) Customer One-way or two-way, your choice Two-way
Product Products and Services One-way or two-way, your choice Two-way (Inventory items only)
Invoice Invoice One-way or two-way, your choice QuickBooks to CRM only
Credit memo Credit memo One-way or two-way, your choice Not listed
Quote, purchase order Estimate, purchase order Not listed QuickBooks to CRM only
Vendor Vendor Not listed Two-way

The direction matters more than the list. HubSpot's own QuickBooks Online app lets you set the direction for each object pair: Contact to Customer, Product to Products and Services, Invoice to Invoice and Credit Memo to Credit Memo. You also pick which system wins when the same field differs on both sides. Zoho's native integration is fixed: contacts or accounts, vendors and products sync both ways, while quotes, invoices and purchase orders come one way, from QuickBooks into the CRM.

A rule of thumb that holds across connectors: let one system own each record type. Customers can be shared. Invoices and payments should have a single owner, usually QuickBooks, because that is where tax, accounts receivable and the general ledger live.

For Salesforce and Dynamics 365 Sales, the QuickBooks apps on AppExchange and AppSource come from third-party vendors, so the object list depends on the connector you install. The DBSync listing on AppExchange, for example, names accounts, contacts, opportunities and payments, and says invoices can be created from Salesforce opportunities.

QuickBooks Online vs QuickBooks Desktop

The edition decides which tools you can use. The HubSpot and Zoho native integrations are documented for QuickBooks Online only. QuickBooks Online connects through Intuit's cloud API, so a CRM app authorizes with your QuickBooks login and syncs over the internet.

QuickBooks Desktop works differently. Cloud apps reach it through the QuickBooks Web Connector, which Intuit describes as "one place to set up and manage your connected apps." The vendor of the CRM connector gives you a .qwc file, and you add it to the Web Connector on the computer where QuickBooks Desktop is installed, signed in as the QuickBooks admin. The installer is a Windows program, so the sync depends on that machine and its QuickBooks file being set up and reachable.

For a Desktop shop that wants Salesforce, the practical choices are a connector whose own listing names QuickBooks Desktop (the DBSync listing on AppExchange names both Online and Desktop) or a custom service built on the Web Connector.

Integration Options

There are three ways to connect QuickBooks to a CRM.

Native or official apps. HubSpot's QuickBooks Online app (installed from the HubSpot Marketplace) and Zoho's QuickBooks integration (installed from the Zoho CRM Marketplace) are the two first-party options among the CRMs in this guide. An admin sets them up without code.

Third-party connectors and iPaaS. Salesforce and Dynamics users pick from marketplace apps: Salesforce on AppExchange, Dynamics on Microsoft AppSource. Each vendor defines its own object list, sync schedule and edition support, so read the listing before you install. DBSync, for example, lists bi-directional sync of accounts, contacts, opportunities and payments with QuickBooks Online and Desktop.

Custom integration. Your own service calls the QuickBooks Online API (or the Web Connector for Desktop) and the CRM's API, with mapping and business rules you control.

Option Best for Limits Cost basis
Native app (HubSpot, Zoho) QuickBooks Online, standard objects, small finance team Fixed object list and rules, no Desktop Included with the CRM plan, some features need paid tiers
Marketplace connector or iPaaS Salesforce, Dynamics, Desktop users Vendor's object model and sync schedule Vendor subscription, pricing set by each vendor
Custom integration Custom objects, several companies, strict reconciliation Build and maintenance effort Project cost plus upkeep

How to Set Up QuickBooks with Each CRM

HubSpot QuickBooks Integration

HubSpot's QuickBooks Online app is the shortest path for HubSpot users. HubSpot lists it as available with all products and plans, with additional subscriptions needed for certain features. You need to be a Super Admin or have App Marketplace permissions.

  1. Install the QuickBooks Online app from the HubSpot Marketplace and sign in with your QuickBooks login.
  2. In Connected apps, open QuickBooks Online and go to CRM syncs.
  3. Set up a sync for each object pair: contacts and customers, products and Products and Services, invoices, credit memos.
  4. For each pair, choose the sync direction, pick which system wins in the data conflict resolution setting, map fields and add filters.
  5. Review the payment sync settings, which HubSpot documents separately from the object syncs.

Test with a few records first. HubSpot's help article states that a QuickBooks sandbox company cannot be connected, so the first sync runs against a real company file.

Salesforce QuickBooks Integration

Salesforce users choose a connector on AppExchange. The listings come from third-party vendors, and each defines its own objects and edition support. The DBSync listing, for example, names accounts, contacts, opportunities and payments, describes the sync as bi-directional, says invoices can be created from Salesforce opportunities, and names both QuickBooks Online and QuickBooks Desktop. It is listed as free on AppExchange, with a limited free plan and full features available through the vendor.

A typical setup: install the package in a Salesforce sandbox, connect the QuickBooks company, map Account to Customer and Product to Item, decide whether a Closed Won opportunity creates an invoice or an estimate, then run a test batch before turning on the schedule. For Salesforce QuickBooks Desktop integration, add the vendor's .qwc file to the Web Connector on the QuickBooks machine as described above.

Zoho QuickBooks Integration

Zoho's native integration works in the Professional edition of Zoho CRM and above, and only a Super Admin can install it.

  1. Go to Marketplace, then Integration, then QuickBooks, and click Install.
  2. Sign in to QuickBooks, choose the company if you have several, and click Connect.
  3. On the configuration page, choose the modules to sync, set duplicate handling (Skip, Overwrite or Clone) and map fields.

Two choices are permanent. You sync either Contacts or Accounts with QuickBooks customers, and you cannot change that later. And once the integration is configured, users can no longer create native Quotes, Invoices or Purchase Orders in Zoho CRM. Those records come from QuickBooks instead, arrive locked for editing, and carry a QuickBooks Record Link field.

Dynamics 365 and QuickBooks

For Dynamics 365 Sales (formerly Dynamics CRM), the QuickBooks options are third-party apps listed on Microsoft AppSource. Check on each listing whether it supports your QuickBooks edition and country, which entities it maps (accounts, products, quotes, orders, invoices) and how often it syncs. If no listing fits your data model, a custom integration through the Dynamics 365 and QuickBooks APIs is the remaining route.

Sage CRM and QuickBooks

Sage CRM and QuickBooks come from different vendors, so check whether a connector vendor names this exact pair on its own site before buying. If none does, a custom integration through each product's API is the route, following the same mapping rules as above.

Common Problems and Limits

Customer matching. HubSpot recommends billing an existing customer through the synced contact and using the email connected to that QuickBooks customer, otherwise the invoice may not land on the right customer record. Zoho offers Skip, Overwrite or Clone for duplicates; choosing Clone on a dirty customer list doubles the mess.

Sales tax. HubSpot says most non-US QuickBooks Online versions require tax on synced invoices, so those accounts cannot use invoice sync. To sync tax data, HubSpot points to creating invoices with its automated sales tax.

Payments. In the HubSpot app, a payment applied to more than one invoice does not sync, and only payments created after you connect the app sync.

Fees. HubSpot states that credit card fees do not sync to QuickBooks Online invoices and processing fees do not create expenses automatically, so someone reconciles them by hand.

Custom fields. In the HubSpot integration, custom invoice fields must be the Text and Number type, and only the first three custom invoice fields created in QuickBooks Online are visible.

Currency and products in Zoho. The home currency must be identical in Zoho CRM and QuickBooks. Currencies created through the integration start with an exchange rate of one, so rates must be updated manually. Only products categorized as Inventory sync.

Desktop availability. With QuickBooks Desktop, the connection depends on the Web Connector setup on the QuickBooks computer. If that machine or the vendor's service has a problem, the sync stops until it is fixed.

Costs

HubSpot lists its QuickBooks Online app as available on all products and plans, with some features requiring additional subscriptions. Zoho's integration requires the Professional edition of Zoho CRM or above, so the cost is the CRM edition. The DBSync listing on AppExchange is marked free with a limited free plan; full pricing is set by the vendor and not shown there. Other connector vendors set their own prices, so compare them against your record volumes and the objects you need.

For a custom build, Itexus publishes ranges on its fintech software development page: discovery and prototyping "start from around $30,000", and enterprise fintech projects "often range from $150,000 to $1,000,000+". A focused CRM to QuickBooks integration is usually a smaller scope than a full platform, so it should be estimated after discovery.

When a Custom Integration Makes Sense

Your objects don't fit the connector. If revenue is driven by subscriptions, usage, custom objects or multi-step approvals in the CRM, a fixed mapping of deals to invoices will not hold. A custom service maps exactly what finance needs.

You run several QuickBooks companies. Native apps connect a CRM to a QuickBooks company you pick at setup. Groups with several entities need routing rules: which customer belongs to which company file, and how intercompany sales are booked.

Reconciliation has to be exact. When payments cover several invoices, fees must be booked as expenses, or refunds must match the original sale, the documented limits above turn into monthly manual work. A custom integration can post these entries the way your accountant wants them.

You are on QuickBooks Desktop with Salesforce or Dynamics. Connector choice is narrower for Desktop, and a service built on the Web Connector lets you control timing, error handling and retries.

Compliance and audit. Regulated businesses often need an audit log of every record that moved, who changed it and when. Building that into the integration is easier than proving it after the fact.

How Itexus Can Help

Itexus has delivered "120+ integrations" for neobanks, payment providers, robo-advisors and trading systems, and integrates CRM systems, ERPs, payment gateways and legacy systems, including custom connectors where an old system has no API.

  • Mapping and discovery: we document which system owns each record and how deals become invoices.
  • QuickBooks Online and Desktop: we build against the QuickBooks API or the Web Connector, depending on your edition.
  • Reconciliation logic: payments, fees, refunds and tax posted the way your accountant expects.
  • Monitoring: sync logs, alerts and retries, so failures surface before month end.

For an example, see our B2B billing and payments platform, which synchronizes invoicing and financial data with Xero and QuickBooks. To discuss your setup, contact us.

Itexus is a trusted partner

40+ reviews on
4.9
Become a client

Frequently Asked Questions

Does QuickBooks have a built-in CRM integration?

QuickBooks connects to CRMs through apps. HubSpot and Zoho CRM offer their own QuickBooks Online integrations, installed from their marketplaces. Salesforce and Dynamics 365 rely on third-party connectors listed on AppExchange and AppSource.

How does the HubSpot QuickBooks integration work?

You install the QuickBooks Online app from the HubSpot Marketplace, then set up syncs for contacts, products, invoices and credit memos. For each pair you choose one-way or two-way sync and which system wins in a conflict. Payment sync is documented separately, and only payments created after you connect the app sync.

Can Salesforce integrate with QuickBooks Desktop?

Yes, through a connector that supports Desktop. The DBSync listing on AppExchange names both QuickBooks Online and Desktop. Desktop connections run through the QuickBooks Web Connector, where you add the .qwc file the vendor provides.

What does the Zoho QuickBooks integration sync?

Contacts or accounts, vendors and products sync both ways. Quotes, invoices and purchase orders sync one way, from QuickBooks into Zoho CRM. It requires the Professional edition or above, and after setup native quotes, invoices and purchase orders can no longer be created in Zoho CRM.

Is there a Dynamics CRM QuickBooks integration?

The QuickBooks options for Dynamics 365 Sales are third-party connectors listed on Microsoft AppSource. A custom integration is an option when none fits your data model.

Should I use a connector or build a custom integration?

Start with the native app or a connector if your objects are standard and you run one QuickBooks company. Consider a custom integration when you need custom objects, several company files, exact payment and fee reconciliation, or an audit trail.


Free expert consultation
Get a free architect consultation or system audit.
Consult with Our FinTech Experts
Sergey Privalov
Co-founder and CTO Itexus

Selected projects

Digital Wallet and App Ecosystem for Coinstar – a $2.2B Global Fintech Firm

A digital wallet app ecosystem for Coinstar, a $2.2B global fintech company — including mobile digital wallet apps, ePOS kiosk software, web applications, and a cloud API server enabling cryptocurrency and digital asset trading, bank account linking, crypto-fiat-cash conversions, and online payments.

  • iOS
  • React.js
  • Kotlin
  • .Net Core
  • DevOps
Read More

Retail Brokerage Platform with Mobile Trading, KYC, and Operations Console

A retail brokerage platform with a mobile trading app and a web console for compliance and operations teams, supporting automated KYC, investor onboarding, account funding and withdrawals, AI-powered market analysis, stock and ETF trading, fractional shares, Auto-Invest through regulated brokerage infrastructure.

  • React.js
  • Kotlin
  • JavaScript
  • Swift
  • Google Cloud
  • DevOps
Read More

Legacy WealthTech Platform Modernization for an SEC-Registered Investment Adviser Serving 450K+ Investors

Modernization of an inherited digital advisory platform combining model portfolio subscriptions, research, alerts, education, and SEC/RIA recordkeeping across mobile, web, and messaging channels.

  • React.js
  • Node.js
  • Flutter
  • NestJS / TypeScript
Read More