Source ERP · 18 of 89
CRMPro → HubSpot — Epicor 11 Kinetic: 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/epicor-11-kinetic". 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/epicor-11-kinetic-hubspot/.
CRMPro → HubSpot — Epicor 11 Kinetic: 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/epicor-11-kinetic (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 contact | ERP customer contacts, customers, sales reps data becomes contact in HubSpot | contact | customer contacts, customers |
| Create Customer | The templates push company to HubSpot | company | customers |
| Create Product | The templates push product to HubSpot | product | parts |
| create sales order | The templates push deal to HubSpot | deal | sales order headers, customers |
| create order line | The templates push line item to HubSpot | line item | sales order lines |
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 Customer | company | 1 |
| Create Product | product | 3 |
| create contact | contact | 5 |
| create sales order | deal | 8 |
| create order line | line item | 9 |
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 | Emits the linked Salesforce record | Source tables |
|---|---|---|---|
| new customer feed | insert only | no | customers |
| new item feed | insert only | no | parts |
| new contact feed | insert + update | no | customer contacts, customers |
| new sales order feed | insert only | no | sales order headers, customers |
| new order line item feed | insert only | yes | sales order lines |
4. Order of work
The templates set run sequence to 1, 3, 5, 8, 9. A run processes active rows in ascending run sequence, which is the order the templates put them in:
- 1 — create Customer
- 3 — Create Product
- 5 — create contact
- 8 — create sales order
- 9 — create order line
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 contact feed reads new customer sync output
- new sales order feed reads new customer sync output, new contact sync output, Order; no template in this set writes Order
- new order line item feed reads new order sync output, new item sync output, Order; no template in this set writes new order sync output, Order
5. Field mapping
Each template carries its intended mapping in field mapping.
| Template | Object | Mapped fields | First ERP → HubSpot pairs |
|---|---|---|---|
| create Customer | company | 10 | Company, Customer identifier → Commercient AR customer code, Name → name, Address 1 → address, Address 2 → address line 2 property, City → city property |
| Create Product | product | 6 | Part number → stock keeping unit property, Part number → name, Part description → description, Company,Part number → record key, Company,Part number → external key property |
| create contact | contact | 11 | Company, Customer number, Shipping address number, Contact number → external key property, Given name → first name property, Family name → last name property, Email address → email, Phone number → phone |
| create sales order | deal | 9 | Company, Order number → external key property, Order date → create date property, Order date → close date property, Company, Order number → deal name property, Order amount → amount |
| create order line | line item | 6 | Document unit price → price, Order quantity → quantity, Part number → product lookup property, Part number → name, Epicor line description → description |
6. Community templates
The catalogue carries 171 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: 171
- Default operations: insert on 171, update on 171, delete on 171
- Marked as circular sync: 0
- Licence groups they span: 9
- Destination objects: company, deal, line item, contact, product, invoice, Contact Matching (custom object), Account Matching (custom object), order, Data Matching (custom object), orders, Product Matching (custom object), products, quote, Company Matching view (custom object), HubSpot update customer (custom object) and 8 custom objects
- Object display names: create Customer, upsert invoice, upsert sales order, upsert contact, upsert Customer, upsert order line, create contact, upsert invoice line, upsert Product, create order line, Create Product, create sales order, 52 more and 9 further templates
- Template groups: Account, CRM Opportunity and Line, CRM Order and Line, Product, CRM Quote and Line, Customer Multi Ship Addresses
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/epicor-11-kinetic.
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 Epicor 11 Kinetic → 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/epicor-11-kinetic, 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.
