Upgrade Path Planner
Epicor Kinetic upgrade path planner: Epicor ERP 9 and 10 to Kinetic
Pick the Epicor release you run today (Vantage, Epicor 9, Epicor ERP 10.x or a Kinetic release) and the Kinetic release or Epicor Cloud you are moving to. The planner lays out the route (database migration or upgrade in the Administration Console, Conversion Workbench, BPM recompile, classic to browser conversion), what changed in every release you cross, and a risk score, effort range and regression test plan sized to your customizations, integrations and reports.
Free, runs in your browser, no sign-in needed. Release data checked 2026-10 against 33 cited sources.
In-place database upgrade: install the target release, upgrade the database in the Administration Console and run the Conversion Workbench. The bigger job is moving classic customizations to Application Studio, since 2025.2 is the final release supporting the Smart Client.
- 1PreparationDocumented
Restore production into a separate test environment
Back up production, restore it to a test database on the target release and run the full upgrade there first, including the Conversion Workbench, so you know the run time and the errors before cutover. Community upgrade reports follow this pattern, and the Administration Console lets you upgrade one registered database and application server at a time.
- 2PreparationDocumented
Pick the target release and read its upgrade documentation
From May 2026 Kinetic moved from two releases a year to a monthly CI/CD cadence (2026.100 onward), and Epicor has announced 2028.1 (January 2028) as the final on-premises release with new features. Choose a target with that roadmap in mind, check the ERP build, ICE and .NET versions it needs, and confirm the supported upgrade path from your release in the release documentation on EpicWeb.
- 3PreparationDocumented
Inventory every customization layer and extension
List classic screen customizations and personalizations, Application Studio layers, BPM method and data directives, Epicor Functions, BAQs and dashboards, UD fields and UD tables, custom SSRS and Crystal reports, Service Connect workflows and external programs that call the REST services or the database. Drop what is no longer used before you convert anything; Epicor's own browser transition guidance starts with this review.
- 4UpgradeDocumented
Install the target release and stand up the application server
Install the base release, then the latest update for it (for example base 11.2.100.0 before update .26). Kinetic 2022.1 and later run the server on ASP.NET Core (.NET 6 for 2022 and 2023, .NET 8 for 2024 and 2025, .NET 10 for 2026.100), so the application server host needs the matching runtime and hosting bundle.
- 5UpgradeDocumented
Upgrade the database in the Administration Console
Register the restored database in the Epicor Administration Console, run Update Common Database where prompted, then upgrade the database to the target ERP build. An ICE version mismatch error at this point usually means the common database or the application server is still registered against the old deployment.
Epicor Administration ConsoleSource 31 - 6UpgradeDocumented
Run the Conversion Workbench to completion
After the database upgrade, the Conversion Workbench runs the release's data and metadata conversions (BAQ, BPM, security and UI tasks). Every task must finish before users log in; tasks that end Complete with Errors need a fix and a rerun. On upgrades from 10.2 to 2023.1 the EnableKineticUI task switches screens to the Kinetic UI and cannot be skipped, so plan the UI change with the upgrade rather than after it.
- 7ConversionDocumented
Recompile and test every BPM directive and Epicor Function
Directives and Functions compile against the new server framework. 2026.100 moved the data layer to EF Core on .NET 10; community reports show BPMs that only needed the compatibility checkbox, BPMs that failed to compile on date conditions, and DbUpdateConcurrencyException errors in custom code that updates the same row twice. Open, save and run each directive and Function on the test copy.
- 8ConversionDocumented
Rebuild classic screen customizations as Application Studio layers
The Smart Client (classic forms) is retired after 2025.2, which Epicor names as the final release supporting it; 2026.100 (May 2026) is browser only. Classic C# screen customizations do not run in the browser. Epicor points to the Analyzer, the Configuration Customization Dashboard and Application Studio for the conversion; in practice teams re-create each layer by hand and publish it through Menu Maintenance with Program Type Kinetic.
- 9ConversionDocumented
Move DMT and other desktop utilities to the Power Tools Client
With the Smart Client gone, the Data Management Tool (DMT), Functions, Advanced Print Routing and SDK Designer are reached through the Power Tools Client, a free EpicWeb download. Licences for those tools are still required. Re-point scheduled DMT loads and any .NET programs that referenced client assemblies.
- 10ConversionDocumented
Decide the route for Crystal and custom SSRS reports
Crystal report styles still run on-premises in Kinetic but are not an option in the Epicor Cloud, and Epicor does not support Crystal. Count each custom report and choose keep, rewrite in SSRS, or replace with a BAQ and dashboard. Re-test custom SSRS report data definitions against the new release.
- 11ConversionDocumented
Repackage Solution Workbench solutions as .zip
Solution Workbench in current releases installs .zip solutions only; .cab solutions must be extracted and re-zipped. Rebuild the solution packages you use to move BAQs, BPMs, layers and reports between environments, and test an install on the upgraded test copy.
Solution WorkbenchSource 27 - 12ConversionDocumented
Re-test REST callers, API keys and Service Connect workflows
REST v2 calls need an API key (API key maintenance arrived in 10.2.400). Run every external caller against the upgraded test system and check the OData service names and custom methods it uses. Service Connect workflows that reference client .NET assemblies need checking after the Smart Client retirement.
- 13PreparationDocumented
Plan browser training through the Epicor Learning Center
Epicor names workforce adoption as the main hurdle in the browser move. The Epicor Learning Center (ELC) has role-based learning paths and courses; essential courses are free and the full catalog needs full access. Schedule training before cutover, not after.
- 14CutoverVerify with vendor
Rehearse, freeze and cut over
Time the full run (database upgrade plus Conversion Workbench) on production-sized data at least once, agree a freeze window, close or post open journal groups and batches, then upgrade, run the conversions and reconcile key balances before users return.
This is a planning model. Before you commit a budget or a date, have an engineer check the path, the effort drivers and the test scope.
How to use the Kinetic upgrade planner
- 1
Pick your releases
Choose your current Epicor release and the target: a Kinetic release on-premises or hosted, or Kinetic in the Epicor Cloud.
- 2
Describe your landscape
Enter counts for customizations, integrations, file and EDI interfaces, custom reports, data size, users and sites, then tick the modules and integrations you use.
- 3
Read the path and the drivers
Review each step with its source, the changes in every release you cross, and the drivers behind the risk score and effort range.
- 4
Export the test plan
Download the regression plan as Excel, Word, PDF or CSV. Critical tests are flagged where your path changes that area.
- 5
Save or get it reviewed
Save the plan to your Netray account to reopen later, or send it to an engineer for a written review.
Questions
What is Epicor Kinetic, and is it the same as Epicor ERP 10?
Kinetic is Epicor's ERP for discrete and make-to-order manufacturers, and the current name of the product previously sold as Epicor ERP 10. Epicor announced the rename in April 2021, with Kinetic planned for general availability on June 10, 2021. Releases are named by year (2021.1 to 2025.2, then 2026.100), with internal ERP builds 11.1.x to 12.2.x. It runs on-premises or in the Epicor Cloud and is licensed by concurrent users.
What is the latest version of Epicor Kinetic?
Kinetic 2026.100, announced in May 2026 (ERP build 12.2.100). From that release Epicor moved Kinetic from two releases a year to a monthly CI/CD cadence. Updates arrive as 2026.100.x builds; cloud customers get them on Epicor's schedule and on-premises customers apply them.
Can I upgrade from Epicor ERP 10.2 directly to Kinetic?
Yes. Community upgrade reports show 10.2.x databases upgraded directly to 2021.2, 2023.1 and 2024.1 by installing the target release, upgrading the database in the Epicor Administration Console and running the Conversion Workbench. The harder part is the user interface: from 10.2 to 2023.1 the EnableKineticUI conversion task must run, and classic customizations must be rebuilt in Application Studio because 2025.2 is the final release supporting the Smart Client.
How do I upgrade from Epicor 9 or Vantage?
It is a database migration, not an upgrade. The Migrate Epicor Database step in the Administration Console moves an Epicor 9.05 database (Progress or SQL) into the SQL Server schema; community reports start from 9.05.702A and recommend running the data scrub scripts first. BAQs with summary tables, Crystal reports and BPM custom code need rework. For Vantage 8, confirm the route with Epicor; Epicor also sells a migration service.
What happens to classic customizations and the Smart Client?
Epicor retired the Kinetic Smart Client (classic forms) after 2025.2, which Epicor names as the final release supporting it; from 2026.100 (May 2026) the browser is the only interface. Classic C# screen customizations do not run in the browser. Epicor points to the Analyzer, the Configuration Customization Dashboard and Application Studio for conversion, and community experience is that each layer is re-created by hand and published on a Kinetic menu item. Count these separately in the planner.
Is on-premises Epicor Kinetic ending?
Epicor announced in January 2026 that release 2028.1, scheduled for January 2028, will be the final on-premises release with new features. Active Support for 2028.1 on-premises continues through December 31, 2029, after which on-premises customers move to Sustaining Support. Later innovation is delivered in the Epicor Cloud. SaaS customers are not affected. Use the planner's cloud target to size that move.
What do Epicor Prism, Epicor CPQ and Epicor Data Analytics change in an upgrade?
Epicor Prism, launched in January 2025, is Epicor's AI agent layer for Kinetic, with natural-language queries from 2025.1 and supplier RFQ automation in 2025.2. Epicor CPQ is the visual 2D, 3D and AR configure-price-quote product, and Epicor Data Analytics (EDA) is the analytics layer on ERP data models. Each is a connected application: re-test its integration after the upgrade and confirm which releases it needs.
Where do we get Epicor training and certification for the new release?
Through the Epicor Learning Center (ELC), which has role-based learning paths and courses for Kinetic; essential courses are free and the full catalog needs full access. Module certification exams (for example Sales Management, Purchase Management and Application Studio) are multiple choice and prepared through ELC courses and exam guides. Instructor-led training comes from Epicor Professional Services.
Who can do an Epicor upgrade?
Epicor Professional Services offers upgrades and migrations, and the Ascend with Epicor program covers on-premises to cloud moves. Epicor also lists authorized channel partners by type: reseller, service and referral partners. Many on-premises customers upgrade in-house; use the planner's effort range and risk drivers to decide what to keep internal.
Sources
- Epicor: Kinetic product page
- Epicor: Kinetic tools and technology
- Epicor: what's new in Kinetic
- Epicor blog: Release 2026.100 of Kinetic (May 2026)
- Epicor blog: Release 2025.2 of Kinetic
- Epicor blog: Release 2025.1 of Epicor Kinetic
- Epicor blog: Kinetic browser user experience
- Epicor news: Epicor Prism vertical AI agents (January 2025)
- Epicor news: expanded Ascend program and 90-day cloud go-lives (May 2026)
- Epicor: Epicor Learning
- Epicor: Epicor Learning Center
- Epicor: Epicor CPQ
- Epicor: channel partners
- Epicor: Professional Services
- EpiUsers: Kinetic and ERP platform version matrix
- EpiUsers: Kinetic is the new name for Epicor ERP (Epicor customer notice, April 2021)
- EpiUsers: on-premises development ends in 2028 (Epicor customer letter, January 2026)
- EpiUsers: classic sunset at 2026.1 (Epicor feature sunset notice)
- EpiUsers: classic to Kinetic upgrade workflow
- EpiUsers: Conversion Workbench EnableKineticUI task
- EpiUsers: E9 to E10 migration cleanup scripts
- EpiUsers: migrate E9 to E10
- EpiUsers: Epicor 9.05.700 to 10.1 BAQs
- EpiUsers: upgrading to 11.2.100 (11.2.300 is 2023.1)
- EpiUsers: 2026.100 upgrade and BPMs
- EpiUsers: 2026.100 EF Core
- EpiUsers: Solution Workbench .zip solutions only
- EpiUsers: generating a REST API key
- EpiUsers: Crystal Reports on Kinetic 11
- EpiUsers: Vantage 8 to E10 Crystal reports
- EpiUsers: Administration Console database upgrade ICE version error
- EpiUsers: Epicor 10.2.200 to Kinetic 11.3.100 (2024.1) upgrade
- EpiUsers: Epicor 10 multi-tenant cloud limitations
Steps marked Verify with vendor are planning inferences, not vendor statements. Effort coefficients are Netray planning assumptions and are shown in full in the Effort tab.