Introduction: Why Epicor DMT Matters for Data-Driven ERP Success
In any Epicor ERP deployment, clean, reliable data is non-negotiable. The Epicor Data Management Tool (DMT) is essential for uploading, updating, and validating data across the system especially during go-lives, module rollouts, or mass record changes.
At Epicforce Tech, we frequently see companies underutilize this powerful tool or skip proper training leading to errors, import failures, or inconsistent records. This guide provides step-by-step Epicor DMT training tips, suitable for new users and system administrators looking to master the tool.
Section 1: What is Epicor DMT and When Should You Use It?
Epicor DMT is a client-side application designed for high-volume data imports into Epicor ERP, including Epicor Kinetic. It uses validated templates and direct connections to safely load:
- Customers and Suppliers
- Inventory and Part records
- BOMs, Routings, and Resources
- Sales Orders and Purchase Orders
- Journal Entries and Financial Data
Use Cases for Epicor DMT:
- Initial ERP implementation data migration
- Module-specific data setup (e.g., production or finance)
- Mass updates to pricing, UOMs, or descriptions
- Ongoing cleanups or legacy record adjustments
Section 2: Preparing for DMT Training Set Your Foundation
1. Get the Right DMT Version
Ensure you have the correct DMT version matching your Epicor build (especially if you’re on Kinetic). Mismatched versions can cause field mapping or validation issues.
2. Request Appropriate Permissions
Your user role must have:
- Access to the DMT tool
- Proper security rights to update records
- Read/write access to the tables being touched
3. Install and Configure DMT
You’ll need:
- DMT client installed on your workstation
- Configured connection to your Epicor environment (Test or Live)
- Access to template folders for .CSV files
Section 3: Understanding DMT Templates Structure & Best Practices
What Is a DMT Template?
Each importable module comes with a structured CSV format. Epicor provides a list of templates inside DMT or through documentation.
Training Tip:
Never create templates from scratch. Use the “Template Builder” feature inside DMT to auto-generate the correct CSV format for each object (e.g., Part, Customer, POHeader).
Best Practices for Working with Templates
- Always save as CSV (comma delimited) not Excel or tab delimited
- Do not modify column headers
- Leave unused columns blank, not deleted
- Maintain field order even if not populated
Section 4: Step-by-Step Training Running Your First Data Load
Let’s walk through the proper sequence to run a typical data import. We’ll use Inventory Part Upload as our example.
Step 1: Select Your Object in DMT
Choose from the left-hand navigation:
Inventory Management → Part → Part
This ensures you’re targeting the correct table.
Step 2: Load Your CSV Template
Click “Browse” to upload your completed CSV file.
Use consistent file naming (e.g., Parts_Import_2025-06.csv) to track versions.
Step 3: Preview Before Import
Click “Validate” to preview your data. DMT will check:
- Required fields
- Data type mismatches
- Referential integrity (e.g., UOM, Class, Sites)
Use this to correct errors before hitting “Import.”
Step 4: Execute the Import
If validation passes:
- Click “Process” or “Import”
- Monitor status logs
- Review the “Results” tab for successes/failures
Step 5: Post-Import Verification
Log in to Epicor and confirm:
- Record counts match
- Key fields (e.g., PartNum, UOMClass) are accurate
- Linked tables (e.g., Sites, Warehouses) populated correctly
Training Tip:
Always import to a Test Environment first. Use the same process in Production only after QA.
Section 5: Common Errors & How to Troubleshoot Them
1. “Column Not Found”
- Check spelling and order in the CSV
- Ensure the file is saved as UTF-8 CSV
2. “Foreign Key Not Found”
- You may be referencing a field that doesn’t exist yet (e.g., UOM or GL Code)
- Resolve by importing dependent records first
3. “Record Already Exists”
- DMT doesn’t automatically overwrite
- You may need to run an Update rather than Insert
Training Tip:
Use Log Files (auto-generated by DMT) to review exact row failures.
Section 6: Advanced Tips for Experienced Users
Batch Uploads
Split large datasets into manageable 1,000–5,000 row batches. Reduces load time and error tracing.
Audit-Friendly Loads
Use consistent naming conventions and maintain:
- Source file logs
- Import logs
- Screenshot proof of successful loads
Use DMT in Scheduled Jobs (Advanced)
DMT can be run from command line, ideal for automation and job scheduling (e.g., daily pricing updates).
Section 7: Epicforce Tech’s Approach to Epicor DMT Training
At Epicforce Tech, our ERP consultants guide clients through:
- Role-based DMT use (admin vs. functional vs. technical)
- Sandbox import testing
- Developing reusable import templates
- Data audit and validation strategies
We empower your teams to handle Epicor data confident whether it’s your first go-live or an upgrade to Kinetic.
Conclusion: DMT Training Is a Must-Have for Every Epicor Admin
Proper training in Epicor’s DMT is not optional it’s foundational to ERP success. It reduces human error, supports data governance, and speeds up change management across modules.
By following this step-by-step guide, your internal team can build DMT proficiency, save time on imports, and reduce costly mistakes.
Need help training your team on DMT best practices?
Reach out to Epicforce Tech for tailored Epicor training plans that fit your system, team, and data governance needs.