HubSpot System Integrations · Epicor

HubSpot + Epicor Integration

Epicor has various ERP products. The four that come up most in industrial HubSpot integration conversations are Kinetic for discrete manufacturers, Prophet 21 for wholesale distributors, BisTrack for building materials and construction supply dealers, and Eclipse for electrical, HVAC, plumbing, and PVF distributors.

Is there a native HubSpot Epicor integration? No.

HubSpot hasn’t built a first-party Epicor connector. Separate third-party marketplace apps, each sold on its own subscription, cover Kinetic (including older installs still running under its pre-Kinetic name, Epicor 10) and Prophet 21. BisTrack has no HubSpot marketplace app, though Epicor's own Automation Studio platform reaches it. For most Epicor integrations, especially BisTrack and Eclipse, the path runs through Epicor's own integration tools or custom API work rather than HubSpot's marketplace.

Start Your Integration Readiness Check
Which paths reach which Epicor product
ProductMarketplace appAutomation StudioCustom API
Kinetic
Prophet 21
BisTrack
Eclipse
Available
Not available
Not confirmed
What to Sync

Which Epicor Objects Are Worth Syncing to HubSpot?

Not every object in Epicor is worth the effort to sync. Sync what changes a conversation with a customer, and leave what only matters to production or warehouse operations inside Epicor.

Order and Quote Status

Worth syncing

Sales and customer service need to see where an order or quote stands without logging into Epicor, especially at building materials dealers where a counter or inside sales rep is fielding the question live.

Account and Credit Status

Worth syncing, carefully

Credit holds and payment status change how a rep should handle a renewal conversation. This data usually needs read-only, one-directional sync from Epicor to HubSpot.

Product Libraries & Inventory Availability

It depends

Worth syncing for distributors and dealers on Prophet 21 or BisTrack, where stock directly answers a sales question. Less critical for discrete manufacturers on Kinetic running to a production schedule rather than off-the-shelf stock.

Deep Production or Routing Data

Not worth syncing

Engineering change control, multi-level BOMs, and shop floor routing live in Kinetic for a reason, and pulling that detail into HubSpot rarely changes a sales or marketing conversation enough to justify the sync.

It Depends

Why “Can It Connect?” Has a Different Answer for Every HubSpot Epicor Integration

Ask a NetSuite customer whether HubSpot can connect to their ERP, and the answer is close to the same for everyone: yes, through the native connector, with some custom work layered on top. Ask an Epicor customer the same question, and the honest answer is “it depends,” on the product line, the version, the deployment, the API license, and how customized the instance is.

This reflects how differently Kinetic, Prophet 21, and BisTrack get configured in practice, especially in discrete manufacturing and building materials, where every shop runs its own version of “standard.”

Will Your Epicor Integration Be a Light Lift or a Heavier Build?

Lighter liftYou’re looking at a lighter lift if:
You’re on Kinetic or Prophet 21 with a current license and a relatively standard configuration
Your needs match what a marketplace app already supports (standard customer, order, and product sync)
You’re on Epicor Cloud rather than an older on-premises install
Heavier buildYou’re looking at a heavier build if:
You’re on BisTrack or Eclipse, where no HubSpot marketplace app exists, only Epicor's own tools or a custom build
You’re on an older on-premises install nearing Epicor’s published sunset dates, BisTrack Desktop especially
Your team relies on custom fields or workflows that don’t map cleanly onto standard HubSpot objects
You need the integration to trigger something specific back in Epicor, not just pull data into HubSpot
Start Here

Which Epicor Are You On?

Before any integration conversation goes further, this is the question that decides everything else: which Epicor product, which deployment, and which version.

Epicor Products Comparison
ProductBuilt ForDeploymentAPI Situation
KineticDiscrete and mixed-mode manufacturersCloud or on-premises (same product line either way)Open REST API and OData v4 catalogue, the same shape on cloud and on-premises
Prophet 21 (P21)Wholesale distributorsCloud-hosted or on-premisesREST API sold as a separate license, split across four different API surfaces
BisTrackBuilding materials and construction supply dealersHistorically on-premises, now moving toward BisTrack Web Browser & APIAPI access tied specifically to the Web Browser & API product, not the older BisTrack Desktop client
EclipseElectrical, HVAC, plumbing, and PVF distributorsOpen, .NET Core-based REST API, with premium API bundles sold for things like sales order management and warehouse integrations

