LN Version Landscape and Support Timeline
Infor LN versions follow a release cadence with major versions every 2-3 years and feature packs between majors. 4 and earlier) are approaching or past end of mainstream support, meaning no new fixes without extended support agreements. Current supported versions offer cloud compatibility, modern UI, and ION integration capabilities that older versions lack.
Understanding where your version sits on the support timeline drives upgrade urgency.
- Identify your current LN version and check its support status against Infor's product lifecycle policy
- Map the feature differences between your current version and the target version to build the business case
- Consider jumping multiple versions in a single upgrade rather than incremental upgrades to reduce total effort
- Factor in extended support costs for staying on older versions versus the investment in upgrading
Upgrade Planning Methodology
A successful LN upgrade follows a structured methodology: environment assessment, customization inventory, technical upgrade in a sandbox, functional regression testing, performance validation, user acceptance testing, and production cutover. The customization inventory is the critical path, every BShell modification, custom session, and custom report must be assessed for compatibility with the target version and either migrated, rewritten, or retired.
- Complete a full customization inventory including BShell scripts, custom sessions, reports, and integrations
- Classify each customization: migrate as-is, rewrite for compatibility, replace with standard functionality, or retire
- Execute the technical upgrade in a sandbox first, measuring execution time and identifying breaking changes
- Plan 3-4 regression testing cycles with defined test scripts covering all critical business processes
Feature Roadmap Alignment
Upgrading is an opportunity to adopt new LN capabilities. Recent LN versions introduce modern web UI, ION integration framework, embedded analytics through Birst, and cloud deployment options. Align your upgrade with your digital transformation roadmap, if cloud migration is planned within 2-3 years, upgrade to a cloud-compatible version now.
If embedded analytics is a priority, ensure your target version supports Birst integration.
- Map your strategic IT priorities against the feature availability in each candidate LN version
- Prioritize upgrade to cloud-compatible versions if cloud migration is on your 2-3 year roadmap
- Plan new feature adoption in phases post-upgrade rather than trying to upgrade and transform simultaneously
- Budget for user training on new features separately from the technical upgrade project
Try it here, free
RPG and IBM i Skills Succession Risk Assessment
Score how exposed your IBM i and RPG environment is to retirements, single points of knowledge and missing documentation.
Plan your LN upgrade with confidence, our team has completed 60+ LN version upgrades for manufacturers.