Navigating the Future of Epicor Kinetic On‑Premise: Preparing for the Final Release in 2028
What Kinetic Customers Need to Know and the Options Available

For organisations running Kinetic on‑premise, whether in their own data centre or a hosted environment, this shift raises important questions about long‑term support, security, and strategic planning.
This article outlines what’s changing, what it means for customers, and the practical paths forward.
Key Takeaways
What Happens to Epicor Kinetic On-Premise After 2028?
Epicor has confirmed that the final feature release for Epicor Kinetic on-premise is planned for January 2028 (Kinetic 2028.1). After this:
- Active Support continues until 31 December 2029
- Sustaining Support begins on 1 January 2030
- No new features will be released for on-premise deployments
- No new security updates or compliance updates will be provided after Active Support ends
- Future innovation, AI capabilities and platform enhancements will be delivered through Epicor Kinetic Cloud
Businesses running Epicor Kinetic on-premise should begin evaluating their long-term ERP strategy now to ensure they have sufficient time to assess options, manage risk and plan future investments.
📅 Key dates for Epicor Kinetc on-premise
Epicor has published a clear timeline for the final stages of Kinetic’s on‑premise lifecycle:
Epicor Kinetic ERP
- Final on‑premise release: Tentatively scheduled for January 2028 (Kinetic 2028.1)
- Active Support ends: 31 December 2029
- Sustaining Support begins: 1 January 2030
These dates represent the last time on‑premise customers will receive new features, enhancements, or compliance updates.
What Happens After the Final Release?
Epicor is not discontinuing Kinetic itself, only the on‑premise development track. After 2028, customers move through two support phases:
Active Support (through 2029)
Includes:
- Security updates
- Critical patches
- Compliance updates
- Technical support
Sustaining Support (from 2030 onward)
Includes:
- Limited technical assistance
- Access to EpicCare knowledge base
- No new features, security patches, or compliance updates
Your system will continue to run, but the lack of ongoing security and compliance updates introduces increasing operational risk over time.
Why Epicor is ending on-premise development for Kinetic
Epicor’s strategy reflects a broader industry shift toward cloud‑first ERP platforms. By consolidating development into the Kinetic Cloud, Epicor can deliver:
- More regular updates
- Built‑in security and uptime guarantees
- Modern AI‑driven capabilities (cloud‑only)
- Lower total cost of ownership
- Faster delivery of new features and integrations
The cloud version of Kinetic is now the primary innovation engine for the product.

