If you run Epicor Kinetic on-prem, Epicor just gave you something most ERP customers never get: a clear, written timeline. That matters because cloud moves are easier when you plan them, not when you are forced into them.
This blog breaks down what Epicor announced, what the dates really mean, and why starting now usually saves the most pain later.
This is not a rumor or “maybe someday.” Epicor published a schedule for the final on-prem feature releases and what support looks like afterward.
Epicor announced that on-premises customers will get a final feature release, then move into defined support phases. After the final on-prem feature release, new innovation is expected to be delivered through Epicor Cloud.
For Kinetic on-prem, Epicor shared these key milestones:
Even if those dates feel far away, cloud planning still needs a runway. Most of the work is not the “migration weekend.” It’s the prep.
On paper, this looks like an ending. In practice, it’s clarity and clarity is what lets you stay in control.
You have time to review what you run today, clean it up, and choose the right path. That is way better than scrambling during a rushed upgrade or an unexpected infrastructure issue.
A calm project is cheaper than an emergency project. Planning early lets you pick timing that fits your business, your staffing, and your busy season, not someone else’s deadline.
Epicor’s message is straightforward: the future of new features and innovation is cloud. If you stay on-prem long term, you are giving up new capabilities. That can be fine, but it should be a conscious decision.
This is not a “your system stops working” situation. But it is a shift in what you can expect over time.
Epicor’s schedule includes a period of Active Support after the final on-prem release, then Sustaining Support after that. So you are not getting cut off tomorrow.
After the final on-prem feature release, you should not expect new on-prem features going forward. Over time, the gap between cloud and on-prem will grow.
Most cloud moves fail or drag out for boring reasons. Old customizations. Messy data. Unclear ownership. Starting now gives you room to fix those problems before they become blockers.
The biggest issues are usually:
You can fix those with a plan. You cannot fix them fast during a last-minute push.
“Lift and shift” sounds easy, but it often moves the same mess into a new environment. A smarter path is to keep what truly adds value, simplify what doesn’t, and use standard cloud capabilities where possible.
Manufacturers have real-world busy cycles. When you start early, you can schedule the riskiest work when the business can handle it, and avoid go-live during peak shipping or production periods.
Write down:
If you cannot explain your current setup, you cannot plan the future one.
Make a simple inventory:
This list becomes your project scope.
Cloud does not fix bad data. Clean up:
Less junk means fewer headaches later.
A real timeline includes:
A good cloud move is not about rushing. It’s about getting control of scope, risk, and business impact.
We help you get a clear view of what you have today: customizations, integrations, data risk, and what will matter most in the cloud.
Not every customization or integration should move to the cloud as-is. We help you decide what to keep, simplify, replace with standard cloud features, or retire altogether. The goal is a cleaner system that is easier to support and upgrade long term.
We support planning, execution, testing, and go-live so operations stay stable. The goal is simple: move to the cloud without breaking what keeps the business running.
No. Epicor’s schedule is about the final on-prem feature release, not your system shutting off. Support continues after that, but changes over time.
Epicor listed Kinetic 2028.1 as the final on-prem feature release, tentatively scheduled for January 2028.
Epicor defines a period of Active Support after the final release, followed by Sustaining Support starting later. The key difference is that support becomes more limited over time, and new features are not expected on-prem.
Epicor gave you the timeline. The best move is to use it.
If you want a clear plan that covers customizations, integrations, data, testing, and timing, TeccWeb can help you map the path and execute it without a fire drill.
Partnering with Teccweb ensures your Epicor setup fully supports this goal by giving your finance teams the tools they need to make informed, confident decisions.
Ready to simplify your multi-site reporting?
