HubSpot + Macola integration

Macola was built for small and mid-sized manufacturers and distributors, and ECI Software Solutions, which owns it now, lists it for existing customers only. Its Macola page points readers to JobBOSS², M1 and Deacom instead. For the shops still running Macola 10, that leaves a working ERP beneath a sales process that increasingly lives somewhere else.

Macola 10 has CRM built in. ECI describes it holding every lead and quote request, linking opportunities to sales quotes and measuring how many turn into orders. Teams that move marketing and pipeline to HubSpot keep Macola for the customer, the price, the order and the invoice, then need those facts in front of sellers who no longer open Macola at all. Macola 10 also runs finance and distribution, so the customer sits beside open orders, invoices and payment terms, the things a seller would otherwise phone the office to ask about.

The route is narrower than it first looks. ECI’s product-agnostic ERP API reads Macola’s customers, contacts, quotes, sales orders and invoices, and it creates customers, contacts and orders for JobBOSS² only. That one fact shapes the design: Macola stays the master for every record it holds, and HubSpot receives a faithful, current copy that sellers can report on.

Five objects, all moving one way. Macola customers, which the ERP API calls organizations, become HubSpot companies, and their contacts become contacts. Quotes become deals. Sales orders and AR invoices land on custom objects, and each order carries the quoteID it came from, so it ties back to the deal that won it.

Macola exposes more sales detail through this API than its sibling products do. Its quotes carry an award probability and a lost sale code, its orders carry an order type, an original order type, a status and a total, and its invoices carry a balance and a paid date. Those fields map to deal and custom object properties that a pipeline report can actually use, which is most of the reason to connect the two.

Keys are the ERP API’s uniqueID, a GUID for Macola records, held in a custom HubSpot property. ECI guarantees it only within one resource and one company account, so each property records the resource it belongs to, and the association pass joins on the customer and quote IDs the API returns.

Macola’s side of the ERP API is read on a schedule, one watermark per resource. The service holds OAuth 2.0 client credentials issued in ECI’s Integration Engine Management Console, caches each 60 minute token, and reads organizations, contacts, quotes, sales orders and invoices in turn, asking for rows whose rowVersion is above the last value saved. ECI documents rowVersion as rising on every new or updated record, and every one of those Macola resources can be filtered and sorted on it.

Pages come back through take and skip. Each batch is upserted into HubSpot on the stored GUID, and only then does the watermark for that resource move. An association pass follows, joining contacts and quotes to companies and orders to the quotes they came from.

Reconciliation uses the API’s count parameter, which returns a total without the rows, compared with HubSpot per resource after each cycle. A replay endpoint re-reads any resource from a chosen rowVersion.

What decides this for Macola is whether ECI will activate its API for your install. With the ERP API switched on, a custom API integration reads exactly the objects above, on watermarks ECI documents, and much of it carries over to M1 or JobBOSS², which the same API serves.

Without the API, the database is the route. ECI describes Macola 10’s reporting as built on SQL Server Reporting Services, with ad hoc reports written as plain SQL queries, so a managed sync on Skyvia can read a read-only SQL login through its on-premises agent. It needs no activation, and it trades the API’s documented resources for table knowledge we build in discovery. Commercient’s ECI Macola app is the third route, with its mapping and support on Commercient’s side.

1. Scope. We confirm your Macola release, whether ECI will activate the ERP API for it and which objects sellers need, and ask about CRM history.
2. Architect. We fix the five resources, the GUID keys, the rowVersion watermarks, the API version and the rule for converted quotes.
3. Build. The service is written against your install with a read-only API user and a HubSpot portal allowlist that fails closed.
4. Validate. We reload every resource into a HubSpot sandbox, reconcile totals with count-only queries, and walk open quotes with the sales lead.
5. Operate. We watch run times and counts, keep replay available, and retest the pinned API version whenever ECI publishes a new one.