Epicor Kinetic Upgrade Checklist (Free, PDF/Excel)

0%

0 of 28 items complete

15 critical items still open - these are the highest-risk gaps.

Download checklist:

Plan and inventory

Confirm current and target versions and the supported upgrade pathCRITICALName a business owner, technical lead and test coordinatorsCRITICALList every customization: BPMs, customizations, personalizations, widgetsCRITICALList all BAQs, dashboards, reports and who uses themCRITICALList integrations, EDI, REST consumers, scripts and scheduled tasksCRITICALIdentify unused customizations to retire instead of upgradeReview release notes and breaking changes for your modulesConfirm licensing, hosting and infrastructure requirements

Build and test environment

Create a pilot environment from a recent copy of productionCRITICALRun the upgrade in pilot and record duration and issuesCRITICALCheck that customizations and BPMs still compile and runCRITICALRe-test BAQs, dashboards and reports with real parametersTest integrations end to end including authenticationCRITICALTest security groups and menu access by roleTest month-end processes such as close job and costingCheck performance on key screens and processes

User readiness

Document changes users will notice and update guidesTrain super users before the pilot sign-offCRITICALRun user acceptance testing against scripted scenariosCRITICALRecord defects with owners and agreed deadlinesAgree a communication plan for the cutover window

Cutover and rollback

Freeze changes and transactions during the cutover windowCRITICALTake full database and application backups and test restoreCRITICALWrite a timed cutover runbook with named ownersCRITICALDefine go and no-go criteria and a rollback decision pointCRITICALRun smoke tests after upgrade: login, job entry, receipt, shipmentReconnect integrations and scheduled tasks and confirm they runMonitor the first week and hold a post-go-live review

Treat unticked critical items as blockers for the go-live decision.

Upgrade readiness review

Share your customization and integration list and ask for an optional readiness discussion.

Optional. The tool and every export work without this. No spam.

How to use the checklist

Start with the inventory group, because every later estimate depends on it. Assign an owner to each item, export the checklist to Excel and track it in your project meetings. Items marked critical should be resolved before cutover. Rerun the pilot upgrade until it completes cleanly and the timing is predictable.

Inventory first, estimate second
Pilot upgrade on a fresh copy of production
Users test their own scenarios
A rehearsed rollback plan

Customizations are the main risk

Standard Epicor upgrades well. Trouble comes from customizations, BPMs and integrations that depend on specific behavior. List them all, decide which to keep, rewrite or retire, and test each against the new version. Retiring unused customizations is the cheapest risk reduction available in most upgrade projects.

Integrations and authentication

REST consumers, EDI connections and scripts often rely on credentials, endpoints and API keys that may change with versions or hosting. Test them with real payloads in the pilot. A shop floor data collection tool that cannot log in on Monday is as disruptive as a database failure.

Cutover discipline

Write the cutover as a timed runbook with owners, a backup and restore test, and a clear rollback point. Decide in advance who can call a no-go and what evidence they need. After go-live, keep hypercare support available and review defects daily for the first week.

Frequently Asked Questions

How long does an Epicor Kinetic upgrade take?

It varies widely with customizations, integrations and data size. A lightly customized site may need weeks of planning and testing around a short cutover. Heavily customized sites often need months. The pilot upgrade gives the most reliable timing for your own system.

Do my BAQs and dashboards survive an upgrade?

Usually they carry over, but you should retest them, especially ones using customizations or unusual joins. Check parameters, calculated fields and security assignments in the pilot, and confirm dashboards still render as expected.

What is the most common upgrade failure?

Missing integrations and customizations from the inventory, so they are untested until go-live. Authentication and endpoint changes for REST or EDI connections are a close second. A full inventory and an end-to-end pilot reduce both.

Should we upgrade in place or build a new environment?

Many teams build a new environment and migrate data to it, which makes rollback simple, while others upgrade in place. The right choice depends on hosting, licensing and your support partner. Whichever you choose, plan and rehearse the rollback.

We can help inventory your customizations and BAQs and use AI to flag the ones most likely to break before the upgrade.

Talk to an Expert Explore More Free Tools

Related Tools

Epicor

More Epicor tools

See all

Epicor Kinetic Upgrade Checklist for Admins and Project Managers