How customers, items, prices, sales orders, invoices and payments in Acumatica can flow into HubSpot, how won deals can become Acumatica sales orders, and how the build extends Acumatica's own HubSpot connector to the full quote-to-cash cycle.
Acumatica is a cloud ERP covering finance, distribution, inventory and a built-in CRM. Acumatica publishes its own HubSpot connector for contacts, customer and lead information, MQLs and campaign results. Orders, invoices, items and pricing are left to a custom build.
Public documentation. The client's own admin issues credentials, with no vendor approval needed.
Open API. The contract-based REST API is documented publicly. The client creates a dedicated API user, which counts against its Acumatica license limits.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
Acumatica gives HubSpot open, documented access to the whole quote-to-cash cycle, so sales can work from real orders, invoices and prices.
Campaign Creators assessment
Acumatica exposes its data through a versioned contract-based REST API, OData feeds for generic inquiries and data tables, and push notifications that post changes to a webhook. Sign-in uses OAuth 2.0 through a connected application. That makes customers, items, sales orders, invoices and payments readable, and lets a won HubSpot deal create a sales order with Acumatica's own validation. The limits that matter are set by the client's Acumatica license (API users, requests per minute and concurrent requests), and the overlap with Acumatica's built-in CRM needs a clear owner for every record.
Ratings are CC judgments from Acumatica's public documentation. Endpoint version, license limits and customizations are confirmed against the client's instance in discovery.
Contract-based endpoints keep the same shape across upgrades, and push notifications send changes to the integration as they happen, with a timestamp filter for catch-up.
Acumatica includes CRM leads, contacts and opportunities. Decide early that HubSpot owns leads and pipeline, and which CRM records Acumatica keeps for service and finance.
Each integration user counts against the Acumatica license, and the license caps requests per minute and concurrent requests. Confirm the client's limits before sizing sync intervals.
Seven Acumatica areas are relevant to HubSpot. Four carry quote-to-cash, two support it, and one is a scope decision to make early.
Customer accounts (CustomerID, CustomerName, CustomerClass) with their main contact, address and additional contacts.
$expand=MainContact returns email, phone and addressThe sellable catalog (InventoryID) and the prices sales should quote from, including customer-specific prices where used.
Sales orders (OrderType, OrderNbr) with customer, date, status, currency, total and order lines.
Posted invoices, their open balances and the payments applied to them.
Push notifications post inserted and deleted rows from a generic inquiry to a webhook. OData exposes inquiries and data tables for bulk reads.
Acumatica's connector syncs contacts, customer and lead information, MQLs and campaign results. The custom build adds orders, invoices, items and pricing.
Acumatica's built-in CRM and HubSpot both hold leads, contacts and opportunities. Decide which system owns each before any sync runs.
HubSpot and Acumatica never talk directly. A CC-built integration layer receives Acumatica push notifications, reads and writes through the contract-based REST API, matches each record, and writes to HubSpot in batches.
HubSpot owns leads, the relationship and the pipeline. Acumatica owns customer accounts once created, items, prices, tax, orders, invoices and payments.
The Acumatica CustomerID is stored on the HubSpot company and the InventoryID on the HubSpot product, so every later update matches without guesswork.
The integration calls one Default endpoint version and moves to a newer one as a planned change, so Acumatica upgrades never break the sync.
Each phase ends on a gate the client signs off before the next begins. Read-only flows go live first, so sales sees Acumatica data in HubSpot before HubSpot writes anything back.
List the companies, branches and currencies in scope, whether Acumatica's HubSpot connector is live, and which system owns leads, contacts and opportunities.
Register a connected application, create a dedicated API user, and confirm the license's API user, request-per-minute and concurrency limits.
Agree how customers match (CustomerID, then domain), how HubSpot owners map to Acumatica salespersons, and which custom fields and attributes are in scope.
Create the acu_ properties, product library, deal pipeline stages tied to order status, and the order and invoice views in a HubSpot sandbox.
Set up push notifications for orders, invoices and payments, plus timestamp-filtered reads for catch-up, with idempotent writes and an error replay queue.
Build new-customer and won-deal-to-sales-order creation through the REST API, so Acumatica pricing, tax and validation run.
Load customers, items and an agreed order and invoice history through OData, run two weeks in parallel, then switch on writes.
Entity and field names follow Acumatica's Default endpoint as shown in its REST examples. Names marked for confirmation are checked against the client's endpoint version and customizations in discovery.
| Acumatica field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Customers & contacts | ||||
| Customer.CustomerID | acu_customer_id | Company | ↔ Both | Primary match key. Written back when HubSpot creates the customer. |
| Customer.CustomerName | name | Company | ↔ Both | HubSpot fills blanks only once the customer exists. |
| Customer.CustomerClass | acu_customer_class | Company | ACU → HS | Drives segments and default terms. |
| Customer.Status | acu_customer_status | Company | ACU → HS | Active, on hold, inactive. |
| MainContact/Address (AddressLine1, City, State, PostalCode) | address, city, state, zip | Company | ↔ Both | Main address. Other locations stay in Acumatica. |
| Customer.CurrencyID | acu_currency | Company | ACU → HS | Confirm field name in discovery. |
| MainContact/Email, MainContact/Phone1 | email, phone | Contact | ↔ Both | Main contact for the account. |
| Contact.FirstName, LastName, Email | firstname, lastname, email | Contact | ↔ Both | Additional contacts. Skip if Acumatica's connector already syncs contacts. |
| Items & prices | ||||
| StockItem.InventoryID | hs_sku | Product | ACU → HS | Primary match key for products. |
| StockItem.Description | name | Product | ACU → HS | Item description. |
| Item class | acu_item_class | Product | ACU → HS | Confirm field name in discovery. |
| Default sales price | price | Product | ACU → HS | Confirm field name; customer-specific prices stay in Acumatica. |
| NonStockItem.InventoryID | hs_sku | Product | ACU → HS | Services and non-stock items. |
| Sales orders | ||||
| SalesOrder.OrderNbr | acu_order_number | Deal | ↔ Both | Written to the deal when Acumatica creates the order. |
| SalesOrder.OrderType | acu_order_type | Deal | ↔ Both | SO by default; confirm order types in use. |
| SalesOrder.CustomerID | Deal ↔ Company association | Deal | ↔ Both | Matched on CustomerID. |
| SalesOrder.Date | acu_order_date | Deal | ACU → HS | Order date. |
| SalesOrder.Status | acu_order_status | Deal | ACU → HS | Drives the deal's fulfillment view. |
| SalesOrder.CurrencyID | deal_currency_code | Deal | ↔ Both | Must match the customer's currency rules. |
| SalesOrder.OrderTotal | amount | Deal | ACU → HS | Acumatica total after pricing and tax overwrites the estimate. |
| Details: InventoryID, OrderQty, UnitPrice | Line items (hs_sku, quantity, price) | Line item | ↔ Both | HubSpot lines become order lines; Acumatica reprices. |
| Branch | acu_branch | Deal | ↔ Both | Confirm field name in discovery. |
| Invoices & payments | ||||
| SalesInvoice.ReferenceNbr | acu_invoice_number | Invoice | ACU → HS | One HubSpot invoice record per Acumatica invoice. |
| Invoice amount and due date | acu_invoice_amount, acu_due_date | Invoice | ACU → HS | Confirm field names in discovery. |
| Invoice balance | acu_invoice_balance | Invoice | ACU → HS | Open amount still owed. |
| Payment amount and status | acu_last_payment_amount, acu_last_payment_date | Company | ACU → HS | Latest payment on the account. |
| Open balance per customer | acu_open_balance | Company | ACU → HS | Rolled up in the integration layer. |
Acumatica is set up by the client's administrator or Acumatica partner. Limits come from the client's license and are confirmed for each instance.
| Topic | Acumatica | HubSpot |
|---|---|---|
| Access model | Client-owned instance (Acumatica cloud or private hosting). A dedicated API user, which counts against the license's API user limit. | Self-serve in the client portal. Custom objects need an Enterprise hub. |
| Interfaces | Contract-based REST API at /entity/Default/<version>/; OData for generic inquiries and data tables; push notifications (SM302000). | REST APIs: CRM objects, products, line items, associations, imports. |
| Authentication | OAuth 2.0 through a connected application (SM303010), with client ID and shared secret. HTTPS required. | Private app access token or OAuth 2.0 public app, scoped per object. |
| Endpoint versioning | Pin one Default endpoint version. Extend it for custom fields (SM207000) or ship a custom endpoint in a customization package. | Versioned public APIs. |
| Change detection | Push notifications post inserted and deleted rows to a webhook with an ID for deduplication; a LastModifiedDateTime filter covers catch-up. | Webhooks for HubSpot changes such as deal stage. |
| Rate limits | Set by the license: API users, requests per minute and concurrent requests, shown on the License Monitoring Console (SM604000). Confirm the client's values. | Per-10-second burst and daily limits by subscription tier. |
| Tenants & branches | One tenant per login; companies and branches inside it. Confirm which tenants, companies and branches are in scope. | One portal; business units or teams can separate companies. |
Severity reflects impact on the SOW, not technical difficulty alone.
Acumatica's built-in CRM and HubSpot both hold leads and opportunities. Sign off record ownership in discovery, or the two systems will create duplicates of each other.
Requests per minute, concurrent requests and API users are capped by the license, and heavy API use can call for a larger resource level. Size sync intervals to the client's limits.
Orders sent from HubSpot must pass Acumatica pricing, tax and credit rules. Finance approves the order type, default values and error handling before writes go live.
If Acumatica's HubSpot connector already syncs contacts and leads, the custom build must not write the same fields. Agree the split field by field.
Custom fields, attributes and screens need endpoint extensions. Inventory them in discovery and plan endpoint upgrades as a change to the integration.
Orders and invoices carry a branch and currency. Map branches to HubSpot business units or teams and report in the deal's currency.
Sales closes in HubSpot and the order lands in Acumatica with the right customer, branch and lines, without rekeying.
Push notifications keep order status current on the deal, so reps answer customer questions without asking operations.
HubSpot products carry InventoryIDs and Acumatica prices, so quotes start from the same catalog finance invoices from.
The customer's open balance and last payment on the company record tell reps when to talk to finance first.
Order history drives HubSpot lists for reorder reminders, cross-sell by item class and win-back campaigns.
HubSpot pipeline and Acumatica orders and invoices meet in one dashboard, split by branch and customer class.
Each step hands the record to the system that owns it. HubSpot runs leads, the pipeline and the quote; Acumatica runs the order, the invoice and the payment, and reports back.
All custom properties use the acu_ prefix in an Acumatica property group. Rollups such as open balance are calculated in the integration layer so every report agrees.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| acu_customer_id | Acumatica Customer ID | Company | Single-line text | Customer.CustomerID; unique |
| acu_customer_class | Acumatica Customer Class | Company | Dropdown | Customer.CustomerClass |
| acu_customer_status | Acumatica Customer Status | Company | Dropdown | Customer.Status |
| acu_open_balance | Acumatica Open Balance | Company | Number (currency) | Sum of open invoice balances |
| acu_last_payment_date | Last Payment Date | Company | Date picker | Latest payment application date |
| acu_item_class | Acumatica Item Class | Product | Dropdown | Item class of the stock or non-stock item |
| acu_order_number | Acumatica Order Number | Deal | Single-line text | SalesOrder.OrderNbr; unique with order type |
| acu_order_type | Acumatica Order Type | Deal | Dropdown | SalesOrder.OrderType |
| acu_order_status | Acumatica Order Status | Deal | Dropdown | SalesOrder.Status |
| acu_branch | Acumatica Branch | Deal | Dropdown | Branch on the order |
| acu_invoice_number | Acumatica Invoice Number | Invoice | Single-line text | SalesInvoice.ReferenceNbr; unique |
| acu_invoice_balance | Acumatica Invoice Balance | Invoice | Number (currency) | Open amount on the invoice |
Choose the Acumatica areas and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.
Based on public documentation from Acumatica and HubSpot. Each item marked for confirmation is verified against the client's instance during the access phase.
Yes. Acumatica’s own HubSpot connector syncs contacts, customer and lead information, MQLs and campaign results. Campaign Creators extends it with a custom integration layer for what the connector leaves out: sales orders, invoices, payments, items and pricing across the full quote-to-cash cycle.
Customers and contacts sync to HubSpot companies and contacts; stock and non-stock items and their prices sync to HubSpot products; won HubSpot deals create Acumatica sales orders; and Acumatica order status, invoices, payments and open balances are written back to HubSpot.
Each record has one owner. HubSpot owns leads, the relationship and the pipeline; Acumatica owns customer accounts once created, items, prices, tax, orders, invoices and payments. Because Acumatica’s built-in CRM also holds leads and opportunities, this split is signed off in discovery before any sync runs.
Seven phases, each closed by a client sign-off: discovery and record ownership, access and license check (a connected application and a dedicated API user), match rules and field list, HubSpot data model, read flows, write flows, and historical backfill with a two-week parallel run before writes are switched on.
Timeline and cost depend on the records, custom fields and Acumatica features in scope (for example multiple companies, branches and currencies, endpoint customizations and the client’s license limits). Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.