How-toEpicor KineticUpgrade / Deployment

Epicor Upgrade Services: Moving From 10.2 to Kinetic Without Surprises

Question
epicor upgrade services

Also searched as

  • upgrade services epicor
  • epicor 10.2 and kinetic run parallel
  • epicor 1099 conversion us kinetic upgrade
  • epicor kinetic client installer

Short answer

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.

Applies to: Epicor ERP 10.2.x moving to a current Kinetic release, on-prem or private cloud. Cloud tenants are upgraded by Epicor on their own schedule.

A safe upgrade sequence

  1. 1Inventory what you have: customizations, BPMs, Epicor Functions, BAQs, SSRS and Crystal reports, EDI, integrations and Dashboards. Note which are in use.
  2. 2Read the current release notes and the upgrade guide for your source and target versions. Confirm your 10.2 build is on a supported upgrade path and apply the required interim version first if not.
  3. 3Build the new server environment (application, database and web tiers) next to production. Do not upgrade in place.
  4. 4Restore a copy of the production database to the new environment and run the upgrade there. Time the run so you can plan the cutover window.
  5. 5Test by role: quote to cash, procure to pay, job entry to shipping, month-end close and the US 1099 forms if you file them. Compare outputs with 10.2 for the same data.
  6. 6Rebuild or convert customizations and BPMs that do not work, then deploy clients (browser or Windows) to a pilot group.
  7. 7Cut over: freeze 10.2, take a final backup, repeat the upgrade run with a final copy, validate, and repoint users.
  8. 8Keep 10.2 read-only for a defined period so people can compare history.

Running 10.2 and Kinetic in parallel

Because you upgrade a copy, the original production database never changes. That gives you a genuine parallel run: users keep working in 10.2 while a test group validates Kinetic against a snapshot.

Parallel does not mean two live systems for the same transactions. Pick a cutover date. Data entered in 10.2 after your snapshot is not in the Kinetic copy unless you repeat the upgrade with a fresh backup, which is exactly what the final cutover run does.

Use the practice upgrades to measure duration, find failing data conversions and train people. Most projects do at least two or three trial runs before the real one.

1099 and other compliance checks

For US companies, treat 1099 reporting as an explicit test case. Epicor has changed the 1099 forms and boxes over several releases, so verify vendor 1099 setup, the AP payment types that feed 1099 amounts and the year-end form output against the release notes for your target version.

Run the 1099 report on the converted data and compare totals to the same period in 10.2. A difference is almost always a vendor flag or payment-type mapping, not lost data.

Apply the same discipline to tax, intrastat or e-invoicing features you use. Anything with a legal filing deserves its own test script.

Client installer and deployment

Kinetic is primarily a browser application, so most users need no installation. The Windows client, where you still use it, is deployed from the server client folder or packaged installer; plan how you will push it with your normal desktop tooling.

Decide early which users stay on the Windows client (some customizations, certain tools) and which move to the browser, because customizations behave differently between the two. Application Studio layers are the Kinetic way to rebuild UI changes.

Test the client against your proxy, SSO and certificate setup. Many go-live problems are infrastructure, not Epicor.

DIY or partner

A lightly customized system with an experienced Epicor admin can be upgraded in-house, given enough trial runs. The risk grows with the number of customizations, integrations and bespoke reports.

Epicor and its partners offer upgrade services that handle the database upgrade, customization conversion and testing. Ask for fixed scope, the number of trial runs included, and who owns the customization rewrite. Typical project length ranges from a few weeks for simple systems to several months for heavily modified ones.

Try it here, free

Epicor Kinetic Upgrade Checklist

Open full tool

A phase-by-phase upgrade checklist covering inventory, testing, integrations, cutover and rollback for Epicor Kinetic.

Common pitfalls

  • !Upgrading production in place; there is no fast rollback.
  • !Discovering customizations at go-live because no one inventoried them.
  • !Testing with a stale database copy so recent master data is missing.
  • !Skipping 1099 or other year-end forms until the filing season.
  • !Assuming the Windows client customizations carry over to the browser unchanged.

How an ERP-grounded AI assistant handles this

Before an upgrade, a grounded assistant can list which customizations, BPMs and BAQs touch a given table and flag the ones likely to break, using your exported metadata. Netray runs that analysis on your own hardware so source code and schema never leave your network.

See ERPray

Frequently asked questions

Can Epicor 10.2 and Kinetic run in parallel?

Yes, as separate environments. You upgrade a copy of the 10.2 database to Kinetic and test while 10.2 remains live. You do not share one live database between them; you cut over on a chosen date.

Do I need Epicor upgrade services or can I do it myself?

Either can work. Simple systems with experienced admins are often upgraded in-house. Heavy customization, many integrations or limited admin time usually justify Epicor or partner services for the conversion and testing.

How long does a 10.2 to Kinetic upgrade take?

The database upgrade run itself may take hours. The project, including testing and customization conversion, typically runs from a few weeks to several months depending on complexity.

Do I need to install a client for Kinetic?

Not for the browser experience. If you keep the Windows client, deploy it from the packaged installer or client folder using your usual desktop software distribution.

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.

Advanced

Epicor Application Studio: understanding customization layers

Kinetic UI is built in layers loaded in order - Base (Epicor-delivered), Customization (Application Studio, company/layer-wide), Personalization (user- or role-specific, applied on top), and optionally Extended (packaged add-on layers) - and a change you make will not appear if a higher layer overrides the same control or if you are testing in the wrong layer context.

How-to

How to Create a BPM Method Directive in Epicor Kinetic

In Epicor Kinetic, open Business Process Management > Method Directive Maintenance (the BPM Workbench), pick the business object and method, choose Pre-Processing, Base Processing or Post-Processing, then add a condition and actions such as Show Message or Set Field. Enable it and test in a pilot company before production.

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)