EpicorFree calculatorPDF, Excel, Word exportEpicor Kinetic

Epicor DMT Load Time Estimator

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.

Your numbers

records

Total rows across the object being loaded

records/min

From a timed sample in a test system

5 %
3 loads
min
hours

Your results

Hours per full load incl. validation
8.0417
Time for one complete load and its validation
Share of cutover window used
67%
Above 100 means the live load does not fit the window
Rows reloaded
2,500
Load minutes, one pass with reloads
437.5 min
Total hours across rehearsals and live
32.1667

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.

Save results:

Hours per full load vs load rate

Sweeps Measured load rate from 20 to 400, holding your other inputs fixed.

Cutover planning help

An optional review of your conversion timings and cutover sequence.

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

How to use the estimator

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.

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

The formula

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

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

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.

Frequently Asked Questions

How do I measure my DMT load rate?

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?

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?

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?

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.

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