# Epicor Customization Migration Estimator

> Source: https://netray.co/tools/epicor-customization-migration-estimator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Count your customizations, BPMs, reports and BAQs and get an hours and cost estimate for retesting and rework in an upgrade or Kinetic move.

## Category

epicor

## Erp

Epicor Kinetic

## Audience

- Epicor project manager
- Epicor consultant
- IT manager

## Tool

**Kind:** calculator

**Currency:** $

**Inputs:**

#### Screen customizations

**Key:** ui_custom

**Type:** number

**Default:** 40

**Min:** 0

**Step:** 1

**Unit:** count

**Help:** Classic customizations or Application Studio layers

#### BPMs (method and data directives)

**Key:** bpm

**Type:** number

**Default:** 60

**Min:** 0

**Step:** 1

**Unit:** count

#### Custom SSRS or Crystal reports

**Key:** reports

**Type:** number

**Default:** 80

**Min:** 0

**Step:** 1

**Unit:** count

#### BAQs and dashboards

**Key:** baq

**Type:** number

**Default:** 150

**Min:** 0

**Step:** 5

**Unit:** count

#### Integrations and REST consumers

**Key:** integrations

**Type:** number

**Default:** 12

**Min:** 0

**Step:** 1

**Unit:** count

#### Share needing real rework

**Key:** rework_pct

**Type:** slider

**Default:** 30

**Min:** 0

**Max:** 100

**Step:** 5

**Unit:** %

**Help:** The rest only needs retest

#### Complexity factor

**Key:** complexity

**Type:** select

**Default:** 1.25

**Options:**

##### Low (clean, documented)

**Value:** 1

##### Medium

**Value:** 1.25

##### High (undocumented, legacy code)

**Value:** 1.6

#### Blended hourly rate

**Key:** rate

**Type:** number

**Default:** 120

**Min:** 0

**Step:** 5

**Unit:** per hour

**Outputs:**

#### Retest hours

**Key:** test_hours

**Expr:** (ui_custom * 1.5 + bpm * 1 + reports * 1 + baq * 0.25 + integrations * 4) * complexity

**Format:** hours

**Description:** Time to retest everything once, scaled by complexity

#### Rework hours

**Key:** rework_hours

**Expr:** (ui_custom * 6 + bpm * 4 + reports * 5 + baq * 1 + integrations * 16) * (rework_pct / 100) * complexity

**Format:** hours

**Description:** Time to fix the share that breaks or must be rebuilt

#### Total hours

**Key:** total_hours

**Expr:** test_hours + rework_hours + (test_hours + rework_hours) * 0.15

**Format:** hours

**Primary:** true

**Description:** Includes 15% for project management and defects

#### Calendar effort at 3 developers

**Key:** weeks

**Expr:** total_hours / (3 * 32)

**Format:** weeks

**Description:** Assumes three people at 32 productive hours a week

#### Estimated cost

**Key:** cost

**Expr:** total_hours * rate

**Format:** currency

**Primary:** true

#### Items in scope

**Key:** items

**Expr:** ui_custom + bpm + reports + baq + integrations

**Format:** integer

**Chart:**

#### Total hours vs share needing rework

**Type:** line

**X:** rework_pct

**From:** 0

**To:** 100

**Steps:** 20

**Series:**

- total_hours

**Disclaimer:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How to use the estimator

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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

**Body:** 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.

**Bullets:**

- Retire unused objects first
- Replace customizations with standard features where possible
- Prepare test scripts and representative data
- Keep an inventory that stays current

**Cta:** 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.

**Faq:**

#### How long does it take to migrate Epicor customizations?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

epicor customization migration estimate, epicor 10 to kinetic migration effort, epicor upgrade customization cost, epicor kinetic upgrade estimate, epicor customization inventory, epicor bpm migration, epicor upgrade project hours, epicor version upgrade planning

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json