A practical strategy for Baan or Infor LN makes a deliberate choice between three routes. You stabilise the current system, move to Infor LN in the cloud, or replace it with another enterprise resource planning (ERP) system. The right route depends on your version and support phase, your customisations and the Baan or LN expertise you still have in-house.
Legacy ERP can hold years of industrial knowledge and still create growing operational risk. A sound strategy protects the first while reducing the second. The right Baan or Infor LN strategy starts with what still works and what is becoming difficult to sustain.
Which support phase applies to your Baan or LN version?
For Baan IV and Baan 5, also known as Baan V, Infor’s extended maintenance is over. Under the LN lifecycle policy Infor published in 2018, it ran until 30 June 2021. The same applied to LN up to and including version 10.2.1. For LN 10.3, that policy gave 30 June 2023.
Sustaining maintenance follows for as long as Infor offers it. Under Infor’s general lifecycle policy (2022), you then keep access to the support portal and existing fixes. New fixes, updates and regulatory enhancements are not part of that standard scope.
Newer LN versions have their own dates. Under the same 2022 policy, Infor typically gives a year’s notice of the end of mainstream maintenance. The policy is not a contract, and Infor can change it without notice. So ask Infor for the current dates for your version.
According to the Belgian federal government, VAT-liable businesses in Belgium have had to exchange structured e-invoices with each other since 1 January 2026. If your version is in sustaining maintenance, that kind of change falls outside the standard scope under the 2022 policy. Infor may offer something for it at extra cost; otherwise the work falls to your own team or a partner. Read what changes with e-invoicing.
How do you make operational risk and technical debt visible?
Leadership teams need a clear view of operational risk, technical debt and future capability requirements. An assessment should map critical processes, interfaces, data ownership, reporting and support dependencies.
For each customisation, record the process that depends on it, who uses it and who knows the code. Customisations that change Baan or LN standard code do not move unchanged in any cloud route. Map every interface too, with its owner, the party on the other side and the message format. You test customer and supplier interfaces together with those parties, so plan their time as well.
Decide which history moves, what goes to an archive and how it stays accessible. The Dutch Tax and Customs Administration (Belastingdienst) requires you to keep your records for seven years, and data on immovable property for ten. If you keep records digitally, the Belastingdienst must be able to use your programs and files during an audit. Belgium sets its own retention periods; have your tax adviser confirm them.
If you move off Baan, you choose between migrating, archiving or keeping Baan running read-only. Each option has its own licence, platform and management costs. Your CFO puts them in the business case. Download the CFO guide to legacy ERP.
Also record who knows the configuration, interfaces and reports; you need those people in every route. That assessment can distinguish urgent stabilisation work from changes that belong in a future ERP programme. For industrial organisations, the target may include IFS for manufacturing, but the route must start with evidence from the current environment.
Which routes do you have, and when does each fit?
There are three realistic routes. Each one needs a decision about your customisations, your data and the people who know the system. You decide which route to take, based on the same inventory.
Stabilise: keep Baan or LN running on purpose
This route fits when the system supports your critical processes well and the case for a replacement is not yet made. Stabilising needs a plan for expertise, platform and legal change. Record who knows your customisations and document them.
Under Infor’s 2018 LN policy, Infor certifies new versions of third-party software only during mainstream maintenance. The same policy says sustaining maintenance may carry extra fees. So the date your operating system or database loses vendor support is a natural end date for stabilising.
Independent third-party support providers also support Baan and Infor LN outside Infor. If you use one, ask explicitly how they handle legal changes and security. Always give stabilisation an end date, so that delay does not become the strategy.
Move to Infor LN in the cloud
This route fits when LN covers your processes well, your team knows LN and you want little process change. According to Infor, LN runs by subscription in a multi-tenant cloud on AWS, one shared environment for many customers, with regular updates. Infor’s two lifecycle policies cover only software on your own servers, not subscriptions. In the cloud, the end dates above therefore do not apply, and you follow Infor’s update rhythm.
Here too, your customisations do not move unchanged. According to Infor’s documentation, extensions in the cloud may only call LN public interfaces.
Under Infor’s general lifecycle policy (2022), Infor may offer temporary support on your existing licence during such a move. It runs for up to 18 months, at a reduced fee. The conditions are an active subscription or maintenance agreement for the new offering and a written agreement with Infor. Ask early, because that period limits how long both systems can run side by side with support.
Replace with another ERP system
Replacement fits when your processes have changed, customisation has become heavy or the expertise has largely gone. Eqeep advises as an IFS partner working with IFS Cloud, not as an independent selection adviser. For a small administrative requirement, the effort of an implementation can outweigh the benefits. We test that first, and if IFS does not fit, we say so.
If you choose IFS Cloud, expect two release updates a year after go-live. How Eqeep plans them with your team is set out under technical upgrades.
Replacement does not require one high-risk cutover
What the assessment covers
- Critical processes and site dependencies
- Interfaces, modifications and reporting ownership
- Master data, support expertise and operational risk
- Coexistence architecture for a phased transition
Sites, business units or capabilities can often transition in controlled stages, supported by explicit coexistence and data strategies. These stages need deliberate architecture so temporary solutions do not become another permanent layer of complexity.
During coexistence, every master data object has one source system and one owner. Count the double costs too, for two systems under management and the interfaces between them. So agree an end date for the parallel period. What else belongs in an estimate is covered in IFS Cloud cost drivers.
Eqeep describes this kind of split by domain for SAP ECC6. There, asset management or field service, for example, moves to IFS Cloud first, finance stays in SAP and you decide on finance later. See how IFS can run alongside SAP ECC6.
Eqeep supports industrial organisations in evaluating and carrying out this transition, including transitions to IFS Cloud. Our approach combines operational understanding with architecture and programme discipline, helping COO and CTO stakeholders protect continuity while creating room for standardisation and sustainable support.
Baan and Infor LN replacement questions
When should an organisation consider replacing Baan or Infor LN?
Replacement becomes relevant when operational risk, limited vendor alignment, scarce expertise or excessive customisation restricts the business. Frequent integration failures and slow process change are additional signals. So is a version that no longer receives regulatory updates.
Can Baan or Infor LN be replaced in phases?
Yes, provided dependencies are understood and coexistence is designed explicitly. A phased approach may separate sites, legal entities or functional domains and requires firm ownership of master data, integrations and reporting.
Does Infor still support Baan IV and Baan 5?
To a limited extent. Under the LN lifecycle policy Infor published in 2018, extended maintenance for Baan IV and Baan 5 ran until 30 June 2021. Sustaining maintenance follows for as long as Infor offers it, with existing fixes as standard but no new fixes, updates or regulatory enhancements. Ask Infor for the current status of your version.
Can Baan or Infor LN customisations move to the cloud?
Not unchanged. In the cloud version of Infor LN, extensions may only call LN public interfaces. In IFS Cloud you choose per customisation between configuration, an extension outside the product or custom code inside it. So judge each customisation on whether the process still needs the deviation.
Tell us which Baan or LN version you run and which processes depend on it. You get one conversation and a clear next step. Discuss your IFS question.
New articles appear in our newsletter. Subscribe to the newsletter.
