Infor LN on-premises past extended maintenance: CloudSuite vs ERPNext for engineer-to-order manufacturers
Short answer
Infor’s own Infor LN Product Lifecycle Policy (March 2023 edition) shows LN 10.3 left Mainstream Maintenance on December 31, 2019 and Extended Maintenance on June 30, 2023. LN 10.2.1 and the FP1 to FP7 feature packs left Extended Maintenance on June 30, 2021. All of them now sit in Sustaining Maintenance, with an end date “to be determined”. Under Infor’s general policy that means pre-existing fixes only. Infor’s main destination is an Infor CloudSuite: Infor says LN is the ERP engine inside its CloudSuites for aerospace and defence, automotive and enterprise industrial manufacturing. For a complex engineer-to-order (ETO) business, that is often the right answer. ERPNext (open source, GPL-3.0, no licence fee) is worth pricing when your “projects” are really make-to-order jobs with some engineering on top: one sales order, one main assembly, a few months of work, cost tracked against the order. Run the fit test in this guide with a real past project before you decide. Infor is quote-only, so we give no Infor estimate.
Contents
- Who this guide is for
- What Infor’s LN lifecycle policy says
- What Sustaining Maintenance means for an ETO business
- Your four options
- The project-driven manufacturing fit test
- How to read the result
- Where ERPNext fits an LN site, area by area
- Moving data off LN
- A phased plan
- Questions to ask Infor and your LN 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 operations directors, finance leads and IT managers at mid-size manufacturers that run Infor LN on their own servers on an older release: LN 10.3, LN 10.2.1 (which Infor’s policy also calls FP8), or one of the FP1 to FP7 feature packs. Most build to order or engineer to order: special machinery, process equipment, fabricated structures, tooling, or assemblies made to a customer’s drawing. Many chose Baan or LN in the first place because it treats a customer project as the centre of planning and costing.
We implement ERPNext, so read our view with that in mind. Infor’s product is built for exactly the businesses this guide talks about, and we say plainly below where it is the better choice. The point of this guide is to give you a fair test, not a sales pitch.
If you are still on Baan IV or Baan 5 rather than LN, read our Baan IV and Baan 5 guide instead; it covers Baan data extraction and the Baan skills problem in more depth. Other Infor guides in the series: SyteLine on-premises and Infor LX and BPCS. The legacy ERP end-of-support hub lists every vendor date we have confirmed.
Sources, checked on Nov 19, 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: every page carries the “Infor LN: Product Lifecycle Policy” footer. The copy we could reach is a five-page excerpt hosted by an Infor partner; Infor distributes the full policy to customers through its support portal, and we found no public copy on infor.com. The edition is from March 2023, so check the current version with Infor 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
| 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.7 | March 7, 2019 | To be determined | To be determined | To be determined |
| Infor LN 10.6 | March 30, 2018 | To be determined | To be determined | To be determined |
| Infor LN 10.5 | June 30, 2016 | To be determined | To be determined | To be determined |
| Infor LN 10.4 | Dec 19, 2014 | 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 (FP8) | Dec 21, 2012 | Already in Extended | June 30, 2021 | To be determined |
| LN FP7 | Jan 31, 2011 | Already in Extended | June 30, 2021 | To be determined |
| LN FP6 | Jan 29, 2010 | Already in Extended | June 30, 2021 | To be determined |
| LN FP5 | Dec 19, 2008 | Already in Extended | June 30, 2021 | To be determined |
| LN FP3 | Oct 20, 2006 | Already in Extended | June 30, 2021 | To be determined |
| LN FP2 | Dec 9, 2005 | Already in Extended | June 30, 2021 | To be determined |
| LN FP1 | December 2004 | 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 19, 2026. FP4 does not appear in the excerpt we could read, so if you run FP4, ask Infor directly. The schedule also shows a 20% Extended Maintenance fee effective January 1, 2020 for LN 10.3, 10.2.1 and the FP releases. A footnote says Extended Maintenance for the releases that ended on June 30, 2021 included Priority 2 fixes.
Two other parts of the policy matter for on-premises sites. First, the LN technology tools (Enterprise Server, ERP LN Studio, the LN UI, the Microsoft Office integration, the SQL Server Reporting Services plug-in, the Web UI known as Webtop, and Worktop) follow the maintenance policy of the ERP release they run with. Your tools are therefore as far out of maintenance as your application. Second, several extension products, including the OpenWorld adapters, eService, the Service Scheduler Assistant, eSales, eProcurement and the Baan CRM Suite, show June 30, 2021 in the Extended Maintenance column. If your interfaces still run through OpenWorld adapters, put them high on the risk list.
Note what the policy does not say. In the March 2023 edition, LN 10.4 to 10.8 all show “to be determined” for every end date. That is not a promise of indefinite on-premises support; it means Infor had not set dates when the edition was published. Ask for the current schedule.
What Sustaining Maintenance means for an ETO business
Infor’s Infor General Product Lifecycle Policy (PDF on infor.com) defines Sustaining Maintenance as access to pre-existing fixes only, with no new product fixes, updates or regulatory enhancements, while keeping access to the Infor Support Portal, support staff and the knowledge base. It continues for a period Infor will determine and may require an additional fee. The same policy describes Transitional Support: a reduced-fee support arrangement, by written agreement and for no longer than 18 months, while a customer moves to a new Infor offering.
For a project manufacturer on LN 10.3 or an FP release, the practical effects are:
- No new fixes. A defect in project costing, planning or invoicing that nobody reported before mid-2021 (or mid-2023 for 10.3) is now yours to work around.
- No new regulatory content. E-invoicing, tax and reporting changes have to be handled with your own customisations or side systems.
- A frozen technology stack. Your LN release supports specific operating system, database and browser versions. Every infrastructure refresh becomes a compatibility test you run yourself.
- Thinning skills. People who know your LN customisations and your project-control setup get harder to find and to replace each year.
None of that stops LN running tomorrow. But it does mean the cost and risk of staying grow each year, and the decision should be made on your timetable rather than after an outage.
Your four options
| Option | What it involves | Best when |
|---|---|---|
| Infor CloudSuite (LN in the cloud) | Infor says LN is a multi-tenant cloud ERP on AWS and the engine inside its CloudSuites for aerospace and defence, automotive and enterprise industrial manufacturing, paired with sector processes and companion applications such as PLM, MES and warehouse management | Complex ETO, project control and multi-site operations that fit LN’s industry focus |
| A newer LN release on-premises | Ask Infor what on-premises options your licence allows; the March 2023 policy lists LN 10.4 to 10.8 with dates to be determined | You must stay on-premises and want to keep the LN data model and skills |
| Stay on Sustaining | Keep running with pre-existing fixes only | Short term only, while you plan and extract data |
| ERPNext | Open-source ERP on Linux; self-host or Frappe Cloud; projects, BOMs, work orders and costing in one system | Make-to-order with moderate engineering, mainstream finance, 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” and lists configure-to-order, engineer-to-order, project-based workflows, assembly line and just-in-time production, and regulated environments such as defence programmes. It says LN serves more than 1,500 discrete manufacturing customers. If your business looks like that description, price the CloudSuite seriously; it is the in-family move and keeps the project-centred way of working your people already know.
The project-driven manufacturing fit test
Most ERP comparisons for ETO firms fail because they compare feature lists. The useful question is narrower: can this system run one of our real projects end to end, and can our people live with how it does it? Pick a completed project from the last two years that was typical, not your largest or strangest, and rebuild it in each candidate system. Score each step:
| Step | What to test | How ERPNext handles it | What to watch |
|---|---|---|---|
| 1. Quote and estimate | Estimate engineering hours, bought-in items and make items; issue a quote | Quotation (ERPNext Quotation documentation); estimated cost on the Project (ERPNext Project documentation) | Detailed cost estimating structures are simpler than LN’s; test your estimate format |
| 2. Order to project | Convert the order and open a project with phases | Sales Order linked to a Project; Project Templates for repeat phase structures (ERPNext Project Template documentation) | Check one order per project suits you |
| 3. Engineering BOM that changes | Release a preliminary BOM, then revise it as design firms up | Multiple BOMs per item, one marked default (ERPNext Bill of Materials documentation); ERPNext’s BOM documentation suggests that for engineer-to-order, each order can be a Project with sub-assemblies as Tasks | No dedicated engineering change workflow found in the standard docs; test revisions mid-build |
| 4. Long-lead buying against the project | Buy castings, motors or steel before the design is final | Material Requests (ERPNext Material Request documentation) and Purchase Orders (ERPNext Purchase Order documentation); purchase cost rolls up to the Project | Project-pegged stock is not described in the standard docs; a warehouse per project is a common workaround to test |
| 5. Make and subcontract | Release work orders for sub-assemblies, send some out | Work Orders linked to the Project (ERPNext Work Order documentation), Job Cards (ERPNext Job Card documentation), Subcontracting (ERPNext subcontracting documentation) | Check routing and capacity for one-off work |
| 6. Engineering and labour time | Book design and assembly hours | Timesheets (ERPNext Timesheets documentation) with Activity Cost rates (ERPNext Activity Cost documentation) | Decide which hours go to the project and which to work orders |
| 7. Milestone billing | Invoice on deposit, approval, shipment and commissioning | Payment schedule on the Sales Order and partial Sales Invoices (ERPNext Sales Invoice documentation) | Retention and revenue recognition rules need configuration; test with finance |
| 8. Project margin | Compare estimate to actual by cost type | Project costing totals for timesheets, purchases, consumed materials and expense claims | Earned value and multi-level cost breakdown structures are not in the standard docs |
ERPNext’s ERPNext Project documentation says a project can be linked to a sales order, and that it collects costing from linked timesheets, purchase invoices, stock consumed against the project, and expense claims. Its ERPNext Work Order documentation says a work order can be linked to a project “to track progress in cases like engineer to order”. That is a real, usable model for jobs that look like a sales order with engineering attached. It is thinner than LN for programmes with many sub-projects, deep work breakdown structures, project-specific inventory and formal engineering change control.
How to read the result
After the rebuild, sort each step into one of three buckets: works as standard, works with configuration (custom fields, workflows, print formats, reports), or needs development. Then be honest about the pattern:
| If most steps are… | What it usually means |
|---|---|
| Standard or configuration in ERPNext | Your “ETO” is really make-to-order with engineering. ERPNext is a credible destination and worth a full proposal. |
| Development for steps 3, 4 and 8 | You depend on project pegging, engineering change and cost structures. Look hard at the CloudSuite; LN was built for this. |
| Development for steps 7 only | Billing rules are specific but solvable. Price the development; it may still be cheaper than a licence change. |
| Unclear because nobody can explain the LN setup | You have a knowledge problem before you have a system problem. Document the current process first. |
Run the same test with your Infor partner. A good CloudSuite proposal should show your project running on LN with its industry processes, not a slide deck. If one side refuses to run a real project, that tells you something too.
Where ERPNext fits an LN site, area by area
| LN area | ERPNext equivalent | Fit |
|---|---|---|
| Items, warehouses, units | Items (ERPNext Item documentation), Warehouses (ERPNext Warehouse documentation) | Good |
| BOMs, routings, work centres | 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, shop floor | Work Orders (ERPNext Work Order documentation), Job Cards (ERPNext Job Card documentation) | Good |
| Planning | Production Plan (ERPNext Production Plan documentation), Capacity Planning (ERPNext Capacity Planning documentation) | Test with real demand and real lead times |
| Project control (PCS) | Projects, Tasks, Timesheets, project costing | Partial: simpler projects yes; deep programme control, test carefully |
| Product configuration | Item Variants (ERPNext Item Variants documentation) | Partial: variants, not a constraint-based configurator |
| Purchasing, subcontracting | Purchase Orders, Request for Quotation (ERPNext Request for Quotation documentation), Subcontracting | Good |
| Quality | Quality Inspection (ERPNext Quality Inspection documentation) | Good for inspection; test hold and release |
| Lot and serial traceability | Batch (ERPNext Batch documentation), Serial No (ERPNext Serial No documentation) | Good |
| Service and installed base | Maintenance Schedule (ERPNext Maintenance Schedule documentation) | Partial: basic; LN service is much deeper |
| 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 summary: ERPNext covers the manufacturing and finance core of most LN sites well. The gap is at the top end of project manufacturing (programme management, project pegging, engineering change, earned value) and in field service. If those are central to how you make money, they decide the choice.
Moving data off LN
LN stores its tables in a relational database through its own database layer, and its data dictionary defines field meanings and enumerated values. Getting data out is rarely the hard part; decoding it is. In our experience, the practical routes are LN’s own exchange schemes to flat files, direct SQL on the database with the data dictionary to decode enumerated values, and existing reports exported to spreadsheets for small master files.
| LN data | ERPNext target | How |
|---|---|---|
| Items, business partners | Items, 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 for items you will make again |
| Open projects | Projects with tasks and remaining budget | Close finished projects in LN; move only live ones |
| Open orders | Sales Orders (ERPNext Sales Order documentation), Purchase Orders (ERPNext Purchase Order documentation), Work Orders | Finish production orders in LN where possible |
| Stock by warehouse, lot and serial | Stock Reconciliation (ERPNext Stock Reconciliation documentation) | Count before go-live |
| Open receivables, payables, GL | Opening entries (ERPNext opening balance documentation) on a new chart of accounts (ERPNext Chart of Accounts documentation) | Reconcile to LN aged reports and trial balance |
Open projects are the hardest part of any ETO cut-over. A project half-way through has committed costs, partial billing and work in progress. The cleanest approach is to let projects that finish within a few months complete in LN, and migrate only those with a long tail, with their remaining budget and actuals to date as opening figures. Keep LN read-only, or archive its database, so that warranty and audit questions can still be answered.
A phased plan
| Phase | What happens | Output |
|---|---|---|
| 1. Inventory | Release, extensions, customisations, interfaces, infrastructure; confirm maintenance status with Infor in writing | Risk register and customisation list |
| 2. Project fit test | Rebuild one real past project in ERPNext, and ask Infor to do the same on the CloudSuite | Scored fit test, step by step |
| 3. Proposals | CloudSuite and ERPNext proposals on the same scope | Five-year cost and risk comparison |
| 4. Build | Configure, rebuild reports, interfaces and print formats; two trial data loads | Signed-off test cycles |
| 5. Cut-over | Go live at a period end; live projects moved with opening figures | Live system, LN read-only |
Questions to ask Infor and your LN partner
- What exactly is our maintenance status? Per release, per tool and per extension product, and what we pay for it today.
- Which CloudSuite would we move to, and what is included? Ask which companion applications (PLM, MES, warehouse management) are in scope and priced.
- Is there an on-premises LN option for our licence? If so, on which release and with what lifecycle dates.
- Would Transitional Support apply while we move? Infor’s general policy describes it as reduced-fee support of no more than 18 months, by written agreement.
- How do our customisations map? A good proposal maps each LN customisation to a standard function, an extension or a rebuild.
Ask the ERPNext side the equivalent: show our real project running, list every step that needs development, and name who supports it after go-live.
Costs: what is published
| Item | USD (published) | GBP | Source |
|---|---|---|---|
| Infor CloudSuite or 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.29 (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.29), checked on Nov 19, 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.3205 per £1 for 17 Nov 2026, the latest published figure when we checked on Nov 19, 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.
Infor does not publish LN or CloudSuite prices on the pages we checked, so we give no Infor figure. On either path, most of the cost is people: process design, data decoding, testing, training and your own staff’s time. Include the cost of keeping the old LN servers, database licences and specialist support alive in the “stay” column.
Decision table
| If this is true for you | Lean towards | Why |
|---|---|---|
| Programmes with many sub-projects, project pegging, earned value | Infor CloudSuite | LN is built for project-driven manufacturing, per Infor |
| A&D or automotive with sector compliance needs | Infor CloudSuite | Infor offers sector CloudSuites built on LN |
| One order, one project, a few months, cost tracked to the order | ERPNext worth pricing | Projects, BOMs and work orders link cleanly |
| Customisations mostly reports and interfaces | ERPNext worth pricing | Easy to rebuild on any platform |
| Must stay on-premises and own the code | ERPNext, or LN on-premises if Infor offers it | GPL-3.0; self-host or Frappe Cloud |
Best for, and wrong choice when
Infor CloudSuite is best for
Complex engineer-to-order and project-driven manufacturers, especially in aerospace and defence, automotive and industrial machinery, where LN’s project control, engineering change and sector processes earn their cost.
ERPNext is best for
Mid-size make-to-order and light ETO manufacturers on LN 10.3 or older FP releases whose projects are essentially sales orders with engineering attached, whose customisations are mostly reports and interfaces, and who want to own their next ERP.
ERPNext is the wrong choice when
Project pegging, formal engineering change control or programme-level cost structures are central to your margins and failed the fit test; you need deep field service; or nobody in the business can own the system after go-live.
Want a second opinion before you commit? Our ERP Engineering practice runs fit tests like the one above on your own data, and we will tell you if the incumbent vendor’s path is the better answer.
Frequently asked questions
When did Infor LN 10.3 support end?
Infor’s LN Product Lifecycle Policy (March 2023 edition) shows Mainstream Maintenance for LN 10.3 ended Dec 31, 2019 and Extended Maintenance ended June 30, 2023. Sustaining Maintenance continues, with an end date to be determined (checked Nov 19, 2026).
Are LN FP7 and LN 10.2.1 still supported?
They are in Sustaining Maintenance. Extended Maintenance for LN 10.2.1 (FP8) and FP1 to FP7 ended June 30, 2021, per the same policy. Sustaining means pre-existing fixes only.
What is Infor’s replacement for LN on-premises?
Infor’s LN page describes LN as a multi-tenant cloud ERP on AWS and the ERP engine inside its CloudSuites for aerospace and defence, automotive and enterprise industrial manufacturing. Ask Infor whether an on-premises release is available for your licence.
Can ERPNext handle engineer-to-order manufacturing?
For simpler ETO, yes: ERPNext links projects to sales orders, BOMs and work orders and collects project costs. Deep programme control, project-pegged inventory and engineering change workflows are not in the standard documentation, so test them with a real project.
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 of the March 2023 edition; check the current version in Infor’s support portal.
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.29 at the Bank of England rate for Nov 17, 2026; checked Nov 19, 2026). Implementation is separate. Infor is quote-only.