Integration guides

How do I integrate HubSpot with Xero?

Flow Mesh · 6 October 2026 · 5 min read

When your sales pipeline lives in HubSpot and your invoices live in Xero, someone usually ends up copying client details and invoice amounts between them. Partners ask in HubSpot whether a client has paid; the answer is in Xero. New clients are typed in twice.

The short answer: start with HubSpot's own Xero integration, called Data Sync. It syncs contacts, products, invoices and payments, and for many firms that is enough. Its limits show up around sync timing, invoices created in HubSpot, custom fields and anything that should happen automatically when a deal is won. That is where an automation platform such as Make or n8n comes in.

What the native HubSpot and Xero integration does

According to HubSpot's knowledge base, the integration syncs four types of record:

• Contacts: one way or both ways.
• Products and items: one way or both ways.
• Invoices: one way from Xero to HubSpot, or both ways.
• Payments: one way from Xero to HubSpot, or both ways.

To install it you need to be a Super Admin in HubSpot or have App Marketplace permissions. The integration is available on all HubSpot plans, but custom field mappings need a Data Hub Starter, Professional or Enterprise subscription, as listed by HubSpot in October 2026. The Xero App Store listing also notes a requirement for two-factor authentication across the HubSpot account.

How fast it syncs

HubSpot's documentation says changes from HubSpot to Xero are detected within a few minutes, while changes from Xero to HubSpot are detected every 30 minutes. There is a Sync Now button for an on-demand sync.

For most firms, 30 minutes is fine. It becomes a problem when something time-sensitive depends on it: a salesperson checking whether a deposit has landed before booking a kickoff, or a workflow that sends a welcome email the moment an invoice is paid. Design those processes knowing there is a delay, or trigger them from Xero directly.

Limits to know before you switch it on

HubSpot lists several limitations in its setup article. The ones that matter most to a professional services firm:

• Payments only sync from the moment you connect. Historical payments will not appear in HubSpot.
• Invoices created in HubSpot must be edited in HubSpot. Edit one in Xero and it can fail to sync. Pick one system where invoices are raised and stick to it.
• Invoices using HubSpot's automated sales tax won't sync to Xero.
• Six currencies are supported: USD, CAD, EUR, GBP, AUD and NZD. A firm billing in CHF or SGD needs another approach.
• Default field mappings can be switched off but not edited or removed.

Deals, quotes and projects are not among the synced objects. If you want a won deal to create a draft invoice in Xero, the native sync does not do that on its own.

A setup order that avoids duplicates

HubSpot recommends syncing contacts first, then products, then invoices. In practice:

1. Choose the source of truth for each record. Typically HubSpot owns contacts and companies, Xero owns invoices and payments. Write this down.
2. Clean both sides. Merge duplicate contacts in HubSpot and Xero before connecting. A contact spelled two ways becomes two contacts.
3. Decide one-way or two-way per object. Two-way contact sync is convenient but means an edit in either system overwrites the other. One-way is easier to reason about.
4. Map fields deliberately. Check where company name, billing email and tax number go. Xero contacts are often companies; HubSpot contacts are people.
5. Test with a few records, then watch the sync log for the first two weeks.

Our article on how much software integration costs covers what to budget for this kind of setup and its upkeep.

When you need Make, n8n or a custom integration

Reach for an automation platform when the firm needs logic the native sync does not have. Common examples:

• Deal won to draft invoice: when a deal moves to closed won, create a draft invoice in Xero with the right line items and the client's billing contact.
• Payment to next step: when an invoice is paid in Xero, update the deal, notify the account lead and start onboarding tasks without waiting for the 30-minute poll.
• Unsupported currencies: firms billing in currencies the native sync does not support.
• Other systems in the chain: a project management tool, a document tool or a proposal tool that also needs the same client record.

Make and n8n both have HubSpot and Xero connectors. Make suits teams that want a visual builder and a hosted service; n8n suits teams comfortable with a more technical tool or with self-hosting. Either way, check each platform's current pricing, because volume (every record processed) drives the monthly bill. See Make's pricing and n8n's pricing.

A few rules keep a mixed setup reliable:

• Do not let two tools write the same record. If the native sync handles contacts, the automation should look contacts up, not create them.
• Use a firm-owned connection, not one person's login. Our guide to why automations keep breaking explains why.
• Log what the automation did. A simple sheet or note on the HubSpot record makes problems traceable.

A fully custom integration using both APIs only makes sense when volumes are high or the logic is unusual. For most 10 to 50 person firms, native sync plus a few focused automations is the better trade-off.

How Flow Mesh helps

Our fixed-fee stack audit (€1,500) looks at how HubSpot, Xero and the rest of your tools fit together, gives each a verdict (keep, configure, consolidate or replace) and writes up exactly which records should flow where. If you want us to build the integration, we quote it in writing after the audit and work inside your own accounts.

Key takeaways

• HubSpot's native Data Sync connects contacts, products, invoices and payments with Xero, and is the right first step.
• Xero to HubSpot changes take up to 30 minutes; plan time-sensitive steps around that.
• Watch the limits: payments only from connection onward, six currencies, HubSpot-created invoices edited in HubSpot only.
• Use Make or n8n for deal-to-invoice and payment-triggered workflows, without two tools writing the same record.
• Decide the source of truth for each record and clean duplicates before you connect.