# Epicor DMT Load Time Estimator

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

## Short answer

Estimate DMT run time from record count, measured rate, rejection percentage and rehearsals, and see how rate changes the total.

## Category

epicor

## Erp

Epicor Kinetic

## Audience

- Epicor consultant
- Data migration lead
- Project manager

## Tool

**Kind:** calculator

**Inputs:**

#### Records to load

**Key:** records

**Type:** number

**Default:** 50000

**Min:** 0

**Step:** 500

**Unit:** records

**Help:** Total rows across the object being loaded

#### Measured load rate

**Key:** rate

**Type:** number

**Default:** 120

**Min:** 1

**Step:** 5

**Unit:** records/min

**Help:** From a timed sample in a test system

#### Rejected rows needing reload

**Key:** reject

**Type:** slider

**Default:** 5

**Min:** 0

**Max:** 40

**Step:** 1

**Unit:** %

#### Rehearsal loads before live

**Key:** rehearsals

**Type:** slider

**Default:** 3

**Min:** 0

**Max:** 8

**Step:** 1

**Unit:** loads

#### Validation time per load

**Key:** validation

**Type:** number

**Default:** 45

**Min:** 0

**Step:** 5

**Unit:** min

#### Cutover window available

**Key:** window

**Type:** number

**Default:** 12

**Min:** 0

**Step:** 1

**Unit:** hours

**Outputs:**

#### Rows reloaded

**Key:** reload

**Expr:** records * reject / 100

**Format:** integer

#### Load minutes, one pass with reloads

**Key:** load_min

**Expr:** (records + reload) / rate

**Format:** minutes

#### Hours per full load incl. validation

**Key:** pass_hours

**Expr:** (load_min + validation) / 60

**Format:** decimal

**Primary:** true

**Description:** Time for one complete load and its validation

#### Total hours across rehearsals and live

**Key:** total_hours

**Expr:** pass_hours * (rehearsals + 1)

**Format:** decimal

#### Share of cutover window used

**Key:** fit

**Expr:** if(gt(window,0), pass_hours / window * 100, 0)

**Format:** percent

**Primary:** true

**Description:** Above 100 means the live load does not fit the window

**Chart:**

#### Hours per full load vs load rate

**Type:** line

**X:** rate

**From:** 20

**To:** 400

**Steps:** 20

**Series:**

- pass_hours

**Disclaimer:** An estimate for planning. Real rates depend on BPM directives, hardware, indexing and record size, so replace the defaults with timings from your own test loads.

## Content

**Intro:** Whether an Epicor conversion fits the cutover weekend depends on load rate, volume and rework. This estimator turns those into hours per load and shows how much of the cutover window a full live load would use.

**Sections:**

#### How to use the estimator

**Body:** Enter the record count for the object, the load rate you measured on a timed sample, the percentage of rows you expect to be rejected and reloaded, the number of rehearsals and the validation time per load. The result shows hours per full load, total hours across rehearsals and live, and the share of your cutover window consumed.

**Bullets:**

- Measure the rate, do not guess
- Include reloads
- Add validation time
- Compare to the real window

#### The formula

**Body:** Rows reloaded equal records times the rejection percentage. Load minutes equal records plus reloaded rows divided by the load rate. Hours per full load equal load minutes plus validation minutes, divided by sixty. Total hours multiply that by rehearsals plus the live load. It is deliberately simple so you can check it by hand and adapt it for each object.

#### Reading the chart

**Body:** The chart sweeps the load rate and plots hours per full load. Gains flatten as the rate climbs, since validation time stays fixed. A low rate can make a load impossible to fit, which points to fixing the cause, such as slow directives or lock contention, instead of simply extending the window.

#### Common mistakes

**Body:** Using a rate from a tiny sample overstates speed because larger loads slow down. Forgetting reloads and validation is the other classic error. Sum objects serially unless you have proved they can run in parallel, since many loads depend on earlier ones.

**Cta:** If a load will not fit your window, Netray can help analyse directives, sequencing and data volume.

**Faq:**

#### How do I measure my DMT load rate?

**Answer:** Load a representative sample of a few hundred or thousand rows into a test environment, record the elapsed time, and divide rows by minutes. Repeat with a larger sample to see whether the rate falls with volume.

#### Why would my rate be low?

**Answer:** Common causes are BPM directives firing per row, many related tables updated per record, network or database contention and under sized servers. Test with directives disabled in a test system to see how much they cost.

#### Can I run several loads at once?

**Answer:** Sometimes, if the objects are independent and the system has headroom, but concurrent loads can lock the same tables and slow each other. Test parallel loading in rehearsal before you rely on it in the cutover plan.

#### What reject percentage should I assume?

**Answer:** Use what rehearsals show. Early loads often reject a large share because of mapping and data quality issues, and later ones fewer. Start with a cautious figure and update it after each rehearsal.

## Search terms

epicor dmt load time, epicor data migration time estimate, epicor cutover window calculator, epicor dmt performance, epicor data conversion estimate, dmt records per minute, erp data load time calculator

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