In January 2026, Epicor announced it would stop releasing new on-premises features for Kinetic, Prophet 21, and BisTrack, pushing future development on those three product lines to Epicor Cloud only. Eclipse was not part of that announcement.

See the full sunset timeline
Your Options

What Are the Different Ways to Integrate HubSpot and Epicor?

There are four ways to connect HubSpot and Epicor: a marketplace app, Epicor’s own Automation Studio, an iPaaS platform, or a custom API build.

Marketplace AppEpicor Automation StudioiPaaSCustom API Build
Best ForCompanies on Kinetic or Prophet 21 wanting a packaged option without a custom buildCompanies already inside Epicor who want a low-code way to reach HubSpot, including BisTrack, which the HubSpot marketplace doesn't coverCompanies connecting Epicor alongside several other systems, not just HubSpotBisTrack, heavily customized Kinetic or P21 instances, or anyone the other two options don’t cover
ProsFaster to launch than a custom build; vendor-managedEmbedded in Kinetic, Prophet 21, and BisTrack; powered by Workato, with 2,000+ prebuilt connectors including HubSpot; Epicor-led implementation and supportVisual workflow builder; prebuilt connectors to many systemsBuilt around your customizations and objects; no recurring per-connector subscription beyond build and maintenance
ConsRequires its own separate paid subscription on top of HubSpot; limited to the objects the app already supports; not available for BisTrackRuns through Epicor's side of the relationship, not HubSpot's marketplace; “embedded” doesn't mean already turned on for your instanceOngoing subscription that scales with usage; still requires mapping Epicor’s API surface and customizations manuallyRequires a development team that owns it long-term
Our TakeWorth evaluating first if you’re on Kinetic or P21 and your needs are standard, but confirm it covers your customizations before counting on itThe closest thing to a packaged option for BisTrack; worth checking if it's already included before assuming you need a custom buildMakes sense when Epicor and HubSpot are two of several systems you’re connectingThe default for BisTrack, and often the realistic answer for Kinetic or P21 once customization enters the picture

Marketplace App

Best For

Companies on Kinetic or Prophet 21 wanting a packaged option without a custom build

Pros

Faster to launch than a custom build; vendor-managed

Cons

Requires its own separate paid subscription on top of HubSpot; limited to the objects the app already supports; not available for BisTrack

Our Take

Worth evaluating first if you’re on Kinetic or P21 and your needs are standard, but confirm it covers your customizations before counting on it

Epicor Automation Studio

Best For

Companies already inside Epicor who want a low-code way to reach HubSpot, including BisTrack, which the HubSpot marketplace doesn't cover

Pros

Embedded in Kinetic, Prophet 21, and BisTrack; powered by Workato, with 2,000+ prebuilt connectors including HubSpot; Epicor-led implementation and support

Cons

Runs through Epicor's side of the relationship, not HubSpot's marketplace; “embedded” doesn't mean already turned on for your instance

Our Take

The closest thing to a packaged option for BisTrack; worth checking if it's already included before assuming you need a custom build

iPaaS

Best For

Companies connecting Epicor alongside several other systems, not just HubSpot

Pros

Visual workflow builder; prebuilt connectors to many systems

Cons

Ongoing subscription that scales with usage; still requires mapping Epicor’s API surface and customizations manually

Our Take

Makes sense when Epicor and HubSpot are two of several systems you’re connecting

Custom API Build

Best For

BisTrack, heavily customized Kinetic or P21 instances, or anyone the other two options don’t cover

Pros

Built around your customizations and objects; no recurring per-connector subscription beyond build and maintenance

Cons

Requires a development team that owns it long-term

Our Take

The default for BisTrack, and often the realistic answer for Kinetic or P21 once customization enters the picture

