Epicor Customization Migration Estimator
Customizations are the hidden cost of an Epicor upgrade or a move to Kinetic. This estimator turns your inventory counts into a rough hours and cost range you can use to start the conversation.
Your numbers
Classic customizations or Application Studio layers
The rest only needs retest
Your results
Planning estimate built from per item averages. Real effort depends on code quality, test data, and release differences. Replace the per item hours with your own history if you have it.
Total hours vs share needing rework
Sweeps Share needing real rework from 0 to 100, holding your other inputs fixed.
Get help inventorying your customizations
Optional: talk through an approach to summarize customizations and BPMs for an upgrade plan.
Optional. The tool and every export work without this. No spam.
How to use the estimator
Start by counting. Use the customization maintenance screens, the BPM list, report styles, BAQ list and your integration inventory. Enter the counts, then set the share you think will need real rework, as opposed to retest only. Choose the complexity factor honestly: undocumented code by a former employee is high, a small well documented set is low. The blended rate should reflect the real mix of internal and partner time.
- Count objects from the system, not from memory
- Separate active from unused items
- Pick complexity based on documentation quality
- Run low, medium and high cases
The method
The model assigns an average retest time per item type, and a larger average rework time for items that break. Retest hours are scaled by the complexity factor. Rework hours apply only to the share you select. A 15 percent allowance covers project coordination and defect handling. Effort in weeks assumes three developers at 32 productive hours each. These per item values are planning assumptions, not benchmarks, so adjust them to your own history.
Reading the result
Use the total as the middle of a range, perhaps minus 25 percent and plus 40 percent, rather than a single number. The chart shows how sensitive the total is to the rework share, which is usually the biggest unknown. A first pass that tests quickly to find the true rework share is often worth doing early. Remember that this covers technical work only, not business user testing, training or data migration.
Ways to reduce the number
Retire unused BAQs, reports and BPMs before you estimate, since each one removed saves test time. Replace old customizations with standard features where the new release covers them. Document what stays. Good test scripts and test data reduce both retest and rework time, because defects are found earlier.
- Retire unused objects first
- Replace customizations with standard features where possible
- Prepare test scripts and representative data
- Keep an inventory that stays current
Frequently Asked Questions
How long does it take to migrate Epicor customizations?
It depends mostly on the count, the code quality and how many items break. Small, well documented sets can be retested in weeks, while large legacy sets can take months. Use the estimator to size your own case.
Do all customizations need rework in a Kinetic move?
No. Many need only retesting, but classic client customizations that depend on older screens or controls often need rebuilding in Application Studio. The rework share input lets you model different outcomes.
What should be in a customization inventory?
List screen customizations, BPMs, function libraries, report styles, BAQs, dashboards, UD tables and integrations, each with owner, last used date, risk and a note on whether standard functionality could replace it.
Is this estimate a quote?
No. It is a planning aid based on averages. A proper estimate needs a review of the actual objects, a sample migration, and agreement on testing scope between your team and any partner.
If the inventory itself is the hard part, Netray can discuss using a private AI assistant to read exports of your customizations and BPMs and summarize what each one does.
Related Tools
Epicor Application Studio Layer Checklist
A checklist for Kinetic Application Studio layers covering naming, scope, events, rules, security, testing and upgrade impact.
EpicorEpicor SSRS Report Template Checklist
A pre-release checklist for custom Epicor SSRS reports covering report style, data definition, layout, parameters, security and testing.
EpicorEpicor Function Library Design Template
A design document for an Epicor function: signature, inputs, outputs, logic notes, security, test cases and sign off.
EpicorEpicor UD Table Design Worksheet
An editable worksheet for planning user defined tables and fields before you build them in Epicor, with a column count and key check.
More Epicor tools
See all- Epicor Kinetic Customization Change Request Form Template
- Epicor Kinetic Go-Live Cutover Plan Template
- Epicor Kinetic User Access Request Form Template
- Epicor Kinetic BPM Directive Inventory Worksheet
- Epicor Kinetic Scheduled Task Register Worksheet
- Epicor Kinetic Custom Report Inventory Worksheet
- Epicor Kinetic Data Migration Mapping Worksheet
- Epicor Kinetic Data Load Effort Calculator
- Epicor Business Object Services Reference
New to Epicor ERP? Start with the Epicor ERP guide and toolkit, or plan with Training Path Builder, ERP Certification Study Planner, Upgrade Path Planner.
Keep exploring
Free tools
- Epicor Kinetic Upgrade Readiness AssessmentTen questions scoring how ready your customizations, BPMs, reports and integrations are for an Epicor upgrade.
- Epicor Customization Code Review ChecklistA checklist for reviewing Epicor custom code, BPM directives and customizations before promotion to live.
- Epicor Kinetic Customization Change Request Form TemplateA fill-in change request form for Application Studio customizations, BPM directives and Epicor Functions, with test and rollback sections.
ERP fixes and how-tos
- Preserving Customizations When Upgrading to Epicor KineticMoving Epicor 10 classic customizations to the Kinetic web UI is a conversion, not an automatic carry-over. Here is the checklist for what survives, what needs rework, and how to sequence the upgrade.
- Epicor Application Studio: understanding customization layersHow Epicor Kinetic Application Studio's layer model works: base, customization, personalization and extended layers, load order, and why changes sometimes do not appear.
- Convert Epicor Classic Dashboards to KineticHow to convert Epicor Classic dashboards to Kinetic during an upgrade: what carries over, what must be rebuilt, and how to verify each dashboard.
AI on your ERP
- Private AI for Epicor Kinetic Cloud, Outside the Multi-Tenant BoundaryRun 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.
- AI for Epicor Kinetic Job Shops: Quote History, Job Variance and Schedule RiskPrivate AI for Epicor Kinetic job shops: quote-to-job history, JobHead and JobOper variance, subcontract delays and schedule risk, via REST and BAQs.
Integrations
- How to add AI agents to Epicor KineticHow to add AI agents to Epicor Kinetic: a tool layer over the REST v2 API and BAQs, MRP exception triage, PO expediting, and human approval before any write.
- How to add an AI chatbot to Epicor KineticAdd an AI chatbot to Epicor Kinetic: an internal assistant for planners and buyers or a customer portal bot, grounded in BAQs and runnable fully on-prem.
Software
- Epicor KineticEpicor Kinetic explained for manufacturers: modules, REST API, BAQs, deployment, strengths, limits and alternatives to compare before choosing or upgrading.
- Epicor CPQEpicor CPQ is a cloud configure-price-quote product with visual 3D configuration for manufacturers. Modules, ERP integrations and alternatives explained.