# SyteLine Data Conversion Mapping Worksheet

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

## Short answer

An editable source to target mapping sheet for SyteLine migrations, with transform rules, owner, record counts and a completion summary.

## Category

syteline

## Erp

Infor SyteLine

## Audience

- Implementation consultant
- Data migration lead
- ERP project manager

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Data object

**Key:** object

**Type:** select

**Options:**

- Item
- Customer
- Vendor
- BOM
- Routing
- Open PO
- Open CO
- Open Job
- On-hand inventory
- GL balance

#### Legacy field

**Key:** source

**Type:** text

#### SyteLine target field

**Key:** target

**Type:** text

#### Transform rule

**Key:** rule

**Type:** text

#### Owner

**Key:** owner

**Type:** text

#### Source records

**Key:** records

**Type:** number

**Format:** integer

#### Rejected in trial load

**Key:** rejected

**Type:** number

**Format:** integer

#### Reject rate

**Key:** reject_pct

**Type:** number

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

**Format:** percent

#### Status

**Key:** status

**Type:** select

**Options:**

- Not started
- Mapped
- Trial loaded
- Validated
- Signed off

**Rows:**

**Object:** Item

**Source:** PART_NO

**Target:** Item

**Rule:** Uppercase, trim, max 30 chars

**Owner:** Materials

**Records:** 18400

**Rejected:** 212

**Status:** Trial loaded

**Object:** Item

**Source:** UOM_CODE

**Target:** U/M

**Rule:** Cross reference table to SyteLine U/M

**Owner:** Materials

**Records:** 18400

**Rejected:** 36

**Status:** Mapped

**Object:** Customer

**Source:** CUST_ID

**Target:** Customer Number

**Rule:** Left pad to agreed length

**Owner:** Sales

**Records:** 2150

**Rejected:** 14

**Status:** Validated

**Object:** Vendor

**Source:** SUPPLIER_CD

**Target:** Vendor Number

**Rule:** Merge duplicates by tax ID

**Owner:** Purchasing

**Records:** 1320

**Rejected:** 61

**Status:** Trial loaded

**Object:** On-hand inventory

**Source:** QTY_ONHAND

**Target:** Qty on hand by location

**Rule:** Use physical count at cutover

**Owner:** Warehouse

**Records:** 9600

**Rejected:** 0

**Status:** Not started

**Object:** GL balance

**Source:** ACCT_BAL

**Target:** Opening balance by account

**Rule:** Map old chart to new chart

**Owner:** Finance

**Records:** 640

**Rejected:** 3

**Status:** Mapped

**Totals:**

#### Total source records

**Key:** records

**Agg:** sum

**Format:** integer

#### Total rejected

**Key:** rejected

**Agg:** sum

**Format:** integer

#### Worst reject rate

**Key:** reject_pct

**Agg:** max

**Format:** percent

**Summary:**

#### Overall reject rate

**Key:** overall_reject

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

**Format:** percent

**Primary:** true

**Description:** Rejected records divided by all source records across the mapping lines.

#### Mapping lines

**Key:** lines

**Expr:** count

**Format:** integer

**Notes:** Add one line per field, not per object, once the design is stable. Record counts are per load, so repeat the object for each load attempt or keep counts on the key field line. Replace target field names with the exact labels in your SyteLine version.

## Content

**Intro:** Data conversion is where SyteLine projects slip. This worksheet gives every legacy field a target, a rule, an owner and a measured reject rate, so you see problems after the first trial load and not at cutover.

**Sections:**

#### How to use the worksheet

**Body:** Add a row for each legacy field you intend to bring across, pick the data object, then name the SyteLine target field and write the transform in plain language. After each trial load, enter the source record count and the number rejected. The reject rate is computed for you per line and overall. Export to Excel to share with business owners who sign off each object.

**Bullets:**

- One owner per line, a named person.
- Write the transform so a new analyst can code it.
- Move status forward only with evidence.
- Keep rejected record lists with the trial results.

#### Reading the reject rate

**Body:** A reject rate under one percent on master data after the second trial load is a reasonable goal, but the right threshold depends on the object. Ten rejected items out of ten thousand is cleanup work; ten rejected opening GL accounts out of a hundred is a blocker. Use the worst line figure to find the field that needs attention first and the overall rate for steering committee reporting.

#### Typical load order

**Body:** Reference data comes first: units of measure, currencies, terms, tax codes, chart of accounts, sites and warehouses. Then items, customers and vendors, then bills of material and routings, then open orders, and last on-hand inventory and balances at cutover. Loading out of order creates rejects that are really dependency errors rather than data errors.

#### Common mistakes

**Body:** Teams migrate years of closed history nobody will use, skip duplicate cleanup in vendor and customer masters, map units of measure by guesswork and leave on-hand inventory until the last night. Decide what to leave in the archive, reconcile quantities and values to the legacy ledger, and rehearse the final load at least twice.

**Cta:** If you are moving from an older ERP into SyteLine and want agents to profile source data and draft mappings for your consultants to review, get in touch.

**Faq:**

#### Should I map every legacy field?

**Answer:** No. Map the fields that drive current transactions and reporting, and archive the rest. Each field migrated has to be cleaned, tested and reconciled, so unneeded fields add risk without adding value.

#### What tool loads the data into SyteLine?

**Answer:** Teams commonly use the standard import and load utilities, IDO based web services or custom scripts. Choose per object, and keep the transform rules in this sheet independent of the loader so they survive a change of method.

#### How many trial loads are enough?

**Answer:** Plan at least three: an early structural load, a full volume load with business validation, and a dress rehearsal timed like cutover. Keep reject rates and timing from each in this sheet to show convergence.

#### How do I handle open transactions?

**Answer:** Prefer to close out what you can in the legacy system and migrate only genuinely open orders, jobs and balances. Reconcile each migrated open item to a source report and have its business owner sign it off.

## Search terms

syteline data conversion template, syteline data migration mapping excel, erp data mapping template, syteline data conversion worksheet, legacy to syteline field mapping, erp data migration mapping spreadsheet, syteline cutover data load, source to target mapping template

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