Upgrade Path Planner

Infor LN upgrade path planner: Baan IV, Baan 5, LN 6.1 and 10.x

Pick the Baan or LN release you run today and the LN 10.x release or LN Cloud tenant you are moving to. The planner lays out Infor's documented update route (Installation Wizard, Component Merge Tool, Data Upgrade Engine, Unicode conversion from 10.7), what changed in every release you cross, and a risk score, effort range and regression test plan sized to your customizations, integrations and reports.

Free, runs in your browser, no sign-in needed. Release data checked 2026-10 against 18 cited sources.

1Releases
Verify with vendorRelease years not verified. Infor's update guide covers SP0, SP1, FP2 to FP8.
Verify with vendorInfor publishes an LN 10.8 documentation library. GA date not verified.
On-premises or hosted
2Landscape
What to count in LN
customizations:
Modified 4GL program and report scripts, DAL and user exit changes, custom sessions and tables, 3GL functions, customer-defined fields and form changes in customer VRCs.
integrations:
ION and BOD flows, Adapter for LN, BDE or web service clients, Infor OS, WMS, MES, PLM, EDI translators, CRM.
interfaces:
Exchange schemes, bdbpre and bdbpost jobs, ASCII file imports, EDI conversion setups, bank and tax files, direct SQL readers.
reports:
Custom LN report scripts and layouts, Report Designer layouts, SSRS or Cognos reports through the Enterprise Server connectors.
sites:
LN environments or logistic and financial company groups that are upgraded and tested separately.
Modules in use
Integration types
LN 6.1 (SP0 to FP8)LN 10.8

In-place feature pack update: Infor's update guide takes LN 6.1 (SP0 onwards) and every 10.x release to the target with the Installation Wizard, a new package combination and the Data Upgrade Engine. No intermediate release is documented, but pre-steps depend on your source level.

