Prophet 21 on-premises ends active support in 2029: options for US distributors, including ERPNext
Short answer
Epicor announced on January 6, 2026 that the final on-premises Prophet 21 release is 2028.1, tentatively scheduled for May 2028, with Active Support for 2028.1 through June 30, 2029 and Sustaining Support from July 1, 2029. New innovation goes to the Epicor Cloud (checked Nov 16, 2026). That is a short window: if 2028.1 ships in May 2028, it gets roughly 13 months of Active Support. On-premises Prophet 21 keeps running after that, but Epicor’s release does not say what Sustaining Support covers. For most Prophet 21 distributors, moving to Epicor Cloud is the lowest-risk path, because you keep the same distribution depth. ERPNext (open source, GPL-3.0, no licence fee) is worth pricing if you will not move to Epicor’s cloud, your pricing can be expressed as price lists and pricing rules, and you can live without a full RF-directed warehouse system or will add one. Supplier rebates are the gap to test first. Epicor is quote-only, so we give no Epicor estimate.
Contents
- Who this guide is for
- What Epicor actually announced
- What the timeline means for a distributor
- Your options
- The distribution fit test: where Prophet 21 sites live or die
- Fit test summary
- Costs: what is published
- What a Prophet 21 to ERPNext migration moves
- Where Epicor Cloud is the better answer
- A practical plan for Prophet 21 sites
- Decision table
- Best for, and wrong choice when
- Frequently asked questions
Who this guide is for
This guide is for owners, CFOs, operations directors and IT managers at US wholesale distributors running Epicor Prophet 21 on their own servers or in their own hosting. Typical Prophet 21 sites are in the industries Epicor lists on its product page: industrial distribution, electrical, fasteners, fluid power, HVAC, janitorial, medical supply, paper and packaging, pipes, valves and fittings, plumbing, safety supply and tile.
We implement ERPNext, so read our view with that in mind. For many Prophet 21 distributors, Epicor Cloud is the right next step, and we say where below. This guide is for the ones who will not, or cannot, put their ERP in Epicor’s cloud, and want to know whether an open-source ERP can carry a distribution business.
It is part of our series on legacy ERP deadlines; the legacy ERP end-of-support hub lists every vendor date we have confirmed. The same Epicor announcement covers Kinetic and BisTrack; see our Epicor Kinetic guide and BisTrack guide.
Sources, checked on Nov 16, 2026: the Epicor press release, Jan 6, 2026, the Epicor Prophet 21 product page, the Frappe Cloud pricing page and Frappe Cloud server plans page, the ERPNext repository on GitHub and the ERPNext documentation linked in each section.
What we do not estimate
Epicor does not publish Prophet 21 or Epicor Cloud prices on the pages we checked, so we give no Epicor estimate. We also give no implementation estimate for either path; it depends on your pricing complexity, branches, integrations and data quality.
What Epicor actually announced
| Milestone | What Epicor states | Source |
|---|---|---|
| Final on-premises Prophet 21 release | 2028.1, tentatively scheduled May 2028 | Epicor press release, Jan 6, 2026 |
| Active Support for 2028.1 | Through June 30, 2029 | Epicor press release, Jan 6, 2026 |
| Sustaining Support | Begins July 1, 2029 | Epicor press release, Jan 6, 2026 |
| After the final feature releases | Customers “transition into defined support phases – Active Support, followed by Sustaining Support – to ensure ongoing security and operational continuity” | Epicor press release, Jan 6, 2026 |
| Migration help | Ascend with Epicor: methodology, business planning support, AI tooling, consulting, and a customised readiness assessment | Epicor press release, Jan 6, 2026 |
Three points matter for planning. First, “tentatively” applies to the 2028.1 release date, not to the support dates; plan from June 30, 2029. Second, the gap between the final release and the end of Active Support is short. Kinetic’s final release is tentatively January 2028 with Active Support to December 31, 2029; Prophet 21’s is tentatively May 2028 with Active Support ending six months earlier, on June 30, 2029. Third, the release does not define Sustaining Support. Ask your Epicor account manager for the Sustaining Support terms in writing: security fixes, tax and regulatory updates, integration and certification changes, and response times.
Nothing in the announcement switches your system off. It is about where new features go after 2028.1, and how much vendor help you get while you run it.
What the timeline means for a distributor
| Period | Your on-premises Prophet 21 | What to do |
|---|---|---|
| Now to May 2028 | Feature releases continue up to 2028.1 | Decide your destination; run a fit test if ERPNext is a candidate |
| May 2028 to June 30, 2029 | On 2028.1 with Active Support, no new features | Upgrade to 2028.1 if you are staying on-premises for now; migrate in this window if you are leaving |
| From July 1, 2029 | Sustaining Support, scope per Epicor’s terms | Avoid running production here without written terms you accept |
Distributors usually avoid go-lives in their peak season and at financial year end. If you want to be live on a new platform before Active Support ends, count back from June 30, 2029: a pilot and parallel run, a build, data cleansing, then selection. A decision during 2027 leaves room. Deciding in 2029 means choosing under time pressure, at the same moment other on-premises Prophet 21 customers are booking the same consultants.
Your options
| Option | What it involves | Best when |
|---|---|---|
| Move to Epicor Cloud | Same Prophet 21 product, hosted and updated by Epicor | You can accept vendor-hosted SaaS and want to keep Prophet 21’s distribution depth |
| Stay on-premises on 2028.1 | Run on Active Support to June 30, 2029, then Sustaining | A bridge while you decide or complete a migration |
| ERPNext, self-hosted | Reimplement on open source on your own servers or a cloud account you control | Hard requirement to self-host, moderate pricing and warehouse complexity |
| ERPNext on Frappe Cloud | Reimplement on managed ERPNext hosting | You want to leave Epicor but not run servers |
Epicor Cloud is the default for a reason: it is the same application, your users keep their screens and habits, and Ascend with Epicor exists to move your data. The questions to ask Epicor are practical: what the subscription costs for your user count, how upgrades are scheduled and how much notice you get, what happens to your custom reports, integrations and database-level extracts, and where your data is hosted.
The distribution fit test: where Prophet 21 sites live or die
Distribution ERPs are judged on three things: whether they price every order correctly, whether they keep rebate money flowing back, and whether the warehouse ships the right goods on time. Run these tests on your own data before you sign anything.
1. Pricing matrices and contract pricing
Prophet 21 sites tend to carry layered pricing: list prices, customer-specific contract prices, price by customer group or job, quantity breaks, and cost-plus pricing. ERPNext handles this with three building blocks:
- Price lists and item prices: as many selling and buying price lists as you need, with item prices per list and per unit of measure (ERPNext Price Lists documentation, ERPNext Item Price documentation).
- Pricing rules: replace the rate, apply a discount or a margin, or add a free item, limited by item, item group, brand, customer, customer group, territory, quantity, value, date, warehouse, company or currency (ERPNext Pricing Rule documentation).
- Promotional schemes: several quantity or amount slabs in one scheme, mixed-item conditions and cumulative purchases, generating the underlying pricing rules (ERPNext Promotional Scheme documentation).
- Blanket orders: long-term commitments to buy or sell at negotiated rates, released over time (ERPNext Blanket Order documentation).
Test: export your 20 largest customers’ price records and every active contract, rebuild them, then price 200 historical order lines in ERPNext and compare with what Prophet 21 charged. Every mismatch is either a rule you have not configured or logic you will need to build. If your pricing depends on many overlapping exceptions, rule priority becomes the design problem; settle it in the fit test, not after go-live.
2. Rebates and supplier agreements
This is the test most likely to fail. Many distributors in electrical, HVAC, plumbing and industrial supply rely on supplier rebates and special pricing agreements, where you sell below normal cost under a supplier’s agreement and claim the difference back. In the ERPNext documentation we checked, pricing rules and promotional schemes cover customer-facing discounts and supplier price lists cover buying rates, but we did not find a dedicated feature for tracking supplier rebate accruals or submitting and reconciling claims. Treat this as a build: a custom app that records agreement terms, computes the claim from sales lines, posts the accrual and tracks payment. Test it against a full quarter of last year’s claims before you commit.
3. Warehouse and branch operations
Epicor describes Prophet 21’s warehouse management as covering receiving, cross-docking, put away, adjustments, picking, cycle counting and inventory operations, with barcoding and automation. ERPNext’s stock module covers:
- Warehouses as a tree, so branches, buildings and bins can be modelled (ERPNext Warehouse documentation).
- Putaway rules that assign incoming stock to warehouses by capacity and priority on purchase receipts and stock entries (ERPNext Putaway Rule documentation).
- Pick lists that choose stock locations first-in-first-out, or by nearest batch expiry for batched items (ERPNext Pick List documentation).
- Batch and serial tracking (ERPNext Batch documentation, ERPNext Serial No documentation), stock reconciliation for counts (ERPNext Stock Reconciliation documentation), item alternatives for substitutes (ERPNext Item Alternative documentation).
- Warehouse-level reorder levels that raise material requests automatically, for purchase or transfer from another warehouse (ERPNext reorder level (auto material request) documentation).
- Shipments with carrier, tracking number and status, and delivery trips for your own trucks (ERPNext Shipment documentation, ERPNext Delivery Trip documentation).
What we did not find in ERPNext’s standard documentation: RF-directed task queues, wave planning and yard management of the kind a dedicated WMS offers. If your busiest branches run on directed RF picking today, either test a mobile scanning approach on ERPNext in a real branch, or plan for a separate WMS integrated through the Frappe Framework REST API documentation.
4. Purchasing, landed cost and multi-branch finance
Material requests, purchase orders and receipts, landed cost vouchers to spread freight and duty into item cost (ERPNext Landed Cost Voucher documentation), multiple companies with inter-company invoices (ERPNext inter-company invoices documentation), and accounting dimensions for branch-level profit and loss (ERPNext accounting dimensions documentation). These are usually straightforward; test them anyway with a real month of transactions.
Fit test summary
| Area | In ERPNext | Typical result | What to test |
|---|---|---|---|
| List and contract prices | Price lists, item prices, blanket orders | Standard | Your top 20 customers’ contracts |
| Quantity breaks and cost-plus | Pricing rules (discount, rate or margin), promotional schemes | Standard to configure | 200 historical order lines priced identically |
| Supplier rebates and special pricing agreements | No dedicated feature found | Build | A full quarter of claims, accrual to cash |
| Bins, putaway, picking, counts | Warehouse tree, putaway rules, pick lists, stock reconciliation | Standard | One busy branch for a week |
| RF-directed tasks, waves, yard | Not found in standard docs | Build or separate WMS | Your highest-volume picking process |
| Replenishment | Warehouse-level reorder levels, material requests | Standard | Branch transfers vs supplier orders |
| Freight and duty in cost | Landed cost vouchers | Standard | Import receipts with freight split |
| Branch P&L | Accounting dimensions, multi-company | Standard | Month-end by branch |
| US sales tax | Tax templates and rules | Test | Your nexus states and exemption certificates in a pilot |
| eCommerce, EDI | Integration via REST API | Integration project | Your top EDI trading partners |
Costs: what is published
| Item | USD (published) | GBP | Source |
|---|---|---|---|
| Prophet 21 on-premises, Epicor Cloud | Quote only; no estimate given | Quote only | Epicor Prophet 21 product page |
| ERPNext software | No licence fee (GPL-3.0) | No licence fee | ERPNext repository on GitHub |
| ERPNext on Frappe Cloud, site plans | From $5 per month | About £3.78 (indicative) | Frappe Cloud pricing page |
| ERPNext on Frappe Cloud, dedicated servers | From $40 per month | About £30.22 (indicative) | Frappe Cloud server plans page |
Frappe Cloud publishes USD prices: site plans from $5 a month (about £3.78) and servers from $40 a month (about £30.22), checked on Nov 16, 2026. The GBP figures are indicative conversions, not Frappe prices.
Indicative GBP conversions use the Bank of England daily spot rate (series XUDLUSS) of US$1.3238 per £1 for 12 Nov 2026, the latest published figure when we checked on Nov 16, 2026. They are not official UK prices: the vendor does not publish a GBP list price for these items, and your invoice currency, rate and VAT treatment may differ.
Hosting is the smallest number in either budget. The real costs of an ERPNext move are the rebuild of pricing and rebates, integrations (EDI, eCommerce, carriers, sales tax), data migration and training. The real costs of Epicor Cloud are the subscription, the move and reworking any database-level customisations. Get both in writing before you compare.
What a Prophet 21 to ERPNext migration moves
| Data | Move to ERPNext as | Notes |
|---|---|---|
| Items, UOMs, product groups, supplier part numbers | Items, UOM conversions, item groups, supplier items | Clean duplicates and dead items first |
| Customers, ship-tos, contacts, terms | Customers, addresses, contacts, payment terms (ERPNext Customer documentation) | Map ship-to addresses carefully |
| Suppliers | Suppliers (ERPNext Supplier documentation) | Include rebate agreement owners |
| Price records and contracts | Price lists, item prices, pricing rules | Rebuilt, not copied |
| Stock on hand by branch and bin | Opening stock reconciliation per warehouse (ERPNext Stock Reconciliation documentation) | Count high-value bins before cutover |
| Open sales and purchase orders | Open orders via Data Import (ERPNext Data Import documentation) | Freeze changes during cutover |
| Open AR and AP | Opening invoices and balances (ERPNext opening balance documentation) | Reconcile to your aged reports |
| General ledger | Opening trial balance on a chart of accounts (ERPNext Chart of Accounts documentation) | Keep Prophet 21 read-only for history |
Do not plan to move years of transaction history into ERPNext. Keep Prophet 21 or a reporting copy of its database read-only for history and audits, and move masters, open items and balances.
Where Epicor Cloud is the better answer
- Rebates, special pricing agreements and complex contracts are a large part of your margin and you do not want to own custom code for them.
- Your warehouses depend on RF-directed picking and you do not want a separate WMS.
- You use Epicor’s surrounding products heavily, such as its eCommerce, CRM and reporting tools, or the AI features Epicor highlights.
- Your team knows Prophet 21 well and change capacity is limited.
ERPNext is a better fit when you need to self-host or control where the system runs, your pricing logic is moderate, per-user licence growth is a concern as you add branches and staff, and you want to own the system and its code.
A practical plan for Prophet 21 sites
Months 1 to 2: inventory and terms
List integrations, custom reports and database extracts. Ask Epicor in writing for Sustaining Support terms and an Epicor Cloud proposal. Pull your pricing, rebate and warehouse data for the fit test.
Months 2 to 4: fit test
Rebuild pricing for your top customers, a quarter of rebate claims and one branch’s warehouse week in ERPNext. Score each area: standard, configure, build, or no-go.
Month 5: decide
Compare five-year cost and risk for Epicor Cloud and ERPNext. Include integrations and the rebate build in the ERPNext column.
Then: build, pilot one branch, roll out
Go live branch by branch if your finance structure allows, or company-wide at a period end with at least one month-end in parallel, before June 30, 2029.
Decision table
| If this is true for you | Lean towards | Why |
|---|---|---|
| Supplier rebates and special pricing agreements drive your margin | Epicor Cloud | No dedicated rebate feature in ERPNext docs; you would build one |
| Directed RF picking in large warehouses | Epicor Cloud, or ERPNext plus a WMS | ERPNext standard stock is not a full WMS |
| Must self-host or control the hosting region | ERPNext | Open source, runs on your servers |
| Simple to moderate pricing, few rebates | ERPNext worth pricing | Price lists and pricing rules cover it |
| No appetite for change before 2029 | Stay on 2028.1, then decide | Active Support to June 30, 2029 |
Best for, and wrong choice when
ERPNext is best for
US distributors with 20 to 300 users who will not move to Epicor Cloud, whose pricing fits price lists and pricing rules, with modest rebate volume they are willing to build for, and who want open source they can self-host.
Epicor Cloud is best for
Prophet 21 distributors who rely on deep rebate and contract handling, RF-directed warehouses or Epicor’s add-on products, and who are comfortable with vendor-hosted SaaS.
ERPNext is the wrong choice when
Rebate claims are a major profit line and you do not want custom code, your warehouses need a full WMS you will not buy separately, or you need go-live before mid-2029 with no time for a proper fit test.
Frequently asked questions
When does Prophet 21 on-premises support end?
Epicor says Active Support for the final on-premises release, 2028.1, runs through June 30, 2029, and Sustaining Support begins July 1, 2029 (press release Jan 6, 2026; checked Nov 16, 2026).
What is the last on-premises Prophet 21 release?
Release 2028.1, tentatively scheduled for May 2028. After it, new innovation goes to Epicor Cloud.
Will Prophet 21 stop working after June 2029?
Epicor does not say the software stops. It moves into Sustaining Support, whose scope the announcement does not define. Ask Epicor for the terms in writing.
How much does Epicor Cloud cost for Prophet 21?
Epicor does not publish a price on the pages we checked. Ask for a quote; we give no estimate.
Can ERPNext handle distributor pricing matrices?
Often, through price lists, item prices, pricing rules (rate, discount or margin by customer, group, quantity, date and more) and promotional schemes. Test it by repricing a sample of your historical order lines.
Does ERPNext handle supplier rebates?
We did not find a dedicated supplier rebate or claims feature in ERPNext’s documentation. Plan it as a custom build and test it with a real quarter of claims.
What does ERPNext cost?
No licence fee (GPL-3.0). Frappe Cloud lists site plans from $5 a month and servers from $40 a month (checked Nov 16, 2026). Implementation is separate.