# Epicor Kinetic Data Migration Mapping Worksheet

> Source: https://netray.co/tools/epicor-kinetic-data-migration-mapping-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A field-by-field mapping sheet from legacy data to Epicor, with transformation rules, status and a completion summary.

## Category

epicor

## Erp

Epicor Kinetic

## Audience

- Epicor consultant
- Data migration lead
- Business analyst

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Entity

**Key:** entity

**Type:** select

**Options:**

- Part
- Customer
- Supplier
- BOM
- Open PO
- Open SO
- Open job
- Inventory balance
- GL balance

#### Legacy field

**Key:** legacy

**Type:** text

#### Epicor field

**Key:** target

**Type:** text

#### Transformation rule

**Key:** rule

**Type:** text

#### Required

**Key:** required

**Type:** select

**Options:**

- Yes
- No

#### Data owner

**Key:** owner

**Type:** text

#### Status

**Key:** status

**Type:** select

**Options:**

- Not started
- Mapped
- Tested
- Signed off

#### Records

**Key:** records

**Type:** number

#### Errors in last test

**Key:** errors

**Type:** number

#### Error rate

**Key:** error_pct

**Type:** number

**Expr:** if(gt(records,0), errors / records * 100, 0)

**Format:** percent

**Rows:**

**Entity:** Part

**Legacy:** ITEM_NO

**Target:** PartNum

**Rule:** Trim, upper case, remove spaces

**Required:** Yes

**Owner:** Engineering

**Status:** Mapped

**Records:** 12400

**Errors:** 310

**Entity:** Part

**Legacy:** UOM

**Target:** IUM

**Rule:** Map EACH to EA, PCS to EA

**Required:** Yes

**Owner:** Engineering

**Status:** Tested

**Records:** 12400

**Errors:** 12

**Entity:** Supplier

**Legacy:** VEND_NAME

**Target:** Name

**Rule:** Max length 50, dedupe on tax ID

**Required:** Yes

**Owner:** Purchasing

**Status:** Mapped

**Records:** 860

**Errors:** 40

**Entity:** Inventory balance

**Legacy:** ON_HAND

**Target:** Quantity

**Rule:** By bin and lot, after count

**Required:** Yes

**Owner:** Warehouse

**Status:** Not started

**Records:** 9300

**Errors:** 0

**Totals:**

#### Total records mapped

**Key:** records

**Agg:** sum

**Format:** number

#### Total errors

**Key:** errors

**Agg:** sum

**Format:** number

**Summary:**

#### Overall error rate

**Key:** overall_err

**Expr:** if(gt(sum_records,0), sum_errors / sum_records * 100, 0)

**Format:** percent

**Primary:** true

**Notes:** Epicor field names above are examples. Confirm the exact target fields and required values in your version before loading.

## Content

**Intro:** 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.

**Sections:**

#### How to use the worksheet

**Body:** 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.

**Bullets:**

- One row per field, not per table
- Write rules that someone else can implement
- Update status after each test load

#### Typical transformations

**Body:** 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

**Body:** 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

**Body:** 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.

**Bullets:**

- No data owner per entity
- Cleansing left until the final load
- Required fields not identified

**Cta:** 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.

**Faq:**

#### Does this work with the Data Management Tool?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** No. It is a planning and tracking tool. Export it to Excel and use it as a reference when building the actual load files.

## Search terms

epicor data migration mapping, erp data mapping template excel, epicor conversion mapping spreadsheet, legacy to epicor field mapping, epicor data conversion plan, epicor dmt mapping

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json