Integration Products | Campaign Creators

Epicor Kinetic HubSpot Integration | Campaign Creators

Written by Campaign Creators | Nov 19, 2026, 6:25:36 AM
Integration Assessment
Integration Assessment · ERP

Epicor Kinetic × HubSpot

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.

Manufacturing ERPKinetic REST API v2OData v4Business Activity QueriesEpicor FunctionsBuilt per company and site
Platform ownerEpicor Software
Integration typeCustom, REST API
Primary directionKinetic → HubSpot
FeasibilityStrong fit
API accessOpen API
01 — Summary

Does Epicor Kinetic integrate with HubSpot?

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.

API access
Open APIOpen with conditionsGated API

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.

Scorecard
API coverageHigh
Public docsGood
Data model fitGood
Build complexityModerate

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.

Strength

The UI and the API are the same services

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.

Plan for

Configured parts and multi-company

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.

Gate

An API key and a service user

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.

02 — API modules

Which Epicor Kinetic APIs does the integration use?

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.

Core

Business Object services

REST API v2 · OData v4

Kinetic's standard business objects as OData services, with filtering, field selection and metadata discovery.

  • Customer, contact, part, quote, sales order and AR invoice services
  • Query with $filter, $select and paging
  • Company ID is part of every request
Core

Customer and contacts

Customer · CustCnt

The customer master, ship-to addresses and customer contacts.

  • Customer ID is the match key to HubSpot companies
  • Contacts belong to a customer and ship-to
  • Credit hold, terms and territory travel with the record
Core

Quotes

QuoteHed · QuoteDtl

Quote headers and lines, the bridge between a HubSpot deal and a Kinetic sales order.

  • Quote status and value on the HubSpot deal
  • Lines become HubSpot line items
  • Accepted quotes convert to sales orders in Kinetic
Core

Sales orders and invoices

OrderHed · OrderDtl · AR invoices

Booked orders, open order value, invoices and balances due.

  • Orders appear as HubSpot orders on the company
  • Invoice balances show on the company record
  • Revenue reporting by customer and part class
Shapes data

Business Activity Queries

BAQ services over REST

Saved queries the client already uses, exposed as REST endpoints. Ideal for rollups such as sales by customer or open order value.

  • One call returns a joined, filtered result
  • Avoids many object-by-object calls
  • Changes to a BAQ are tested before release
Write-back

Epicor Functions

Custom server logic over REST

Reusable functions inside Kinetic that HubSpot can call through the API, for example to create a customer with the client's own defaults.

  • Keeps Kinetic's business rules inside Kinetic
  • One call per business action
  • Versioned with the client's other customizations
Scope decision

Quoting for configured parts

Kinetic configurator · Epicor CPQ

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.

  • Option A: quote in Kinetic, sync the result to the HubSpot deal
  • Option B: start the quote in HubSpot for standard parts only
  • Recorded in the SOW before build
03 — Framework

How does the Epicor Kinetic HubSpot integration work?

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.

Epicor Kinetic
Customer & contactsCustomer, CustCnt services
Parts & pricingPart service, price lists
Quotes & sales ordersQuoteHed, OrderHed and lines
AR invoices & BAQsbalances, rollups, saved queries
CC integration layer
Scheduled readerchanged records since last run
Company & site routerKinetic company → HubSpot business unit or property
Identity matcherCustomer ID · email · domain
HubSpot writerbatch upserts, associations
Write-back servicewon deal → customer or order in Kinetic
HubSpot
Companies & contactscustomers, ship-tos, buyers
Productsparts and list prices
Deals, quotes & line itemspipeline and Kinetic quotes
Orders & invoicesbooked orders, balances due
Reports & workflowsreorder, credit hold and renewal views
Kinetic → HubSpot (primary flow)HubSpot → Kinetic (new customers, contacts and orders from won deals)
Principle

Each record has one owner

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.

Principle

Kinetic's rules stay in Kinetic

Pricing, configuration, credit and tax are calculated by Kinetic. HubSpot stores the results and never recalculates them.

Principle

Read with BAQs, write with services

Rollups come from BAQs the client can see and audit. Writes go through business object services or Epicor Functions, never directly to the database.

04 — Process

What does Epicor Kinetic HubSpot integration setup involve?

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.

1

