Time to Get Moving to Kinetic UI


+ Full Transcript

Moving from Epicor Classic UI to Kinetic UI: What You Need to Know

Moderator: Welcome and thanks for joining us today. We’re discussing why it’s time to start moving from the Epicor Classic UI to the modern Kinetic user experience.

Today’s presenters are Sam, our Epicor Practice Director, and Zach, our Epicor Tools Practice Manager.

2W Tech is an Epicor ERP partner, managed service provider, and IT solutions provider helping manufacturers and distributors modernize ERP, infrastructure, Microsoft technologies, cybersecurity, and other areas of their technology environment.

I’ll turn it over to Sam to get us started.

Why Do Epicor Users Need to Move from Classic UI to Kinetic?

Sam: The transition from Epicor Classic UI to the browser-based Kinetic user interface is an important change for Epicor customers.

Starting with Epicor Kinetic 2026.1, the traditional Smart Client and Classic forms are being retired in favor of the browser-based Kinetic experience.

That means organizations still relying on Classic UI screen customizations, custom dashboards, or other Classic-dependent Unique Business Components need to evaluate those items before moving forward with newer Kinetic releases.

For companies that have been using Epicor ERP for many years, this can be a significant project.

You may have customizations or dashboards that were created years ago but have become an important part of how employees do their jobs.

That’s why waiting until your next upgrade project to begin evaluating them can create unnecessary risk and pressure.

What Is the Difference Between Epicor Classic UI and Kinetic UI?

Zach: Classic refers to the traditional Epicor Windows-based Smart Client experience.

Classic customizations were built using the older client-side architecture and could include screen changes as well as custom code running through the client.

Kinetic uses Epicor’s modern browser-based user interface.

That gives users greater flexibility in how and where they access Epicor while also moving more business logic away from the client and toward server-side architecture.

For organizations modernizing Epicor, the goal is to reach a point where employees can perform the work they need through the browser without depending on the traditional Smart Client.

What Epicor Customizations Should You Review Before Moving to Kinetic?

Zach: You don’t necessarily have to rebuild everything in your Epicor environment.

The areas that generally need the most attention are the parts of the system that depend on the Classic user interface.

That can include:

Classic screen customizations
Custom versions of screens such as Order Entry, Quote Entry, Part Entry, Customer Entry, and other Epicor applications.

Custom dashboards
Dashboards created specifically within your Epicor environment that haven’t yet been generated or rebuilt for the Kinetic experience.

BAQ report interfaces
Custom report entry screens or interfaces that still depend on the Classic client.

Client-side custom code
Business logic that was embedded inside Classic screen customizations may need to be moved to supported server-side functionality such as Epicor Functions or BPMs.

How Do You Identify Epicor Unique Business Components?

Zach: Epicor provides tools that can help organizations identify their Unique Business Components, or UBCs.

Depending on your environment and Epicor version, the Configuration Upgrade Dashboard can provide visibility into customizations and other components within the system.

This can help identify Classic customizations, dashboards, reports, menu items, BPMs, BAQs, and other components that may need to be evaluated as part of an upgrade or Kinetic transition.

The important thing is not simply creating a list.

You need to determine which components are actually being used and which ones still matter to the business.

How Do You Prioritize Epicor Classic Customizations for Conversion?

Don’t assume every customization deserves the same priority.

Ask:

Is this customization actively used?

Which employees or departments use it?

How frequently is it used?

What business process does it support?

What happens if we remove it?

Does modern Epicor Kinetic functionality already solve the problem the customization originally addressed?

That last question is especially important.

A customization that was necessary ten years ago may no longer be necessary today.

The migration to Kinetic is a good opportunity to reduce unnecessary technical debt rather than blindly rebuilding every historical customization.

How Can Epicor Activity Tracking Help Prioritize Customizations?

Zach: Usage information can help answer some of those questions.

Epicor Activity Tracking can provide visibility into how often certain menu items and other components are being used.

That means instead of asking, “Does anybody use this screen?” you can begin identifying actual usage patterns.

You can also identify the employees using those components so you know who should participate in requirements gathering and user acceptance testing.

This can help you separate business-critical workflows from applications or customizations that may no longer need to be carried forward.

