ERP integration
{Read Time} min read

Epicor is ending on‑premises Prophet 21: dates, Eclipse, and your integrations

Vitaly Kan, Founder of ProfitPad
Vitaly Kan, Founder, ProfitPad
October 28, 2026
Illustration of an on-premises ERP server moving to the cloud on a set date

Epicor will stop releasing on-premises Prophet 21 after P21 2028.1, tentatively scheduled for May 2028, with Active Support for that release through June 30, 2029. After that, Epicor says new features ship only in Epicor Cloud. If your P21 connects to HubSpot or any other system, that move changes how the integration has to work.

This article covers what Epicor announced, which products it covers, what is still unknown, and what to check in your CRM integration before you migrate. Epicor has not published Epicor Cloud pricing or a migration deadline, so those questions go to your account manager.

What Epicor announced

On January 6, 2026, Epicor published a schedule of final on-premises feature releases for Kinetic, Prophet 21, and BisTrack. In Epicor's words: "The final on-premises release for Kinetic, Prophet 21, and BisTrack will be 2028.1." After that, "further innovation will be delivered exclusively in the Epicor Cloud."

ProductFinal on-premises releaseActive Support ends
Prophet 212028.1, tentatively May 2028June 30, 2029
Kinetic2028.1, tentatively January 2028December 31, 2029
BisTrack Web and API2028.1, tentatively July 2028June 30, 2029

Epicor marks every date as tentative. Also, the end of Active Support is not the end of all support: Sustaining Support begins after it, and Epicor has not published an end date for that. Enterprise Times describes Sustaining Support as excluding new features and comprehensive bug fixes. Whether security updates continue under it is not confirmed in anything public.

What about Epicor Eclipse?

Eclipse is not named in the announcement. Epicor already sells Eclipse as a cloud product, described on its site as "a scalable, SaaS private cloud solution," but we found no Epicor statement ending on-premises Eclipse releases. If you run Eclipse on your own server, nothing in this announcement sets a deadline for you. Ask your Epicor account manager what applies to your contract.

Will a P21 cloud migration break my integrations?

An on-premises P21 sits on your server, so an integration can usually reach its database directly, often over a VPN. In Epicor Cloud, that changes.

  • Direct database writes likely go away. Epicor partners report that a cloud P21 customer gets a separate read-only copy of the production database for queries, and that anything that writes data has to go through Epicor's API layer. Epicor's Insights 2026 session listing mentions new cloud database access features on its roadmap, without published details.
  • Integrations that write to the database need rework. If your CRM sync writes to the database directly, plan to rebuild it on the API. Syncs that only read may work against the read-only copy; confirm with Epicor.
  • Deletions still need handling. The Eclipse API doesn't announce deleted records, so on our Eclipse integrations deletions run as a scheduled reconciliation. Expect to check the same on cloud P21.
  • Where the integration runs can change. On-premises integrations often run inside your network to reach the ERP. Against a cloud API, they don't have to.

What to do before you migrate

  1. List every system that touches P21. CRM, ecommerce, EDI, quoting, reporting. For each, note whether it reads the database, writes to it, or uses the API.
  2. Ask Epicor what your cloud tier allows. Database access, API limits, and pricing are not published, so get them in writing for your account.
  3. Decide what the CRM should hold. In our Eclipse builds, customers, contacts, open orders, and line items sync to HubSpot. P21 stays the system of record for orders, invoices, inventory, and pricing. Migration is a good moment to drop syncs nobody uses.
  4. Rebuild integrations on the API once, not twice. If you are building or replacing a HubSpot integration now, build it against the P21 API so it is more likely to survive the move to the cloud.

Frequently asked questions

When does on-premises Prophet 21 end?

The final on-premises feature release is P21 2028.1, tentatively May 2028. Active Support for that release runs through June 30, 2029, and Sustaining Support begins July 1, 2029. Epicor has not published an end date for Sustaining Support. New features after 2028.1 ship only in Epicor Cloud.

Is Epicor Eclipse affected?

Not by this announcement. Epicor's January 2026 schedule names Kinetic, Prophet 21, and BisTrack. Eclipse is not named. Epicor already offers Eclipse as a cloud product, but we found no published end date for on-premises Eclipse. Confirm with your Epicor account manager.

Will my HubSpot integration break when P21 moves to the cloud?

Only if it writes to the database directly. Partners report that cloud P21 customers get read-only database access and must write through the API, so those integrations will likely need rework. Integrations built on the P21 API are the likeliest to carry over, but test them before you migrate.

We connect ERPs to HubSpot for distributors. We've shipped two Epicor Eclipse integrations and an Agility integration, and we haven't shipped a P21 integration yet. For the build options and costs, see our ERP and CRM integration guide. If you are planning a P21 move and want the HubSpot side built to survive it, see how we approach P21 or book a free 30-minute review.

Sources: Epicor press release, "Epicor Announces Schedule of Final On-Premises Feature Releases for Kinetic, Prophet 21, and BisTrack" (January 6, 2026); Epicor Innovation Pathway; Epicor Eclipse product page; Epicor Insights 2026 session listing; Enterprise Times (January 9, 2026); partner commentary from SimpleApps and Atlas Precision Consulting. Dates checked October 28, 2026.