Epicor’s Migration to Kinetic UI: What You Need to Know Before the 2026 Deadline

Epicor has announced the official sunset of its classic Smart Client UI, marking a significant transition for all Epicor ERP users. With the upcoming release of Kinetic 2026.1, scheduled for May 2026, the Classic UI will no longer be available or supported. The Kinetic browser-based interface will become the standard for all users, both on-premise and in the cloud.

This transition presents both a technical and strategic opportunity. Understanding the implications and preparing ahead of time will be essential to minimize disruption and take advantage of the latest platform enhancements.

Key Deadline: May 2026

Beginning with Kinetic 2026.1, Epicor will fully retire the Smart Client. All modules, custom screens, and business processes currently built on the Classic UI will need to be rebuilt or migrated to Kinetic using modern tools such as Application Studio.

Modules and Tools Affected by the Migration

Here is a snapshot of what is changing with the 2026.1 release:

Module / Tool	Post-May 2026 Status
Smart Client (Classic UI)	Retired
Epicor Information Worker	Retired
Epicor Handheld (Data Collection)	Replaced by Kinetic Warehouse (EKW)
Classic Configurator	Requires conversion or transition to CPQ
Inspection Configurator	Must be rebuilt using Application Studio
Epicor Work Anywhere (EWA)	No longer needed
Power Tools Client	Introduced for non-browser utilities (starting 2025.2)

Why Epicor Is Moving to the Kinetic Browser Interface

Epicor’s push toward a unified browser-based experience reflects broader trends in enterprise software. The Kinetic UI is designed to be faster, more accessible, and easier to use. Organizations that begin their transition early will benefit from enhanced usability and long-term platform alignment.

Benefits of the Kinetic UI:

• A modern, streamlined interface with fewer clicks and more intuitive navigation

• Device flexibility that enables access from laptops, tablets, and mobile browsers

• Improved performance across key screens and transactions

• Low-code customization through Application Studio, reducing reliance on traditional development

• Access to new features, including enhanced MRP tools, nested BAQs, and Explorer views

• A future-ready architecture that aligns with cloud deployment options

What Happens to Your Customizations?

One of the most critical aspects of this transition is the treatment of customizations developed in the Classic UI. Many organizations rely heavily on BPMs, custom forms, embedded C# scripts, and layered personalization. These elements will not transfer directly into the Kinetic framework.

Considerations:

• C# scripting and Classic personalization layers must be reviewed and often re-engineered. Application Studio now handles most screen logic using visual tools and event-driven actions.

• Embedded logic in Classic screens may need to be restructured. Business logic can be moved to Epicor Functions or BAQs, offering more sustainable and upgrade-friendly alternatives.

• Dashboards and BAQs may require adjustments to formatting, structure, or parameters to align with the Kinetic UI’s responsive design.

Where possible, organizations should treat this migration as an opportunity to streamline and modernize rather than replicate existing processes.

Application Studio: From Rebuild to Redesign

Application Studio is at the center of the Kinetic customization model. It allows users to create tailored forms using drag-and-drop tools, event handlers, and layering, all within a low-code environment.

Real-World Example:

Suppose your team has a custom order entry form built in the Classic UI with additional UD fields, auto-populating values, and validation rules. In Application Studio, this can be reconstructed using:

• Layered customizations that allow enhancements without affecting the base system

• Event handlers such as "On Field Change" or "On Load" to manage screen behavior

• BAQ calls for real-time data retrieval or field population

• Visual scripting to replace procedural C# logic

The result is a more maintainable interface that remains upgrade-safe and aligned with Epicor’s future development path.

Testing and Validation Before Go-Live

Even if forms have been migrated to Kinetic, proper validation is critical. The visual structure, screen behaviors, and responsiveness can all impact workflow if not thoroughly tested.

Recommendations:

• Set up a dedicated sandbox environment for Kinetic UI

• Validate form performance under real user conditions

• Confirm screen behavior, field logic, and user roles across all modules

• Review security groups, user permissions, and personalization

• Conduct parallel testing for high-impact transactions

Testing should be treated as an essential phase, not an afterthought. It ensures confidence before system-wide adoption.

Common Misconceptions About the Migration

Despite widespread communication from Epicor, several misconceptions still circulate. Clearing up these points early helps stakeholders stay aligned and encourages proactive planning.

Myth	Reality
Kinetic is only for cloud users	Kinetic UI is required for both on-premise and cloud deployments
The browser interface is slower	Performance improvements have significantly enhanced response times
Customization is no longer possible	Customization is supported through new tools like Application Studio and Epicor Functions
You can wait until 2026	Delaying migration increases risk and reduces time to train users and optimize forms

What Is the Power Tools Client?

To support functions that are not yet fully supported in the browser, Epicor is introducing the Power Tools Client in release 2025.2. This standalone utility will provide access to:

• Data Management Tool (DMT)

• Epicor Functions

• Advanced Print Routing

• Service Designer (for SDK)

These tools will ensure continuity for key administrative tasks during the migration phase.

Preparing for a Successful Migration

Transitioning from Classic to Kinetic requires structure, prioritization, and phased execution. Teams should consider the following approach:

1. Review Your Current Release

If your environment is not yet on Kinetic 2024.1 or later, an upgrade is recommended before initiating the UI transition. Earlier versions may lack necessary compatibility updates.

2. Audit Classic Dependencies

Document all forms, dashboards, custom scripts, and business logic that rely on Classic UI components. Identify what needs to be migrated, replaced, or redesigned.

3. Train and Prepare Your Users

Training is critical to user adoption. Begin with internal champions or power users, and provide hands-on experience through sandbox environments. Epicor Learning Center resources can support ongoing training.

4. Rebuild Customizations with Purpose

Prioritize the most heavily used screens and those with the most business impact. Avoid direct replicas where possible and use the transition as a chance to simplify and improve user experience.

5. Address Tool Retirement

• Retire Epicor Work Anywhere, which is no longer necessary in the browser version

• Migrate data collection activities to Epicor Kinetic Warehouse (EKW)

• Rebuild inspection workflows using Application Studio or grid-based layouts

Why Early Planning Matters

Waiting until the 2026 deadline introduces risk. By starting the migration process now, teams can avoid deadline pressure, ensure proper testing, and take full advantage of Epicor’s newer features and interface improvements.

• Minimize disruption during the transition

• Give users time to adjust and train

• Improve adoption through phased rollout

• Unlock features already available in recent releases

Final Thoughts

Epicor’s transition to the Kinetic browser interface is more than a cosmetic upgrade. It represents a shift in how enterprise users interact with their ERP system. Teams that begin this process early will be better positioned to manage change, reduce risk, and streamline operations.

Approach this change as an opportunity to clean up legacy systems, modernize processes, and build a foundation for long-term growth. With the right preparation, the shift to Kinetic can be a turning point in creating a more flexible and responsive ERP environment.