EpicorFree worksheetPDF, Excel, Word exportEpicor Kinetic

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.

Download:

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%

Total records mapped

34,960

Total errors

362

Overall error rate

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.

Talk to an Expert Explore More Free Tools

Related Tools

Epicor

More Epicor tools

See all

Back to All Tools