# Convert Epicor Classic Dashboards to Kinetic

> Source: https://netray.co/erp-help/epicor-convert-classic-dashboard-to-kinetic
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

Classic dashboards built on BAQs convert most easily to Kinetic because the query survives and only the presentation changes. Dashboards with custom code, complex layouts or tracker panels often need to be rebuilt in Application Studio. Inventory them, convert in a test environment, then verify data, filters, actions and security one by one.

## Kind

how-to

## System

epicor

## Erp

Epicor Kinetic

## Module

Upgrade / Dashboards

## Query

epicor convert classic dashboard to kinetic

## Alternate Queries

- epicor turn classic dashboard to kinetic
- epicor configuration upgrade dashboard
- epicor classic dashboard kinetic upgrade

## Applies To

Epicor upgrades from Classic (Smart Client) dashboards to Kinetic; conversion tooling and coverage vary by target release

## Steps

### How to move Classic dashboards to Kinetic

**Items:**

- List every Classic dashboard in use: who opens it, how often, and which BAQs and custom code it relies on. Retire the ones nobody uses.
- In a test copy of the upgraded environment, check your release for a dashboard conversion utility and run it against a small set first.
- Open each converted dashboard in Application Studio and compare the grids, filters, parameters and actions against the Classic original.
- Rebuild panels that did not convert: complex layouts, custom code, charts and tracker views, using the same BAQ as the data source.
- Re-test any actions that open other programs, such as launching Order Entry from a row, and the parameter passing to them.
- Check security: menu placement, dashboard security and BAQ access for each role.
- Compare row counts and key totals between Classic and Kinetic for a known date range.
- Roll out in groups and keep the Classic version available until users sign off.

## Sections

### What usually converts and what does not

**Body:**

The data layer is the stable part. A BAQ is the same object in both worlds, so a dashboard that is a grid over a BAQ with a few filters generally converts with little rework. Layout is the unstable part, because Kinetic uses a different layout model and component set.

Expect manual work for dashboards that embed custom code, use many nested panels, rely on tracker or tree views, or carry chart settings. These are rebuilt rather than converted, and a rebuild is also a good time to simplify.

### Treat it as a clean-up

**Body:**

Most long-lived Epicor environments hold dashboards no one opens, duplicated BAQs and queries with hardcoded dates. Use the conversion as the moment to retire them. Fewer dashboards means less to test and less to maintain after the upgrade.

Where several dashboards differ only by a filter, consider one Kinetic dashboard with parameters. That reduces the maintenance surface and makes future changes cheaper.

### Verification checklist

**Body:**

For each converted dashboard check four things: the data matches, the filters and parameters work, the row actions open the right program with the right key, and the right roles can see it. Record the result so the sign-off is evidence, not memory.

Run the check with a restricted user as well as an administrator. Security differences are the most common surprise after a conversion.

## Pitfalls

- Assuming a converted dashboard is finished because it opens.
- Converting dashboards nobody uses.
- Skipping testing with restricted roles.
- Forgetting that custom code in Classic does not carry over automatically.
- Moving everything at once instead of in small groups.

## Ai Angle

An assistant that reads your dashboard and BAQ definitions can build the inventory, flag which queries are shared, and compare Classic and Kinetic output for the same date range. That inventory is useful before an upgrade, and with a private deployment none of it leaves your network.

## Faq

### Do Classic dashboards work in Kinetic automatically?

**Answer:** Not fully. The BAQ queries remain, but the presentation layer differs, so some dashboards convert with a tool and others must be rebuilt in Application Studio. Plan time for testing and rework.

### Which dashboards must be rebuilt?

**Answer:** Those with custom code, complex layouts, charts, trackers or tree views typically need rebuilding. Simple BAQ grids with filters convert most easily.

### Should I keep Classic dashboards after the upgrade?

**Answer:** Keep the definitions until users sign off the Kinetic versions, then retire them. Keep a record of what was retired.

### How do I verify a converted dashboard?

**Answer:** Compare row counts and totals for a known range, test filters and actions, and run it as a restricted user. Record results per dashboard.

## Search terms

epicor convert classic dashboard to kinetic, epicor classic dashboard kinetic, epicor upgrade dashboards, epicor dashboard conversion, epicor configuration upgrade dashboard, epicor kinetic upgrade, epicor dashboard application studio, epicor classic to kinetic

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json