How to connect HubSpot to your ERP without a blowout

Before anyone builds anything, write down which system owns each record and each field: customers, products and price books, quotes, orders, invoices, stock and payments. Then sync the smallest useful set first. That usually means customers and products flowing one way, and orders and invoices coming back into HubSpot as read only.

Next, pick the method. Use the HubSpot marketplace app if your ERP has a decent one, an integration platform if it does not, and custom code against both APIs only when the first two cannot do the job.

Last, decide what happens when a sync fails, who hears about it, and which key matches a HubSpot company to an ERP customer. Get those three things on paper and a HubSpot ERP integration stays the size you scoped.

Why ERP integrations blow out

We hear the same phrase on discovery calls: the ERP integration "grows arms and legs". It starts as "can HubSpot see our customers" and six weeks later someone is asking for live stock by warehouse, credit holds, rebate pricing and a two-way sync on every field.

The cause is almost never the connector. Nobody decided up front which system wins when the two disagree, so every field becomes a debate, and every debate becomes more build.

The buyers who end up happiest ask for the same thing: get phase one live, then scope phase two as its own piece of paid work once phase one has run for a while.

Is this post for you, or do you need the Xero guide?

If your finance team runs Xero, start with our guide to connecting HubSpot and Xero. That is a smaller, better-trodden path.

This post is for when you have outgrown Xero or already run an ERP: NetSuite, MYOB Acumatica or another MYOB product, Microsoft Dynamics 365 Business Central, SYSPRO or Pronto Xi. The usual signs are multiple entities, stock across sites, manufacturing or job costing.

Step 1: which system owns each record?

Ownership means one system is where a value gets created and changed. The other system can show it, and in some cases suggest a change, but it never overwrites it. Here is the split we start from for most 60 to 200 person businesses:

The customer record matters most. A HubSpot company and an ERP customer are the same business, but each system cares about different fields. Split ownership by field and write it down in a spreadsheet both teams sign.

Step 2: what to sync in phase one

Phase one should answer the question a sales team actually has: who is a customer, what do they buy, and are they paying. Everything else can wait.

Phase two is the first time HubSpot writes into the ERP, which is why it waits until finance trusts that HubSpot holds the same customers and products as the ERP. Our quote to cash guide covers what the HubSpot side of that flow looks like.

Step 3: marketplace app, integration platform or custom code?

Check the HubSpot App Marketplace first: who built the app, how many installs, and what recent reviews say. Here is what we found on 8 October 2026:

• NetSuite. HubSpot builds and certifies a NetSuite app with about 2,000 installs. It syncs companies, contacts, deals, products, invoices, sales orders and support cases, one way or two way, and can create a NetSuite sales order from a HubSpot deal.
• Microsoft Dynamics 365 Business Central. HubSpot builds a certified Business Central app with 400 plus installs. Its listing says it syncs Business Central customers with HubSpot contacts and does not yet sync companies, which is worth knowing before you plan around it. HubSpot's separate Dynamics 365 integration covers companies, deals, products, invoices and sales orders.
• MYOB. MYOB Acumatica has a built-in HubSpot integration that syncs contacts, leads, business accounts and marketing lists. For orders and invoices, the marketplace apps for MYOB and Acumatica we found are built by Commercient, each with fewer than 10 installs.
• SYSPRO and Pronto Xi. We could not confirm a current HubSpot-built app for either. Pronto describes itself as an Australian ERP developer, and SYSPRO has partner-built connectors. Expect an integration platform or custom build.

On every HubSpot-built app above, custom field mappings need a paid Data Hub subscription. Budget for that seat, because the default mappings rarely cover the fields your finance team cares about.

If there is no good app, an integration platform (Make, Workato, Boomi and similar) gives you mapping, scheduling and error logs without writing everything from scratch. Custom code against the HubSpot and ERP APIs is right when you have complex rules, high volumes or an on-premise ERP. Our HubSpot API guide covers the HubSpot side, and when to move from configuration to code covers the ownership cost.

Construction businesses running Procore alongside an ERP face the same choice: we found Procore and HubSpot connected through integration platforms such as Zapier and Workato, with no marketplace app.

Step 4: what happens when the sync fails?

