Epicor DMT Data Load Checklist (Free, PDF)

0%

0 of 29 items complete

12 critical items still open - these are the highest-risk gaps.

Download checklist:

Planning and scope

List every data object to load and the source system and owner for eachCRITICALDefine in-scope history (open orders, open POs, on-hand, open AR/AP) versus what stays archivedCRITICALAgree a data cut-off date and freeze window with the businessCreate a mapping document from source fields to Epicor fieldsDecide naming and numbering rules for customers, vendors and partsAssign a data owner who signs off each object

Environment and configuration

Use a dedicated test company or database copy for rehearsalsCRITICALConfirm company, plant, warehouse, bin and site configuration is finishedCRITICALSet up reference data first: UOMs, payment terms, tax, currencies, ship viaConfirm user and security setup for the DMT userReview which BPMs fire on loaded tables and decide whether to disable themCRITICALBack up the target database before each major loadCRITICAL

Load sequence

Load in dependency order: reference data, customers and vendors, parts, then BOM and routingsCRITICALLoad open sales orders and purchase orders after parts, customers and vendors existLoad inventory balances last, via adjustments or counts with correct valuationCRITICALLoad a small sample first and review it in the applicationUse the same DMT templates and mapping for test and productionLog each run with date, file, user and row counts

Validation and sign-off

Reconcile row counts between source files and Epicor tablesCRITICALReconcile inventory quantity and value to the general ledgerCRITICALReconcile open AR and AP totals to sourceSpot check parts, BOMs and routings with engineeringReview DMT error logs and fix root causes, not just rowsObtain written sign-off from each data owner

Cutover and rollback

Document the go-live load runbook with times and ownersCRITICALDefine the rollback decision point and restore procedureCRITICALRe-enable BPMs and any disabled integrations after loadingRun a smoke test of order entry, receiving, job release and invoicingKeep legacy system read-only for a defined period

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.

Migration data validation help

Optional: discuss AI-assisted reconciliation for an Epicor migration.

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

How to use the checklist

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

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.

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

Common mistakes

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.

Frequently Asked Questions

Should I disable BPMs during a DMT load?

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?

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?

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?

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.

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

Talk to an Expert Explore More Free Tools

Related Tools

Epicor

More Epicor tools

See all

Epicor DMT Data Load Checklist (Data Management Tool Migration)