Source ERP · 2 of 89
CRMPro → HubSpot — Acumatica Cloud: what the shipped templates set up
This is the capability summary the dlake CLI repository publishes; whitelisted customers fetch the operational skill with "dlake admin get_skill dlake-crmpro-hubspot/erps/acumatica-cloud". It extends the dlake-crmpro-hubspot skill, which holds what is true whatever the source ERP. Both directions for this pair are summarised at /integrations/acumatica-cloud-hubspot/.
CRMPro → HubSpot — Acumatica Cloud: what the shipped templates set up
This is a capability summary, not an operating guide. To receive the operational skill you must be a
registered, whitelisted Commercient customer. Whitelisted customers fetch it with
dlake admin get_skill dlake-crmpro-hubspot/erps/acumatica-cloud (or list_skills) against the
Commercient admin plane. Existing customers who need access or help: contact
support@commercient.com. New customers: contact sales@commercient.com to become a customer and be
whitelisted.
dlake-crmpro is the parent skill and the authority for everything general: the CRMPro tools, process configuration and field list, the sync history, how source data is selected, and what a run that finds nothing does. Read it first; this page does not repeat it. dlake-crmpro-hubspot is the destination skill this page is a child of, and the authority for the HubSpot conventions that hold across every ERP: read it first, then come back here for what this source’s own templates set. This page grows as the catalogue does.
1. What the templates deliver
| Group | Business outcome | Objects | Source tables and views |
|---|---|---|---|
| create invoice | The templates push deal to HubSpot | deal | sales invoices |
| create invoice detail | The templates push line item to HubSpot | line item | sales invoice lines |
| create order | The templates push deal to HubSpot | deal | sales orders |
| create order detail | The templates push line item to HubSpot | line item | sales order details |
| create quote | The templates push deal to HubSpot | deal | sales orders |
| create quote detail | The templates push line item to HubSpot | line item | sales order details |
| create product | ERP stock items data becomes product in HubSpot | product | stock items |
| create company | ERP customers, contacts, customer contacts data becomes company in HubSpot | company | customers, contacts, customer contacts |
| (ungrouped) | The templates push deal to HubSpot | deal | — |
2. The process rows the templates create
Each template’s setup writes one process configuration row. These are the values it sets; a column the inserts never set is not listed.
| Display name | Destination object | Run sequence |
|---|---|---|
| create company | company | 5 |
| create product | product | 10 |
| create invoice | deal | 11 |
| create invoice detail | line item | 12 |
| create order | deal | 13 |
| create order detail | line item | 14 |
| create quote | deal | 15 |
| create quote detail | line item | 16 |
Every one of these inserts the active setting as 0, so an imported process is inactive until an operator activates it.
3. The views
“Change detection” names which of the three kinds dlake-crmpro defines the view’s own filter makes it; where a view’s shape is not one of those three the column is left empty and the view’s own filter is the authority.
| View | Change detection | Source tables |
|---|---|---|
| new customer feed | insert only | customers, contacts, customer contacts |
| new item feed | insert only | stock items |
| new invoice deal feed | insert only | sales invoices |
| new invoice line item feed | insert only | sales invoice lines |
| new order deal feed | insert only | sales orders |
| new order line item feed | insert only | sales order details |
| new quote deal feed | insert only | sales orders |
| new quote line item feed | insert only | sales order details |
4. Order of work
The templates set run sequence to 5, 10, 11, 12, 13, 14, 15, 16. A run processes active rows in ascending run sequence, which is the order the templates put them in:
- 5 — create company
- 10 — create product
- 11 — create invoice
- 12 — create invoice detail
- 13 — create order
- 14 — create order detail
- 15 — create quote
- 16 — create quote detail
These views read another process’s sync output, which is what makes the order a dependency order: the row appears in the view only once the process that writes that sync output has run, so a parent flows on one run and its children on the next.
- new invoice deal feed reads new customer sync output, invoice record sync output (generic name); no template in this set writes invoice record sync output (generic name)
- new invoice line item feed reads new item sync output, invoice record sync output (generic name); no template in this set writes invoice record sync output (generic name)
- new order deal feed reads new customer sync output, Order; no template in this set writes Order
- new order line item feed reads new item sync output, Order; no template in this set writes Order
- new quote deal feed reads new customer sync output, quote sync output (generic name), opportunity sync output (generic name); no template in this set writes quote sync output (generic name), opportunity sync output (generic name)
- new quote line item feed reads new item sync output, quote sync output (generic name); no template in this set writes quote sync output (generic name)
5. Field mapping
Each template carries its intended mapping in field mapping.
| Template | Object | Mapped fields | First ERP → HubSpot pairs |
|---|---|---|---|
| deal | deal | 4 | Contact identifier → Commercient AR contact code, Contact name → Name, Contact email → Email, Contact phone → Phone |
| create company | company | 9 | Customer identifier → Commercient AR customer code, Customer name → name, Main address line 1 → address, Main address line 2 → address line 2 property, Address city → city property |
| create product | product | 6 | Inventory identifier → stock keeping unit property, Description → name, Description → description, Current standard cost,Last cost → cost of goods sold property, Default price → price |
| create invoice | deal | 8 | Reference number → external identifier property, Due date → close date property, Date → create date property, Amount → amount, Description,Reference number → deal name property |
| create invoice detail | line item | 5 | Inventory identifier → product lookup property, Sales invoice number → deal association, Unit price → price, Quantity → quantity, Inventory identifier, Description → name |
| create order | deal | 8 | Order number → external key property, Effective date → close date property, Date → create date property, Order total → amount, Order number, Description → deal name property |
| create order detail | line item | 6 | returned inventory identifier → product lookup property, Order number → deal association, Unit cost → price, Order quantity → quantity, Order line description → name |
| create quote | deal | 10 | Order number → record key, Order number → external key property, Effective date → close date property, Date → create date property, Order total → amount |
| create quote detail | line item | 5 | returned inventory identifier → product lookup property, Order line description → name, Order quantity → quantity, Unit price → price, Order number → deal association |
6. Community templates
The catalogue carries 10 community templates for this pair. A community template is authored in a tenant rather than shipped with the product, and it imports the same way as any other. Its own names, notes, field mapping and SQL are tenant content, so what this section states is what the set amounts to: how many templates there are, what they default to doing, which destination objects they write and which groups they fall in. They are not part of the shipped set described above.
- Templates: 10
- Default operations: insert on 10, update on 10, delete on 10
- Marked as circular sync: 0
- Licence groups they span: 2
- Destination objects: line item, company, deal, Commercient Contact object, product and a custom object
- Object display names: create item, delete line item, Sync Contact, update company, upsert company, upsert inventory item, upsert invoice deal, upsert invoice line item, upsert order deal, upsert order line item
- Template groups: Account
7. Verifying
The detail of this section is part of the operational skill. Whitelisted customers fetch it with
dlake admin get_skill dlake-crmpro-hubspot/erps/acumatica-cloud.
8. Where this sits
dlake-crmpro is the general operating surface — the CRMPro tools, the setup and transaction tables, field mapping, and the source view contract that applies to every destination. This page adds what the shipped Acumatica Cloud → HubSpot templates set up. dlake-crmpro-hubspot is the destination skill this page sits under: its own text is the authority for the HubSpot conventions that hold across every ERP, and its ERP table lists this page alongside every sibling ERP page for this destination. For the extract leg that fills the source data, see dlake-normalsync; for the on-premises agent that runs it, dlake-syncagent; for the writeback leg, dlake-txdownloaderpro; for standing an integration up, dlake-integration-setup.
How to get started
- Already a customer: the operational skill tells you how to connect, choose what to sync and run it.
Fetch it with
dlake admin get_skill dlake-crmpro-hubspot/erps/acumatica-cloud, or ask support@commercient.com. - New to Commercient: contact sales@commercient.com. Becoming a customer includes registration and whitelisting, after which the operational skills and tools are available to you.
