How customers, contacts, parts, quotes, sales orders and AR invoices in Epicor Kinetic connect to HubSpot, so sales works the full quote-to-cash picture from HubSpot while Kinetic keeps running manufacturing and finance.
Epicor Kinetic is a manufacturing ERP. It holds the customer master, the part catalog, quotes, sales orders, shipments and receivables. HubSpot does not offer its own app for Kinetic, so the connection is a custom build on Kinetic's own APIs.
Public documentation. The client's own admin issues credentials, with no vendor approval needed.
Open API. Interactive REST help is built into each Kinetic instance. The client's administrator issues an API key and an integration user.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
Kinetic exposes nearly everything in its user interface as REST services, so a direct Kinetic-to-HubSpot integration is a strong fit.
Campaign Creators assessment
Epicor publishes the Kinetic REST API as OData v4 services, secured with API keys, access scopes and standard authentication tied to existing ERP user permissions. Business Activity Queries (BAQs) and Epicor Functions are also callable over REST, which lets CC shape exactly the data HubSpot needs without changing Kinetic. The decisions that set the scope are business ones: which system creates customers, where quotes for configured parts are built, and how multiple companies and sites map into one HubSpot portal.
Ratings are CC judgments from Epicor's public materials. Service names, field names and limits are confirmed in the client's own Kinetic REST help during discovery, because UD fields and versions differ by instance.
Kinetic's REST services use the same architecture as its own screens, so anything a user can see in Kinetic can be read or written by the integration, including custom UD fields.
Configured products are priced by Kinetic's configurator, and many Kinetic tenants run several companies and sites. Both need a clear rule in HubSpot before any build starts.
The client's Kinetic administrator issues an API key with the right access scope and a dedicated integration user. Nothing is built until a test call succeeds against the client's test environment.
Seven Kinetic capabilities matter to a HubSpot build. Five carry the integration, one shapes data for it, and one is a scope decision the client makes up front.
Kinetic's standard business objects as OData services, with filtering, field selection and metadata discovery.
$filter, $select and pagingThe customer master, ship-to addresses and customer contacts.
Quote headers and lines, the bridge between a HubSpot deal and a Kinetic sales order.
Booked orders, open order value, invoices and balances due.
Saved queries the client already uses, exposed as REST endpoints. Ideal for rollups such as sales by customer or open order value.
Reusable functions inside Kinetic that HubSpot can call through the API, for example to create a customer with the client's own defaults.
Configured products get their price and bill of materials from Kinetic. The client decides whether reps build these quotes in Kinetic or start them from HubSpot.
A CC-built integration layer reads Kinetic's REST services on a schedule, matches each record to HubSpot, and writes in batches. For the few actions that flow back, such as creating a customer from a won deal, it calls Kinetic services or Epicor Functions so Kinetic's own rules run.
HubSpot owns prospects, contacts and pipeline. Kinetic owns customer accounts once created, parts, prices, orders and invoices. The SOW lists the owner of every field.
Pricing, configuration, credit and tax are calculated by Kinetic. HubSpot stores the results and never recalculates them.
Rollups come from BAQs the client can see and audit. Writes go through business object services or Epicor Functions, never directly to the database.
Each phase ends on a gate the client signs off before the next begins. Read-only flows go live first, so sales sees ERP data in HubSpot before any write-back is switched on.
Confirm the Kinetic deployment (cloud or on-premises), the companies and sites in scope, and the HubSpot hubs and tiers. The client's administrator issues an API key, an access scope and an integration user in a test environment.
Agree which system creates customers, contacts and parts, where configured-part quotes are built, and how Kinetic companies map to HubSpot.
Read each service's metadata from the client's REST help, list UD fields in use, and select the BAQs that will feed rollups.
Create properties, products, the deal and order pipelines, association labels and property groups in a HubSpot sandbox.
Build customers, contacts, parts, quotes, orders and invoices into HubSpot with change tracking, idempotent writes and an error replay queue.
Build the won-deal path into Kinetic, then load current customers, open quotes, open orders and an agreed invoice history.
Run two weeks in parallel with workflows paused, then switch on automations and hand over monitoring.
Object names follow Kinetic's standard business objects. Field names are shown where Epicor's standard tables use them and are confirmed against the client's own REST help, since UD fields and versions vary by instance.
| Kinetic field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Customers & contacts · Customer, CustCnt | ||||
| Customer.CustID | ek_cust_id | Company | EK → HS | Match key. Unique per Kinetic company. |
| Customer.Name | name | Company | ↔ Both | HubSpot fills blanks only once Kinetic owns the account. |
| Customer address fields | address, city, state, zip, country | Company | EK → HS | Billing address from the customer master. |
| Ship-to addresses | Ship-to (association label) | Company | EK → HS | Child companies or a custom object. Confirm in discovery. |
| Territory and sales rep | ek_territory, hubspot_owner_id | Company | EK → HS | Sales rep mapped to a HubSpot owner. |
| Terms, credit limit, credit hold | ek_terms, ek_credit_hold | Company | EK → HS | Read only in HubSpot. |
| CustCnt name, email, phone | firstname, lastname, email, phone | Contact | ↔ Both | Email is the contact match key. |
| New customer from won deal | Customer (create) | Company | HS → EK | Created through the Customer service or an Epicor Function. |
| Parts & pricing · Part, price lists | ||||
| Part.PartNum | hs_sku | Product | EK → HS | Match key for products. |
| Part description | name, description | Product | EK → HS | |
| Product group and class | ek_product_group | Product | EK → HS | Used for reporting and line-item rules. |
| List price | price | Product | EK → HS | Base price only. Customer price lists stay in Kinetic. |
| Inactive flag | ek_part_active | Product | EK → HS | Inactive parts hidden from new HubSpot quotes. |
| Quotes · QuoteHed, QuoteDtl | ||||
| QuoteHed.QuoteNum | ek_quote_num | Deal | ↔ Both | Links the HubSpot deal to the Kinetic quote. |
| Quote status and expiration | ek_quote_status, ek_quote_expires | Deal | EK → HS | Drives deal stage rules. |
| Quote total | amount | Deal | EK → HS | Kinetic's calculated value, including configured lines. |
| QuoteDtl lines | Line items | Line item | EK → HS | Part, quantity and price per line. |
| Won deal | Quote or sales order (create) | Deal | HS → EK | Only for the paths chosen in the SOW. |
| Sales orders · OrderHed, OrderDtl | ||||
| OrderHed.OrderNum | ek_order_num | Order | EK → HS | Unique. Associated to company, contact and deal. |
| Order date and need-by date | ek_order_date, ek_need_by_date | Order | EK → HS | |
| Order total and currency | hs_total_price, hs_currency_code | Order | EK → HS | Document currency kept as entered. |
| Open or closed status | hs_pipeline_stage | Order | EK → HS | Mapped to an order pipeline. |
| OrderDtl lines | Line items | Line item | EK → HS | Part, quantity and price per line. |
| AR invoices | ||||
| Invoice number and date | ek_invoice_num, invoice date | Invoice | EK → HS | HubSpot invoice object or custom object. Confirm in discovery. |
| Invoice amount and balance | ek_invoice_balance | Invoice | EK → HS | Balance due updates as payments post. |
| Open AR by customer | ek_open_ar | Company | EK → HS | Rollup from a BAQ. |
| Last invoice date | ek_last_invoice_date | Company | EK → HS | Drives reorder and win-back workflows. |
Kinetic access is granted by the client's own administrator. Values Epicor does not publish are marked for confirmation.
| Topic | Kinetic | HubSpot |
|---|---|---|
| Interfaces | Kinetic REST API (OData v4) for business objects and BAQs; Epicor Functions as custom REST services. Interactive REST help in each instance shows the services available. | REST APIs: CRM objects, associations, products, line items, orders, imports. |
| Authentication | API key with access scopes, plus standard authentication (for example basic or token) for an integration user whose ERP permissions limit what it can see. Confirm the method for the client's deployment. | Private app access token or OAuth 2.0 public app, scoped per object. |
| Access model | Issued by the client's Kinetic administrator for a dedicated integration user. | Self-serve in the client portal. Custom objects need an Enterprise hub. |
| Multi-company | The Kinetic company is part of each request. Sites (plants) sit inside a company. | One portal. Companies map to business units or a company property. |
| Change detection | Filter on change dates where the table carries them, or use a BAQ built for the sync. Confirm per object in discovery. | Writes are immediate; batch endpoints handle volume. |
| Rate limits & paging | OData paging with $top and $skip. Rate limits for Kinetic cloud are not published. Confirm with Epicor. | Per-10-second burst and daily limits by subscription tier. |
| Customizations | UD fields and BAQs appear in the REST metadata once published. Upgrades are retested before release. | Custom properties and custom objects created per the approved schema. |
Severity reflects impact on the SOW, not technical difficulty alone.
Kinetic's configurator sets price and structure for configured parts. HubSpot cannot reproduce that logic, so the SOW names where these quotes are built and HubSpot only shows the result.
Kinetic and HubSpot can both add accounts. Without one creation path, duplicates appear in both systems. The won-deal handoff is the usual single path.
One customer can exist in several Kinetic companies with different IDs. The match rule and the HubSpot company structure are agreed before the build.
Every Kinetic instance has its own UD fields and BAQs. Budget a short field inventory against the client's REST help rather than relying on standard field lists.
Kinetic cloud receives regular updates from Epicor. Include a regression check of the integration in the client's upgrade routine.
Customer-specific price lists and discounts can be large. Sync list prices to HubSpot products and leave customer pricing in Kinetic unless a use case needs it.
Open quotes, open orders, invoice balance and credit hold sit beside every email and meeting, so reps walk into calls prepared.
A won deal creates the Kinetic customer and contacts, so order entry starts from clean data.
Last order date and order frequency by part class drive HubSpot tasks and sequences when a customer goes quiet.
Quotes near expiration enter HubSpot workflows, so no quote expires without a follow-up.
Reps see a credit hold before they promise a delivery, and a workflow alerts the account owner.
Orders and invoices in HubSpot let leaders compare pipeline, bookings and billed revenue in one dashboard.
The integration follows the path a sale already takes. Each step has one system in charge, and the other system sees the result.
All custom properties use the ek_ prefix in an Epicor Kinetic property group. Rollups come from BAQs so HubSpot and Kinetic reports agree.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| ek_cust_id | Kinetic Customer ID | Company | Single-line text | Customer.CustID; unique per company |
| ek_company | Kinetic Company | Company | Dropdown | Kinetic company the customer belongs to |
| ek_territory | Territory | Company | Dropdown | Customer territory |
| ek_terms | Payment Terms | Company | Single-line text | Customer terms |
| ek_credit_hold | Credit Hold | Company | Single checkbox | Customer credit hold flag |
| ek_open_ar | Open AR | Company | Number (currency) | BAQ: sum of open invoice balances |
| ek_open_order_value | Open Order Value | Company | Number (currency) | BAQ: sum of open order lines |
| ek_last_invoice_date | Last Invoice Date | Company | Date | Most recent AR invoice |
| ek_quote_num | Kinetic Quote Number | Deal | Single-line text | QuoteHed.QuoteNum |
| ek_quote_status | Kinetic Quote Status | Deal | Dropdown | Quote header status |
| ek_order_num | Kinetic Order Number | Order | Single-line text | OrderHed.OrderNum; unique |
| ek_product_group | Product Group | Product | Dropdown | Part product group |
Choose the Kinetic objects 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. Service names, UD fields and limits are confirmed in the client's own Kinetic REST help during discovery.
Yes, but HubSpot does not offer its own app for Kinetic, so the connection is a custom build. Epicor publishes the Kinetic REST API as OData v4 services, secured with API keys and access scopes tied to existing ERP user permissions, plus callable Business Activity Queries and Epicor Functions, all shapeable without changing Kinetic itself.
Customers and contacts, parts and price lists, quotes, sales orders and AR invoices sync from Kinetic to HubSpot companies, deals and line items. A won HubSpot deal can create the customer in Kinetic, and invoice and balance data flows back so sales sees what was billed and paid.
Kinetic runs the order: quotes for configured parts, booked sales orders and invoicing stay in Kinetic and HubSpot never edits them. HubSpot runs the deal, holding the prospect and company record, with the two systems meeting at the point a deal is won and becomes a Kinetic customer.
Seven phases, each closed by a client sign-off: discovery and API access through the client's own Kinetic administrator, a data-ownership decision on which system creates customers and quotes, a field inventory against the client's own REST help (UD fields and versions differ by instance), the HubSpot data model, building the inbound sync flows, building write-back and backfill, and a parallel run before launch.
Timeline and cost depend on the client's Kinetic companies and sites, which business objects and BAQs are in scope, and how quotes for configured parts are handled. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.