Infor LX and BPCS past extended maintenance: an ERPNext migration path for IBM i manufacturers
Short answer
We could not find a public Infor page with support dates for Infor LX or BPCS releases, so this guide gives no end-of-support date. Infor partners report that older LX 8.3 releases and BPCS are past extended maintenance, which under Infor’s published General Product Lifecycle Policy means Sustaining Maintenance: access to pre-existing fixes and Infor support, but no new fixes, updates or regulatory enhancements, for a period Infor will determine. Infor’s own LX product page names Infor LX 8.4 (release 8.4.2) as the latest release, available on IBM i on-premises or in Infor’s cloud. If you are an IBM i process or discrete manufacturer on LX 8.3 or BPCS, you are choosing between an LX 8.4 upgrade, Infor’s cloud, and leaving IBM i. ERPNext (open source, GPL-3.0, no licence fee) is a credible destination when your RPG skills are retiring and your customisations are mostly reports and interfaces. The fit tests are formula handling (ERPNext has no potency-based formulas that we could find), lot and quality control, and multi-plant planning. Infor is quote-only, so we give no Infor estimate.
Contents
- Who this guide is for
- What is actually known about LX and BPCS support
- What Sustaining Maintenance means under Infor’s policy
- Your options
- The IBM i skills question
- Process manufacturing fit: the honest test
- Discrete manufacturing and planning fit
- Getting data off IBM i
- A phased plan for leaving LX
- Costs: what is published
- Decision table
- Best for, and wrong choice when
- Frequently asked questions
Who this guide is for
This guide is for CFOs, plant and operations managers and IT leads at manufacturers that run Infor LX, or its predecessor BPCS, on IBM i. Infor’s Infor LX product page describes the customer base: process and discrete manufacturers of all sizes, in more than 50 countries, using LX for source to pay, prospect to cash, design to manufacture and financial reporting. Many LX and BPCS sites run several plants on one system, have done so for decades, and depend on a small in-house team that knows RPG.
We implement ERPNext, so read our view with that in mind. For many LX sites, upgrading to LX 8.4 is the right answer, especially where the IBM i team is healthy. This guide is for the sites where the release is old, the platform skills are thinning, and the board wants a real alternative priced before signing another long Infor commitment.
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 IBM i guides in the series: Infor XA (MAPICS) and JD Edwards World.
Sources, checked on Nov 18, 2026: the Infor LX product page, the Infor General Product Lifecycle Policy (PDF on infor.com), Virtutem’s April 2020 summary of an Infor LX town hall (Infor partner), the Frappe Cloud pricing page and Frappe Cloud server plans page, the ERPNext repository on GitHub and the ERPNext documentation linked in each section.
What is actually known about LX and BPCS support
Be precise about sources, because LX dates get repeated without them:
| Source | What it says | How much weight to give it |
|---|---|---|
| Infor LX product page | Infor LX 8.4 is “the latest release”, available “in the Infor Cloud or on-premises”, on IBM i; the latest version is release 8.4.2. LX was “previously known as BPCS”. Infor says it is committed to ongoing investment in LX | Infor’s own page: high |
| Infor General Product Lifecycle Policy (PDF on infor.com) | Defines Mainstream, Extended and Sustaining Maintenance for Infor products; product-specific policies give the dates | Infor’s own policy: high, but it has no LX dates |
| Virtutem’s April 2020 summary of an Infor LX town hall (Infor partner) | Reports lifecycle information given at an Infor LX customer town hall: older LX 8.3 releases moving past mainstream and extended maintenance, and BPCS long past mainstream | Partner source: useful context, not confirmation |
Infor publishes product-specific lifecycle policies to customers through its support knowledge base. We could not find a public copy of the BPCS/LX policy on infor.com, so we do not quote any LX or BPCS end-of-maintenance date in this guide. If you are an Infor customer, look up the current BPCS/LX Product Lifecycle Policy in the Infor support portal, or ask your Infor account manager for it in writing. That document, together with your maintenance contract, is what counts.
What we can say safely
Infor’s current LX release is 8.4. If you run LX 8.3.x or any BPCS release, partners report you are past extended maintenance, and under Infor’s general policy that means Sustaining Maintenance: no new fixes. Confirm your exact status with Infor before you plan around a date.
What Sustaining Maintenance means under Infor’s policy
Infor’s Infor General Product Lifecycle Policy (PDF on infor.com) sets out three stages:
| Stage | Product fixes | Support access | Pricing (Infor’s wording) |
|---|---|---|---|
| Mainstream | Priority 1 and 2 fixes, updates, and regulatory and statutory enhancements for released localisations | Infor Support Portal and Infor Support Staff | Standard Maintenance pricing |
| Extended (at Infor’s discretion) | Priority 1 (critical) only; regulatory updates at Infor’s discretion; no regulatory enhancements; no new updates | Infor Support Portal and Infor Support Staff | Standard Maintenance pricing plus 20% premium unless otherwise determined by Infor |
| Sustaining | Access to pre-existing fixes only; no new product fixes, updates, or regulatory enhancements | Infor Support Portal and Infor Support Staff; full Knowledge Base access | Standard Maintenance pricing unless otherwise determined by Infor |
Infor says Sustaining Maintenance continues “for a period of time to be determined by Infor” and “may require payment of an additional fee, in Infor’s sole discretion”. Infor also says it will typically give one year’s notice of a Mainstream end date. The policy is not contractual; your maintenance agreement governs.
For an LX 8.3 or BPCS site, the practical meaning is this: the system keeps running, and you can still raise calls, but nothing new will be built for your release. New tax or e-invoicing rules, certification on newer IBM i releases and fixes for newly found defects all belong to the current release.
Your options
| Option | What it involves | Best when |
|---|---|---|
| Upgrade to LX 8.4 on IBM i | Stay on the platform; Infor or an LX partner upgrades, and RPG modifications are retrofitted | Your IBM i team is healthy, modifications are manageable, and LX still fits your processes |
| Move LX to Infor Cloud | Infor says LX 8.4 is available in the Infor Cloud; ask Infor what that involves for your modifications | You want Infor to run the platform and are comfortable with Infor’s cloud terms |
| Stay on LX 8.3 or BPCS on Sustaining | Keep running with pre-existing fixes only | Short term only, while you plan |
| Leave IBM i for ERPNext | Open-source ERP on Linux with MariaDB; self-host or Frappe Cloud | RPG skills are retiring, modifications are mostly reports and interfaces, and process fit tests pass |
Infor does not publish LX licence, maintenance or cloud prices on the pages we checked, so we give no Infor estimate. Ask for a written quote for an 8.4 upgrade and for Infor Cloud, and compare both with an ERPNext proposal over five years.
The IBM i skills question
For most LX and BPCS sites the decision is less about software features and more about people. LX runs on IBM i, and decades of modifications at a typical site are written in RPG against DB2 for i. Ask three questions honestly:
- Who maintains the RPG today, and when do they plan to retire? If the answer is one or two people in their sixties, that is a business continuity risk regardless of which option you choose.
- What do your modifications actually do? List every modified program and sort it: reports and extracts, interfaces to other systems, screen changes, and real business logic. Reports and interfaces are easy to replace on any platform. Business logic is where the effort is.
- Does anything else run on the IBM i? Payroll, EDI, a warehouse system or custom applications on the same box change the economics of leaving it.
If your team is healthy and your modifications are deep, an LX 8.4 upgrade keeps that investment working. If the team is shrinking and the modifications are mostly reports, leaving IBM i is a reasonable plan, and an open-source ERP on mainstream Linux hosting is one way to make the next system easier to staff.
Process manufacturing fit: the honest test
Infor’s LX page highlights process manufacturing capabilities: quality specifications for testing and item disposition, and “yield factors, potency rates, and shelf life”. If you are a process manufacturer, test these first.
| LX capability (per Infor’s page) | ERPNext equivalent | Fit |
|---|---|---|
| Formulas and recipes | Bill of Materials (ERPNext Bill of Materials documentation) with quantities per batch size | Good for fixed recipes |
| Yield factors and scrap | BOM scrap percentage per raw material, scrap items and process loss on the BOM | Good; ERPNext v16 replaces the Scrap Items table with Secondary Items, so check your version |
| Potency rates | Not found in ERPNext’s documentation | Gap: needs custom work or a process outside ERPNext |
| Shelf life and lot control | Batch with expiry dates (ERPNext Batch documentation); Serial and Batch Bundle (ERPNext Serial and Batch Bundle documentation) | Good |
| Quality specifications and disposition | Quality Inspection (ERPNext Quality Inspection documentation) with templates (ERPNext Quality Inspection Template documentation) | Good for inspection; test hold and release workflow |
| By-products and co-products | Scrap or secondary items with a rate on the BOM | Test with your real co-product costing |
ERPNext’s BOM documentation says a scrap item can carry a rate “if it is a by-product and not waste”, and that if the scrap item is the same as the item being made, it is treated as process loss and subtracted from the output. That covers many food and chemical cases. What we did not find is potency-based formula adjustment, where ingredient quantities change with the measured strength of each lot. If your business depends on that, plan for custom development or keep it in a specialist tool.
Discrete manufacturing and planning fit
| In LX | In ERPNext | Notes |
|---|---|---|
| Item master, facilities and warehouses | Items (ERPNext Item documentation), Companies, Warehouses (ERPNext Warehouse documentation) | Decide how LX facilities map to companies or warehouses |
| Routings and work centres | Routing (ERPNext Routing documentation), Operations (ERPNext Operation documentation), Workstations (ERPNext Workstation documentation) | Workstation hours and costs drive capacity planning |
| Shop orders | Work Orders (ERPNext Work Order documentation) and Job Cards (ERPNext Job Card documentation) | Finish open shop orders in LX at cut-over |
| MRP and master scheduling | Production Plan (ERPNext Production Plan documentation), Material Request (ERPNext Material Request documentation) | Test with a real month of demand across plants |
| Purchasing and subcontracting | Purchase Orders (ERPNext Purchase Order documentation), Subcontracting (ERPNext subcontracting documentation) | Map approval rules to Workflows |
| Customer orders and pricing | Sales Orders (ERPNext Sales Order documentation), Pricing Rules (ERPNext Pricing Rule documentation) | Load your real price agreements |
| Multi-company finance | Inter-company invoices (ERPNext inter-company invoices documentation), multi-currency (ERPNext multi-currency accounting documentation), Accounting Dimensions (ERPNext accounting dimensions documentation) | Common for multi-country LX sites |
Multi-plant planning is the second fit test. Run a Production Plan across two plants with real demand and check that the suggested work orders and transfers make sense to your planners.
Getting data off IBM i
LX data lives in DB2 for i. It can be read over ODBC or JDBC, or copied to CSV with standard IBM i tools, so extraction is rarely the hard part. The hard part is cleaning decades of item, customer and supplier records and deciding what not to move.
| LX data | ERPNext target | How |
|---|---|---|
| Items, UOMs, customers, suppliers | Items, UOM conversions, Customers (ERPNext Customer documentation), Suppliers (ERPNext Supplier documentation) | Extract, clean, load with Data Import (ERPNext Data Import documentation) |
| Active formulas, BOMs and routings | BOMs, Routings, Workstations | Only items you will make again |
| Lot-controlled stock with expiry | Stock Reconciliation (ERPNext Stock Reconciliation documentation) with batches | Count and verify lots before go-live |
| Open customer and purchase orders | Sales Orders, Purchase Orders | Freeze during cut-over |
| Open AR and AP | 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 LX read-only for history |
Keep the IBM i, or a read-only copy of the LX database, available for lot traceability history, audits and warranty claims. For regulated industries, agree the retention approach with your quality manager before you start.
A phased plan for leaving LX
| Phase | What happens | Typical output |
|---|---|---|
| 1. Discovery | Confirm your LX release and maintenance status with Infor; list modifications, interfaces and anything else on the IBM i | Status letter and a modification inventory |
| 2. Fit tests | Formulas, lot and quality, multi-plant planning and month end in an ERPNext trial | Pass, configure or develop, per test |
| 3. Quotes | LX 8.4 upgrade and Infor Cloud quotes from Infor; ERPNext proposal with the same scope | Five-year comparison |
| 4. Build | Configure ERPNext, rebuild the reports and interfaces you kept, load test data twice | Signed-off test cycles |
| 5. Cut-over | Go live at a period end; finish open shop orders in LX; LX read-only | Live ERPNext, archived LX |
Costs: what is published
| Item | USD (published) | GBP | Source |
|---|---|---|---|
| Infor LX upgrade, maintenance, Infor Cloud | Quote only; no estimate given | Quote only | Infor LX 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.
Include IBM i hardware, operating system support and RPG staffing in the “stay” column, and implementation, data work and retraining in the “move” column. Those lines usually outweigh software and hosting on both sides.
Decision table
| If this is true for you | Lean towards | Why |
|---|---|---|
| Healthy IBM i team, deep business-logic modifications | LX 8.4 upgrade | Keeps the investment and the skills working |
| RPG skills retiring, modifications mostly reports | ERPNext worth pricing | Reports and interfaces rebuild easily |
| Potency-based formulas are core | LX 8.4, or ERPNext plus custom work | We found no potency handling in ERPNext docs |
| Want Infor to run the platform | Infor Cloud | Infor says LX 8.4 is available in its cloud |
| Must own the code and avoid platform lock-in | ERPNext | GPL-3.0 on mainstream Linux hosting |
Best for, and wrong choice when
ERPNext is best for
IBM i manufacturers on LX 8.3 or BPCS whose RPG skills are retiring, whose modifications are mostly reports and interfaces, and whose formulas, lot control and planning pass a fit test with real data.
An LX 8.4 upgrade is best for
Sites with a healthy IBM i team, deep modifications that still earn their keep, and processes, such as potency-based formulas, that LX handles natively.
ERPNext is the wrong choice when
You depend on potency or other process functions you have not tested elsewhere, you need a go-live within months, or nobody can own the new system after the project.
Frequently asked questions
When did Infor LX 8.3 support end?
We could not find a public Infor page with LX or BPCS dates, so we give none. Infor partners report older LX 8.3 releases are past extended maintenance. Check the BPCS/LX Product Lifecycle Policy in the Infor support portal for your release.
What is the current Infor LX release?
Infor’s LX product page names Infor LX 8.4 as the latest release, with release 8.4.2 as the latest version, available on-premises on IBM i or in the Infor Cloud (checked Nov 18, 2026).
What does Sustaining Maintenance mean for LX?
Under Infor’s General Product Lifecycle Policy, Sustaining Maintenance gives access to pre-existing fixes, the knowledge base and Infor support, but no new fixes, updates or regulatory enhancements. Infor decides how long it lasts.
Can ERPNext handle process manufacturing?
For many recipes, yes: BOMs with scrap and process loss, batches with expiry, and quality inspections are standard. We found no potency-based formula handling in ERPNext’s documentation, so test that first if you rely on it.
How do we get data out of LX on IBM i?
LX data is in DB2 for i and can be read over ODBC or JDBC or exported to CSV. Clean it, then load masters and open items into ERPNext with Data Import.
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.