HubSpot + Aptean integration

Aptean is less one ERP than a portfolio of them. It has added products by acquisition, WorkWise among them, and it now sells food and beverage, process, industrial and distribution systems under its own name, several with an edition suffix that still names the product it started as. For a HubSpot project, that history matters more than the logo on the login screen.

The request itself is familiar. A food processor or an industrial manufacturer runs production and finance on Aptean, while sales and marketing have moved to HubSpot. Aptean’s own answer to CRM is Aptean CRM, which its AppCentral platform connects to Made2Manage through documented integrations. Teams on HubSpot get none of that, so sellers cannot see open orders, invoice status or what an account buys without asking the office.

What decides the build is the foundation under the product. Aptean’s Food and Beverage ERP is built on Microsoft Business Central, and Aptean describes its process manufacturing ERPs as built on the Dynamics 365 foundation. Its Food and Beverage ERP Enterprise Edition runs on Dynamics 365 Finance and Operations. Its industrial editions, Made2Manage, Intuitive and WorkWise, are Aptean products in their own right, and none has a public API reference. Only the Business Central editions come with Microsoft’s documented API, so scoping starts by naming the product and the platform beneath it.

On a Business Central edition, five objects carry the relationship. Customers map to HubSpot companies and sales orders to deals, posted sales invoices sit on a custom object tied to their order, and items feed the product library. The fifth object is small and deliberate: the lot numbers each posted shipment carried, stored as reference text.

Everything moves one way. The ERP owns the customer, the price, the stock and the invoice, and HubSpot presents them as read-only reference.

Keys come from Business Central. Customers key on the customer number, orders and invoices on their document numbers, items on the item number, each stored in its own HubSpot property. Names get tidied; numbers do not.

The lot object needs care for a different reason. Aptean sells its food ERP on traceability and recall readiness, and the answer to a recall has to come from the ERP’s own records. HubSpot must never become a second version of that trail, so it receives lot numbers as text on the shipment and nothing else, and nothing in HubSpot writes back.

Events drive this sync, and a nightly sweep checks it. A Microsoft Entra application authenticates with the OAuth client credentials flow, which Microsoft documents for unattended service to service access on Business Central online and on premises.

The service subscribes to customers, sales orders and invoices. Business Central delays each notification by thirty seconds, and when more than a thousand records change during that delay it sends a single collection notice carrying a filter. The consumer reads the full record, or the filtered page, and upserts into HubSpot on the Business Central numbers, then runs an association pass.

Microsoft’s standard item ledger entry resource has no lot number field, so we add a custom API page as a small extension. Built on a table with a single key, such as the item ledger, it can take webhook subscriptions of its own. Subscriptions expire after three days, so a daily job renews them. A nightly sweep re-reads records modified since the last sweep and repairs anything the stream missed.

The edition decides this, more than budget does. On a Business Central edition, a service on API v2.0 is the route that carries orders and invoices at near real time, and it is the one we recommend.

On the industrial editions the marketplace offers Commercient’s third-party app, named for Aptean Industrial Manufacturing. It fits a team that can live with Commercient’s mapping and does not want to run anything itself, and it leaves the runtime and the roadmap with Commercient. A build there starts from the Web API Aptean documents for Made2Manage, once Aptean shares its reference.

An iPaaS is the route we steer away from on every edition. It meets the same Business Central limits as any client and charges per task on every order line.

1. Scope. We confirm the Aptean product, the platform underneath, whether it runs online or on premises, and which objects sellers need.
2. Architect. We fix the Business Central numbers as keys, the webhook subscriptions, the sweep cadence and the fields the lot API page exposes.
3. Build. The service and the API page are built against a sandbox or a copy of the environment, and an allowlist blocks writes to any other portal.
4. Validate. Aptean’s own reports set the benchmark for record counts and open order values, and the finance lead signs off each difference.
5. Operate. We watch the queue and the sweep, renew subscriptions daily, and re-test the lot API page after every Aptean update.