IFS Applications 10 end of support: IFS Cloud vs ERPNext for 200 to 1,000 person manufacturers
Short answer
The IFS Global Support Policy lists IFS Applications 10 Standard Support as ended on March 27, 2025, with Extended Support ending on March 27, 2028 and Restricted Support beyond that (checked Nov 13, 2026). Extended Support is reduced in scope and carries additional terms and fees. Under Restricted Support, IFS still accepts and diagnoses cases, but new fixes, targeted response times, legal-change updates and new platform certifications are not included. IFS’s route forward is IFS Cloud, which has two releases a year and monthly service updates. For a 200 to 1,000 person manufacturer that uses IFS deeply, especially for project-based manufacturing, asset management or service, IFS Cloud is usually the right answer and we say so. ERPNext is worth pricing in narrower cases: plants or subsidiaries with simpler discrete or batch manufacturing, groups that want to stop paying per-user licences on part of the estate, or firms that already face a large rebuild of Apps 10 customisations. ERPNext has no licence fee (GPL-3.0); Frappe Cloud hosting starts at $5 a month for a site and $40 for a server. IFS Cloud pricing is quote-only.
Contents
- Who this guide is for
- The IFS dates, exactly as the policy lists them
- What Extended and Restricted Support actually cover
- The IFS Cloud path, and where it wins
- Where ERPNext fits for a manufacturer of this size
- A pilot that settles the question
- Mapping IFS Applications 10 to ERPNext
- Cost: what is published and what is not
- A timeline that works with March 27, 2028
- Best for, and wrong choice when
- Frequently asked questions
Who this guide is for
This guide is for CFOs, CIOs, operations directors and ERP managers at manufacturers of roughly 200 to 1,000 people that still run IFS Applications 10, on premises or hosted. You are probably on Extended Support now, or deciding whether to buy it, and IFS has been talking to you about IFS Cloud.
We build and support ERPNext, but we are not going to pretend it replaces IFS for every manufacturer of this size. IFS is a broad, deep product, and many Apps 10 sites use it in ways a general open-source ERP does not match without significant work. This guide sets out what the IFS support dates actually mean, where IFS Cloud wins, and the cases where ERPNext is a serious option, often for part of a group rather than the whole of it.
It is part of our series on legacy ERP deadlines; the legacy ERP end-of-support hub lists every vendor date we have confirmed. For a similar two-tier question with SAP, see our SAP ECC end of maintenance guide.
Sources: the IFS Global Support Policy (PDF) (version dated 2023-01-13, valid until superseded) for every IFS statement here; the Frappe Cloud pricing page and ERPNext repository on GitHub for ERPNext; ERPNext’s ERPNext Bill of Materials documentation, ERPNext Routing documentation, ERPNext Work Order documentation, ERPNext Job Card documentation, ERPNext Production Plan documentation, ERPNext Quality Inspection documentation and ERPNext subcontracting documentation for manufacturing features. All checked on Nov 13, 2026.
What we do not do here
We do not quote or estimate IFS Cloud subscription prices, Extended Support fees, or implementation costs on either side. IFS does not publish them, and they depend on your modules, user count and contract. We also do not use a March 27, 2027 milestone that some sources mention, because we could not find it on an IFS-owned page.
The IFS dates, exactly as the policy lists them
| IFS product | Standard Support ends | Extended Support ends | Restricted Support | Update cadence |
|---|---|---|---|---|
| IFS Applications 10 | March 27, 2025 | March 27, 2028 | Beyond March 27, 2028 | Quarterly updates |
| IFS Applications 9 | Expired | March 27, 2023 | Beyond March 27, 2023 | Quarterly updates |
| IFS Cloud | Not applicable: each release gets service updates for 23 months from release to manufacturing | Not applicable | Not applicable | Two releases a year; monthly service updates |
The policy adds that Extended Support is offered for a maximum of three years, with additional terms and fees, and that it does not apply to IFS Cloud 2021 R1 and later releases. So for Apps 10, March 27, 2028 is the end of the paid extension, not a soft target.
If you are still on IFS Applications 9 or earlier, you are already on Restricted Support, and the decision is more urgent than it is for Apps 10.
What Extended and Restricted Support actually cover
This is the table to show your board. It compares what IFS commits to under each level, from the support services overview in the policy.
| Service | Standard | Extended | Restricted |
|---|---|---|---|
| Accept cases for suspected security vulnerabilities and demonstrated errors | Yes | Yes | Yes |
| Diagnosis of accepted cases | Yes | Yes | Yes |
| Targeted response times | Yes | Yes | Not offered |
| Fix new security vulnerabilities | Yes | Yes | Not included |
| Fix new errors | Yes | Priority 1 and 2 cases only | Not included |
| Deliver accumulated fixes | Yes | Yes, at a potentially reduced cadence | Not included |
| Right to new releases (while paying for support and maintenance) | Yes | Yes | Yes |
| Improvements due to legal changes in supported countries | Yes | Yes | Not included |
| Certify new platforms | Yes | Yes, as needed so at least one certified version of each platform component is still vendor-supported | Not included |
| Translations for supported languages | Yes | Not included | Not included |
Read the Restricted column carefully. After March 27, 2028, IFS will still log and diagnose your cases, but it will not ship new fixes, it will not make legal-change updates, and it will not certify new platforms. For a manufacturer, the legal-change line matters most: tax, e-invoicing and statutory reporting change every year in most countries.
Also note the response-time guidance in the policy: IFS aims to respond within 1 hour for Priority 1 cases, 4 hours for Priority 2, 12 hours for Priority 3, 40 hours for Priority 4 and two working weeks for Priority 5. IFS says this is a guide, not a service level agreement. Under Restricted Support, targeted response times are not offered at all.
The IFS Cloud path, and where it wins
IFS Cloud is the successor product. The support policy describes two releases a year and monthly service updates, with each release receiving service updates for 23 months from release. For customers on the IFS Cloud Services, the policy requires you to stay on a current release and no more than three service updates behind the latest one.
That cadence is a real change from Apps 10’s quarterly updates. It means a standing test and release process inside your IT team, and it rewards keeping customisations small. Ask IFS and your partner to show you how they handle that rhythm for a customer like you.
Where IFS Cloud is the better answer
- You use IFS across many functions: manufacturing, supply chain, finance, projects, maintenance and service, so the integration across modules is a large part of the value.
- You run project-based or engineer-to-order manufacturing where project, cost and production structures are tightly linked in IFS today.
- Enterprise asset management or field service is core to the business, not an add-on.
- Your partner and internal team know IFS well, and you want continuity of concepts and terminology.
- You need one vendor accountable for the whole estate, with a published support policy.
Questions to put to IFS before you sign
Ask IFS or your IFS partner
- Is our move from Apps 10 to IFS Cloud an upgrade of our data and configuration, or a reimplementation? Which parts of each?
- Which of our Apps 10 customisations carry forward, which need rebuilding, and which become standard?
- What does Extended Support cost for us until March 27, 2028, and does buying it change the IFS Cloud price?
- How will we absorb two releases a year and monthly service updates, and what testing do you provide?
- What is the subscription for our user count and modules over five years, in writing?
Where ERPNext fits for a manufacturer of this size
ERPNext is open source under GPL-3.0, with manufacturing built in. Its documentation covers multi-level bills of materials, routings and operations, workstations, work orders, job cards for shop-floor operations, production planning from sales orders and material requests, quality inspection, subcontracting, batch and serial tracking, multiple currencies and multiple companies in one site.
That covers the core of discrete and batch manufacturing. In our experience, the honest scope for ERPNext in a 200 to 1,000 person IFS estate is usually one of these:
| Scenario | Why ERPNext can fit | What to watch |
|---|---|---|
| A subsidiary or smaller plant in a group that keeps IFS Cloud centrally | No per-user licences for the smaller entity; simpler processes | Group consolidation and inter-company flows need design |
| A whole business with discrete or batch manufacturing and modest complexity | BOMs, routings, work orders, job cards and quality inspection cover the core | Performance and reporting at your volumes must be tested |
| An Apps 10 site with heavy customisation that faces a rebuild anyway | The rebuild cost lands on both options; ERPNext removes licences afterwards | Do not recreate every customisation; use standard features first |
| A business that wants to self-host or control the code | Open source; self-host or choose a Frappe Cloud region | You own more of the operations burden |
Where ERPNext is the wrong tool
- Engineer-to-order manufacturing with deep project, cost and production integration that IFS handles today.
- Enterprise asset management or field service at scale as a primary use of the ERP.
- Highly regulated industries where you rely on a vendor’s validated processes and documentation.
- Organisations without the internal capacity to own an ERP partner relationship and a test process.
A pilot that settles the question
For a manufacturer of this size, do not decide from demos. Pick one plant, product line or subsidiary and run a 10 to 12 week pilot on your own data. Measure it against four tests.
Test 1: product structure
- Load active multi-level BOMs and routings for a representative product family.
- Check costing roll-ups against IFS standard costs and explain every difference.
- Confirm engineering changes and alternative items work the way your engineers need.
Test 2: planning and the shop floor
- Run a production plan from real sales orders and forecasts.
- Release work orders, record operations on job cards, and book materials and time.
- Check that capacity at workstations and lead times are realistic.
Test 3: quality and traceability
- Run incoming, in-process and final quality inspections.
- Trace a batch or serial number from supplier receipt to customer delivery and back.
Test 4: finance and volume
- Close a pilot month, including inventory valuation and work in progress.
- Load a realistic transaction volume and check response times for the reports people use daily.
- Test tax and statutory reporting for every country the pilot entity operates in.
How to read the result
If ERPNext needs heavy custom code to pass tests 1 or 2, it is the wrong tool for that part of your business. Take IFS Cloud, and consider ERPNext only for smaller entities where it passes cleanly.
Mapping IFS Applications 10 to ERPNext
| IFS Applications 10 area | ERPNext | Notes |
|---|---|---|
| Companies and sites | Companies, with warehouses per site | Inter-company via inter-company documents; design consolidation early |
| Inventory parts and part catalog | Item, with Item Variants where useful | Clean part numbers and units of measure first |
| Product structures (multi-level) | Bill of Materials (multi-level) | Load active revisions only |
| Routings and work centers | Routing, Operations and Workstations | Map labour and machine rates carefully |
| Shop orders and operations | Work Orders and Job Cards | Finish or migrate open orders at cutover |
| MRP and master scheduling | Production Plan, Material Requests | Planning logic differs; validate on real demand |
| Quality management | Quality Inspection templates and inspections | Map acceptance criteria per item |
| Lot batch and serial tracking | Batch and Serial No | Migrate live batches with remaining quantities |
| Subcontracting | Subcontracting orders and receipts | Test material supply to subcontractors |
| Finance: accounts, code parts | Chart of Accounts, Cost Centers, Accounting Dimensions | Map IFS code parts to cost centres and dimensions |
| Customer and supplier orders | Sales Orders, Delivery Notes, Sales Invoices; Purchase Orders, Receipts, Invoices | Migrate open documents; archive closed history |
| Fixed assets | Assets with depreciation schedules | Load net book value and remaining life |
| Projects | Projects, Tasks, Timesheets | Deep project manufacturing is a warning sign; see above |
Masters load through ERPNext’s ERPNext Data Import documentation using CSV or Excel templates. Opening balances post against a temporary opening account as the ERPNext opening balance documentation describes. There is no IFS-published or Frappe-published IFS-to-ERPNext migration tool that we know of, so plan a designed extract, transform and load, with at least two full dress rehearsals.
Cost: what is published and what is not
| Item | IFS Cloud | ERPNext |
|---|---|---|
| Software | Subscription; quote-only | No licence fee (GPL-3.0) |
| Staying on Apps 10 until March 27, 2028 | Extended Support, additional terms and fees; quote-only | Not applicable |
| Hosting | IFS Cloud Services or other deployment; quote-only | Frappe Cloud sites from $5 / month, servers from $40 / month (USD), or self-host |
| Implementation | Partner or IFS services; varies | Partner services; varies |
Frappe Cloud publishes USD prices: site plans from $5 a month (about £3.76) and servers from $40 a month (about £30.12), checked on Nov 13, 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.3282 per £1 for 11 Nov 2026, the latest published figure when we checked on Nov 13, 2026. They are not official UK prices: the vendor does not publish a GBP list price for these items, and your invoice currency, rate and VAT treatment may differ.
For a manufacturer of this size, Frappe Cloud’s entry prices are not the number that matters. You will want dedicated servers sized to your load, plus implementation, support and internal staff time. The licence line is what differs between the two options, and it grows with every user. Get both proposals in writing on the same scope and compare five-year totals.
A timeline that works with March 27, 2028
| Phase | Work | Done when |
|---|---|---|
| Now | Decide whether to buy Extended Support; inventory customisations, integrations and reports | A written view of what Apps 10 does for each business unit |
| First half of 2027 | Request the IFS Cloud proposal; run an ERPNext pilot on one plant or subsidiary in parallel | A go or no-go per business unit |
| Second half of 2027 | Build: either the IFS Cloud project, or ERPNext for the units that passed the pilot | User acceptance testing signed off |
| Early 2028 | Dress rehearsals and cutover, ideally at a period or financial year start | Live before Restricted Support begins on March 27, 2028 |
This is our planning view, not IFS guidance, and it is tight for a large estate. If you have not started, the realistic plan for many firms is IFS Cloud for the core business, with ERPNext considered for smaller entities where it passed a pilot.
Best for, and wrong choice when
IFS Cloud is the right move when
IFS runs most of your business, you depend on its depth in project-based manufacturing, asset management or service, and you want one vendor with a published support policy. It is the lower-risk path for most 200 to 1,000 person IFS manufacturers.
ERPNext is the right move when
A plant, product line or subsidiary has simpler discrete or batch manufacturing, passes a pilot on your own data without heavy custom code, and you want to stop paying per-user licences for it.
ERPNext is the wrong choice when
You need engineer-to-order project manufacturing, enterprise asset management or field service at scale, or you cannot fund a proper pilot and two dress rehearsals before March 2028.
Frequently asked questions
When does IFS Applications 10 support end?
The IFS Global Support Policy lists Standard Support for IFS Applications 10 as ended on March 27, 2025 and Extended Support ending on March 27, 2028, with Restricted Support beyond that (checked Nov 13, 2026).
What is IFS Extended Support?
Product support of reduced scope for a defined maximum period after Standard Support, offered for at most three years with additional terms and fees. For Apps 10, new error fixes are limited to Priority 1 and 2 cases, and translations are not included.
What happens under IFS Restricted Support?
IFS still accepts and diagnoses cases and you keep the right to new releases while paying for support, but targeted response times are not offered and new fixes, legal-change improvements and platform certifications are not included.
How often does IFS Cloud update?
The IFS support policy describes two releases a year and monthly service updates, with each release receiving service updates for 23 months. IFS Cloud Services customers must stay no more than three service updates behind the latest.
Can ERPNext replace IFS for a 500 person manufacturer?
Sometimes, for simpler discrete or batch manufacturing, and often for a subsidiary or smaller plant. For engineer-to-order, asset management or field service at scale, IFS Cloud is usually the better fit. Run a pilot on your own data first.
How much does ERPNext cost?
ERPNext has no licence fee under GPL-3.0. Frappe Cloud lists sites from $5 a month and servers from $40 a month (USD, checked Nov 13, 2026). A manufacturer of this size will also pay for larger hosting, implementation and support.
Is there an IFS to ERPNext migration tool?
Not one published by IFS or Frappe that we know of. Plan a designed extract, transform and load using ERPNext’s Data Import, with at least two full dress rehearsals.