# Epicor DMT Data Load Plan Worksheet

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

## Short answer

Sequence your Epicor Data Management Tool loads with record counts, rates and estimated run time, then export the plan to Excel.

## Category

epicor

## Erp

Epicor Kinetic

## Audience

- Epicor consultant
- Data migration lead
- Epicor developer

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Seq

**Key:** seq

**Type:** number

#### Data object

**Key:** object

**Type:** text

#### DMT load type

**Key:** dmt

**Type:** select

**Options:**

- Add
- Update
- Add or update
- Delete

#### Source file or system

**Key:** source

**Type:** text

#### Records

**Key:** records

**Type:** number

#### Records per minute

**Key:** rate

**Type:** number

**Help:** Measure in a test system

#### Est. minutes

**Key:** minutes

**Type:** number

**Expr:** records / rate

**Format:** decimal

#### Owner

**Key:** owner

**Type:** text

#### Status

**Key:** status

**Type:** select

**Options:**

- Not started
- Mapped
- Test loaded
- Validated
- Loaded to live

**Rows:**

**Seq:** 1

**Object:** Company and site configuration

**Dmt:** Update

**Source:** Config workbook

**Records:** 40

**Rate:** 40

**Owner:** Consultant

**Status:** Validated

**Seq:** 2

**Object:** Customers

**Dmt:** Add

**Source:** Legacy customer.csv

**Records:** 2400

**Rate:** 120

**Owner:** Sales ops

**Status:** Test loaded

**Seq:** 3

**Object:** Suppliers

**Dmt:** Add

**Source:** Legacy vendor.csv

**Records:** 900

**Rate:** 120

**Owner:** Purchasing

**Status:** Mapped

**Seq:** 4

**Object:** Parts

**Dmt:** Add

**Source:** Item master.xlsx

**Records:** 18500

**Rate:** 150

**Owner:** Engineering

**Status:** Mapped

**Seq:** 5

**Object:** Bills of material

**Dmt:** Add

**Source:** BOM export

**Records:** 31000

**Rate:** 200

**Owner:** Engineering

**Status:** Not started

**Seq:** 6

**Object:** Opening inventory balances

**Dmt:** Add

**Source:** Cycle count file

**Records:** 12000

**Rate:** 90

**Owner:** Warehouse

**Status:** Not started

**Totals:**

#### Total records

**Key:** records

**Agg:** sum

**Format:** integer

#### Total estimated minutes

**Key:** minutes

**Agg:** sum

**Format:** decimal

**Summary:**

#### Estimated load hours (one pass)

**Key:** hours

**Expr:** sum_minutes / 60

**Format:** decimal

**Primary:** true

#### Hours for three full rehearsals

**Key:** three

**Expr:** sum_minutes * 3 / 60

**Format:** decimal

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

## Content

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

**Sections:**

#### How to use the worksheet

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

**Bullets:**

- Replace the sample rows
- Measure rates, do not guess
- Update status after every rehearsal
- Re-export before each rehearsal

#### Load order and dependencies

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

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

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

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

**Faq:**

#### What does DMT stand for in Epicor?

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

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

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

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

## Search terms

epicor dmt load plan, epicor data migration plan excel, epicor dmt order of loading, epicor data conversion worksheet, epicor dmt template, epicor cutover data load, epicor data migration checklist

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