Steps
15
1 to confirm
Releases crossed
7
LN 10.4 to 10.8
Risk
61 / 100
High
Effort
210-492 d
about 11-25 person-months
  1. 1
    PreparationDocumented

    Build a test environment from production and back up the LN environment

    Infor's update guide opens with one instruction: back up the LN environment before you install any update. Run the full update first on a copy of production so the Data Upgrade Engine runtime and any data errors are known before the cutover.

    Source 1
  2. 2
    PreparationDocumented

    LN 6.1 sources: finish open invoicing, project cost and bank statement data

    Before installing LN 10.2 or later, data must be processed on the old feature pack. Invoicing (cisli) is restructured: post every invoice with status Printed using Post Invoices (cisli3200m000) and check that Billing Requests (cisli2100m000) shows none left, or data is corrupted and cannot be converted. Project (tpppc): approve and process all costs and revenues with Global Approving (tpppc4200m000) and Process Transactions (tpppc4802m000), because the five cost type tables are merged into one. Electronic Bank Statements: post open statements through Post Electronic Bank Statements (tfcmg5222m000). EDI conversion setups for the invoice message changed in 10.5.x; download the definitions for the target version.

    Source 1
  3. 3
    PreparationDocumented

    Install the PMC prerequisites for your current Enterprise Server level

    The update guide lists the PMC solutions to install first for LN SP0, SP1/ES7, FP2/ES8.2 and FP3/ES8.3 environments. From FP3/ES8.4 onwards there are no prerequisites. Enterprise Server 8.4 introduced maintenance licensing, so older environments add product id 10365 to the Solution License Manager. Sites still on Adapter 2.6 or 2.7 must choose to move to the Adapter delivered with Enterprise Server AddOn or keep the old one.

    PMCSolution License ManagerSource 1
  4. 4
    ConversionDocumented

    Convert single-byte or multibyte environments to Unicode (target 10.7 or later)

    As of LN 10.7, updating a non-Unicode environment is no longer supported, so the database must first be converted to the new Unicode standard. The Unicode Migration Guide lists the prerequisites: LN with Enterprise Server 10.5.1 or later, porting set 9.1b.01 or later, Oracle or Microsoft SQL Server (DB2 uses the earlier conversion procedure), and no multiple database configurations. It uses parallel bdbreconfig runs driven from a central session. Skip this step if the environment is already Unicode.

    bdbreconfigUnicode Migration GuideSource 1Source 3
  5. 5
    ValidationDocumented

    Validate data against domain constraints before the data upgrade

    Run Validate Data Integrity (ttaad4233m000) for each company that will be upgraded and fix what it reports. Data loaded with bdbpost while ignoring domain constraints causes error 205 (Out of range) when the Data Upgrade Engine updates those records. The session only selects data, so it can run during online hours, split by company.

    Source 1
  6. 6
    UpgradeDocumented

    Stage the installable units and run the Installation Wizard full update

    Create a new staging area with the Staging Wizard (never reuse an old one) holding the Installation Wizard, latest ES Porting Set, ES PMC Solutions, ES AddOn PMC Solutions and the LN PMC Solutions with the BOD package. Stop the environment, then run the full update. The LN PMC Solutions IU carries the application update to the new feature pack and the BODs used for integration. Enterprise Server (tools) can also be updated on its own ahead of the application.

    Staging WizardInstallation WizardES Porting SetLN PMC SolutionsSource 1Source 2Source 13
  7. 7
    UpgradeDocumented

    Create the new package combination and update VRCs

    When the LN PMC Solutions IU is installed you create a new package combination and new update VRCs for the LN, BO and TA packages, for example 107U 0 a000, 107U 0 b000 and 107U 0 t000 with package combination 1070000 for 10.7. Customer VRCs and derived-from structures must be rebuilt on top of the new base before customizations are merged.

    Source 1
  8. 8
    ConversionDocumented

    Merge customizations into the new release with the Component Merge Tool

    Create a derived-from VRC structure in the new release that matches the old one, copy customized components with Copy Software Components (ttadv6265m000), set up Merge Data (ttcmt0500m000), link scripts by merge code (ttcmt4110m000), simulate and then run Merge Script Parts (ttcmt4220m000), and remove merge comments with Delete Merge Comments (ttcmt4251m000) once the scripts work. Every merged script, DAL and report then needs a compile and a test.

    Component Merge ToolSource 15Source 4
  9. 9
    UpgradeDocumented

    Move companies to the new package combination

    As a super user linked to the target package combination, run Change Package Combination by Company (ttaad1101m000), Change Package Combination for Users (ttaad2200m000) and Convert Changes to Runtime (ttams2200m000), then log on again. A company not yet converted reports that it needs a data upgrade; run Create Tables (ttaad4230m000) per company and check table sharing data.

    Source 1
  10. 10
    UpgradeDocumented

    Run the Data Upgrade Engine for every company

    Companies on the new package combination show status Upgrade Needed in Companies (ttaad1100m000). If you use table sharing, adjust it manually with the Table Sharing Modeler first. In Data Upgrade Runs (ttspt2500m000), initialize the run, check that the Source Feature Pack is the one you are coming from (Global Change Source Feature Pack in ttspt2520m000 corrects it), optionally simulate, then run the Data Upgrade Engine. This is required for every feature pack upgrade.

    Data Upgrade EngineSource 1
  11. 11
    ValidationDocumented

    Refresh integration mapping and tax defaulting

    Run Initialize Mapping Scheme Data (tcfin0210m000), copy the active mapping scheme to a new version in Mapping Scheme (tfgld4573m000), check it, resolve errors and activate it. Review tax defaulting (General Company Data, Tax Parameters, Tax Codes by Country, Tax Handling, Tax Numbers by Business Partner) and use Test Tax Model (tctax8100m000) to simulate scenarios.

    Source 1
  12. 12
    ConversionDocumented

    LN 6.1 sources: post-upgrade conversions

    Invoices moved from cisli205 to cisli305 in LN 10.2, so Report Archiving Rules (ttaad3542m000) split fields must be changed. Customized forms from FP5 or earlier need unique field identifiers (UUID conversion). Run Update History Counter Posting (tdsta2299m000) when coming from FP1 to FP3, Generate Order Planning (cprrp1210m000) for SP1 and later, and Clear Obsolete Invoice Tables (cisli9205m000) once the data upgrade is complete. Instruments need an instrument group (qmptc0124m000) after moving from a release without that field.

    Source 1
  13. 13
    ConversionDocumented

    From 10.5 or earlier: generate subcontracting models

    From LN 10.6, independent subcontracting purchase orders require a subcontracting model instead of the job shop BOM. Run Generate Subcontracting Models (tisub1230m000) to build them from the old setup and the Approved Supplier List (tdipu0110m200).

    Source 1
  14. 14
    ValidationDocumented

    Restart shared memory and apply the latest Enterprise Server solutions

    Restart the shared memory and logic services so no references to pre-migrated objects remain, install the latest generic tools solution, and check the tools build with the Support Information Tool (ttsit01000). Shared memory content can be tuned with Shared Memory Data (ttaad4156m000) and its measurement logging.

    Source 1
  15. 15
    CutoverVerify with vendor

    Rehearse, freeze and cut over

    Time at least one full rehearsal with production-sized companies, including Unicode conversion and the Data Upgrade Engine run. Agree a freeze window, complete the open-document steps above in production, run the update, then reconcile key balances and open orders before users return.

Free, optional. Reopen it on any device.
Export plan:

This is a planning model. Before you commit a budget or a date, have an engineer check the path, the effort drivers and the test scope.