What options do Kinetic customers have?
As the 2028 deadline approaches, organisations face four strategic paths.
Option 1: Migrate to Epicor Kinetic Cloud (Epicor’s Recommended Path)
This is where all future innovation will occur.
Benefits:
- Continuous feature updates
- Access to Epicor’s AI tools and automation capabilities
- Automatic security and compliance updates
- Reduced infrastructure and maintenance costs
- Improved scalability and performance
Migration Support:
Epicor offers tools and programs, such as Ascend with Epicor, to streamline data migration, reduce risk, and accelerate cloud adoption.
This option is ideal for organisations seeking modernisation, reduced IT overhead, and access to the latest capabilities.
Option 2: Remain On‑Premise Beyond 2028 (Short‑ to Mid‑Term)
Some organisations may choose to stay on-premise temporarily due to:
- Regulatory or data‑sovereignty requirements
- Heavy customisations
- Existing infrastructure investments
- Internal IT strategy
What you keep:
- A fully functional Kinetic system
- Access to EpicCare
- Limited support during Sustaining Support
What you lose:
- New features after 2028
- Security and compliance updates after 2029
- Access to new AI and automation tools
- Long‑term alignment with Epicor’s product roadmap
This path is viable for a few years but becomes increasingly risky over time.
Option 3: Move to a Hosted or Hybrid Model
Some customers may choose to:
- Move their on-premise Kinetic instance to a private cloud or hosting provider
- Use managed services to reduce internal IT workload
- Integrate cloud services around their on-premise core
This does not extend Epicor’s support timelines, but it can:
- Improve uptime and performance
- Reduce internal maintenance
- Serve as a bridge strategy before full cloud migration
This is a transitional option rather than a long‑term solution.
Option 4: Migrate to Another On‑Premise ERP System
For organisations committed to remaining fully on-premise long‑term, migrating to a different on-premise ERP platform is a viable though more complex path. Additionally as time moves on the choices of ERP system available for on premise hosting become less.
Why customers consider this option:
- Long‑term on-premise strategy driven by security, regulatory, or operational requirements
- Desire to avoid cloud‑only roadmaps
- Need for deep customisation or control not available in SaaS environments
- Preference for perpetual licensing models
Considerations:
- Full ERP replacement projects require significant planning, cost, and change management
- Data migration and process redesign can be extensive
- Third‑party integrations may need to be rebuilt
- Vendor selection should include long‑term on-premise commitment verification
When this option makes sense:
- Organisations with strict data‑sovereignty or air‑gapped requirements
- Businesses with highly specialised manufacturing or operational processes
- Companies that prefer full control over infrastructure and upgrade cycles
1. Assess your current version, customisations, and integrations
Older or heavily customised systems may require more planning.
2. Build a 2–4 year roadmap
The earlier you plan, the more options you have.
3. Engage Epicor or your implementation partner
Migration assessments, cost modelling, and data planning take time.
4. Evaluate security and compliance risks
Especially if you plan to remain on-premise beyond Active Support.
5. Budget for transformation, not just migration
Cloud ERP often aligns with broader modernisation initiatives.
Frequently Asked Questions About ERP Implementation Timelines
Is Epicor discontinuing Kinetic?
No. Epicor is continuing to invest in Epicor Kinetic, but future innovation and development will focus on the cloud version of the platform. The on-premise development track is scheduled to end with the final feature release in 2028.
When is the final Epicor Kinetic on-premise release?
Epicor has indicated that the final on-premise feature release is planned for January 2028, currently referred to as Kinetic 2028.1.
How long will Epicor support Kinetic on-premise?
Active Support is scheduled to continue until 31 December 2029. After that, customers move to Sustaining Support, which provides limited assistance but no new features, security updates or compliance updates.
Can I continue using Epicor Kinetic on-premise after 2028?
Yes. Your system will continue to operate beyond 2028. However, after Active Support ends in 2029, you will no longer receive new security patches, compliance updates or feature enhancements.
Should I move to Epicor Kinetic Cloud?
The right decision depends on your business requirements, infrastructure strategy, security considerations and long-term objectives. For many organisations, moving to Epicor Kinetic Cloud provides access to ongoing innovation, AI capabilities, automatic updates and reduced infrastructure management.
What are the risks of staying on-premise after 2029?
The primary risks include:
- No new security updates
- No compliance updates
- Increasing technical debt
- Reduced alignment with Epicor’s product roadmap
- Limited access to future innovations and AI capabilities
These risks will generally increase over time as the platform moves further beyond Active Support.
Can I move to a hosted or hybrid model instead of the cloud?
Yes. Some organisations choose a hosted or hybrid approach as an interim step. While this does not extend Epicor’s support lifecycle, it can reduce infrastructure management requirements and provide a bridge towards future cloud adoption.
When should businesses start planning for the 2028 deadline?
The best time to start planning is now. Businesses with complex customisations, integrations or regulatory requirements may require several years to assess options, develop a roadmap and execute a successful transition.
Customers who begin planning now will have more flexibility, lower risk, and a smoother transition, whether they migrate to Kinetic Cloud, remain on-premise temporarily, adopt a hybrid model, or move to a different on-premise ERP entirely.
What should your next step be?
Every Epicor Kinetic environment is different.
Factors such as customisations, integrations, regulatory requirements, infrastructure strategy and future business goals all influence the most appropriate path forward.
Whether you’re considering:
- Migrating to Epicor Kinetic Cloud
- Extending the life of your current on-premise environment
- Exploring a hosted or hybrid approach
- Evaluating alternative ERP solutions
early planning will provide the greatest flexibility and reduce future risk.
If you’re unsure what the 2028 timeline means for your organisation, Blue Sky ERP can help you assess your current environment, understand the implications of Epicor’s roadmap, and build a practical plan for the future.
Book a no-obligation consultation with one of our Epicor specialists to discuss your options and create a roadmap that aligns with your business objectives.
About Blue Sky ERP
Blue Sky ERP has extensive experience helping manufacturers, distributors and growing businesses implement, optimise and upgrade Epicor ERP solutions. Our team works closely with organisations to align ERP strategy with operational goals, helping customers navigate technology change with confidence.