What Epicor announced
Epicor published a phased schedule to retire on-premises releases across its three core ERP lines. Kinetic, its platform for mid-market discrete manufacturers, gets a final on-premises release in January 2028, with active support running through the end of 2029 and sustaining support starting in 2030. Prophet 21, aimed at wholesale and industrial distributors, hits its final release in May 2028. BisTrack, used heavily in building materials and construction distribution, splits into two tracks: the web browser and API version gets a final release in July 2028, while BisTrack Desktop's final on-premises release lands in December 2026, a fraction of the runway the other product lines get.
After each final release, Epicor moves customers into a tiered support model: active support for roughly a year, then sustaining support for a further period, after which the on-premises product effectively stops receiving meaningful investment. All future feature development, including Epicor's new AI agent capabilities, is committed exclusively to Epicor Cloud. The company frames this as accelerating access to AI-powered functionality and reducing the operational burden of managing on-premises infrastructure, and it already has more than 20,000 businesses running on the cloud platform as a reference base.
Why analysts call this an operating model shift, not a hosting decision
Manish Jain, principal research director at Info-Tech Research Group, put it directly: organizations shouldn't see this as a hosting decision shift, it signals a long-term operating model change. His sharper point is worth sitting with: it's not customers choosing the cloud, it's vendors taking alternatives off the table. That reframes the decision entirely. This isn't a cost-benefit exercise where cloud ERP competes against on-premises ERP on its merits over a multi-year evaluation. It's a forced migration on a vendor-set clock, and the negotiating leverage that comes with an open choice disappears the moment the on-premises option has a published expiration date.
Robert Kramer, VP and principal analyst at Moor Insights & Strategy, softened the urgency slightly by noting Epicor isn't turning off on-premises systems overnight, but he confirmed the substance: all new capabilities, improvements, and investment go to the cloud exclusively going forward. His framing is useful for planning purposes: staying on-premises becomes a supportable maintenance decision, not a growth one. That's an honest way to describe where you'll be if you don't migrate. You can keep the lights on for a while. You cannot keep innovating on that platform.
The compliance and control trade-off nobody markets loudly
Jain's most pointed warning concerned regulated industries: cloud migration shifts operational risk from internal IT to vendor architecture and SLAs, and for compliance-heavy businesses, compliance becomes an engineering challenge. That's a real cost, not a hypothetical one. If your ERP handles regulated financial data, controlled manufacturing specifications, or data subject to sovereignty requirements, moving to a vendor-hosted cloud platform means your compliance posture now depends partly on contract terms and vendor architecture decisions you don't fully control, rather than on infrastructure your own team configured and audited directly.
Kramer flagged the operational flip side too: cloud outages are no longer localized, they can halt entire value chains, which means governance planning has to treat vendor uptime as a supply chain risk, not just an IT availability metric. If Epicor Cloud goes down, every customer running on it goes down simultaneously, in a way a well-architected on-premises deployment with its own failover wouldn't. For manufacturers and distributors running just-in-time operations, that's a business continuity conversation your risk committee should be having now, well before the migration deadline forces the issue.
The December 2026 deadline nobody's talking about
Buried in the broader announcement is a detail that deserves more attention than it's getting: BisTrack Desktop's final on-premises release comes in December 2026, four months from now. If you're a building materials or construction distributor running BisTrack Desktop on-premises, your window to receive new on-premises functionality closes this year, with active support running only through the end of 2028. That's a materially shorter runway than Kinetic or Prophet 21 customers get, and if your migration planning hasn't started, you're already behind the timeline analysts consider reasonable for an ERP transition of this scope.
The practical move is to get your Epicor account team on the phone this quarter and secure a written migration timeline and cost estimate specific to your instance, rather than a generic roadmap deck. Ask specifically about data migration complexity for whatever customizations you've layered onto BisTrack over the years, since those customizations are almost always the long pole in an ERP cloud migration timeline. Build a realistic testing and cutover window around that answer, and confirm which of your integrations, reporting tools, and EDI connections need rework before you commit a go-live date to your leadership team.
The pattern beyond Epicor
This is not an isolated vendor decision. SAP customers are living through an almost identical dynamic with the 2027 deadline for standard support on ECC ahead of the push to S/4HANA, and other major ERP vendors have signaled similar cloud-first trajectories over the past two years. The lesson generalizes: if your core ERP vendor still offers on-premises deployment as a first-class option, treat that as a temporary state, not a permanent architectural choice. Vendors are converging on cloud-only roadmaps because it standardizes their support burden, accelerates their own AI feature velocity, and locks in recurring revenue, all of which are rational business reasons that have nothing to do with what's best for any individual customer's risk tolerance.
For CIOs managing any legacy ERP platform, the actionable step is to get your vendor's cloud-only timeline in writing now, even if you have years of runway left, and build it into your multi-year capital planning immediately. Waiting until the vendor sets a deadline, as Epicor's BisTrack Desktop customers now face, compresses your negotiating position and your implementation timeline simultaneously. The businesses that come out ahead on these forced migrations are the ones that started planning before the deadline was published, not after.
