MYOB Acumatica partner · HubSpot integration
HubSpot and MYOB Acumatica integration: what syncs, what we build, and a five-minute scoping tool
The standard MYOB Acumatica HubSpot connector syncs four record types both ways: business accounts, contacts, leads and marketing lists. Deals, quotes, won deals to sales orders, products, prices, and order and invoice status back to HubSpot are built on top as extensions. Use the scoping tool below to mark what you need, and we come back with a written approach and cost.
At a glance
- Who it is for
- Businesses running sales in HubSpot and operations and finance in MYOB Acumatica
- Standard connector
- Business accounts, contacts, leads and marketing lists, both ways
- Built as extensions
- Deals, quotes, won deals to sales orders, products and prices, order and invoice status back to HubSpot
- Sync modes
- Real time, scheduled, or on demand from the record
- Typical timeline
- Typically days for connector setup, weeks per extension
- Where we work
- Brisbane, working Australia-wide
- Last verified
- October 2026
Out of the box
What does the standard MYOB Acumatica HubSpot connector sync?
Four record types, each its own sync job, each switched on separately. Field mapping is done in setup screens rather than code, so any HubSpot property, including custom ones, can be mapped to a field in MYOB Acumatica.
Business accounts
Both waysHubSpot companies
Account name, website, phone and address. The HubSpot company ID is kept on the account as its reference.
Good to know: Only prospects and customers go to HubSpot, never vendors or employees. Acumatica looks for a HubSpot company with the same website domain before creating a new one.
Contacts
Both waysHubSpot contacts
Name, email, phone, mobile, job title, company, website and address. The HubSpot contact ID is kept on the contact.
Good to know: A contact needs an email address before it goes to HubSpot. Matching is by HubSpot ID first, then email.
Leads
Both waysHubSpot contacts
The same fields as contacts. A lead coming in from HubSpot is created with the status Open.
Good to know: A setting decides whether a new HubSpot contact lands as a lead or a contact. Converted and closed leads are not pushed back.
Marketing lists
Both waysHubSpot contact lists
The list name, with members pushed or pulled as a separate step.
Good to know: Works with static lists, with options to remove members missing from the other side and to include subscribed members only.
Which system wins. Each record type has a master, either HubSpot or MYOB Acumatica. When the same record changes in both between syncs, the master's version is kept and the other side is overwritten. Deletions flow too, unless Acumatica refuses because the record has history, such as a customer with invoices. That shows as a sync error rather than a deletion.
How often it runs. Real time, with HubSpot changes arriving through a webhook or picked up by polling every 60 seconds. A failed and missed resync can run nightly as a safety net, a full resync brings both sides into line after a mapping change, and Sync, Push and Pull buttons on each record handle one-off fixes.
Extensions
What has to be built on top of the connector?
Deals, quotes, orders, invoices, products and prices are not part of the standard connector. HubSpot's API supports all of them, so each one can be built as an extension.
| Record | Standard or extension | Direction | Notes |
|---|---|---|---|
| Companies and business accounts | Standard | Both ways | Only prospects and customers go to HubSpot. Existing companies are matched by website domain. |
| Contacts | Standard | Both ways | Needs an email address. Matched by HubSpot ID, then email. |
| Leads (new enquiries) | Standard | Both ways | A setting decides whether a new HubSpot contact lands as a lead or a contact. |
| Contact lists and marketing lists | Standard | Both ways | Static lists. Members are pushed and pulled as a separate step. |
| Deals to opportunities | Extension | Usually both ways | Mirrors the whole pipeline in Acumatica. Deal stages are mapped to opportunity stages. |
| Quotes to sales quotes | Extension | Usually to Acumatica | Decide first which system produces the quote and which one numbers it. |
| Won deals to sales orders | Extension | To Acumatica | A chosen deal stage creates the order. Line items need SKUs that match Acumatica inventory IDs. |
| Products to stock and non-stock items | Extension | Usually to HubSpot | The SKU is the key. Inactive Acumatica items can be archived in HubSpot. |
| Price books and tiers | Extension | Usually to HubSpot | Maps to price classes and quantity breaks. Price books need a paid HubSpot tier (Revenue Hub Professional or above). |
| Order and shipment status | Extension | Acumatica to HubSpot only | Order number, status, shipment date and tracking as custom properties on the deal. |
| Invoices | Extension | Usually to HubSpot | As properties on the deal, or as HubSpot invoice records. |
| Customer balance, overdue and credit hold | Extension | Acumatica to HubSpot only | Custom properties on the company. Can warn sales or block new quotes. |
| Tickets to cases | Extension | Both ways | Only if you use Service Hub. |
| Notes, emails, calls and tasks (activities) | Extension | Both ways | Possible, and rarely worth it. |
How much work is each addition?
01
Setup only
"We also need field X to come across", or "only sync contacts in lifecycle stage Y".
Mapped in the setup screens with no programming. Covers any HubSpot contact or company property, including custom ones, and filters on which records are included.
02
Small customisation
Changing how an account or contact is created, or what happens to it after import.
A developer adjusts how an existing sync job behaves. Usually a short piece of work.
03
New record type
A won deal creating a sales order, order and invoice status going back to the deal, products and prices going to HubSpot.
A development job against the HubSpot API, scoped and quoted in writing before anything is built.
Scoping tool
Scope your HubSpot and MYOB Acumatica integration in five minutes
Answer the questions below. You get a scope summary on screen and we come back with a written approach and cost. Nothing is committed.
Scoping tool
Your scope summary
Standard connector
Extensions to build
Key decisions
What happens next
- We map your answers against what the standard connector does.
- We mark each row as setup, small customisation or build.
- You get a written approach and cost within two business days. Nothing is committed.
How it runs
How does the connector decide which system wins?
Every record type has a master. When the same company or contact changes in both systems between syncs, the master's version is kept and the other side is overwritten on the next sync. It is the decision that matters most, so we walk through it for each record type during setup.
Our suggested starting point: real time on for accounts, contacts and leads, with MYOB Acumatica as master for accounts and HubSpot as master for leads. A failed and missed resync scheduled nightly, and marketing lists synced on demand. We adjust it once we have seen your process.
When a sync fails, the connector retries automatically, five times as standard. A HubSpot Sync State screen lists every synced record with its status, attempt count and a plain-language error, and lets you resync or reset a single record. If HubSpot asks the connector to slow down because of rate limits, it waits and carries on.
The connector signs in with a HubSpot private app token and needs read and write access to contacts, companies and lists, nothing else. Instant updates from HubSpot need a webhook subscription in your HubSpot account; without it, the connector polls instead. Both are set up during the project.
Cost and timeline
What does a HubSpot and MYOB Acumatica integration cost?
Setting up the standard connector is configuration work: switching on each record type, mapping fields, choosing the master and the schedule. It typically takes days, and it usually sits inside a MYOB Acumatica implementation rather than running as a separate project. If you are still choosing who implements the ERP side, we are a MYOB Acumatica partner in Brisbane.
Each extension row is development against the HubSpot API. We scope it from your answers to the tool above and quote it in writing, and each one typically takes weeks rather than days. For the detail behind each row, read our guide to what syncs between HubSpot and MYOB Acumatica.
The cost driver is rarely the connection. It is the exception handling: a deal line with no matching SKU, a customer on credit hold, a salesperson's price that differs from the Acumatica price list. Distributors feel this most, because won deals become orders against real stock, price classes and credit limits. Our page on ERP for wholesale distribution in Australia covers that side of the business.
Not a fit
When is a HubSpot integration not worth building yet?
- A handful of orders a month. Keying them into Acumatica costs less than building and maintaining a deal to order sync.
- Quotes are already produced in Acumatica. If sales are comfortable quoting there, a quote extension adds a second source of truth.
- HubSpot is not settled with the sales team. Pipelines and properties change in the first months, and every change is rework on the integration.
- Nobody in sales needs financials. If sales never ask about balances or invoices, leave those rows out.
In each case, start with the standard connector for accounts, contacts, leads and lists. Run it for a few months, then scope the extensions against how the team actually works.
FAQ
HubSpot and MYOB Acumatica: common questions
Does HubSpot integrate with MYOB Acumatica?
Yes. MYOB Acumatica has a standard HubSpot connector that syncs business accounts, contacts, leads and marketing lists, one way or both ways. Deals, quotes, sales orders, invoices, products and prices are not part of it, but HubSpot's API supports all of them, so they can be built on top as extensions.
Can a won HubSpot deal create a sales order in MYOB Acumatica?
Yes, as an extension. A chosen deal stage, typically Closed Won, triggers the integration to create the sales order in MYOB Acumatica with the customer, salesperson and line items mapped across. The questions that shape the build are which stage fires it, what happens when a line has no matching product, and whether a new customer is created automatically or waits for an admin.
Can sales see invoices and customer balances in HubSpot?
Yes, as an extension. HubSpot has no built-in fields for these, so we add custom properties on the deal or company for invoice number, due date, amount outstanding, customer balance, overdue amount and credit hold. Custom properties work on every HubSpot tier, and on paid tiers invoices can also come across as HubSpot invoice records.
Do HubSpot price books sync with Acumatica price classes?
They can, as an extension. Each Acumatica customer price class maps to a HubSpot price book, with Acumatica as the source and prices pushed on a schedule, and quantity breaks map to HubSpot volume tiers. Price books and tiers need HubSpot Revenue Hub Professional or above.
How long does it take to set up?
Setting up the standard connector is configuration work and typically takes days, usually inside a MYOB Acumatica implementation. Each extension is development against the HubSpot API and typically takes weeks, depending on how many exceptions it has to handle. The scoping tool on this page gets you a written approach and timeline.
Prefer to talk it through first?
Thirty minutes with the people who build it. We tell you which rows are setup and which are build before you fill anything in.