# Epicor Kinetic Upgrade Readiness Assessment (Customizations, BPMs, Reports) > Source: https://netray.co/tools/epicor-kinetic-upgrade-readiness-assessment > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Ten questions scoring how ready your customizations, BPMs, reports and integrations are for an Epicor upgrade. ## Category epicor ## Erp Epicor Kinetic ## Audience - Epicor developer - Epicor administrator - IT manager ## Tool **Kind:** assessment **Questions:** #### Do you have a current inventory of all customizations and personalizations? **Options:** ##### Complete and maintained **Score:** 10 ##### Partial or outdated **Score:** 5 ##### No inventory **Score:** 0 #### How well documented are your BPM directives? **Options:** ##### Each has purpose, owner and test case **Score:** 10 ##### Names only **Score:** 4 ##### Undocumented **Score:** 0 #### Do customizations use supported approaches (Application Studio, BPM, functions) rather than direct database changes? **Options:** ##### Yes, no direct database writes **Score:** 10 ##### Mostly **Score:** 5 ##### Some direct SQL or unsupported methods **Score:** 0 #### How many classic customizations still need to be moved to the newer UI approach? **Options:** ##### None or very few **Score:** 10 ##### A moderate number **Score:** 5 ##### Many or unknown **Score:** 0 #### Are your BAQs, dashboards and reports inventoried and tested? **Options:** ##### Yes, with owners and regression tests **Score:** 10 ##### Partly **Score:** 5 ##### No **Score:** 0 #### Do you have a test environment that mirrors production? **Options:** ##### Yes, refreshed regularly **Score:** 10 ##### Yes, but stale **Score:** 5 ##### No **Score:** 0 #### How are external integrations documented? **Options:** ##### Documented with owners and contract tests **Score:** 10 ##### Documented but untested **Score:** 5 ##### Not documented **Score:** 0 #### Do you have automated or scripted regression tests for key transactions? **Options:** ##### Yes, run before each change **Score:** 10 ##### Manual test scripts **Score:** 5 ##### None **Score:** 0 #### Is there a business owner and an agreed schedule for user acceptance testing? **Options:** ##### Yes, scheduled **Score:** 10 ##### Informal **Score:** 4 ##### No **Score:** 0 #### Do you have a rollback and communication plan for cutover? **Options:** ##### Written and rehearsed **Score:** 10 ##### Draft **Score:** 5 ##### No **Score:** 0 **Bands:** #### Not ready **Min:** 0 **Max:** 39 **Verdict:** Significant unknowns in customizations, testing or rollback would put an upgrade at high risk. **Recommendations:** - Build a full inventory of customizations, BPMs, BAQs, reports and integrations - Create or refresh a test environment that mirrors production - Remove or document anything that bypasses supported methods #### Partly ready **Min:** 40 **Max:** 69 **Verdict:** You have a base, but gaps in documentation or testing will cause surprises. **Recommendations:** - Document each BPM and customization with an owner and test case - Script regression tests for order entry, receiving, job and invoicing - Confirm the plan for classic customizations and reports #### Mostly ready **Min:** 70 **Max:** 89 **Verdict:** Good control of your estate. Focus on testing depth and cutover rehearsal. **Recommendations:** - Rehearse the cutover and rollback end to end - Run UAT with named business owners - Review integrations for version-specific changes #### Ready to plan **Min:** 90 **Max:** 100 **Verdict:** Your inventory, testing and governance are strong. Proceed to detailed upgrade planning. **Recommendations:** - Lock scope and schedule with business sign-off - Keep regression tests current through the upgrade - Plan post go-live support and monitoring ## Content **Intro:** Epicor upgrades rarely fail on the core software. They fail on the things around it: forgotten customizations, undocumented BPMs, fragile integrations and no regression testing. This assessment scores those areas in two minutes. **Sections:** #### How to use the assessment **Body:** Answer each question for your current Epicor environment. Be honest about what is documented versus what people remember. The total is converted to a percentage and mapped to a readiness band with recommended next steps. Use it to build the case for an inventory project or to prioritize prework before engaging a partner. #### What is being measured **Body:** The questions cover four risk areas: visibility of the customization estate, use of supported techniques, testing and environments, and governance for cutover. Customizations and BPMs carry the most upgrade effort, because each must be reviewed and retested. Integrations and reports are next, as they depend on field names, services and layouts that can change between versions. **Bullets:** - Visibility: inventory of customizations, BPMs, BAQs, reports - Technique: supported methods versus direct database changes - Testing: environment parity and regression scripts - Governance: owners, UAT schedule and rollback plan #### Common mistakes **Body:** Teams estimate effort from the number of customizations without checking whether they are still used. Retiring unused items before the upgrade cuts cost significantly. Others skip testing integrations until late, or fail to refresh the test system so results do not reflect production. Treat the score as a starting point and confirm with your Epicor partner and the release notes for your target version. **Cta:** Netray can run AI-assisted analysis over your customizations and BPMs to estimate upgrade effort, with models that stay on your own infrastructure. **Faq:** #### Does a low score mean I cannot upgrade? **Answer:** No. It means there is preparation to do. Building an inventory, documenting rules and creating a test environment are manageable steps that reduce risk and cost. #### What drives upgrade effort the most? **Answer:** Typically customizations, BPMs, custom reports and integrations. Each must be reviewed, adjusted and tested. The more undocumented items you have, the more discovery time is needed. #### Should I remove unused customizations first? **Answer:** Usually yes. Confirm with users and usage data, then retire what is not needed. Every item removed is one less to migrate and test. #### Is this a substitute for a partner assessment? **Answer:** No. It is a quick self check. A partner or vendor assessment against your target version and actual configuration is still recommended before committing a budget. ## Search terms epicor kinetic upgrade readiness, epicor upgrade assessment, epicor classic to kinetic, epicor customization audit, epicor upgrade risk, epicor 10 to kinetic upgrade, epicor customization inventory, epicor upgrade checklist --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json