Epicor DMT Data Load Checklist (Data Management Tool Migration)
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.
0 of 29 items complete
12 critical items still open - these are the highest-risk gaps.
Planning and scope
Environment and configuration
Load sequence
Validation and sign-off
Cutover and rollback
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.
Related Tools
Epicor Kinetic Upgrade Readiness Assessment
Ten questions scoring how ready your customizations, BPMs, reports and integrations are for an Epicor upgrade.
EpicorEpicor BPM Directive Types Reference
Lookup table of Epicor BPM directive types, when each runs, whether it can stop a save, and typical use.
EpicorEpicor Business Object Service Reference
Lookup table of common Erp.BO services with their main table, primary key and standard method names.
EpicorEpicor Job Lifecycle Flags Reference
Lookup table of the job status flags on Erp.JobHead and related tables, what they mean and how to use them in BAQs.
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
New to Epicor ERP? Start with the Epicor ERP guide and toolkit, or plan with Training Path Builder, ERP Certification Study Planner, Upgrade Path Planner.
Keep exploring
Free tools
- Epicor DMT Data Load Plan WorksheetSequence your Epicor Data Management Tool loads with record counts, rates and estimated run time, then export the plan to Excel.
- Epicor DMT Data Load Time CalculatorPlan DMT load windows by combining record counts, throughput, error rates and fix time into total hours.
- Epicor DMT Load Time EstimatorEstimate DMT run time from record count, measured rate, rejection percentage and rehearsals, and see how rate changes the total.
ERP fixes and how-tos
- How to import data with Epicor DMT (Data Migration Tool)Step by step guide to Epicor Data Migration Tool (DMT): generating templates, mapping fields, preprocessing steps, running imports, and reading the error log for failed rows.
- Epicor BPM Runtime Error: Where to Look and How to Fix ItHow to diagnose an Epicor BPM runtime error: where to find it in the server log, the common causes (null reference, compile, directive order) and fixes.
- Epicor BPM Send Email: Widget, Function and SMTP SetupHow to send email from an Epicor Kinetic BPM or Epicor Function: SMTP prerequisites, Send Email widget settings, attachments, and a test method that works.
AI on your ERP
- AI for Epicor Kinetic, Beyond What Prism CoversAdd AI to Epicor Kinetic beyond Prism: private LLM over BAQs, BPM data, and REST v2, on-prem or private cloud, with honest guidance on when Prism already covers you.
- Private AI for Epicor Kinetic Cloud, Outside the Multi-Tenant BoundaryRun a private LLM on Epicor Kinetic private cloud or Kinetic Cloud data via BAQs, REST v2 and Data Fabric, keeping sensitive manufacturing data off shared AI.
Integrations
- How to add WhatsApp to Epicor KineticHow to connect WhatsApp Business to Epicor Kinetic: REST and BPM triggers, template messages, opt-in rules and two-way replies that post back to the ERP.
- How to add an AI chatbot to Epicor KineticAdd an AI chatbot to Epicor Kinetic: an internal assistant for planners and buyers or a customer portal bot, grounded in BAQs and runnable fully on-prem.