Epicor Kinetic Data Migration Mapping Worksheet
A mapping sheet is the contract between the legacy system and Epicor. If a field has no owner or no rule, it will break on load day. This worksheet makes the rules, owners and error rates visible.
| Entity | Legacy field | Epicor field | Transformation rule | Required | Data owner | Status | Records | Errors in last test | Error rate | |
|---|---|---|---|---|---|---|---|---|---|---|
2.5% | ||||||||||
0.1% | ||||||||||
4.7% | ||||||||||
0% |
Epicor field names above are examples. Confirm the exact target fields and required values in your version before loading.
Data profiling support
Share a sample extract and we can discuss profiling and cleansing on your own infrastructure.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
Add one row per field. Name the entity, the legacy field, the Epicor field, the transformation rule and the person who can answer questions about it. After each test load, enter record counts and errors, and the error rate is calculated. Export to Excel for the data team. Replace the sample rows.
- One row per field, not per table
- Write rules that someone else can implement
- Update status after each test load
Typical transformations
Most mapping work is clean-up: trimming and standardising part numbers, mapping units of measure to the target list, splitting address lines to fit field lengths, and removing duplicates in customer and supplier records. Opening balances need rules too, such as loading inventory by bin and lot after a physical count. Write each rule in a sentence so testers can verify it.
Reading the error rate
The error rate is errors divided by records, as a percentage. A high rate in an early test is normal; the trend matters. If errors for one field stay high after several loads, the rule is wrong or the source data needs cleaning by its owner. Set a target, such as zero errors on required fields, before the final load.
Common mistakes
Teams map technical field names without business owners, so nobody can answer why a value looks odd. Others skip cleansing and discover duplicates after go-live. Assign owners early and agree sign-off criteria for each entity.
- No data owner per entity
- Cleansing left until the final load
- Required fields not identified
Frequently Asked Questions
Does this work with the Data Management Tool?
It supports any load method. Use the mapping to prepare load templates for Data Management Tool or other approaches. The sheet captures decisions; the load mechanics depend on your chosen tool.
How do I know the Epicor field names?
Check the field list for the relevant table or service in your version, and the required fields for each load type. Names vary by entity and release, so verify rather than copy examples.
What error rate is acceptable?
For required fields, aim for zero before go-live. Optional fields may allow small exceptions that you document and fix later. Agree the threshold with data owners in advance.
Can I load the worksheet into Epicor?
No. It is a planning and tracking tool. Export it to Excel and use it as a reference when building the actual load files.
If your source data is messy, we can help build a private data profiling assistant that finds duplicates and inconsistent values on your own servers.
Related Tools
Epicor Kinetic Go-Live Cutover Plan Template
A fill-in cutover plan covering system freeze, opening balance loads, validation and go/no-go decisions for an Epicor go-live.
EpicorEpicor Kinetic Data Load Effort Calculator
Estimate total data migration hours for an Epicor project from record counts, error rate and number of test cycles.
EpicorEpicor Kinetic Customization Change Request Form Template
A fill-in change request form for Application Studio customizations, BPM directives and Epicor Functions, with test and rollback sections.
EpicorEpicor Kinetic Custom Report Inventory Worksheet
An editable register of custom reports, BAQs and dashboards to support upgrade testing and clean-up of unused items.
More Epicor tools
See all- Epicor Kinetic User Access Request Form Template
- Epicor Kinetic BPM Directive Inventory Worksheet
- Epicor Kinetic Scheduled Task Register Worksheet
- Epicor Business Object Services Reference
- Epicor BAQ Performance Tuning Checklist
- Epicor Administration Maturity Assessment
- Epicor BAQ Calculated Field Examples Reference
- Epicor Function Library Design Template
- Epicor SSRS Report Template Checklist
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 Kinetic Data Load Effort CalculatorEstimate total data migration hours for an Epicor project from record counts, error rate and number of test cycles.
- Epicor Kinetic Upgrade ChecklistA phase-by-phase upgrade checklist covering inventory, testing, integrations, cutover and rollback for Epicor Kinetic.
- Epicor Kinetic Job Status ReferenceA searchable lookup of the job lifecycle flags and related fields in Epicor Kinetic job entry, so you can build BAQs and dashboards with the right filter.
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.
- Preserving Customizations When Upgrading to Epicor KineticMoving Epicor 10 classic customizations to the Kinetic web UI is a conversion, not an automatic carry-over. Here is the checklist for what survives, what needs rework, and how to sequence the upgrade.
- How to Add AI to Epicor Kinetic On-Premises Without Moving Your DataReference architecture for a private AI assistant on Epicor Kinetic on-premises: BAQ and REST v2 access, SQL replica, local LLM, roles, audit and rollout.
Guides
- Epicor vs Infor: Should You Switch ERP Platforms?Compare Epicor Kinetic vs Infor CloudSuite for manufacturing. Functional analysis, migration costs, and decision framework for switching platforms.
- ERP Data Mapping Best PracticesMaster ERP data mapping with source-to-target techniques, transformation rules, and field-level documentation. Prevent data loss during ERP migration.
AI on your ERP
- 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.
- Epicor Kinetic AI for Metal Fabrication: Jobs, Heat Numbers and Outside Processing in Plain EnglishPrivate AI on Epicor Kinetic for metal fabricators: ask about jobs, nests, heat numbers and outside processing in plain English, grounded in live data.
Integrations
- How to add AI agents to Epicor KineticHow to add AI agents to Epicor Kinetic: a tool layer over the REST v2 API and BAQs, MRP exception triage, PO expediting, and human approval before any write.
- How to build an MCP server for Epicor KineticDesign a Model Context Protocol server for Epicor Kinetic: which read tools to expose, BAQ and REST v2 mapping, auth, stdio vs HTTP transport and audit logging.
Software
- Epicor KineticEpicor Kinetic explained for manufacturers: modules, REST API, BAQs, deployment, strengths, limits and alternatives to compare before choosing or upgrading.
- Epicor CPQEpicor CPQ is a cloud configure-price-quote product with visual 3D configuration for manufacturers. Modules, ERP integrations and alternatives explained.