Epicor is ending new feature development for on-premises Prophet 21 (P21) after version 2028.1, targeted for May 2028. Active support continues through June 30, 2029. After that, on-prem P21 customers move to sustaining support only: no security patches, no compliance updates, no new capabilities. Epicor-managed cloud customers are unaffected.
The date is fixed. Whether P21 is actually your bottleneck is still an open question.
Crestwood Associates put this breakdown together because our team fields this exact question from distribution and manufacturing companies every week. As a Gold-certified Acumatica partner and Microsoft Solutions Partner with 27 years in business and more than 5,000 ERP implementations completed, in-house, start to finish, we’ve guided companies off P21, Sage, and Dynamics GP long before this announcement made it urgent.
What Epicor Actually Announced
In January 2026, Epicor announced the Prophet 21 phase-out for on-premises customers, prioritizing cloud innovation going forward. That is not an end-of-life notice and it is not a forced shutdown. Existing on-premises systems will keep running. What changes is the roadmap: new features, AI tooling, and regulatory updates will ship to Epicor-managed cloud customers first, and eventually only.
Version 2028.1 is the last on-premises release scheduled to include new functionality. After that, on-prem P21 gets a fixed window of active support, then a long tail of sustaining support with no forward motion.
The P21 On-Premises Timeline
Milestone | Date | What It Means for P21 On-Prem Customers |
Final on-premises feature release (v. 2028.1) | Targeted May 2028 | Last version to receive new features, enhancements, or AI tooling like Prism. |
Active support window closes | Through June 30, 2029 | Security updates, critical patches, compliance updates, and technical support continue on 2028.1. |
Sustaining support begins | July 1, 2029 | No new releases, no security patches, no compliance updates. Limited support focused only on keeping the system running. |
Who Is Affected, and Who Isn’t
This applies to every on-premises, private-datacenter, or self-hosted P21 customer, including perpetual license holders and systems hosted on unmanaged Azure or AWS infrastructure. If Epicor is not managing your cloud environment, you are on the affected list.
Customers on Epicor-managed cloud infrastructure are not affected. They continue to receive every future feature, security update, and AI capability Epicor ships, on the same schedule as everyone else on that path.
What Actually Changes When the Clock Runs Out
After May 2028, on-prem P21 stops evolving. No new AI tools like Prism, no automation improvements, no adaptation to future regulatory changes. The system freezes in place.
After June 30, 2029, the risk profile changes. Three things start compounding at once:
1. Security exposure. No patches means every newly discovered vulnerability stays open indefinitely.
2. Compliance drift. Tax and regulatory changes in jurisdictions like Mexico or the UK stop being addressed in the software.
3. Operational ceiling. Direct SQL access and heavy customizations, common on P21, get harder to maintain without vendor-side updates to lean on.
None of this shuts the system off. A frozen P21 instance can run for years. But an auditor, an insurer, or a PE firm evaluating the business will ask about the ERP roadmap, and “we’re on sustaining support for a platform with no forward development” is not the answer that closes that conversation quickly.
The Real Cost of Waiting
Migration timelines for mid-market distributors typically run 12 to 18 months from decision to go-live. Counted back from June 2029, that leaves a shrinking window to plan a controlled transition instead of a rushed one.
Waiting does not remove the decision. It just moves it to a point where data migration, process review, customization assessment, and staff training all have to happen under a deadline instead of on a schedule you set yourself. Crestwood sees this pattern play out the same way almost every time a legacy platform hits its final support window: the companies that start the conversation early get to choose their timeline. The ones that wait get handed one.
If You Do Start Evaluating: Platform, Partner, People
Not everyone reading this is ready to pick a platform yet, and that is fine. When the time comes, Crestwood evaluates every legacy exit against three legs of the same stool: Platform, Partner, and People. Skip one and the other two do not hold the implementation up.
- Platform: does the system fit how a distribution or manufacturing business actually operates, order flow, inventory accuracy, landed cost, multi-entity accounting, not just what the feature list claims.
- Partner: is the same team selling, implementing, and supporting the system, or does the relationship get handed off after the contract signs.
- People: is the organization ready to run the new system day to day, with training built into the plan instead of bolted on at the end.
The comparison below reflects where a frozen on-premises P21 instance stands next to a modern cloud ERP once the support clock runs out, and who’s actually in the room when it’s time to migrate.
Operational Focus | On-Premises P21 After 2029 | Modern Cloud ERP (Acumatica / Business Central) |
Order Flow & Margin Management | Static, no new integrations, manual workarounds accumulate | Native WMS and order management, 300+ marketplace integrations |
Security & Compliance | No patches after June 2029, growing exposure to ransomware and audit findings | Automated cloud patching, SOC 2 controls, encryption at rest and in transit |
Access & Scalability | On-prem hardware refresh cycles, VPN-dependent access | Cloud-native, real-time access from any browser or device |
Intelligence & Automation | Reactive reporting, no roadmap for AI-driven exception handling | Embedded AI for anomaly detection, forecasting, and automated data entry |
Customization & Data Access | Direct SQL access, harder to maintain without vendor updates | Governed, read-only data access with modern extensibility tools |
Who Implements It | Original VAR relationship may be years old or dissolved | Crestwood Associates: sells, implements, and supports in-house, 27 years, 5,000+ implementations |
Choosing an Implementation Partner: What Actually Matters
The platform decision gets most of the attention. The partner decision determines whether the migration works. Look for a partner that sells, implements, and supports the system with in-house employees throughout, not a reseller who hands the account to a different team after the deal closes. Crestwood has run this exact model since 1998: one hand to shake, no handoffs, the same people at the table from the first conversation through post-go-live support.
Ask direct questions before signing anything: Who exactly touches your data during migration? What does support look like six months after go-live? Has this team migrated a business off the specific platform you’re leaving, not just onto the platform you’re moving to.
How Crestwood Approaches a P21 Exit
Crestwood Associates has guided mid-market distributors, manufacturers, and professional services firms through ERP transitions since 1998, with more than 5,000 implementations completed. The approach starts with a diagnostic, not a pitch: understanding what P21 is actually being asked to do today before recommending what replaces it.
That starts with the Business Optimization Assessment. No homework before it. No pitch during it. The business may not have a people problem. It may have an operating model problem, and the assessment is built to tell the difference before any platform gets recommended. We sell it, implement it, and support it. In-house employees throughout. One hand to shake.
Frequently Asked Questions
Do I need to migrate off Prophet 21 immediately?
No. On-premises P21 keeps running after May 2028 and continues receiving active support through June 30, 2029. There is no forced shutdown. The urgency is about planning a controlled migration inside a 12 to 18 month window, not an emergency cutover.
Does this phase-out affect Epicor’s cloud-hosted P21 customers?
No. Customers on Epicor-managed cloud infrastructure continue to receive all future features, security updates, and AI tooling on the standard release schedule. The phase-out applies only to on-premises, private-datacenter, and self-hosted deployments, including unmanaged Azure or AWS instances.
What happens to my P21 system after sustaining support begins in July 2029?
The system keeps running, but Epicor stops shipping new releases, security patches, and compliance updates. Support is limited to keeping the existing installation operational, not evolving it. Risk accumulates the longer the business stays on that version.
How long does a typical ERP migration take for a mid-market distributor?
Most mid-market distribution and manufacturing migrations run 12 to 18 months from initial decision to go-live, depending on data complexity, customization depth, and how many integrations need to be rebuilt on the new platform.
What should I look for in an ERP implementation partner?
A partner who sells, implements, and supports the system with in-house staff throughout, has direct experience migrating businesses off your specific legacy platform, and can show a fixed-scope path to go-live rather than an open-ended timeline. Crestwood Associates is one of the few partners that does all three under one roof.
Where to Start
If P21 is running the business today but the roadmap has stopped moving, the next move isn’t picking a platform. It’s getting a straight, outside read on what’s actually driving cost and risk in the current operating model, software, process, or both. That’s exactly what the Business Optimization Assessment is built to answer.
Connect with our team of ERP experts to explore next steps.
