Epicor Prophet 21 and HubSpot: What Distributors Need to Know Before Integrating

If you run a wholesale distribution business, there's a good chance Prophet 21 runs it with you. And if you're reading this, there's a good chance your sales and marketing teams live somewhere else. Probably HubSpot, or about to be.

This guide covers what P21 is, what its API actually supports, what an integration really involves, and the questions to answer before you sign anything, with anyone, including us.

What is Epicor Prophet 21?

Epicor Prophet 21 (usually shortened to P21) is an ERP built specifically for wholesale distributors. It handles the operational core of a distribution business: inventory, purchasing, order management, warehouse operations, pricing, and financials. It's part of Epicor's ERP portfolio, alongside Eclipse, Epicor's other major distribution ERP.

P21 runs on a Microsoft stack (.NET, SQL Server) and is offered both in the cloud and on-premise. That deployment detail matters more than it sounds: it changes how an integration reaches your data, and we'll come back to it.

If your business is distribution (HVAC, plumbing, electrical, industrial supplies, jan-san, fasteners, safety equipment), P21 is one of the handful of ERPs actually built for how you operate. That's why distributors keep it for decades.

P21 has a CRM module. So why do distributors add HubSpot?

Honest answer first: Prophet 21 includes CRM functionality. Contact records, activity notes, order history: it's in there.

But an ERP's CRM module and a sales team's CRM are different tools solving different problems. The pattern we see in distribution sales teams:

• Outside reps won't live in an ERP. P21 is built for operations: counter sales, purchasing, warehouse. A rep on the road needs pipeline views, mobile access, sequences, and a UI they'll actually open.
• Marketing doesn't exist in P21. Email campaigns, lead capture, attribution, nurture flows: that's CRM-platform territory.
• Leadership reporting lives in dashboards, not ERP queries. Pipeline coverage, rep activity, win rates by product line: HubSpot makes these visible without a report request to IT.

So distributors end up with both: P21 running the operation, HubSpot running the revenue team. Which creates the real problem: the two systems don't talk on their own. Your reps see contacts without order history. Your ERP has customers your CRM has never heard of. Every quote starts with a lookup in a second system.

That's the integration case. Not replacing P21, connecting it.

What “open API” actually means for P21

Prophet 21 has genuinely good API surfaces by ERP standards. This is one of the reasons a P21-to-HubSpot integration is a well-bounded project rather than a science experiment:

• The v2 P21 API: a stateless REST API with a metadata model. This is the workhorse for reading and writing business data from outside.
• The Entity API: structured, fit-for-purpose business-object endpoints (customers, orders, and so on).
• The Interactive API: lets external systems drive P21 transactions the way a user session would.

Two practical caveats that a sales pitch won't tell you:

• API access depends on your P21 agreement and version. Before scoping any integration, confirm what API access your license includes and which version you're running. It's a five-minute question to your Epicor rep that can save weeks.
• Hosting changes the plumbing. Cloud-hosted P21 exposes APIs over the internet. On-premise P21 usually sits behind your firewall or VPN, which rules out most cloud-only integration tools unless something runs inside your network. This is a solved problem (more below), but only if whoever you hire has actually solved it.

Your three options for connecting P21 to HubSpot

1. Packaged connectors. Off-the-shelf P21↔HubSpot sync apps exist on the HubSpot Marketplace. They're the fastest start and the least flexible finish: a fixed object list, synced their way, on a yearly subscription (typically $10-15k/year). If your workflow fits their template, they're a legitimate choice. If you need custom objects, your own field logic, or deletion handling, you'll hit the template's walls.

2. iPaaS platforms. Middleware like Celigo or a managed integration platform sits between the systems. More flexible than a packaged connector, but you're paying platform fees on top of implementation, often $15k+/year before anyone configures anything, and the integration logic lives inside a vendor's black box.