Epicor sells a second iPaaS beyond Automation Studio: Epicor Integration Cloud is positioned specifically for companies managing ITAR or other regulatory data-handling requirements, which shows up often among defense-adjacent manufacturers. Service Connect is the legacy equivalent, still running at some shops on Epicor 9, ERP 10, or on-premises P21 or Eclipse, though Epicor's own guidance is pushing customers toward Automation Studio from here.

Where to start, by product

For Kinetic and Prophet 21, a marketplace app or Automation Studio are both worth evaluating before a custom build. For BisTrack, Automation Studio is the packaged option, not a HubSpot marketplace app, since none exists. For Eclipse, custom API work is where most HubSpot integrations start today, since neither a marketplace app nor confirmed Automation Studio coverage exists for it yet.

Budgeting

What Does HubSpot Epicor Integration Cost?

Build cost

Build cost depends on how customized your Epicor product is, and whether a packaged app already covers your objects or the work has to be built against the API directly. On the packaged end, marketplace apps for Kinetic and Prophet 21 start around $400 a month per product line, plus scoped onboarding, a real number we can publish because the marketplace listing itself is public. A BisTrack or Eclipse build, or a heavily customized instance built against the API from scratch, costs meaningfully more than that.

~$400/moMarketplace app starting point, per product line (Kinetic, P21), plus onboarding
Maintenance cost

Maintenance cost is where Epicor integrations ask for more ongoing attention than most. Custom fields and workflows added during implementation keep evolving, and a sync built around last year's configuration can quietly fall out of step with this year's. Budgeting for someone to own the integration after launch, not just build it, matters more here than on ERPs with a simpler packaged option.

Plan Around It

The Epicor On-Premises Sunset Timeline

On January 6, 2026, Epicor announced the schedule of final on-premises feature releases for Kinetic, Prophet 21, and BisTrack, confirming that future development on all three moves to Epicor Cloud only.

ProductFinal On-Premises Feature ReleaseSupport After That
Kinetic2028.1, tentatively January 2028Active Support through December 31, 2029; Sustaining Support begins January 1, 2030
Prophet 212028.1, tentatively May 2028Not detailed in Epicor’s announcement
BisTrack Web Browser & API2028.1, tentatively July 2028Active Support through June 30, 2029; Sustaining Support begins July 1, 2029
BisTrack Desktop2028.1, tentatively December 2026Sustaining Support begins January 1, 2029
BisTrack Desktop is the one to pay attention to.

Its final on-premises release is scheduled for December 2026, a fraction of the runway the other three product lines still have. If your team is still running BisTrack Desktop rather than BisTrack Web Browser & API, that timeline is worth resolving before any integration conversations.

What about Eclipse?

Eclipse wasn’t named in the January 2026 announcement. That doesn’t mean nothing is planned for it, only that nothing has been confirmed here; treat Eclipse's roadmap as a separate, open question.

As a HubSpot Elite Solutions Partner built around industrial, manufacturing, and building materials companies, we scope Epicor integrations through the Industrial Growth System: strategy first, then people, then process, then technology, so we're syncing what your team actually needs, not every object Epicor happens to expose.

Explore the Industrial Growth System
Before Build Work Starts

For Your ERP Team

Everything above is what shapes the pitch and the budget. Everything in this section is what your ERP admin or IT contact will be asked to confirm, pull, or provision, before any build work starts. Forward it to them directly, or walk through it together on our Integration Readiness Check.

Key HubSpot Epicor Integration Terms

Kinetic
Epicor’s ERP for discrete and mixed-mode manufacturers, formerly sold as Epicor ERP 10.
Prophet 21 (P21)
Epicor’s ERP for wholesale distributors, with its own API surfaces separate from Kinetic.
BisTrack
Epicor’s ERP for building materials, lumber, and construction supply dealers, the product line with the least packaged connector support.
Eclipse
Epicor’s ERP for electrical, HVAC, plumbing, and PVF distributors; has its own REST API, no HubSpot marketplace app confirmed.
Marketplace app
A third-party app sold through HubSpot’s App Marketplace that requires its own subscription on top of HubSpot. Kinetic and Prophet 21 each have their own separate marketplace app and subscription, not one app covering both.
Epicor Automation Studio
Epicor's own low-code integration platform, powered by Workato, embedded in Kinetic, Prophet 21, and BisTrack, with prebuilt connectors including HubSpot.
Custom API build
An integration built directly against the relevant Epicor product’s API rather than through a packaged app; the default path for BisTrack.
For Your ERP Team

