Infor LN and Baan Customization Inventory Worksheet (Excel)
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.
| Ref | Session / object | Type | Module | Business owner | Used in last 12 months | Rework hours (h) | Rate per hour | Estimated cost | Disposition | |
|---|---|---|---|---|---|---|---|---|---|---|
$5,700 | ||||||||||
$2,280 | ||||||||||
$1,520 | ||||||||||
$0 | ||||||||||
$12,600 |
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.
Customization review
Optional: send us your completed inventory and we will give a plain second opinion on the dispositions and the largest risks.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
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.
- 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
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
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
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.
Frequently Asked Questions
What counts as a customization in Baan or LN?
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?
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?
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?
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.
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.
Related Tools
Baan to Infor LN Data Conversion Mapping Worksheet
Field-level mapping sheet for Baan or legacy data moving into Infor LN, with transform rules, owners and load status.
Infor LN & BaanInfor LN Cutover Runbook Template
Editable task-by-task cutover plan with owners, durations, dependencies and total cutover hours.
Infor LN & BaanInfor LN Customization Complexity Scorer
Score how manageable your Infor LN customization portfolio is - and how much risk it adds to every upgrade, CloudSuite move, and support handover.
Infor LN & BaanBaan to Infor LN Migration Readiness Assessment
Score your organization's readiness to migrate from Baan IV or Baan V to Infor LN across ten dimensions, from data quality to executive sponsorship.
More Infor LN & Baan tools
See all- Infor LN Session and Module Code Reference
- Infor LN Production Order Status and Lifecycle Reference
- Infor LN 4GL Session Script Template
- Infor LN Company and Enterprise Unit Design Worksheet
- Infor LN DAL Hook Review Checklist
- Infor LN Warehousing Order Origins and Types Reference
- Infor LN Table Name and SQL Query Builder
- Infor LN Regression Test Effort Calculator
- Infor LN User Role and Authorization Matrix Worksheet