3. A custom build on open tooling. An integration built on n8n (open-source workflow automation) syncs your objects, your way. Self-hosted, the platform costs nothing: it runs on your own server, which also solves the on-premise/VPN problem, since the integration lives inside your network. You pay for the build, not a perpetual toll. The trade-off: you need someone who genuinely knows both the ERP side and the HubSpot side.

There's no universally right answer. Small object list, standard workflow, cloud-hosted P21? A connector may be fine. Complex pricing logic, on-prem server, or a two-way sync? The template approaches get expensive or impossible fast.

Five questions to answer before you integrate

This is the due diligence that separates a six-week project from a six-month one:

• Which P21 version and hosting do you run? Cloud or on-premise, and which release. This determines API access and whether the integration needs to live inside your network.
• Is API access included in your agreement? Confirm with Epicor before scoping. Retroactively licensing API access mid-project is a bad surprise.
• What syncs, and in which direction? List the objects (customers, contacts, orders, invoices, products) and be honest about direction. One-way (P21 → HubSpot) solves most sales-team problems and is dramatically simpler. Two-way is buildable (we've done it on Epicor Eclipse at production scale), but only add it if a workflow genuinely requires it.
• What happens when a record is deleted? Most integrations sync creates and updates and silently ignore deletions. The result: contacts that no longer exist in your ERP live on in your CRM as ghost data, polluting lists and reports until reps stop trusting the system. Ask any vendor directly: “how do you handle deletions?” A hand-wavy answer here predicts the whole project.
• Who owns it after go-live? Integrations aren't fire-and-forget. Who monitors sync errors, handles API changes after a P21 upgrade, and audits data quality in the first weeks? Get that in the scope, not in the aftermath.

Where we're honest about our own experience

ProfitPad hasn't shipped a Prophet 21 integration yet. We've built two Epicor Eclipse-to-HubSpot integrations, both live in production and one of them a two-way sync, and we're mid-build on Agility ERP. The sync architecture, the deletion tracking, and the on-prem/VPN hosting pattern all transfer to P21's open API; the ERP changes, the approach doesn't.

We wrote this guide the way we'd want it written if we were the buyer: the trade-offs are real, the connectors and platforms have legitimate use cases, and the right choice depends on your setup, not on whoever's writing the blog post.

If you want the specifics of how we'd approach a P21 build (scope, timeline, fixed-fee pricing, and the founding-client arrangement for our first P21 project), it's all on our Prophet 21 to HubSpot integration page.

FAQ

What is Epicor Prophet 21 used for?

Prophet 21 is an ERP for wholesale distributors. It manages inventory, purchasing, order entry, warehouse operations, pricing, and financials: the operational core of a distribution business. It's part of Epicor's portfolio alongside Eclipse, Epicor's other distribution ERP.

Does Prophet 21 have a built-in CRM?

Yes. P21 includes CRM functionality for contacts, activities, and order history. Most distributors that add HubSpot do it for what an ERP module doesn't cover: outside-rep pipeline management, marketing automation, lead capture, and leadership dashboards.

Does Prophet 21 integrate with HubSpot?

Yes, three ways: packaged Marketplace connectors (fixed sync template, yearly subscription), iPaaS middleware platforms, or a custom build on P21's REST APIs. The right option depends on your object list, sync direction, and whether your P21 is cloud or on-premise.

Is Prophet 21 cloud-based or on-premise?

Both. Epicor offers P21 in the cloud and on-premise. Many established distributors still run on-premise, which means integration tooling has to reach a server behind your firewall or VPN. Self-hosted integration platforms solve this by running inside your network.

What does a Prophet 21 to HubSpot integration cost?

Packaged connectors run roughly $10-15k per year, indefinitely. iPaaS platforms charge similar platform fees before implementation. A custom build is a one-time project cost. ProfitPad prices these fixed-fee after a scoping call, and our first P21 client gets a reduced founding-client rate in exchange for a case study.