What Epicor API Access Looks Like, By Version

Turning on an Epicor integration means confirming which API surface you have.

Kinetic

Kinetic exposes an Open REST API and an OData v4 catalogue, and the shape of that API is the same whether you’re on Epicor Cloud or an on-premises install.

Authentication runs through API access keys, access scopes, and a security token server, and a cloud-hosted Kinetic instance’s REST API is reachable the same way as an on-premises one, without a VPN.

Prophet 21

P21 exposes four separate API surfaces:

  • →A v2/Entity API for standard record creation and updates
  • →A stateful Interactive API that mirrors P21’s own screens for business logic
  • →An OData Data Services API
  • →A Transaction API for bulk operations

Each API has different coverage and limitations. The REST API itself is typically sold as a separate license, so confirming it’s part of your P21 agreement is an early step.

BisTrack

BisTrack’s API access depends on which BisTrack you’re running. Epicor’s current roadmap ties ongoing feature development and API access to “BisTrack Web Browser & API,” not the older BisTrack Desktop client, which is being phased out on a separate, earlier timeline.

If your team is still on BisTrack Desktop, that’s the first thing to resolve before an integration conversation.

Eclipse

Eclipse exposes its own Open API, a .NET Core engine delivering REST endpoints, with premium API bundles sold on top for things like sales order management and warehouse integrations.

Not sure which Epicor product, deployment, or API license you have? That’s what our Integration Readiness Check sorts out before you start.

Start Your Readiness Check
The Checklist to Hand Your ERP Contact

What It Takes to Connect

Before any integration work starts, there are five things worth confirming.

  1. 01Confirm the product and version.Kinetic, Prophet 21, BisTrack, or Eclipse, and which release.
  2. 02Confirm the API license.Prophet 21’s REST API is typically a separate line item on your agreement, not something every P21 customer already has.
  3. 03Create the API access key and scopes in Kinetic.This is the credential the integration will actually run on.
  4. 04Confirm BisTrack Desktop versus BisTrack Web Browser & API.The two have different API access and different timelines.
  5. 05Confirm whether Epicor Automation Studio is already included in your subscription.It’s embedded in Kinetic, Prophet 21, and BisTrack, but “embedded” isn’t the same as “already turned on” for your instance.
The Cost Driver

Customization Is the Integration Cost Driver

On Epicor, the biggest integration cost driver is how heavily your instance has been customized.

Kinetic 2026.1, released May 2026, also retired the Smart Client (the Classic forms interface) across every deployment. Anyone upgrading to that release or later has to move users onto the browser-based Kinetic UI, which is worth knowing before scoping any integration work that touches the interface layer.

Customization that tends to drive cost up
Custom fields, screens, and business object modifications built during implementation
Industry-specific workflows layered on top of standard Epicor modules, like configured-product rules for manufacturers or will-call and delivery scheduling for building materials dealers
Custom reports, business activity queries (BAQs), or saved views built around how your team really works, not how Epicor ships out of the box. Epicor's own position is that all Kinetic services, BAQs and Epicor Functions included, are reachable through REST on OData v4, so the cost isn't in getting at this data, but deciding what it means and where it belongs in HubSpot
Multi-site or multi-company configurations, common at discrete manufacturers running several plants and LBM dealers running several yards
Case Study

See It In Action: Spruce Industries

Spruce logo Distribution
Spruce Industries · HubSpot + Prophet 21

From Chaos to Clarity: How Evenbound Helped Spruce Industries Optimize Their CRM

Spruce Industries, an industrial janitorial and cleaning supplies wholesaler running Epicor Prophet 21, was using P21 itself as a stand-in CRM, with no real customer relationship system and no clean data architecture to build on. We implemented HubSpot Marketing Hub and Sales Hub, built a comprehensive data mapping sheet to carry Spruce's P21 customer data into HubSpot cleanly, and set up the workflows and reporting P21 alone couldn't give them.