How Do You Convert Epicor Dashboards to Kinetic?

Zach: Dashboards are one of the most important areas to evaluate.

Epicor provides functionality that can generate a Kinetic application from an existing dashboard.

That gives organizations a starting point rather than requiring every dashboard to be rebuilt from scratch.

Once the Kinetic application has been generated, it can be opened and further modified in Epicor Application Studio.

Many elements of the existing dashboard can carry forward, including BAQ data views, highlighting rules, filtering, and other functionality.

The resulting Kinetic application can then be adjusted to improve the user experience or take advantage of newer Kinetic capabilities.

What Is Epicor Application Studio?

Zach: Application Studio is the primary design environment for customizing the Epicor Kinetic user experience.

If you’ve previously customized Classic screens, think of Application Studio as the modern environment where you’ll work with Kinetic applications and layers.

You can use Application Studio to modify layouts, add fields, configure buttons, create events, apply rules, and control other aspects of the user experience.

A key difference is that much of the design experience is based around configuration, events, conditions, and reusable widgets rather than embedding large amounts of custom client-side code directly into the screen.

What Are Layers in Epicor Kinetic?

Zach: Kinetic customizations are organized using layers.

A layer allows you to apply customized behavior or layout changes to an Epicor application without altering the underlying base application.

Organizations can also work with multiple layers, giving them more flexibility in how customizations are structured and maintained.

This creates a more modular approach than many organizations were accustomed to with the Classic experience.

Can Kinetic Dashboards Look Similar to Classic Dashboards?

Yes.

Some design elements may appear differently after an initial conversion, but Application Studio provides flexibility to adjust the resulting user experience.

For example, filters that initially appear through a slide-out interface can potentially be reorganized into a more traditional filter or tracker-style experience when that better supports the workflow.

The goal isn’t simply to make Kinetic look exactly like Classic.

The better question is whether the new Kinetic experience makes the workflow easier, clearer, and more efficient for employees.

Can You Add Buttons and Actions to Epicor Kinetic Dashboards?

Zach: Yes.

Application Studio provides capabilities for adding buttons and triggering events from the interface.

That means a dashboard doesn’t have to remain a passive visualization.

Users can potentially launch reports, perform actions, interact with data, or trigger other supported workflows directly from the application.

This is one reason we want customers to see the Kinetic transition as more than a forced migration.

It’s an opportunity to improve workflows that may have been built years ago.

How Do You Convert BAQ Reports to the Epicor Kinetic UI?

Zach: BAQ reports are another area organizations should review.

Epicor provides functionality to generate a Kinetic application for BAQ report interfaces.

Existing options, filters, and report parameters can then be presented through the Kinetic experience.

Once generated, the report application can also be brought into Application Studio if additional customization is required.

In some situations, you may not need to do anything beyond generating and validating the Kinetic application.

Can You Customize Kinetic BAQ Report Behavior?

Zach: Yes.

Application Studio events can be used to configure behavior inside the Kinetic application.

For example, perhaps you have a BAQ report that’s almost always exported to Excel.

Rather than requiring the user to select Excel every time, you could configure the application so the appropriate output format is automatically selected when the screen loads.

Many of these changes can be created using event-driven configuration and widgets instead of traditional client-side programming.

Do You Need to Know How to Code to Use Epicor Application Studio?

Not for everything.

Many Application Studio changes can be accomplished using visual configuration, events, widgets, data views, row updates, rules, and other low-code functionality.

More complex workflows can still require technical knowledge, particularly when you’re recreating sophisticated custom business logic.

But straightforward UI changes don’t necessarily require someone to write traditional client-side code.

What Happens to Custom C# Code When Moving from Classic to Kinetic?

Zach: This is where organizations need to spend more time.

Classic screen customizations may contain substantial client-side C# code.

That code doesn’t simply become browser-compatible because the screen is moving to Kinetic.

Start by understanding what the code actually accomplishes.

Then determine whether that logic belongs in an Epicor Function, BPM, Application Studio event, or another supported architecture.

In many cases, business logic that historically lived in the UI may be better placed on the server anyway.

What Are Epicor Functions and BPMs?