How to use the LN upgrade planner

  1. 1

    Pick your releases

    Choose your current release (Baan IV, Baan 5, an LN 6.1 feature pack or LN 10.x) and the target: an on-premises LN 10.x release or LN Cloud.

  2. 2

    Describe your landscape

    Enter counts for customized scripts and sessions, integrations, file and EDI interfaces, custom reports, data size, users and sites, then tick the packages and integrations you use.

  3. 3

    Read the path and the drivers

    Review each step with its Infor source and session codes, the changes in every release you cross, and the drivers behind the risk score and effort range.

  4. 4

    Export the test plan

    Download the regression plan as Excel, Word, PDF or CSV. Tests are flagged critical where your path changes that area, and marked where automation pays back on every feature pack.

  5. 5

    Save or get it reviewed

    Save the plan to your Netray account to reopen later, or send it to an engineer for a written review.

Questions

What is the latest version of Infor LN?

For on-premises customers, the most recent numbered documentation library Infor publishes is LN 10.8. LN Cloud (CloudSuite) is run by Infor and its documentation is published per year, such as 2026.x. Infor does not publish support end dates openly, so confirm the current on-premises release and its support window with Infor.

Can we upgrade from LN 6.1 or 10.x directly to the latest release?

Infor's update guide covers LN 6.1 from SP0 onward and every 10.x release with the same full update: Installation Wizard, a new package combination and update VRCs, then the Data Upgrade Engine per company. No intermediate release is documented, but older sources carry extra steps: PMC prerequisites for SP0 to FP3, and finishing open invoices, project costs and bank statements before installing 10.2 or later.

Why does the upgrade to LN 10.7 or later need a Unicode conversion?

From LN 10.7 an update of a non-Unicode environment is no longer supported. Single-byte and multibyte environments are converted first with the procedure in the Enterprise Server Unicode Migration Guide, which needs Enterprise Server 10.5.1 or later and porting set 9.1b.01 or later on Oracle or SQL Server.

How do we upgrade from Baan IV or Baan 5?

It is a migration. The LN update guide and the Data Upgrade Engine start at LN 6.1, so Baan data and customizations must be mapped onto an LN release first. The Enterprise Server still ships runtime files for Baan IVc (6.1 level) and Baan 5 (6.2 level), so the tools layer can be brought current before the application move. Agree the migration route and landing release with Infor.

What happens to our customizations during an LN upgrade?

Customizations live in customer VRCs. After the new base is installed you rebuild the derived-from structure and merge changed scripts with the Component Merge Tool, simulate, merge, then compile and test. Customer-defined fields, extended in Enterprise Server 10.3 and 10.4 and in LN 10.5, are designed to be added without conflicting with the standard software on upgrade, so moving changes to them lowers future upgrade effort.

How should we test an LN upgrade, and what should we automate?

Check the Data Upgrade Engine results and company status first, then run a regression on a copy of production: platform tests (sign-in, authorizations, jobs, merged customizations, reports, Unicode data), the packages you use, and every integration with saved production files. LN feature packs and solutions keep coming, so the tests marked for automation repay the effort on every update. The planner flags tests as critical where your path changes that area.

Should we stay on-premises or move to LN Cloud?

On-premises LN keeps source-level customizations in your VRCs, at the cost of merging them on every feature pack. LN Cloud is extended through extension points such as table, session, report, BOD and OData extensions. Run the planner with both targets and compare the customization and cloud drivers.

Sources

  1. Infor LN Specific Installation Guide - Updates, 10.7.x (November 2021)
  2. Infor LN Installation Guide, 10.7.x (October 2023)
  3. Infor Enterprise Server Unicode Migration Guide, LN 10.7.x (May 2021)
  4. Infor Enterprise Server Technical Manual, LN 10.7.x (September 2020)
  5. Infor LN 10.7 Release Notes (March 5, 2019)
  6. Infor LN 10.7 documents by type
  7. Infor LN 10.6 Release Notes
  8. Infor LN 10.6 release information (on-premises and CE 2018 notes)
  9. Infor LN 10.5 Release Notes
  10. Industrial Machinery Digest: Infor LN 10.5 released globally (August 8, 2016)
  11. Infor LN 10.4 Version Definition
  12. Infor LN 10.8 documentation library
  13. Infor docs: Infor LN PMC Solutions installable unit (10.8)
  14. Infor LN Documentation Library (Cloud)
  15. Infor docs: Component Merge Tool merge procedure
  16. Infor LN Extensions Development Guide
  17. Infor docs: LN extension points
  18. Infor docs: Product Maintenance and Control (PMC) introduction

Steps marked Verify with vendor are planning inferences, not vendor statements. Effort coefficients are Netray planning assumptions and are shown in full in the Effort tab.