Discovery & access

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.

Gate to next phaseSuccessful test call to the client's test environment
2

Data ownership

Agree which system creates customers, contacts and parts, where configured-part quotes are built, and how Kinetic companies map to HubSpot.

Gate to next phaseSigned field ownership matrix
3

Field inventory

Read each service's metadata from the client's REST help, list UD fields in use, and select the BAQs that will feed rollups.

Gate to next phaseApproved field list with Kinetic and HubSpot names
4

HubSpot data model

Create properties, products, the deal and order pipelines, association labels and property groups in a HubSpot sandbox.

Gate to next phaseSchema approved and created in sandbox
5

Build inbound flows

Build customers, contacts, parts, quotes, orders and invoices into HubSpot with change tracking, idempotent writes and an error replay queue.

Gate to next phaseAll inbound flows running in sandbox with clean reconciliation
6

Build write-back and backfill

Build the won-deal path into Kinetic, then load current customers, open quotes, open orders and an agreed invoice history.

Gate to next phaseHubSpot totals reconcile to Kinetic reports within an agreed tolerance
7

Parallel run & launch

Run two weeks in parallel with workflows paused, then switch on automations and hand over monitoring.

Gate to next phaseFive consecutive days with no unresolved sync errors
05 — Data mapping

What does the Epicor Kinetic HubSpot integration sync?

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 fieldHubSpot propertyObjectDirectionNotes
Customers & contacts · Customer, CustCnt
Customer.CustIDek_cust_idCompanyEK → HSMatch key. Unique per Kinetic company.
Customer.NamenameCompany↔ BothHubSpot fills blanks only once Kinetic owns the account.
Customer address fieldsaddress, city, state, zip, countryCompanyEK → HSBilling address from the customer master.
Ship-to addressesShip-to (association label)CompanyEK → HSChild companies or a custom object. Confirm in discovery.
Territory and sales repek_territory, hubspot_owner_idCompanyEK → HSSales rep mapped to a HubSpot owner.
Terms, credit limit, credit holdek_terms, ek_credit_holdCompanyEK → HSRead only in HubSpot.
CustCnt name, email, phonefirstname, lastname, email, phoneContact↔ BothEmail is the contact match key.
New customer from won dealCustomer (create)CompanyHS → EKCreated through the Customer service or an Epicor Function.
Parts & pricing · Part, price lists
Part.PartNumhs_skuProductEK → HSMatch key for products.
Part descriptionname, descriptionProductEK → HS
Product group and classek_product_groupProductEK → HSUsed for reporting and line-item rules.
List pricepriceProductEK → HSBase price only. Customer price lists stay in Kinetic.
Inactive flagek_part_activeProductEK → HSInactive parts hidden from new HubSpot quotes.
Quotes · QuoteHed, QuoteDtl
QuoteHed.QuoteNumek_quote_numDeal↔ BothLinks the HubSpot deal to the Kinetic quote.
Quote status and expirationek_quote_status, ek_quote_expiresDealEK → HSDrives deal stage rules.
Quote totalamountDealEK → HSKinetic's calculated value, including configured lines.
QuoteDtl linesLine itemsLine itemEK → HSPart, quantity and price per line.
Won dealQuote or sales order (create)DealHS → EKOnly for the paths chosen in the SOW.
Sales orders · OrderHed, OrderDtl
OrderHed.OrderNumek_order_numOrderEK → HSUnique. Associated to company, contact and deal.
Order date and need-by dateek_order_date, ek_need_by_dateOrderEK → HS
Order total and currencyhs_total_price, hs_currency_codeOrderEK → HSDocument currency kept as entered.
Open or closed statushs_pipeline_stageOrderEK → HSMapped to an order pipeline.
OrderDtl linesLine itemsLine itemEK → HSPart, quantity and price per line.
AR invoices
Invoice number and dateek_invoice_num, invoice dateInvoiceEK → HSHubSpot invoice object or custom object. Confirm in discovery.
Invoice amount and balanceek_invoice_balanceInvoiceEK → HSBalance due updates as payments post.
Open AR by customerek_open_arCompanyEK → HSRollup from a BAQ.
Last invoice dateek_last_invoice_dateCompanyEK → HSDrives reorder and win-back workflows.
06 — Auth & API

How are authentication and API limits handled?

