Epicor sets timeline to sunset on-prem ERP as cloud becomes the only path forward

Reflecting the continued push by ERP vendors to the cloud, Epicor has announced its schedule to sunset several of its legacy on-premises tools.

The company will roll out final releases for Epicor Kinetic, Epicor Prophet 21, and Epicor BisTrack, and will offer tiered support levels in a phased schedule beginning later this year.

Epicor says this will allow enterprises to take advantage of tools exclusive to Epicor Cloud without having to maintain infrastructure. But the move will present challenges for some organizations, particularly those in highly regulated and data-sensitive industries, analysts point out. 

“These organizations shouldn’t just see this change as a hosting decision shift; it signals a long-term operating model change,” noted Manish Jain, a principal research director at Info-Tech Research Group. It’s not customers choosing the cloud, he said, “It’s about vendors taking alternatives off the table.”

Not an overnight shift, but a fundamental one

With this move, customers will have quicker access to new features and AI-powered capabilities, such as the first ERP AI agent with outcomes-based pricing, as well as a “a modern, resilient platform” that reduces IT burden and operational risk, Epicor said.

Customers using on-premises versions of Kinetic, Prophet 21, and BisTrack will continue to receive support, the company noted, but final releases will roll out between 2026 and 2028, based on platform. Enterprises will then transition into ‘active support’ until 2029 at the latest, and ‘sustaining support’ will begin as early as 2027.

More than 20,000 businesses run on Epicor Cloud. Generally, Epicor Kinetic is used by mid-market and upper mid-market manufacturers, such as discrete manufacturers with complex production, supply chain, and shop-floor requirements, explained Robert Kramer, VP and principal analyst at Moor Insights & Strategy.

Wholesale and industrial distributors who require strong inventory management, pricing, and order fulfillment steer toward Prophet 21, while BisTrack is popular among building materials, lumber, and construction supply distribution sectors, he explained.

“Epicor is not turning off on-premises systems overnight,” Kramer emphasized, but all new capabilities, platform improvements, and long-term roadmap investments will be cloud-only.

The Epicor sunset timeline is as follows:

Kinetic

• Final on-premises release tentatively scheduled for January 2028
• Active support, which provides full access to Epicor phone support, security updates, new issue investigation, and more, will be offered through December 31, 2029
• Sustaining support, which offers limited phone support, access to the latest release (but not to new modules), and an online knowledge base, begins January 1, 2030

Prophet 21

• Final on-premises release tentatively scheduled for May 2028
• Active support through June 30, 2029
• Sustaining support beginning July 1, 2029

BisTrack

• Final on-premises BisTrack Web Browser & API release tentatively scheduled for July 2028
• Active support for on-premises BisTrack Web Browser & API through June 30, 2029
• Sustaining support for on-premises BisTrack Web Browser & API release beginning July 1, 2029

BisTrack Desktop

• Final on-premises release tentatively scheduled for December 2026
• Active support through December 31, 2028
• Sustaining support beginning January 1, 2029

BisTrack UK 3.9 (2017)

• Active support through December 31, 2026
• Sustaining support beginning January 1, 2027

New possibilities, different risks

This move will benefit customers looking to modernize and take advantage of the ERP systems of tomorrow: agentic AI and event-driven, noted Moor’s Kramer. Benefits will include simpler infrastructure, more predictable upgrades, and access to new capabilities without the need to manage servers, databases, or patches, or to cycle through time and resource-intensive upgrades.

“Staying on-prem becomes a supportable maintenance decision, not a growth one,” said Kramer.

Organizations will gain the freedom to innovate and “dynamically match costs” with revenue through unit economics, noted Info-Tech’s Jain. “This move will be projected as one that favors organizations prioritizing speed, scalability, and reduced infrastructure management, especially those with limited IT capacity to maintain ERP environments at production-grade reliability.”

For businesses with continuous operations, tight schedules, or requiring limited downtime, operational risk moves from internal IT to the vendor’s architecture, SLAs, and incident response, he explained.

Going forward, enterprises must plan for vendor-led upgrade cycles, tighter dependency on release roadmaps, and reduced control over infrastructure, he said. Cloud ERPs (whether Epicor, Microsoft, or SAP) don’t eliminate risk; they reshape it. Companies trade on-prem localized failures for platform-wide dependencies that can halt entire value chains if resilience and governance aren’t engineered deliberately.

“For organizations that rely on these solutions, the strategic shift is from deployment flexibility to dependency management, and many CIOs aren’t fully resourcing that transition,” said Jain.

Highly-regulated sectors won’t be excluded, he noted. Rather, they will be forced to adopt and combine cloud ERP cores with stricter data controls, residency requirements, and compensating governance mechanisms. Or, if they require strict data sovereignty, they may need to shift to sovereign clouds.

“Going forward, regulated industries aren’t cloud-blocked; they’re architecture blocked,” Jain emphasized. “As on-prem options disappear from the ERP space, compliance becomes an engineering challenge.”

The cloud is the future, and all enterprises must adapt

Across the board, ERP vendors, and most SaaS providers, have been converging on cloud-first models.

This helps them “accelerate innovation, standardize platforms, embed AI capabilities, and, most importantly, sustain recurring revenue,” Jain pointed out. ERP companies have considered on-premises architectures as roadblocks in achieving these objectives.

Concentrating development in the cloud has become the primary way vendors deliver continuous updates, embed AI integrated analytics, and provide security at scale without “forcing disruptive upgrade projects every few years,” said Kramer.

“Maintaining parallel on-prem and cloud platforms slows innovation and increases cost, which is why vendors are trying to draw a clearer line now,” he said.

The move will allow Epicor to focus engineering, security, and innovation on a single deployment model instead of “fragmenting effort across cloud and on-prem versions,” he said.

Customers do give up some control and accept dependencies on a centralized service. Cloud platforms are resilient, Kramer emphasized, but outages are no longer local events that customers can mitigate with internal failover or workarounds.

For regulated or sensitive industries that can’t fully pivot to public cloud, “this does not mean an immediate cliff, but it does narrow long-term options,” he pointed out. Hybrid, private cloud, and sovereign deployments will become the middle ground, but they come with their own challenges, requiring more deliberate planning, stronger governance, and clearer accountability.

“Over time, even highly regulated organizations will be pushed to modernize how they consume ERP,” Kramer noted. “Not because on-prem stops working, but because it gradually stops evolving in ways that support new business and regulatory demands.”