CIO briefingEpicor KineticReleases / Upgrades / Cloud and On-Prem

Epicor Kinetic Update Schedule: Release Cadence, Versions and Upgrade Planning

Question
epicor kinetic update schedule

Also searched as

  • epicor kinetic release schedule
  • epicor kinetic version numbering
  • epicor kinetic cloud vs on-prem update

Short answer

Epicor Kinetic ships versioned releases in a year-and-number pattern with point releases in between, and the cloud service applies updates on a vendor-managed schedule while on-premises customers choose when to upgrade. Confirm exact dates and the supported-version policy on the Epicor support site, then plan a regression-tested upgrade at a pace your customizations allow.

Applies to: Epicor Kinetic cloud (multi-tenant and single-tenant) and on-premises; exact dates and support windows change, so verify them with Epicor before committing a project plan

How to plan around Kinetic updates

  1. 1Find your current version in the Kinetic client (Help, About) or the server and database information, and write down the full version string.
  2. 2Read the release notes and the supported-versions policy on the Epicor support portal for the target and your current release.
  3. 3Ask whether your tenancy is multi-tenant cloud, single-tenant cloud or on-premises, since this decides who controls the update date.
  4. 4Inventory customizations: Application Studio layers, BPM directives, Epicor Functions, BAQs, reports and integrations.
  5. 5Upgrade a test environment copied from production, and run regression tests on the processes that matter, such as job entry, receiving and invoicing.
  6. 6Review changes to REST APIs, deprecated features and security or browser requirements, and adjust integrations.
  7. 7Schedule the production change outside month end, train users on interface changes, and keep a rollback plan.

How versions are named

Kinetic uses a release name based on the year and a number, with build numbers on the end for patches. Earlier Epicor ERP 10 versions used a three-part number. The release name tells you the feature level, and the build tells you the patch level, so support cases should always quote the full string.

Epicor has historically published major releases a small number of times per year, with more frequent cumulative patch releases. Because the cadence has changed over the years, treat any fixed calendar you read on a blog as dated, and check the current policy.

Cloud versus on-premises

In a multi-tenant cloud service, Epicor schedules updates for all tenants, and customers get notice and a window to test in a pilot environment. The benefit is less upgrade work, and the cost is less control over timing and a need to keep customizations compatible with the shared platform.

On-premises and some single-tenant arrangements let you pick the release and the date, but you also carry the server, SQL Server, Windows and IIS work, and you must stay within the supported window to receive fixes. Falling several versions behind turns a routine update into a project.

What to test

Customizations are the main risk. Application Studio layers, BPM directives and Epicor Functions may reference fields or methods that change. Run every critical path with customizations enabled, and compare the output of key reports and BAQs between old and new versions.

Integrations are the second risk. Check REST v2 endpoints, API keys, authentication flows, EDI, and connectors to other systems. For the cost of a few days of testing, you avoid a production incident at the first close after the update.

Try it here, free

Epicor Upgrade Regression Test Effort Calculator

Open full tool

Size the regression testing for an Epicor upgrade from test cases, failure rate, fix time and tester count.

Common pitfalls

  • !Taking a blog's release calendar as current; check Epicor's official policy.
  • !Skipping the test upgrade from a recent production copy.
  • !Not documenting customizations, so nobody knows what to retest.
  • !Upgrading in the last week of a financial period.
  • !Assuming cloud updates need no testing; customizations and integrations still break.

How an ERP-grounded AI assistant handles this

An assistant grounded in your own customization inventory, BAQs and BPM definitions can list which ones touch tables or methods affected by a release note, and draft a regression checklist from your actual usage. SyteRay-style accelerators exist for SyteLine; for Epicor, ERPray reads the live system read-only and can show what is in use so testing focuses on it.

See ERPray

Frequently asked questions

How often does Epicor Kinetic release updates?

Epicor publishes major releases a few times a year and more frequent cumulative patches, but the cadence has changed over time. Check the current release policy on the Epicor support site rather than relying on third-party calendars.

Do cloud customers control when Kinetic updates?

In multi-tenant cloud Epicor schedules updates for the service, and customers test in a pilot environment during a notice window. On-premises and some single-tenant setups give more control over the date.

How do I find my Kinetic version?

Use Help and About in the Kinetic client, which shows the application and server versions. Quote the full version and build when raising support cases.

How long can I stay on an older Kinetic release?

Epicor defines a support window per release. Staying outside it means no fixes and harder upgrades later, so check the policy and plan upgrades within the window.

Related

How-to

Preserving Customizations When Upgrading to Epicor Kinetic

Epicor Kinetic's web UI does not simply inherit classic smart-client customizations - most need to go through the Update Customization / Application Studio conversion process, and some WinForms-specific customizations cannot convert directly and must be rebuilt in the Kinetic designer. Plan the upgrade as a customization inventory and rework project, not a single technical cutover step.

How-to

Epicor Upgrade Services: Moving From 10.2 to Kinetic Without Surprises

An Epicor 10.2 to Kinetic upgrade is normally done into a new environment: you copy your production database, run the upgrade there, test, and cut over, while 10.2 stays live. Running both in parallel is routine. The work that costs time is customizations, BPMs, reports and integrations, not the database step. Use Epicor or a partner for the upgrade if you have heavy customization; a vanilla system can be done in-house.

How-to

Convert Epicor Classic Dashboards to Kinetic

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.

Error fix

Fixing Epicor BusinessObjectException: BPM Directive Errors

A BusinessObjectException that says "A Business Process Management (BPM) directive has raised the following error" means a directive on that business object stopped the transaction, either deliberately via a Raise Exception widget or accidentally via an unhandled .NET error in Custom Code. Expand the InnerException on the error dialog to see the real message and the directive name, then open BPM Designer for that object and method to find the widget that fired.

How-to

Fixing a Slow Epicor BAQ (Business Activity Query)

A slow BAQ in Epicor is usually caused by unindexed join columns, a subquery or calculated field forcing a table scan, or the BAQ pulling far more rows than the dashboard actually displays before filtering client-side. Fix it by reading the SQL Server execution plan Epicor generates, moving filters into the BAQ criteria instead of the dashboard filter panel, and replacing subqueries with joins where possible.

How-to

Epicor MRP Runs but Generates No Suggestions

When Epicor's MRP process completes without a job or purchase suggestion for a part you expect one for, the cause is almost always the part's own configuration (Part Class Type, Make Direct, Non-MRP flag, planning Time Fence) or the demand not being linked in a way MRP recognizes, not a defect in the MRP engine. Work through the part's Planning tab, its safety stock and lead time setup, and the demand source (sales order line status, job material requirement) before assuming the run itself failed.

AI for ERP

AI for Epicor Kinetic, Beyond What Prism Covers

Add AI to Epicor Kinetic beyond Prism: private LLM over BAQs, BPM data, and REST v2, on-prem or private cloud, with honest guidance on when Prism already covers you.

AI for ERP

Private AI for Epicor Kinetic Cloud, Outside the Multi-Tenant Boundary

Run a private LLM on Epicor Kinetic private cloud or Kinetic Cloud data via BAQs, REST v2 and Data Fabric, keeping sensitive manufacturing data off shared AI.

Stuck on Epicor Kinetic?

Talk to engineers who work inside Epicor Kinetic every week, and who build private AI that answers these questions from your own ERP data.

Talk to an ERP engineerBrowse ERP Help
All ERP Help articles

Keep exploring

Free tools

ERP fixes and how-tos

Guides

AI on your ERP

Integrations

Comparisons

Software

TermsEpicor BPM (Business Process Management)Epicor BAQ (Business Activity Query)