Baan IV or Baan 5 still in production: migrating to ERPNext instead of Infor LN Cloud
Short answer
Infor’s own Infor LN Product Lifecycle Policy (March 2023 edition) shows Extended Maintenance for Baan 4, Baan 5.0b, 5.0c, 5.1 and 5.2 ended on June 30, 2021, along with LN FP1 to FP7 and LN 10.2.1. Sustaining Maintenance continues, with its end “to be determined”. In Infor’s policy, Sustaining means access to pre-existing fixes only: no new fixes, updates or regulatory enhancements. So a Baan IV or Baan 5 site has had no new fixes for years, and the real deadline is people: the developers and administrators who know Baan Tools, your customisations and your database. Infor’s answer is Infor LN, now a multi-tenant cloud ERP on AWS. ERPNext (open source, GPL-3.0, no licence fee) is a credible alternative for sites whose processes are mainstream make-to-order or make-to-stock manufacturing, whose customisations are mostly reports and interfaces, and who want to own their next system. Complex engineer-to-order, aerospace and defence or automotive sites should look hard at LN first. Infor is quote-only, so we give no Infor estimate.
Contents
- Who this guide is for
- What Infor’s LN lifecycle policy says about Baan
- What Sustaining Maintenance means in practice
- The real deadline: Baan skills
- Your options
- Where ERPNext fits a Baan site, and where it does not
- A Baan data extraction plan
- A phased plan for leaving Baan
- Questions to ask Infor and your Baan partner
- Costs: what is published
- Decision table
- Best for, and wrong choice when
- Frequently asked questions
Who this guide is for
This guide is for finance directors, operations managers and IT leads at manufacturing sites that still run Baan IV or Baan 5 in production. Many have run it for twenty years or more, often on a Unix or Windows server that has been carefully kept alive, with heavy customisations written in Baan Tools by people who may have long since moved on. Some are single plants; others are subsidiaries of groups that moved the rest of the business to another ERP years ago.
We implement ERPNext, so read our view with that in mind. Infor LN is the direct successor to Baan and, for complex project and engineer-to-order manufacturers, often the right destination. This guide is for sites where LN in the cloud is not an obvious fit, or where the business wants a genuine alternative priced before deciding.
It is part of our series on legacy ERP deadlines; the legacy ERP end-of-support hub lists every vendor date we have confirmed. Other Infor guides in the series: Infor LX and BPCS, Infor XA (MAPICS) and SyteLine on-premises.
Sources, checked on Nov 18, 2026: the Infor LN Product Lifecycle Policy (Infor PDF, March 2023 edition, excerpt hosted by an Infor partner), the Infor General Product Lifecycle Policy (PDF on infor.com), the Infor LN product page, the Frappe Cloud pricing page and Frappe Cloud server plans page, the ERPNext repository on GitHub and the ERPNext documentation linked in each section.
About the source
The LN lifecycle policy we cite is an Infor document (each page carries the “Infor LN: Product Lifecycle Policy” footer, and the structure matches Infor’s other lifecycle policies), but the copy we could reach is a five-page excerpt hosted by an Infor partner, and Infor distributes the full policy to customers through its support knowledge base. We found no public copy on infor.com. Check the current version in Infor’s support portal before you rely on any date; Infor’s general policy says lifecycle policies are not contractual, and your maintenance agreement governs.
What Infor’s LN lifecycle policy says about Baan
| Release | General availability | End of Mainstream | End of Extended | End of Sustaining |
|---|---|---|---|---|
| Infor LN 10.8 | March 1, 2023 | To be determined | To be determined | To be determined |
| Infor LN 10.4 to 10.7 | Dec 19, 2014 to March 7, 2019 | To be determined | To be determined | To be determined |
| Infor LN 10.3 | July 31, 2013 | Dec 31, 2019 | June 30, 2023 | To be determined |
| Infor LN 10.2.1 | Dec 21, 2012 | Already in Extended | June 30, 2021 | To be determined |
| LN FP1 to FP7 | Dec 2004 to Jan 31, 2011 | Already in Extended | June 30, 2021 | To be determined |
| Baan 5.1 and 5.2 | 2000 | Already in Extended | June 30, 2021 | To be determined |
| Baan 5.0c | 2000 | Already in Extended | June 30, 2021 | To be determined |
| Baan 5.0b | 1999 | Already in Extended | June 30, 2021 | To be determined |
| Baan 4 (Baan IV) | 1996 | Already in Extended | June 30, 2021 | To be determined |
Source: the product support schedule in the Infor LN Product Lifecycle Policy (Infor PDF, March 2023 edition, excerpt hosted by an Infor partner), checked Nov 18, 2026. The same table shows a 20% Extended Maintenance fee effective January 1, 2020 for the releases that ended Extended in 2021 and 2023, and notes that Extended Maintenance for the releases that ended on June 30, 2021 included Priority 2 fixes. A footnote says industry extensions to Baan IV, such as those built for aerospace and defence, automotive and construction, follow the Baan 4 policy.
The policy also says the Baan and LN technology tools, including the Enterprise Server, LN Studio, the Web UI (Webtop) and Worktop for Baan IV and Baan 5, follow the maintenance policy of the ERP version they run with. Several Baan-era extension products, including the OpenWorld adapters, eService, eSales, eProcurement and the Baan CRM Suite, also show June 30, 2021 in the Extended Maintenance column.
What Sustaining Maintenance means in practice
Infor’s Infor General Product Lifecycle Policy (PDF on infor.com) defines Sustaining Maintenance as “access to pre-existing fixes only; no new product fixes, updates, or regulatory enhancements”, with access to the Infor Support Portal, support staff and the knowledge base. Infor says it continues “for a period of time to be determined by Infor” and “may require payment of an additional fee”.
For a Baan IV or Baan 5 site, that has three consequences:
- No new fixes since mid-2021. Anything you hit now is either already fixed in an old patch, or yours to work around.
- No regulatory changes. New tax, e-invoicing or reporting rules will not be added to Baan. Most long-running sites already handle these with local customisations or side systems.
- Infrastructure risk grows. Your Baan release depends on specific operating system, database and porting set versions. Every server, storage or security change is a test you run yourself.
None of that stops Baan working tomorrow. The risk is slow, and it is mostly about people.
The real deadline: Baan skills
Baan IV was released in 1996 and Baan 5 around 2000, per Infor’s policy. The developers and administrators who built and ran those systems learned their trade a long time ago. Before choosing a destination, take an honest inventory:
Baan skills and dependency inventory
- Who can change a Baan Tools script or session today, and how many hours a month do they spend on it?
- Who administers the Baan server, the database and the porting set? Is that one person or a team?
- Which customisations exist? Sort them into reports and prints, interfaces and EDI, screen and session changes, and business logic.
- Which add-ons or extension products are in use (for example an industry extension, OpenWorld adapters, EDI or a CRM extension)?
- What else depends on the Baan database: a data warehouse, a shop-floor system, a web portal?
- Is there an external Baan support partner, and what happens if they stop?
If one or two named people hold most of that knowledge, the migration deadline is set by their plans, not by Infor’s. Plan the project so they spend their remaining time documenting and extracting, not firefighting.
Your options
| Option | What it involves | Best when |
|---|---|---|
| Move to Infor LN (cloud) | Infor says LN is now a multi-tenant cloud ERP on AWS and the ERP engine inside its CloudSuites for aerospace and defence, automotive and industrial manufacturing | Complex discrete, project or engineer-to-order manufacturing that fits LN’s industry focus |
| Upgrade to a supported LN release on-premises | Ask Infor what on-premises options are available for your licence; the policy lists LN 10.4 to 10.8 with dates to be determined | You must stay on-premises and want to stay with the Baan lineage |
| Stay on Baan IV or Baan 5 on Sustaining | Keep running with pre-existing fixes only | Short term only, while you plan |
| Move to ERPNext | Open-source ERP on Linux; self-host or Frappe Cloud | Mainstream manufacturing processes, customisations mostly reports and interfaces, and a wish to own the next system |
Infor’s Infor LN product page describes LN as built for “complex, global, project-driven discrete manufacturers”, with more than 1,500 customers across aerospace and defence, automotive, high tech, industrial manufacturing and engineering and construction, and support for configure-to-order, engineer-to-order, project-based workflows and assembly-line production. If that describes you, price LN seriously. Infor does not publish LN prices on the pages we checked, so we give no Infor estimate.
Where ERPNext fits a Baan site, and where it does not
| Baan area | ERPNext equivalent | Fit |
|---|---|---|
| Item data, warehouses | Items (ERPNext Item documentation), Warehouses (ERPNext Warehouse documentation) | Good |
| Engineering BOMs and routings | BOMs (ERPNext Bill of Materials documentation), Routings (ERPNext Routing documentation), Workstations (ERPNext Workstation documentation) | Good for make-to-stock and make-to-order |
| Production orders and shop-floor reporting | Work Orders (ERPNext Work Order documentation), Job Cards (ERPNext Job Card documentation) | Good |
| Planning (MRP) | Production Plan (ERPNext Production Plan documentation), Material Request (ERPNext Material Request documentation) | Test with real demand |
| Project manufacturing and engineer-to-order | Projects (ERPNext Project documentation) linked to sales orders and work orders, Timesheets (ERPNext Timesheets documentation) | Partial: works for simpler project jobs; test complex ETO carefully |
| Product configuration | Item Variants (ERPNext Item Variants documentation) | Partial: variants, not a constraint-based configurator |
| Purchasing and subcontracting | Purchase Orders (ERPNext Purchase Order documentation), Subcontracting (ERPNext subcontracting documentation) | Good |
| Quality | Quality Inspection (ERPNext Quality Inspection documentation) | Good for inspection; test your hold and release process |
| Lot and serial traceability | Batch (ERPNext Batch documentation), Serial No (ERPNext Serial No documentation) | Good |
| Multi-company finance | Inter-company invoices (ERPNext inter-company invoices documentation), multi-currency (ERPNext multi-currency accounting documentation), Accounting Dimensions (ERPNext accounting dimensions documentation) | Good |
The honest pattern: ERPNext fits Baan sites that make standard or lightly configured products to stock or to order. It is weaker where Baan was chosen for deep project manufacturing with complex engineering change, multi-level project cost control or constraint-based configuration. For those sites, a fit test with real projects is mandatory, and LN may simply be the better answer.
A Baan data extraction plan
Getting data out of Baan is usually achievable; the challenge is meaning, not access. Baan stores its tables in a relational database through its own database driver, and its data dictionary defines field meanings and enumerated values. In our experience, three routes work:
| Route | How it works | Watch out for |
|---|---|---|
| Baan exchange or export sessions | Use Baan’s own exchange functions to write tables to flat files | Needs someone who can set up exchange schemes; slow on large tables |
| Direct SQL on the underlying database | Read tables directly from the database engine with standard tools | Enumerated values are stored as codes; you need the data dictionary to decode them |
| Reports to spreadsheets | Run existing Baan reports and save the output | Fine for small masters; not for transactions |
Whichever route you use, plan the move like this:
| Baan data | ERPNext target | How |
|---|---|---|
| Items, units, business partners | Items, UOM conversions, Customers (ERPNext Customer documentation), Suppliers (ERPNext Supplier documentation) | Extract, decode, clean, load with Data Import (ERPNext Data Import documentation) |
| Active BOMs and routings | BOMs, Routings, Workstations | Only items you will make again |
| Open sales, purchase and production orders | Sales Orders (ERPNext Sales Order documentation), Purchase Orders (ERPNext Purchase Order documentation), Work Orders | Finish open production orders in Baan where possible |
| Stock by warehouse, lot and serial | Stock Reconciliation (ERPNext Stock Reconciliation documentation) | Physical count before go-live |
| Open receivables and payables | Opening invoices (ERPNext opening balance documentation) | Reconcile to aged reports |
| GL balances | Opening trial balance on a new chart of accounts (ERPNext Chart of Accounts documentation) | Keep Baan read-only, or archived, for history |
Before the server is switched off, take a full database backup and decide how you will answer history questions in five years. A reporting database or a read-only Baan instance on a virtual machine both work; what matters is that someone can still read it when the last Baan expert has gone.
A phased plan for leaving Baan
| Phase | What happens | Typical output |
|---|---|---|
| 1. Inventory | Skills, customisations, add-ons, interfaces and infrastructure; confirm maintenance status with Infor | A risk register and customisation list |
| 2. Extraction proof | Extract and decode items, BOMs and open orders | Clean sample data in spreadsheets |
| 3. Fit tests | Rebuild a product family, a month of orders and a real project in ERPNext | Pass, configure or develop, per area |
| 4. Quotes | Infor LN proposal and ERPNext proposal with the same scope | Five-year comparison |
| 5. Build and test | Configure, rebuild reports and interfaces, two full data loads | Signed-off test cycles |
| 6. Cut-over | Go live at a period end; Baan read-only | Live ERPNext, archived Baan |
Questions to ask Infor and your Baan partner
Whichever way you lean, get these answers in writing before you compare proposals. They turn a vague “Baan is old” worry into numbers you can plan with:
- What is our exact maintenance status today? Ask Infor to confirm, per release and per extension product, whether you are on Sustaining Maintenance and what you pay for it.
- What does Infor offer to move us? Ask what LN in the cloud would cover for your sites, what an on-premises LN option would involve, and whether Infor’s Transitional Support (described in its general policy as a reduced-fee support period of no longer than 18 months while you move to a new offering, by written agreement) would apply.
- Which customisations have a standard LN equivalent? A good LN proposal should map your Baan customisations to standard LN functions, extensions or rebuilds.
- Who supports our Baan system until cut-over? Name the people and the response times. If the answer is one contractor, that is your biggest risk.
- Can we get a full, documented data export? Agree the format, the decoding of enumerated values, and who validates it.
Ask the ERPNext side the same last three questions. A credible ERPNext partner should be able to show you, with your own data, how items, BOMs and open orders land in ERPNext before you sign anything.
Costs: what is published
| Item | USD (published) | GBP | Source |
|---|---|---|---|
| Infor LN subscription, migration services | Quote only; no estimate given | Quote only | Infor LN product page |
| ERPNext software | No licence fee (GPL-3.0) | No licence fee | ERPNext repository on GitHub |
| ERPNext on Frappe Cloud, site plans | From $5 per month | About £3.79 (indicative) | Frappe Cloud pricing page |
| ERPNext on Frappe Cloud, dedicated servers | From $40 per month | About £30.33 (indicative) | Frappe Cloud server plans page |
Frappe Cloud publishes USD prices: site plans from $5 a month (about £3.79) and servers from $40 a month (about £30.33), checked on Nov 18, 2026. The GBP figures are indicative conversions, not Frappe prices.
Indicative GBP conversions use the Bank of England daily spot rate (series XUDLUSS) of US$1.3187 per £1 for 16 Nov 2026, the latest published figure when we checked on Nov 18, 2026. They are not official UK prices: Frappe does not publish a GBP list price for these plans, and your invoice currency, rate and VAT treatment may differ.
On either path, the big costs are people: data extraction and cleaning, process design, testing, training and the time of your own staff. Include the cost of keeping old Baan hardware and specialist support alive in the “do nothing” column.
Decision table
| If this is true for you | Lean towards | Why |
|---|---|---|
| Complex ETO, project control, A&D or automotive | Infor LN | LN is built for that, per Infor |
| Standard make-to-stock or make-to-order | ERPNext worth pricing | Core manufacturing maps cleanly |
| Customisations mostly reports and interfaces | ERPNext worth pricing | Easy to rebuild on any platform |
| Must self-host and own the code | ERPNext | GPL-3.0, self-host or Frappe Cloud |
| Last Baan expert retiring soon | Start extraction now, either way | Knowledge is the critical path |
Best for, and wrong choice when
ERPNext is best for
Long-running Baan IV or Baan 5 sites with mainstream manufacturing processes, customisations that are mostly reports and interfaces, and a wish to own and host their next ERP.
Infor LN is best for
Complex discrete, project-driven and engineer-to-order manufacturers, especially in aerospace and defence, automotive and industrial machinery, where LN’s depth justifies the move.
ERPNext is the wrong choice when
You depend on deep project manufacturing or constraint-based configuration you have not tested in ERPNext, you need a go-live within months, or nobody can own the new system after go-live.
Frequently asked questions
When did Baan IV support end?
Infor’s LN Product Lifecycle Policy (March 2023 edition) shows Extended Maintenance for Baan 4 ended June 30, 2021. Sustaining Maintenance continues, with an end date to be determined (checked Nov 18, 2026).
Is Baan 5 still supported?
Baan 5.0b, 5.0c, 5.1 and 5.2 also left Extended Maintenance on June 30, 2021, per the same policy. They are in Sustaining Maintenance: pre-existing fixes only, no new fixes or regulatory updates.
Is the LN lifecycle policy an official Infor document?
Yes. Each page carries the “Infor LN: Product Lifecycle Policy” footer. The copy we cite is a partner-hosted excerpt because we found no public copy on infor.com. Check the current version in Infor’s support portal.
What is Infor’s replacement for Baan?
Infor LN, the direct successor. Infor’s LN page describes it as a multi-tenant cloud ERP on AWS for complex, project-driven discrete manufacturers.
Can ERPNext replace Baan?
For mainstream make-to-stock and make-to-order manufacturing, often yes. Test complex engineer-to-order projects and product configuration carefully; those are ERPNext’s weaker areas.
What does ERPNext cost?
No licence fee (GPL-3.0). Frappe Cloud lists site plans from $5 a month and servers from $40 a month (about £3.79 and £30.33 at the Bank of England rate for Nov 16, 2026; checked Nov 18, 2026). Implementation is separate.