+1,450%
Increase in calls and meetings the year after launch
750+
New contacts created in HubSpot
Advanced Reporting
Visibility Spruce didn’t have running out of P21
FAQ

Frequently Asked Questions

What is Epicor?

Epicor is a vendor that sells multiple ERP products. Its main lines include Kinetic (discrete manufacturing), Prophet 21 (wholesale distribution), BisTrack (building materials and construction supply), and Eclipse (electrical, HVAC, plumbing, and PVF distribution), each with its own data model and integration path.

Does HubSpot integrate with Epicor?

Not through a connector HubSpot built itself. Separate marketplace apps, each on its own subscription, can cover Kinetic and Prophet 21. BisTrack has no HubSpot marketplace app, but Epicor's own Automation Studio platform reaches it. Neither is confirmed for Eclipse today, so integrating it means a custom build against Epicor’s API.

Which Epicor product do I need before integrating?

All of them work, and all of them answer differently. Kinetic serves discrete manufacturers, Prophet 21 serves wholesale distributors, BisTrack serves building materials and construction supply dealers, and Eclipse serves electrical, HVAC, plumbing, and PVF distributors. Each has a different API situation, so confirming which one you're on is the first step.

When does Epicor stop releasing on-premises features?

It depends on the product. Epicor's January 2026 announcement set BisTrack Desktop's final on-premises release for December 2026, the nearest deadline of the group, with Kinetic, Prophet 21, and BisTrack Web Browser & API between 2028 and mid-2028. Eclipse wasn't part of that announcement.

Is a HubSpot Epicor integration free?

No. Unlike ERPs with a HubSpot-built native connector, every Epicor integration path costs something: a marketplace app subscription on top of HubSpot, an iPaaS subscription, or a custom build and its ongoing maintenance.

How much does a HubSpot Epicor integration cost?

Cost depends on the product line, whether a marketplace app already covers your needs, and how customized your instance is. Marketplace apps for Kinetic and Prophet 21 start around $400 a month per product line plus scoped onboarding; a custom BisTrack or Eclipse build costs meaningfully more.

Does it sync custom fields and objects?

Only with custom work. Epicor instances are customized as a rule, and neither a marketplace app nor a standard iPaaS connector will know about fields or objects specific to your instance without configuration built around them.

Does a HubSpot Epicor integration work the same on cloud and on-premises?

Not always. Kinetic's API has the same shape on cloud and on-premises deployments. Prophet 21 and BisTrack have more version- and deployment-specific differences, which is why confirming your deployment matters before scoping the work.

How long does a HubSpot Epicor integration take?

It depends heavily on the product line and the customization involved. A standard Kinetic or Prophet 21 setup covered by a marketplace app can move faster than a custom BisTrack build, which more closely resembles a full custom development project.

What is Epicor Automation Studio, and can it connect to HubSpot?

Epicor Automation Studio is Epicor's own low-code integration platform, powered by Workato, embedded in Kinetic, Prophet 21, and BisTrack. It includes prebuilt connectors to more than 2,000 applications, HubSpot among them, so it's Epicor's packaged answer even where no HubSpot marketplace app exists.

Can I integrate BisTrack with HubSpot?

Yes, though not through HubSpot's own marketplace, which has no BisTrack app. The packaged option is Epicor Automation Studio, which is built into BisTrack and includes a prebuilt HubSpot connector. A BisTrack-HubSpot integration can also be a custom API build; which makes more sense depends on how customized your instance is and whether Automation Studio is already part of your subscription.

Does Epicor Eclipse integrate with HubSpot?

Not through a packaged option today. Eclipse has its own REST API, but no HubSpot marketplace app, and this page doesn't have confirmed Automation Studio or iPaaS coverage for it either. An Eclipse-HubSpot integration is a custom API build until that changes.

💡 ERP Integration Readiness Check

Start Your HubSpot System Integration Project

Before you scope an Epicor integration, find out which product line, version, and API access you're actually working with. Our ERP Integration Readiness Check starts with that question.