Epicor Functions and Business Process Management, or BPM, provide server-side options for implementing business logic.

BPMs are useful for logic tied to particular business process events.

Epicor Functions provide reusable server-side logic that can be called from other parts of the application.

A Kinetic screen can trigger a Function from an Application Studio event, allowing the browser interface to initiate business logic without embedding that logic directly in the client.

That’s a much more important architectural change than simply making the new screen look like the old screen.

Do Existing Epicor BPMs Need to Be Rewritten for Kinetic?

Zach: Generally, BPMs aren’t the primary concern in the Classic-to-Kinetic UI transition because BPMs already operate on the server side.

As with any Epicor upgrade, some validation or remediation may still be required depending on changes to business objects, fields, methods, or surrounding functionality.

But the Kinetic UI transition doesn’t automatically mean hundreds of existing server-side BPMs need to be rewritten from scratch.

Do Existing Epicor SSRS Reports Need to Be Rebuilt for Kinetic?

Existing report definitions don’t automatically need to be rebuilt simply because you’re changing user interfaces.

The report interface or launch experience may require attention, but the underlying report itself may continue to work.

Again, normal upgrade validation still applies.

Why Is Moving to Kinetic an Opportunity to Reduce Epicor Technical Debt?

Zach: Don’t just replicate every customization.

Ask why it exists.

If Order Entry takes minutes to save because years of custom logic have accumulated around it, now is a good time to understand what’s happening.

Maybe newer Kinetic functionality already solves some of those problems.

Maybe employees aren’t using parts of the customization anymore.

Maybe business logic belongs on the server instead of inside the user interface.

Moving to Kinetic provides an opportunity to simplify the environment rather than automatically carrying every historical decision forward.

What Is the Best Epicor Classic-to-Kinetic Migration Strategy?

A practical transition plan looks like this:

1. Inventory the Classic components.
Identify screen customizations, dashboards, BAQ reports, menu items, and other Classic-dependent interfaces.

2. Track usage.
Use Epicor Activity Tracking and input from business users to determine which components are actually being used.

3. Prioritize by business impact.
Start with the workflows employees rely on most heavily.

4. Eliminate what you don’t need.
Retire unused customizations and evaluate whether newer Kinetic functionality can replace older custom development.

5. Convert what Epicor can convert.
Generate Kinetic applications for dashboards and BAQ reports when appropriate.

6. Rebuild required UI customizations.
Use Application Studio layers, events, controls, rules, and widgets.

7. Move business logic server-side when appropriate.
Evaluate BPMs and Epicor Functions instead of recreating unnecessary client-side code.

8. Test in the browser.
Test the experience employees will actually use, not only the Kinetic screens running inside the old Smart Client.

9. Test with real users.
Have the employees who depend on the workflow validate the Kinetic version.

10. Document and deploy.
Update training materials, SOPs, technical documentation, and your upgrade plan before moving the changes into production.

Epicor Kinetic UI Transition: Webinar Q&A

Does Every Epicor Classic Form Have a Kinetic Equivalent?

Sam: The answer can depend on your Epicor release and the specific application you’re asking about.

If you’re unsure whether a Kinetic version of a particular application exists, review the Epicor menu configuration for your release and verify the available browser application.

Organizations on older releases should also recognize that Kinetic capabilities have continued to mature substantially over time.

Why Should You Upgrade Epicor Before Starting a Major Kinetic UI Project?

Epicor’s browser experience and development tools have improved significantly across Kinetic releases.

If you’re running a much older Epicor version, moving relatively current before investing heavily in customization uplift can give your team access to a more mature user interface and newer Application Studio capabilities.

The exact upgrade path depends on your environment, so verify supported versions and infrastructure requirements before selecting the target release.

How Do You Export Large Kinetic Datasets to Excel?

Very large datasets can behave differently from smaller interactive grids because of pagination and performance considerations.

If employees regularly need thousands or tens of thousands of rows, reconsider whether manually copying or exporting from the user interface is the best design.

BAQs, OData, Power BI, dedicated reports, and other reporting or integration options may provide a better solution for large datasets.

