Epicor DMT Data Load Plan Worksheet
Every Epicor go live depends on loading data in the right order with realistic timing. This worksheet keeps the whole DMT plan in one place: sequence, source, volume, measured rate and the estimated minutes that tell you whether the cutover window is realistic.
| Seq | Data object | DMT load type | Source file or system | Records | Records per minute | Est. minutes | Owner | Status | |
|---|---|---|---|---|---|---|---|---|---|
1 | |||||||||
20 | |||||||||
7.5 | |||||||||
123.3333 | |||||||||
155 | |||||||||
133.3333 |
Load order matters: reference data first, then masters, then structures, then transactions and balances. Replace the example rates with timings from your own test loads, since rates depend on directives, hardware and record size.
Conversion plan review
An optional review of your Epicor data conversion sequence, reconciliation and rehearsal approach.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
List each data object in the order it must load, with the DMT load type and the file or system it comes from. Enter the record count from the source and a records per minute rate measured in a test load. The worksheet calculates minutes per object and the total, so you can compare it to the cutover window. Export to Excel to share with the business owners.
- Replace the sample rows
- Measure rates, do not guess
- Update status after every rehearsal
- Re-export before each rehearsal
Load order and dependencies
Dependencies drive sequence. Customers need their terms, ship vias and tax settings first. Parts need product groups, units of measure and sites. Bills of material need parts and operations. Opening inventory needs parts, warehouses and bins. Transactions such as open orders or purchase orders come last. Write down any prerequisite beside the object so nothing is loaded before its references exist.
Why rates differ
A load that runs at a high rate for simple masters can crawl on objects that fire many BPM directives or update several tables per record. Time one small sample for each object and extrapolate cautiously. Rehearse the largest objects at full volume at least once, because indexing, locking and directive behaviour often change with size.
Common mistakes
Plans often forget rework. Add time for rejected rows and reloads, and for validation between steps. Another mistake is loading into live without recording row counts before and after. Keep a reconciliation count per object so finance and operations can sign off the migrated data.
Frequently Asked Questions
What does DMT stand for in Epicor?
DMT is the Data Management Tool, Epicor's utility for bulk loading and updating data in the application using its own business logic. It is widely used for conversions and mass updates, and it can be run from a screen or the command line for repeatable loads.
How do I estimate DMT load time?
Load a representative sample in a test environment, note records per minute, and multiply for the full volume. Then add a margin for rejected rows and reloads. Treat the number as a planning range until you have rehearsed the full volume at least once.
Should I load in the live system first?
No. Load and validate in a pilot or test environment, rehearse the full sequence, and only then load live. Keep row counts before and after each object so you can reconcile what was loaded and prove nothing was lost.
Can DMT trigger BPM directives?
Yes, loads use the same business logic as the application, so directives on those methods can fire during a load. That can slow rates or block rows, so review directives before a conversion and make sure they behave safely for non interactive callers.
If your data conversion involves a legacy ERP and you want help mapping and validating before the first rehearsal, Netray can review the plan with you.
Related Tools
Epicor DMT Load Time Estimator
Estimate DMT run time from record count, measured rate, rejection percentage and rehearsals, and see how rate changes the total.
EpicorEpicor UAT Test Script Worksheet
An editable UAT script for Epicor with expected results, tester, status and defect counts. Track pass rate and export to Excel.
EpicorEpicor BPM Directive Inventory Worksheet
Inventory your BPM directives, score complexity and retest effort, and see total upgrade retest hours. Export to Excel.
EpicorEpicor Customization Change Request Template
A change request form for Epicor customizations that captures the business need, impact, test plan and approvals before anyone opens the tool.
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