# Baan to Infor LN Data Conversion Mapping Worksheet > Source: https://netray.co/tools/infor-ln-baan-data-conversion-mapping-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Field-level mapping sheet for Baan or legacy data moving into Infor LN, with transform rules, owners and load status. ## Category infor-ln ## Erp Infor LN ## Audience - Data migration lead - LN developer - Functional consultant ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Business entity **Key:** entity **Type:** text #### Source table **Key:** src_table **Type:** text #### Source field **Key:** src_field **Type:** text #### Target LN table **Key:** tgt_table **Type:** text #### Target field **Key:** tgt_field **Type:** text #### Transform rule **Key:** rule **Type:** select **Options:** - Direct copy - Lookup / cross-reference - Concatenate - Split - Default value - Derive - Drop #### Load method **Key:** load **Type:** select **Options:** - Exchange scheme - Session import - BOD / API - SQL load - Manual #### Owner **Key:** owner **Type:** text #### Source rows **Key:** rows_src **Type:** number #### Rows loaded **Key:** rows_loaded **Type:** number #### Row gap **Key:** gap **Type:** number **Expr:** rows_src - rows_loaded **Format:** integer #### Status **Key:** status **Type:** select **Options:** - Not started - Mapped - Tested - Loaded - Signed off **Rows:** **Entity:** Business partner **Src table:** legacy_customer **Src field:** cust_no **Tgt table:** tccom100 **Tgt field:** bpid **Rule:** Lookup / cross-reference **Load:** Exchange scheme **Owner:** Sales ops **Rows src:** 4200 **Rows loaded:** 4188 **Status:** Loaded **Entity:** Item **Src table:** legacy_item **Src field:** descr **Tgt table:** tcibd001 **Tgt field:** dsca **Rule:** Direct copy **Load:** Session import **Owner:** Engineering **Rows src:** 18500 **Rows loaded:** 18500 **Status:** Signed off **Entity:** Item **Src table:** legacy_item **Src field:** unit **Tgt table:** tcibd001 **Tgt field:** cuni **Rule:** Lookup / cross-reference **Load:** Session import **Owner:** Engineering **Rows src:** 18500 **Rows loaded:** 17900 **Status:** Tested **Entity:** Open sales orders **Src table:** legacy_so_line **Src field:** due **Tgt table:** tdsls401 **Tgt field:** ddta **Rule:** Derive **Load:** Session import **Owner:** Sales ops **Rows src:** 960 **Rows loaded:** 0 **Status:** Mapped **Totals:** #### Source rows **Key:** rows_src **Agg:** sum **Format:** integer #### Rows loaded **Key:** rows_loaded **Agg:** sum **Format:** integer #### Rows outstanding **Key:** gap **Agg:** sum **Format:** integer **Summary:** #### Load completeness **Key:** pct **Expr:** sum_rows_loaded / sum_rows_src * 100 **Format:** percent **Notes:** Table and field codes in the example rows are illustrative. Confirm every target table and field against your LN data dictionary and VRC before use. ## Content **Intro:** A data migration fails in the details: a unit of measure that does not match, a status that has no target, a date held as text. This worksheet puts every field decision in one place so the team and the business can see what is mapped, who owns it and how much has loaded. **Sections:** #### How to use it **Body:** Create a row for each source field you intend to carry across. Name the business entity so reviewers can filter by Item, Business partner, Open sales orders and so on. Record source and target table and field, then choose a transform rule. Pick the load method that matches how you will load the data: an exchange scheme, a session import, a BOD or API call, a SQL load or a manual entry for small sets. Enter source rows and rows loaded after each trial run. The row gap column shows what is missing, and the completeness summary gives a single progress number. **Bullets:** - One row per field, grouped by entity - Pick a rule for every row, including Drop - Name an owner who can answer data questions - Update row counts after each trial load #### Choosing transform rules **Body:** Direct copy is rare in practice. Units, statuses, tax codes, currencies and warehouse codes almost always need a lookup table, so keep that cross-reference as its own signed-off artifact and name it in the notes. Concatenate and Split cover fields that were merged or divided differently in the old system. Default value is acceptable only when the business confirms what the value should be. Mark fields you will not carry as Drop, with the owner's agreement, so nobody wonders later whether it was missed. #### Reading the gap and completeness **Body:** A small row gap on a master entity such as business partners usually points to rejected records: duplicate keys, missing mandatory fields or invalid references. Open the load log and group the rejections by reason, then fix the cause in the source or the rule rather than patching individual records. A large gap on transactional entities such as open orders often means the entity was loaded in the wrong sequence. Load masters first, then the transactions that refer to them. Completeness is a progress measure, not a quality measure, so also reconcile values and totals. #### Common mistakes **Body:** Teams map only the fields they can see in the old screens and miss fields used by reports and integrations. They also skip reconciliation: a load that reports success can still carry wrong values. Plan at least two full trial loads and compare record counts, financial totals and a sample of records field by field. Finally, freeze the mapping before the final rehearsal, and put later changes through change control. **Cta:** If your legacy data is messy and the mapping is stalling, we can discuss using a private, on-prem model to profile source data and suggest cross-references, with your team approving every rule. **Faq:** #### Does this worksheet load data into LN? **Answer:** No. It is a planning and tracking sheet. The actual load runs through exchange schemes, import sessions, BODs or your chosen method. Use the sheet to control scope, ownership and progress, and export it to Excel for reviews. #### How many trial loads should I plan? **Answer:** At least two full trial loads before cutover plus a final rehearsal is a sensible minimum. Complex data with many cross-references often needs more. Each trial should have a documented reconciliation. #### What order should entities be loaded in? **Answer:** Load reference data first, then business partners and items, then structures and routings, then open transactions. The rule is that referenced records must exist before the records that point to them. #### Are the example table codes correct for my system? **Answer:** They are illustrative. Table and field names depend on your LN version and customer VRC. Verify them in the data dictionary before you commit them to the mapping. ## Search terms baan data migration mapping template, infor ln data conversion mapping excel, baan to ln field mapping, ln data migration worksheet, legacy erp to infor ln data mapping, data conversion mapping spreadsheet erp --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json