Every integration fails sometimes: an API times out, someone deletes a product, a customer has no ABN. The question is whether anyone finds out before the reporting dashboard is wrong.

Decide these before go live:

• The matching key. HubSpot's data sync matches companies on name or domain by default, and lets you pick your own text field instead. For an ERP, store the ERP customer ID on the HubSpot company and match on that. HubSpot warns that the wrong match field can create duplicate records.
• A second check on the ABN. Store the ABN on both sides and validate it with the free ABN Lookup web service. Two records with the same ABN and different ERP IDs is a duplicate to investigate before it syncs.
• Retries that do not double up. If a "create order" call fails halfway and retries, it must not create two orders. Send a unique reference, such as the HubSpot deal ID, and have the ERP side reject a second order with the same one. Engineers call this idempotency.
• Who gets told. Name a person in finance and one in RevOps. Failed records go to a HubSpot list or Slack channel they watch, with the reason attached, and the deal shows the order did not reach the ERP.

Clean your existing duplicates before the first sync, in both systems.

The Australian details: ABN, GST and Peppol

ABN. It is the one identifier both your sales team and your finance team already trust, which makes it the best second key you have.

GST. HubSpot's automated sales tax only works for businesses based in the US and Canada. Australian businesses use the tax library instead: set up a GST rate and a GST-free rate, assign them to products, and they apply to line items on quotes and invoices. Make sure the tax treatment on each product matches the ERP, or your quote totals will not match the invoice.

Peppol e-invoicing. The ATO runs Australia's Peppol network, and business.gov.au presents e-invoicing as an option businesses can take up. If you invoice government or large customers over Peppol, keep sending those invoices from the system that issues them today, and sync the invoice status back to HubSpot. Our invoicing decision guide covers when moving invoicing into HubSpot makes sense.

Frequently asked questions

Does HubSpot integrate with NetSuite? Yes. HubSpot builds a certified NetSuite app on its marketplace that syncs companies, contacts, deals, products, invoices and sales orders, and can create a NetSuite sales order from a HubSpot deal. Custom field mappings need a paid Data Hub subscription.

Is there a HubSpot integration for MYOB? MYOB Acumatica has a built-in HubSpot integration for contacts, leads, business accounts and marketing lists. For orders and invoices from MYOB products, the marketplace apps we found are third-party, so most businesses use an integration platform or a custom build.

Does HubSpot integrate with Dynamics 365 Business Central? Yes. HubSpot builds a certified Business Central app that syncs customers, items, opportunities and sales orders both ways. Its listing says Business Central customers sync to HubSpot contacts and that companies do not sync yet, so check that fits how you sell.

What should sync first between HubSpot and an ERP? Customers and products from the ERP into HubSpot, then orders and invoices back into HubSpot as read only. Leave HubSpot creating sales orders in the ERP until that first phase has run cleanly.

How do you stop duplicates in a HubSpot ERP sync? Match on the ERP customer ID, keep the ABN as a second check, clean existing duplicates before the first sync, and send a unique reference with every create request so a retry cannot make a second record.

Sources

• NetSuite app listing, HubSpot App Marketplace, for builder, installs and objects.
• Use HubSpot's integration with NetSuite, HubSpot Knowledge Base, for mappings and the Data Hub requirement.
• Microsoft Dynamics 365 Business Central app listing, HubSpot App Marketplace, for builder and mappings.
• Connect HubSpot and Microsoft Dynamics 365, HubSpot Knowledge Base, for synced objects and sales orders.
• Integration with HubSpot: General Information, MYOB Acumatica Implementation Guide, for the built-in integration.
• MYOB SYNC by Commercient and Acumatica SYNC by Commercient, HubSpot App Marketplace, for builder and installs.
• About Pronto Software, Pronto, for its Australian description.
• HubSpot and Procore integrations, Zapier, for the Procore connection.
• Match records in data sync, HubSpot Knowledge Base, for matching and duplicates.
• ABN Lookup web services, Australian Business Register, for free ABN validation.
• Create and use taxes, HubSpot Knowledge Base, for the tax library.
• E-invoicing, business.gov.au, for Peppol and the ATO's role.

---

Want phase one scoped properly before anyone writes a line of code? See our RevOps and HubSpot integration work, or talk to us.