Prophet 21 On-Premises End of Life Guide

Epicor's final on-premises feature release for Prophet 21 is version 2028.1, tentatively scheduled for May 2028. Active Support, which includes security updates and critical patches, continues through June 30, 2029. After that, Sustaining Support offers only limited phone help and access to the last release, with no new features or fixes, so distributors who stay on-premises past 2029 fall increasingly behind on capability and security.

The exact timeline Epicor has announced

Prophet 21's final on-premises feature release is version 2028.1, tentatively scheduled for May 2028. No new features will be developed for on-premises after that date.

Active Support, which includes security updates, critical patches, phone support, and new issue investigation, continues through June 30, 2029. Starting July 1, 2029, Sustaining Support provides only limited phone support and access to the latest release along with the online knowledge base, with no new features or modules.

• May 2028: final on-premises feature release (version 2028.1)
• June 30, 2029: Active Support ends
• July 1, 2029 onward: Sustaining Support only, no new fixes or features

What end of life actually means, and what it does not

The May 2028 deadline marks the final on-premises feature release, not a forced migration cutoff. A Prophet 21 system will not stop working in 2028, and distributors will not be forced off the platform on that date.

But migrating before June 2029 ensures continued security and compliance updates during the Active Support phase. All future feature development, AI capabilities, and platform innovation will be exclusive to Epicor Cloud, so distributors who remain on-premises will receive diminishing support over time and will not gain access to new functionality.

For Texas distributors in healthcare supply, energy, oilfield, and food service distribution, where regulatory compliance, system security, and operational capability matter most, staying on-premises past 2029 creates compounding risk that grows every year.

The technology stack problem distributors often miss

Prophet 21 depends on supporting tools like SQL Server and Windows Server, which carry their own separate support timelines. Distributors running older versions of those may already be close to important deadlines on the underlying infrastructure, not just the ERP itself.

Since SQL Server Reporting Services is tied to SQL Server, when SQL Server support ends, the reporting layer is affected too. This means the real project is not just a Prophet 21 upgrade, it is a full technology stack assessment. A proper cloud migration review should cover the entire stack, not only the P21 application layer.

Why starting migration planning now matters

ERP changes take time, and a well-planned migration can run several months or more. Waiting too long forces a rushed migration, which increases both risk and cost. Starting early gives distributors more control and better outcomes.

Distributors who begin planning in 2026 and 2027 have time to run a thorough environment assessment, inventory customizations, plan integration updates, prepare data, test in a staging environment, and execute a controlled migration that does not disrupt operations.

Distributors who wait until 2027 or 2028 face a crowded consulting market, since experienced Prophet 21 cloud migration consultants become less available and more expensive as the deadline approaches. Those who planned early will have already executed while the ones who waited compete for the same limited resources.

What the cloud migration process actually involves

For distributors with limited customizations or API integrations, the process is fairly direct: provide a full database backup, Epicor restores it in the cloud, and access to a test environment with real data typically follows within a couple of weeks.

Complexity increases significantly for distributors with heavy DynaChange customizations, since custom menus, user-defined fields, validation rules, approval workflows, and custom portals all require review, and not all on-premises customizations transfer directly to the cloud. Complex third-party integrations, including EDI connections, eCommerce integrations, shipping carrier connections, and reporting platform integrations, need testing and possible reconfiguration. Large data volumes from years of historical transactions require careful migration planning for data integrity and performance, and multi-branch operations across cities like Houston, Dallas, Austin, and San Antonio need structured planning that allows branch-by-branch validation before full go-live.

• Heavy DynaChange customizations
• Complex third-party integrations (EDI, eCommerce, shipping)
• Large historical data volumes
• Multi-branch operations needing phased validation

Key takeaways

• Final on-premises feature release is version 2028.1, tentatively May 2028.
• Active Support ends June 30, 2029; Sustaining Support afterward offers no new fixes or features.
• Underlying SQL Server and Windows Server support timelines can compound the migration urgency.
• Migration complexity rises sharply with heavy DynaChange customizations and multi-branch operations.
• Starting migration planning in 2026-2027 avoids the expensive, crowded consulting market near the deadline.

Frequently asked questions

What happens to my Prophet 21 system after June 2029 if I stay on-premises?

The system will continue running, but it moves into Sustaining Support, which provides only limited phone assistance and access to the last release with no new fixes, patches, or features. All future feature development and AI capabilities go exclusively to Epicor Cloud, so an on-premises system falls further behind in both capability and security every year it remains unmigrated. For distributors in regulated industries, this creates growing compliance and security risk rather than an immediate shutdown.

Do I need to migrate my SQL Server and Windows Server at the same time as Prophet 21?

In most cases, yes, because Prophet 21 on-premises depends on both, and each has its own separate support timeline that may already be close to expiring. Since SQL Server Reporting Services is tied to SQL Server, its support timeline affects your reporting capability too. A proper migration assessment should cover the entire technology stack together, not treat the ERP as an isolated project from the infrastructure it runs on.

How much lead time should a Texas distributor plan for a Prophet 21 cloud migration?

For distributors with heavy customizations, complex integrations, or multi-branch operations, planning should start well over a year before the desired go-live date, following the assessment, inventory, planning, testing, and go-live sequence. For distributors with limited customizations, the process can move faster, sometimes achieving a test environment with real data within a couple of weeks of providing a database backup. Starting in 2026 or 2027 avoids the crowded, more expensive consulting market that is expected to form as the 2028-2029 deadlines approach.