HubSpot and MYOB Acumatica: What Syncs Out of the Box and What Has to Be Built

The standard MYOB Acumatica HubSpot connector syncs four record types: business accounts, contacts, leads and marketing lists, each one way or both ways, with one system set as master. Deals, quotes, sales orders, products, prices, invoices and tickets are not included. HubSpot’s API supports all of them, so they can be built as extensions, scoped and quoted before any work starts.

At a glance

• Who it is for: Australian businesses running MYOB Acumatica for finance and stock that have chosen HubSpot, or are about to, for sales and marketing
• Problem it solves: Knowing which records move between HubSpot and MYOB Acumatica without development, which need building, and what decisions sit behind a won deal becoming a sales order
• Platforms: MYOB Acumatica with its HubSpot integration, and HubSpot Marketing Hub, Sales Hub, Revenue Hub and Service Hub
• Typical cost: Standard connector setup is configuration work inside an implementation; each extension is scoped development quoted in writing after the scoping worksheet
• Typical timeline: Typically days for the standard connector setup and weeks for extension work
• Last verified: 21 October 2026 against MYOB’s Enhanced HubSpot Data Provider guide and HubSpot’s price books article

The request usually arrives as one sentence: we want HubSpot and Acumatica talking. Nobody can price that sentence. It has to become a list, and for every piece of information that moves we need four things: the record and the event that moves it (a deal reaching Closed Won, say), the direction, the speed, and the fields, with the source of truth for each. Once the list exists, each row is either covered by the standard connector or built on top of it.

What does the MYOB Acumatica HubSpot connector sync out of the box?

Four record types. MYOB’s Enhanced HubSpot Data Provider guide pairs them as leads and contacts with HubSpot contacts, business accounts with HubSpot companies, and marketing lists with HubSpot contact lists. Its configuration prerequisites call for a HubSpot Marketing Hub subscription that includes lists, at Starter, Professional or Enterprise, and the HubSpot Integration feature switched on in Acumatica. HubSpot planned to retire the API the older Acumatica integration used at the end of April 2026, and MYOB’s 2025.1.501 release notes say this is addressed in MYOB Acumatica 2025.2.100 and later, so if you are on an older build, check your version first.

• Business accounts. Name, website, phone and address, with the HubSpot company ID kept on the account. Only prospects and customers go to HubSpot, and Acumatica checks for a company with the same website domain before creating one.
• Contacts. Name, email, phones, job title, company and address. A contact needs an email before it goes to HubSpot, and matching is by HubSpot ID, then email. Linking the contact to its company is off as standard, so we switch it on during setup.
• Leads. HubSpot has one contact record, with a lifecycle stage property showing where that contact sits. A connector setting decides whether a new HubSpot contact lands in Acumatica as a lead or a contact (lead is the default). Converted and closed leads are not pushed back.
• Marketing lists. Static lists, with members pushed or pulled as a separate step. MYOB’s guide notes that list properties sync in real time, while membership syncs on demand or on a schedule.

Any HubSpot contact or company property, including custom ones, can be mapped in setup screens without code.

Which system wins

Each record type has a master, either Acumatica or HubSpot. When the same record changes in both systems between syncs, the master’s version is kept and the other side is overwritten on the next sync. Deletions flow too, unless Acumatica refuses because the record has history, such as a customer with invoices. Then it shows as a sync error instead of being deleted.

Real time, scheduled or on demand

Nothing syncs until it is switched on, one record type at a time. Acumatica changes go to HubSpot straight away, and HubSpot changes arrive through a webhook, or by polling every 60 seconds as standard. A nightly resync catches failures, a full resync realigns everything after a mapping change, and Sync, Push and Pull buttons sit on each record. Our usual starting point is real time for accounts, contacts and leads, Acumatica as master for accounts, HubSpot as master for leads, and lists on demand.

When a sync fails

Failed syncs retry automatically, five attempts as standard. The HubSpot Sync State screen shows each record’s status, attempt count and a plain-language error, and lets you resync or reset it. The connector signs in with a HubSpot private app access token (or OAuth) and needs read and write access to contacts, companies and lists only.

What does not sync, and what has to be built?

The standard connector does not touch deals, quotes, sales orders, invoices, products, pricing, activities, tickets, record owners or custom objects. That is most of what a sales team means by an integration.

The HubSpot side of each gap is reachable. HubSpot’s deals API creates and updates deals with their pipeline and stage, the line items API handles the products attached to a deal or quote, and the invoices API creates and updates invoice records. The properties API adds custom properties to any object, and webhooks notify on creation, deletion and property changes for contacts, companies, deals, products and line items.

