# Infor LN and Baan Customization Inventory Worksheet (Excel) > Source: https://netray.co/tools/infor-ln-baan-customization-inventory-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Editable worksheet to list every Baan or LN customization with type, owner, effort and a retire, keep or replace decision. ## Category infor-ln ## Erp Infor LN ## Audience - LN developer - ERP architect - Migration lead ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Ref **Key:** ref **Type:** text #### Session / object **Key:** object **Type:** text #### Type **Key:** type **Type:** select **Options:** - Session - Report - Table field - DAL hook - Script - Library - Integration - Form #### Module **Key:** module **Type:** text #### Business owner **Key:** owner **Type:** text #### Used in last 12 months **Key:** used **Type:** select **Options:** - Yes - No - Unknown #### Rework hours **Key:** hours **Type:** number **Unit:** h #### Rate per hour **Key:** rate **Type:** number **Format:** currency #### Estimated cost **Key:** cost **Type:** number **Expr:** hours * rate **Format:** currency #### Disposition **Key:** action **Type:** select **Options:** - Retire - Keep as is - Rebuild - Replace with standard - Replace with extension - Investigate **Rows:** **Ref:** C-001 **Object:** Custom pricing session **Type:** Session **Module:** Sales **Owner:** Sales ops **Used:** Yes **Hours:** 60 **Rate:** 95 **Action:** Rebuild **Ref:** C-002 **Object:** Customer pick list report **Type:** Report **Module:** Warehousing **Owner:** Logistics **Used:** Yes **Hours:** 24 **Rate:** 95 **Action:** Replace with standard **Ref:** C-003 **Object:** Extra field on item table **Type:** Table field **Module:** Common **Owner:** Engineering **Used:** Yes **Hours:** 16 **Rate:** 95 **Action:** Replace with extension **Ref:** C-004 **Object:** Legacy label export script **Type:** Script **Module:** Shop floor **Owner:** Production **Used:** No **Hours:** 0 **Rate:** 95 **Action:** Retire **Ref:** C-005 **Object:** EDI inbound order converter **Type:** Integration **Module:** Sales **Owner:** IT **Used:** Yes **Hours:** 120 **Rate:** 105 **Action:** Rebuild **Totals:** #### Total rework hours **Key:** hours **Agg:** sum **Format:** hours #### Total estimated cost **Key:** cost **Agg:** sum **Format:** currency #### Customizations listed **Key:** ref **Agg:** count **Format:** integer **Summary:** #### Average hours per item **Key:** avg_hours **Expr:** sum_hours / count **Format:** decimal #### Average cost per item **Key:** avg_cost **Expr:** sum_cost / count **Format:** currency **Currency:** $ **Notes:** Start from the customer VRC and list every object that differs from the standard package VRC. Confirm usage from session audit or user statistics, not from memory. Rates are placeholders. ## Content **Intro:** Every Baan or LN migration and upgrade starts with the same question: what did we change, and does anyone still use it? This worksheet gives you a structured list you can fill in with the business and export to Excel. **Sections:** #### How to use the worksheet **Body:** Add one row per customized object. Use the Type column to separate sessions, reports, table fields, DAL hooks, scripts, libraries, integrations and forms, because each is migrated differently. Record the business owner so someone can sign off on retirement. Fill Used with Yes, No or Unknown and treat Unknown as a task, not an answer. Enter rework hours and a blended rate, and the cost column computes. The disposition column drives the plan: Retire costs nothing, Replace with standard needs a fit check, Rebuild needs a developer. **Bullets:** - One row per object, not per project - Compare against the standard package VRC, not last year's backup - Mark unknown usage and chase it with audit data - Keep the business owner name next to every Rebuild #### Where the inventory comes from **Body:** In Baan and LN the customer VRC holds changed or new objects layered over the standard package VRC. Compare objects between those layers, and add table definitions with extra fields, report layouts, scripts attached to sessions and DAL hooks. Add objects outside the VRC too: interface programs, scheduled jobs, shell scripts and spreadsheets that read LN data. Each source tends to miss one category, so combine at least two sources and let the business reviewers add what the technical scan cannot see. #### Reading the totals **Body:** Total hours and cost give a first-pass rework envelope, and the average per item shows whether your estimates are plausible. A long list of small Replace with standard rows is good news, because it means the customization exists mainly from habit. A short list with a few very large Rebuild rows is where migration risk concentrates. Sort by cost and review the top ten with the business first. Treat the output as a planning estimate until a developer has opened each large item. #### Common mistakes **Body:** Teams usually undercount reports and integrations, which are less visible than sessions. They also keep objects because deleting feels risky, even though no one has run them in years. Another mistake is estimating hours before choosing the disposition, which inflates the plan. Decide Retire, Replace or Rebuild first, then estimate only the rows that remain. Finally, do not treat the inventory as one-time: update it whenever a change request closes. **Cta:** If you want the inventory built from your actual VRC and usage data rather than by hand, we can talk through how an on-prem AI assistant can help read LN customizations without moving your data out. **Faq:** #### What counts as a customization in Baan or LN? **Answer:** Anything that differs from the standard package VRC: changed or new sessions, reports, tables and fields, scripts, DAL hooks, libraries, forms and external interfaces. Spreadsheets and scripts that read LN data are not in the VRC but still need migrating, so include them. #### Should I list unused customizations? **Answer:** Yes. List them with Used set to No and a Retire disposition, so the decision is recorded and signed off by the owner. An unlisted object that silently disappears in an upgrade creates a support call later. #### How accurate are the hour estimates? **Answer:** They are planning figures. Use them to rank items and size the budget, then have a developer review the largest rows before committing a fixed price or date. Expect ranges, not single numbers. #### Can I use it for an LN to LN upgrade? **Answer:** Yes. The same columns work for an upgrade or a move to a newer LN release, where the question is which customizations survive, which are replaced by standard features and which must be rebuilt. ## Search terms baan customization inventory, infor ln customization list excel, baan to ln migration customization assessment, infor ln custom sessions inventory, ln customization tracking spreadsheet, baan 4gl customization catalogue, infor ln upgrade customization review --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json