Design the workflow around what users actually need to accomplish rather than trying to turn every Kinetic grid into a bulk data-export tool.

Which Browser Should You Use with Epicor Kinetic?

Use a current browser supported by your Epicor Kinetic release and organizational IT policies.

Browser-based testing is important because that’s the experience organizations are ultimately moving toward.

If your employees primarily use Microsoft Edge, for example, test your applications, dashboards, and workflows directly in Edge rather than assuming that working through the Smart Client represents the final user experience.

Does Epicor 10 Have an End-of-Support Date?

Epicor support availability depends on the specific release and its lifecycle status rather than the broad label “Epicor 10.”

Older releases may remain under sustaining support with more limited fixes and resources available than currently supported Kinetic releases.

Organizations should review Epicor’s current lifecycle documentation for the specific release they’re running rather than assuming all Epicor 10 versions have the same support status.

Is Application Studio Easier Than Classic Epicor Customization Tools?

Sam: It’s different.

Application Studio provides modern visual and low-code tooling, but more complex Epicor customization still requires knowledge of the ERP, its data structures, events, processes, and architecture.

Straightforward personalization and UI adjustments may become easier for more users, while sophisticated business applications can still require specialized Epicor expertise.

What’s Different about Epicor Menu Maintenance in Kinetic?

Zach: The fundamental purpose is similar, but Kinetic introduces some differences around browser applications, application layers, search capabilities, and security.

Kinetic also lets organizations apply multiple custom layers to an application, giving administrators greater flexibility in how functionality is assigned.

Menu-related administrative and security capabilities can also be separated to provide more appropriate access control.

Why Is Kinetic More Secure Than Classic Client-Side Customization?

Zach: One architectural advantage is moving critical business logic away from client-side screen scripts.

Instead of embedding powerful custom code directly inside a user’s screen, organizations can use more controlled server-side functionality such as BPMs and Epicor Functions.

Application Studio then becomes responsible primarily for the user experience and interaction with those supported business services.

This creates a cleaner separation between the user interface and critical business logic.

What Replaces Client Trace in Epicor Kinetic?

Zach: Developers have several diagnostic options in the Kinetic browser experience.

Kinetic includes debugging information that can help identify application events and behavior.

Browser developer tools can also provide valuable information about network activity, calls to Epicor services, requests, responses, and payloads.

For users accustomed to Classic Client Trace, the browser’s network tools become an important part of troubleshooting and development.

Can You Upgrade an Epicor Test Environment First?

Sam: Yes, and testing in a separate environment is a valuable way to begin preparing.

The exact technical steps depend on your current Epicor version, hosting model, operating system, SQL Server version, .NET requirements, licensing, and other infrastructure considerations.

An older on-premises environment may require more infrastructure preparation than an environment already running a relatively current Kinetic release.

How Do You Limit Access to Epicor Application Studio?

Zach: Development and customization privileges should be restricted to the users who actually need them.

Administrators can use Epicor’s customization privileges and security settings to control access to development functionality such as Application Studio.

That’s particularly important in production environments where most employees should consume configured applications rather than modify them.

What Can Normal Users Personalize in Epicor Kinetic?

Kinetic personalization can help users simplify their own experience without requiring a formal development project.

For example, users with appropriate permissions may be able to hide panels they don’t need or adjust which columns appear in grid views.

This is another reason not to automatically treat every user-experience request as a customization.

If one employee simply doesn’t need several fields or panels, personalization may be a better answer than creating another company-wide custom layer.

Final Takeaway: Don’t Wait to Inventory Your Epicor Classic UI Dependencies

The biggest mistake organizations can make is assuming the move to Kinetic is simply a visual redesign that can be dealt with during the next upgrade.

Start now by understanding what your business actually depends on.

Inventory the Classic components. Measure usage. Talk to users. Retire what isn’t needed. Convert what can be converted automatically. Rebuild business-critical functionality with modern Epicor tools. Then test it in the browser with the people who actually perform the work.

The goal isn’t to recreate your old Epicor environment pixel for pixel.

The goal is to enter the Kinetic era with a cleaner, more supportable ERP environment that still gives employees the functionality they need.

Moderator: Thanks, everybody, for joining us today.