Every request falls into one of three effort levels.

• Setup only. “We also need field X” or “only sync contacts in lifecycle stage Y”. Mapped and filtered in setup screens, no programming.
• Small customisation. Changing how an account or contact is created, or what happens to it after import. A developer adjusts an existing sync job.
• New record type. A won deal creating a sales order, order status going back to the deal, products and prices going to HubSpot. A proper development job, scoped and quoted before anything is built.

How does a won HubSpot deal become a MYOB Acumatica sales order?

Through a chain of decisions, and the first one shapes the rest.

Mirror the pipeline, or only create the order when won. A deal can live in Acumatica as an opportunity through every stage, which suits a business that forecasts from Acumatica. Most only want the order created when the deal is won.

Which stage fires the order. Usually Closed Won, sometimes a later stage or a tick box. You also decide whether the order arrives on hold or ready to ship, its order type and warehouse, and what happens if the deal is edited or lost afterwards.

Customer creation. If the company is not yet a customer, it needs terms, tax zone, customer class and price class. The integration can create it with defaults, or the order waits for an admin. HubSpot has no ABN field, so ABN becomes a custom property. A credit check before the first order, and what sales sees on credit hold, both belong in the design.

Line items need matching SKUs. In HubSpot, a product attached to a deal or quote becomes a line item, per the line items API guide. Each line must carry a SKU that equals an Acumatica inventory ID, or the order cannot be built. You decide what happens when it doesn’t match: reject and flag, create a non-stock line, or create the product.

HubSpot has no unit of measure. A HubSpot quantity is just a number. If you sell by the each, box and carton, the integration has to know which Acumatica unit the HubSpot quantity means.

Who owns price. HubSpot holds a default price per product and price books assigned to deals. Acumatica holds price classes, customer-specific prices, quantity breaks and promotions. Either Acumatica’s prices are pushed into HubSpot, or the salesperson types a price and Acumatica checks it. Pick one, and decide what happens when they disagree.

“The order itself is the easy part. The work is in the five decisions around it: which stage fires, who creates the customer, what happens to a SKU that doesn’t match, what the quantity means and whose price wins. Get those written down and the build is predictable.”

Josh Craig, Director, Auboros

What flows back. Sales usually wants the order number, status, shipment and invoice on the deal, plus balance, overdue amount and credit hold on the company. HubSpot has no built-in fields for these, so they arrive as custom properties, which work on every tier.

Which system should own which data?

Every record needs one owner. The usual answer:

• MYOB Acumatica owns customers, ABN, payment terms, credit limits, products, prices and invoices, because finance and the warehouse depend on them.
• HubSpot owns the pipeline, deal stages and marketing lists, because sales and marketing work there all day.
• Contacts go both ways. Sales adds people in HubSpot, accounts adds billing contacts in Acumatica, and both are right.

“Both” is where integrations go wrong. When two systems change the same field and neither is master, the last sync wins and nobody knows which version was right. Contacts are the one place where both is genuinely the answer, so that is where the master setting gets the most attention.

When is this integration NOT worth building?

Be honest about these before spending money on extensions.

• You win a handful of orders a month. Rekeying five orders takes less time than maintaining an integration.
• Quotes are already produced in Acumatica. If sales quotes from Acumatica and the customer accepts there, a deal-to-order build duplicates a step that already works.
• Nobody in sales needs financials. If no salesperson asks about balances or shipments, don’t build the flow back.
• HubSpot isn’t settled yet. Pipelines, stages and properties change in the first few months. Building against a moving pipeline means building twice.

In all four cases, start with the standard connector, run it for a quarter, and add extensions once you can see where the rekeying hurts.

What happens after the scoping worksheet?

Our scoping worksheet asks the questions above in plain language, and Parts A and B take about 30 minutes. We map your answers against what the standard connector does, mark each row as setup, small customisation or build, and come back with a written approach and a cost. Nothing is committed until you have seen that. To start, scope your own HubSpot MYOB Acumatica integration with the five-minute scoping tool on that page.

Stop rekeying won deals into MYOB Acumatica

We’re a MYOB Acumatica partner in Brisbane working Australia-wide, and we set up the HubSpot connector and build the extensions on top of it. If you want to know which of your records the standard connector covers, book a free consultation. We’ll walk through your sales-to-cash process and tell you plainly what needs building.

Goes well with

• Scope your HubSpot and MYOB Acumatica integration in five minutes
• MYOB Acumatica eCommerce connector: what syncs and what to check
• ERP for wholesale distribution in Australia