# Epicor DMT Data Load Checklist (Data Management Tool Migration)

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

## Short answer

Checklist for planning and running Epicor DMT loads: prerequisites, load order, BPM impact, validation and rollback.

## Category

epicor

## Erp

Epicor Kinetic

## Audience

- Epicor consultant
- Epicor developer
- Data migration lead

## Tool

**Kind:** checklist

**Scoring Note:** Complete every critical item before loading into production. Run the full sequence at least twice in a test company, and record row counts at each step.

**Groups:**

#### Planning and scope

**Items:**

**Text:** List every data object to load and the source system and owner for each

**Critical:** true

**Text:** Define in-scope history (open orders, open POs, on-hand, open AR/AP) versus what stays archived

**Critical:** true

Agree a data cut-off date and freeze window with the business

Create a mapping document from source fields to Epicor fields

Decide naming and numbering rules for customers, vendors and parts

Assign a data owner who signs off each object

#### Environment and configuration

**Items:**

**Text:** Use a dedicated test company or database copy for rehearsals

**Critical:** true

**Text:** Confirm company, plant, warehouse, bin and site configuration is finished

**Critical:** true

Set up reference data first: UOMs, payment terms, tax, currencies, ship via

Confirm user and security setup for the DMT user

**Text:** Review which BPMs fire on loaded tables and decide whether to disable them

**Critical:** true

**Text:** Back up the target database before each major load

**Critical:** true

#### Load sequence

**Items:**

**Text:** Load in dependency order: reference data, customers and vendors, parts, then BOM and routings

**Critical:** true

Load open sales orders and purchase orders after parts, customers and vendors exist

**Text:** Load inventory balances last, via adjustments or counts with correct valuation

**Critical:** true

Load a small sample first and review it in the application

Use the same DMT templates and mapping for test and production

Log each run with date, file, user and row counts

#### Validation and sign-off

**Items:**

**Text:** Reconcile row counts between source files and Epicor tables

**Critical:** true

**Text:** Reconcile inventory quantity and value to the general ledger

**Critical:** true

Reconcile open AR and AP totals to source

Spot check parts, BOMs and routings with engineering

Review DMT error logs and fix root causes, not just rows

Obtain written sign-off from each data owner

#### Cutover and rollback

**Items:**

**Text:** Document the go-live load runbook with times and owners

**Critical:** true

**Text:** Define the rollback decision point and restore procedure

**Critical:** true

Re-enable BPMs and any disabled integrations after loading

Run a smoke test of order entry, receiving, job release and invoicing

Keep legacy system read-only for a defined period

## Content

**Intro:** DMT is powerful and unforgiving: it writes through business logic, so BPMs, validation and order of loads decide whether a migration goes smoothly. This checklist covers what experienced Epicor migration teams verify before go-live.

**Sections:**

#### How to use the checklist

**Body:** Work through each group during planning and again before every rehearsal. Mark critical items as blockers. Keep the checklist with your load runbook so each run is documented. Export to PDF or Excel to share with data owners and project leadership.

#### Why order matters

**Body:** Epicor records depend on each other. A sales order needs a customer and parts, a PO needs a vendor, a BOM needs its component parts, and inventory needs warehouses and bins. Loading in dependency order avoids errors and cleanup. Inventory should be loaded after structures are final, and reconciled to the ledger so valuation is correct from day one.

**Bullets:**

- Reference data and configuration first
- Customers, vendors and parts next
- Structures, routings and open documents after
- Inventory balances and financial balances last

#### Common mistakes

**Body:** Teams often skip rehearsals, leave BPMs active that email customers or alter data during a load, or load inventory before costs are set. Another frequent issue is cleaning data in Excel by hand with no repeatable process. Script and version the clean-up so reruns are identical, and keep an audit trail of every load.

**Cta:** Netray can help validate migrated Epicor data with AI-assisted reconciliation, including on-prem for sensitive data.

**Faq:**

#### Should I disable BPMs during a DMT load?

**Answer:** Often yes for BPMs that send notifications or modify data, but evaluate each one. Some validations are worth keeping. Document which you disabled and re-enable them afterwards.

#### How many rehearsals are enough?

**Answer:** At least two full rehearsals in a test company are common, with the second timed to confirm the cutover window. More are warranted for complex inventory or multi-site migrations.

#### What loads last?

**Answer:** Inventory balances and financial opening balances usually go last, after structures and costing are final, so valuation and reconciliation are clean.

#### Can DMT roll back a bad load?

**Answer:** DMT does not provide a general undo, so take a database backup before major loads and define a restore plan. Some objects can be corrected by reloading, but do not rely on that.

## Search terms

epicor dmt checklist, epicor dmt load order, epicor data migration checklist, epicor data management tool, epicor dmt best practices, epicor go live data load, epicor dmt bpm disable, epicor migration validation

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