# Epicor DMT Data Load Time Calculator > Source: https://netray.co/tools/epicor-dmt-data-load-time-calculator > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Plan DMT load windows by combining record counts, throughput, error rates and fix time into total hours. ## Category epicor ## Erp Epicor Kinetic ## Audience - Epicor consultant - Data migration lead - Epicor developer ## Tool **Kind:** calculator **Inputs:** #### Records to load **Key:** records **Type:** number **Default:** 60000 **Min:** 1 **Step:** 1000 **Unit:** records **Help:** Total rows across the DMT files in this load. #### Load speed **Key:** rate **Type:** number **Default:** 1200 **Min:** 1 **Step:** 100 **Unit:** records/min **Help:** Measure on a 500 row test file in your environment. #### Error rate on first pass **Key:** error_pct **Type:** slider **Default:** 4 **Min:** 0 **Max:** 30 **Step:** 0.5 **Unit:** % #### Time to fix one error **Key:** fix_min **Type:** number **Default:** 2 **Min:** 0 **Step:** 0.5 **Unit:** min **Help:** Analyse the message, correct the source cell, save the file. #### Records per DMT file **Key:** batch **Type:** number **Default:** 5000 **Min:** 1 **Step:** 500 **Unit:** records #### Overhead per file **Key:** setup_min **Type:** number **Default:** 10 **Min:** 0 **Step:** 1 **Unit:** min **Help:** Open, map, validate, and archive logs. #### Post-load verification **Key:** verify_hours **Type:** number **Default:** 6 **Min:** 0 **Step:** 1 **Unit:** hours **Outputs:** #### DMT files **Key:** files **Expr:** ceil(records / batch) **Format:** integer #### First pass load time **Key:** load_min **Expr:** records / rate **Format:** minutes #### Records in error **Key:** errors **Expr:** records * error_pct / 100 **Format:** integer #### Error fix and reload time **Key:** rework_min **Expr:** errors * fix_min + errors / rate **Format:** minutes #### File handling overhead **Key:** overhead_min **Expr:** files * setup_min **Format:** minutes #### Total effort **Key:** total_hours **Expr:** (load_min + rework_min + overhead_min) / 60 + verify_hours **Format:** hours **Primary:** true **Description:** Hands-on plus machine time for the load. **Chart:** #### Total effort vs first pass error rate **Type:** line **X:** error_pct **From:** 0 **To:** 30 **Steps:** 30 **Series:** - total_hours **Disclaimer:** Planning estimate. Throughput varies with entity, triggers, BPMs and server load. Always rehearse the load in a copy of production. ## Content **Intro:** Cutover weekends fail when the data load runs longer than the window. This calculator turns record counts and a measured DMT speed into a realistic effort figure, including the rework that clean-looking files still generate. **Sections:** #### How to use it **Body:** Count the records in each load, then time a small test file to get records per minute. Enter your first pass error rate from earlier rehearsals, the average time to fix an error and the number of records per file. The result splits machine load time, rework and per-file overhead, then adds verification time so you can size a cutover window. **Bullets:** - Load order matters: reference data, parts, customers, then transactions. - Re-run the estimate after each rehearsal with the real error rate. - Use the chart to see how much cleansing before the load is worth. #### The formula **Body:** Load time is records divided by speed. Errors equal records times the error rate. Rework is errors times the fix time plus the time to reload those errors at the same speed. Overhead is the number of files times the per-file handling time. Total hours add all three, converted from minutes, plus verification. The model ignores parallel loading, which can shorten wall-clock time when entities do not depend on each other. #### Reading the chart **Body:** The sweep shows effort rising almost linearly with the error rate, because each error costs human time rather than machine time. That is why data cleansing in the source spreadsheet usually beats faster hardware. If a few percentage points of errors add a full working day, invest in validation formulas and lookup checks before running DMT. #### Common mistakes **Body:** Teams measure speed on an empty test company and assume it holds in a full one with BPMs, UD triggers and big indexes active. Others forget attachments, multi-company loads and sign-off time. Plan for at least one full dress rehearsal and keep the DMT logs so you can fix patterns, such as one bad unit of measure, in bulk. **Cta:** If you need to script or accelerate migrations into Epicor, Netray can help design the validation and load pipeline. The calculator is free either way. **Faq:** #### What is a realistic DMT speed? **Answer:** It varies widely by table and by triggers. Simple masters may load quickly, while transactional tables with BPMs are slower. Always measure with a sample file in your own environment rather than trusting a rule of thumb. #### Can I run several DMT sessions in parallel? **Answer:** Often yes for independent entities, which reduces elapsed time though not total effort. Avoid parallel loads that touch the same records or depend on each other, and watch database locking. #### Why add a verification step? **Answer:** A load that finishes without errors can still be wrong. Reconcile counts and totals against the source, such as on-hand quantity and open order value, before declaring the load complete. #### Does this cover Epicor Kinetic cloud? **Answer:** The arithmetic is the same, but cloud tenants may restrict how and when large loads run. Confirm limits and scheduling with your Epicor cloud contact when planning the window. ## Search terms epicor dmt load time, epicor data migration estimate, epicor dmt performance, epicor dmt errors, epicor cutover data load, dmt batch size, epicor go live data migration plan --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json