# Infor LN Customization Complexity Scorer > Source: https://netray.co/tools/infor-ln-customization-complexity-scorer > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Score how manageable your Infor LN customization portfolio is - and how much risk it adds to every upgrade, CloudSuite move, and support handover. ## Category infor-ln ## Tool **Kind:** assessment **Questions:** #### Roughly how many custom objects (sessions, scripts, reports, tables) exist in your LN environment? **Options:** ##### 500+ or unknown **Score:** 0 ##### 200-500 **Score:** 1 ##### 50-200 **Score:** 2 ##### Fewer than 50 **Score:** 3 #### How were most customizations built? **Help:** Modified standard objects are the most upgrade-hostile technique and block multi-tenant CloudSuite entirely. **Options:** ##### Directly modified standard LN objects **Score:** 0 ##### Mix of modified standard and custom objects **Score:** 1 ##### Mostly custom sessions in separate packages **Score:** 2 ##### Extension points and LN Studio / Extensions only **Score:** 3 #### How well documented is each customization? **Options:** ##### No documentation - code is the only record **Score:** 0 ##### Names and locations listed, no functional docs **Score:** 1 ##### Most have functional descriptions and owners **Score:** 2 ##### All documented with business purpose, owner, and test cases **Score:** 3 #### Do you know which customizations are actually used? **Help:** Usage data is what turns an upgrade from remediating everything into remediating what matters. **Options:** ##### No idea - we assume everything is used **Score:** 0 ##### Anecdotal knowledge from key users **Score:** 1 ##### Partial usage logging on major customizations **Score:** 2 ##### Systematic usage tracking across the portfolio **Score:** 3 #### Are the developers who built your customizations still available? **Options:** ##### No - original developers are gone with no handover **Score:** 0 ##### One person holds most of the knowledge **Score:** 1 ##### Knowledge spread across a small internal or partner team **Score:** 2 ##### Documented codebase maintainable by any qualified LN developer **Score:** 3 #### How are custom integrations and reports built? **Options:** ##### Direct database access and hand-rolled scripts **Score:** 0 ##### Mixed - some direct DB, some supported interfaces **Score:** 1 ##### Mostly supported interfaces with a few exceptions **Score:** 2 ##### ION, BODs, and published APIs throughout **Score:** 3 #### When did you last apply an LN feature pack or version upgrade? **Help:** Regular upgrades are the best evidence that customizations are not blocking you. **Options:** ##### Never, or more than 5 years ago **Score:** 0 ##### 3-5 years ago, and it was painful **Score:** 1 ##### Within 2-3 years with moderate effort **Score:** 2 ##### Regular cadence with predictable, low effort **Score:** 3 #### Is there business willingness to retire customizations and return to standard? **Options:** ##### No - every customization is defended as essential **Score:** 0 ##### Reluctant - would need executive pressure **Score:** 1 ##### Open to it where standard now covers the need **Score:** 2 ##### Active standardization policy with executive backing **Score:** 3 #### What development and testing infrastructure supports custom code? **Options:** ##### Changes made directly in production or a stale test copy **Score:** 0 ##### Basic DEV/TEST landscape, manual promotion **Score:** 1 ##### Managed landscape with change control **Score:** 2 ##### Full landscape with version control and automated regression tests **Score:** 3 **Bands:** #### High Complexity - Customizations Control Your Roadmap **Min:** 0 **Max:** 39 **Verdict:** Your customization portfolio is large, opaque, or built with upgrade-hostile techniques - likely all three. Every upgrade, audit, and support transition will be priced against this uncertainty until you convert it into an inventory with decisions. **Recommendations:** - Run an automated customization inventory with usage analysis before planning any upgrade or CloudSuite move - Freeze new modified-standard-object development immediately - extensions only from today - Capture knowledge from remaining original developers as a named, funded workstream - Classify the portfolio retire / replace-with-standard / rebuild-as-extension, starting with unused objects - Budget upgrades with a heavy customization multiplier until the inventory proves otherwise #### Moderate Complexity - Manageable With Deliberate Cleanup **Min:** 40 **Max:** 69 **Verdict:** You have real customization debt but also real visibility, which puts rationalization within reach. A focused cleanup ahead of your next upgrade will pay for itself in reduced remediation scope, and likely more than once. **Recommendations:** - Add usage logging to the customizations you have not yet measured - it is cheap and decisive - Rebuild your highest-value modified standard objects as extensions during normal maintenance windows - Move remaining direct-database integrations onto ION or supported APIs before they break an upgrade - Establish a customization review board so the portfolio shrinks over time instead of growing - Re-run this scorer after cleanup - crossing into the low-complexity band changes your upgrade economics #### Low Complexity - Upgrade-Friendly Portfolio **Min:** 70 **Max:** 100 **Verdict:** Your customization portfolio is disciplined: extension-based, documented, and governed. Upgrades and even a multi-tenant CloudSuite move are primarily testing exercises for you rather than remediation projects. The task now is protecting that position. **Recommendations:** - Keep the extension-only policy enforced in change control - discipline erodes one exception at a time - Add automated regression coverage for your critical extensions if not already in place - Evaluate CloudSuite multi-tenant seriously - your portfolio shape removes the usual blocker - Use your position to negotiate: clean environments get better fixed-price upgrade terms - Review the portfolio annually and retire anything usage data shows is dormant ## Content **Intro:** This free scorer measures how complex - and how upgrade-hostile - your Infor LN customization portfolio is, built for IT managers and ERP owners planning upgrades, CloudSuite moves, or support transitions. Nine questions cover volume, build technique, documentation, usage visibility, key-person risk, and governance. The output is a complexity band with specific actions, because customization complexity is the single biggest driver of LN upgrade cost variance: two companies with identical user counts can see upgrade quotes differ by 3x based purely on what this assessment measures. **Sections:** #### Why these nine dimensions **Body:** The questions target the factors that determine what a customization portfolio actually costs you. Volume matters less than technique: 300 extension-based customizations upgrade almost for free, while 50 modified standard objects can dominate an entire upgrade budget and categorically block multi-tenant CloudSuite. Documentation and usage visibility determine whether remediation is a scoped decision list or an archaeology project. Key-person risk converts to schedule risk the moment a program depends on one retiring developer. And governance - upgrade cadence, standardization willingness, landscape discipline - predicts whether the portfolio shrinks or grows from here. Each dimension scores 0-3, and your percentage places you in one of three complexity bands. #### The benchmarks behind the scoring **Body:** Patterns from LN and legacy Baan environments give the bands their teeth. What we consistently observe across customization inventories: **Bullets:** - 30-50% of customizations in mature LN estates are unused or duplicate standard functionality that later releases added - Remediating a modified standard object costs 3-5x rebuilding the same logic as an extension, before counting repeat cost at every future upgrade - Environments with usage tracking cut upgrade remediation scope by a third on average, purely by not rebuilding dead code - Undocumented portfolios add 20-40% discovery overhead to any upgrade or migration quote - uncertainty is priced, not absorbed #### What your band means for real decisions **Body:** Use your band as a gate for the decisions in front of you. High complexity means do not sign an upgrade or CloudSuite contract yet - any quote you receive is pricing uncertainty, and an inventory-plus-rationalization phase will reduce both the price and the risk. Moderate complexity means you can plan upgrades, but sequence a targeted cleanup first and re-quote afterward; the cleanup typically pays back within the same program. Low complexity means your negotiating position is strong: pursue fixed-price terms and treat multi-tenant CloudSuite as a live option. In every band, the trendline matters as much as the score - governance determines whether you are climbing or sliding. #### How Netray turns your score into a smaller number **Body:** Netray built AI-assisted analysis tooling specifically for Infor LN and Baan codebases: it inventories every custom object, maps dependencies, detects modified standard code, and correlates objects with actual usage - in weeks, not the months manual inventories take. From that evidence we deliver a rationalization plan with per-object retire, replace, or rebuild decisions and effort estimates you can hand straight to an upgrade program. For high-complexity portfolios we also run extension-conversion sprints that systematically move modified objects to clean extension points, permanently lowering the cost of every future upgrade. **Cta:** Score your portfolio now, then let Netray replace assumptions with an automated customization inventory of your actual environment. **Faq:** #### What is the difference between a modified standard object and an extension? **Answer:** A modified standard object changes Infor-delivered code directly, so every upgrade overwrites or conflicts with your change and it must be re-applied and retested each time - and multi-tenant CloudSuite forbids it outright. An extension adds your logic through supported extension points, LN Studio, or Infor Extensions, leaving standard code untouched. Extensions survive upgrades largely intact, which is why conversion from modifications to extensions is the highest-leverage cleanup an LN customer can do. #### We have hundreds of customizations - is a CloudSuite move impossible? **Answer:** Not impossible, but it must be sequenced. Multi-tenant CloudSuite requires eliminating modified standard objects and moving integrations to supported interfaces, so the realistic path is inventory, rationalize, convert, then migrate. The encouraging pattern: usage analysis typically shows 30-50% of a large portfolio is retireable, and much of the remainder maps to capabilities newer LN releases include as standard. Single-tenant CloudSuite is also an intermediate option with more customization tolerance while you rationalize. #### How long does a customization inventory and rationalization take? **Answer:** With automated code analysis, the inventory itself takes two to four weeks for a typical LN estate, including usage correlation and dependency mapping. The rationalization decisions - workshops with business owners to classify retire, replace, or rebuild - add another two to four weeks. Executing conversions then runs alongside normal maintenance over several months, prioritized by upgrade impact. Compare that to the alternative: discovering the same facts one change order at a time in the middle of a live upgrade program. ## Search terms infor ln customization, ln extension points, infor ln modified standard objects, ln customization assessment, infor ln upgrade risk, ln studio extensions, erp technical debt score --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json