Kinetic access is granted by the client's own administrator. Values Epicor does not publish are marked for confirmation.

TopicKineticHubSpot
InterfacesKinetic 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.
AuthenticationAPI 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 modelIssued by the client's Kinetic administrator for a dedicated integration user.Self-serve in the client portal. Custom objects need an Enterprise hub.
Multi-companyThe 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 detectionFilter 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 & pagingOData 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.
CustomizationsUD 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.
07 — Issues & opportunities

What should you plan for, and what does the integration unlock?

Severity reflects impact on the SOW, not technical difficulty alone.

Challenges to plan for

Configured-part pricingHigh

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.

Two places can create customersHigh

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.

Multiple companies and sitesMedium

One customer can exist in several Kinetic companies with different IDs. The match rule and the HubSpot company structure are agreed before the build.

UD fields and customizations varyMedium

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.

Upgrade testingMedium

Kinetic cloud receives regular updates from Epicor. Include a regression check of the integration in the client's upgrade routine.

Price list detailLow

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.

Opportunities in HubSpot

The full account on one HubSpot recordHigh value

Open quotes, open orders, invoice balance and credit hold sit beside every email and meeting, so reps walk into calls prepared.

Won deals become customers without rekeyingHigh value

A won deal creates the Kinetic customer and contacts, so order entry starts from clean data.

Reorder and win-back signalsHigh value

Last order date and order frequency by part class drive HubSpot tasks and sequences when a customer goes quiet.

Quote follow-up from Kinetic quotesMedium value

Quotes near expiration enter HubSpot workflows, so no quote expires without a follow-up.

Credit hold visibility for salesMedium value

Reps see a credit hold before they promise a delivery, and a workflow alerts the account owner.

Revenue reporting by product lineMedium value

Orders and invoices in HubSpot let leaders compare pipeline, bookings and billed revenue in one dashboard.

Quote-to-cash

HubSpot runs the deal. Kinetic runs the order.

The integration follows the path a sale already takes. Each step has one system in charge, and the other system sees the result.

  1. Prospect and deal in HubSpot; the company becomes a Kinetic customer when the deal is won.
  2. Quote in Kinetic for configured parts, or in HubSpot for standard parts, with the result on the deal.
  3. Sales order booked in Kinetic and shown on the HubSpot company and deal as an order.
  4. Invoices and balances flow back to HubSpot, so sales sees what was billed and paid.
08 — Property schema

Which HubSpot properties does the integration create?

All custom properties use the ek_ prefix in an Epicor Kinetic property group. Rollups come from BAQs so HubSpot and Kinetic reports agree.

Internal nameLabelObjectTypeSource / logic
ek_cust_idKinetic Customer IDCompanySingle-line textCustomer.CustID; unique per company
ek_companyKinetic CompanyCompanyDropdownKinetic company the customer belongs to
ek_territoryTerritoryCompanyDropdownCustomer territory
ek_termsPayment TermsCompanySingle-line textCustomer terms
ek_credit_holdCredit HoldCompanySingle checkboxCustomer credit hold flag
ek_open_arOpen ARCompanyNumber (currency)BAQ: sum of open invoice balances
ek_open_order_valueOpen Order ValueCompanyNumber (currency)BAQ: sum of open order lines
ek_last_invoice_dateLast Invoice DateCompanyDateMost recent AR invoice
ek_quote_numKinetic Quote NumberDealSingle-line textQuoteHed.QuoteNum
ek_quote_statusKinetic Quote StatusDealDropdownQuote header status
ek_order_numKinetic Order NumberOrderSingle-line textOrderHed.OrderNum; unique
ek_product_groupProduct GroupProductDropdownPart product group
09 — Scope builder

Interactive scope builder

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.

Scope summary

0Fields
0Inbound
0Write-back
10 — Sources

Sources & verification

Based on public documentation. Service names, UD fields and limits are confirmed in the client's own Kinetic REST help during discovery.

Kinetic × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

Epicor Kinetic HubSpot integration FAQ

Does Epicor Kinetic integrate with HubSpot?

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.

What data syncs between Epicor Kinetic and HubSpot?

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.

Which system owns which data?

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.

What does setting up the Epicor Kinetic HubSpot integration involve?

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.

How long does the integration take and what does it cost?

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.