IFS Applications 9 in restricted support: a two-step IFS upgrade or ERPNext?
Short answer
IFS’s own Global Support Policy lists IFS Applications 9 with Standard Support “Expired”, Extended Support ended March 27, 2023, and Restricted Support beyond March 27, 2023. In Restricted Support, IFS still accepts cases and diagnoses them, but new security fixes, new error fixes, legal-change updates and platform certification are “not included”. The upgrade is not one step: IFS’s current technical documentation says IFS Cloud only supports direct upgrades from IFS Applications 10, so an Apps 9 database goes through Apps 10 on the way, or you re-implement IFS Cloud and migrate data. For an asset-intensive, project-heavy or service-heavy business, staying with IFS is usually right. For a mid-size manufacturer or distributor with mostly standard processes that skipped Apps 10 and now faces a large retrofit of customisations, ERPNext (open source, GPL-3.0, no licence fee) deserves a proposal next to IFS. IFS is quote-only, so we give no IFS estimate.
Contents
- Who this guide is for
- The IFS dates, exactly as the policy lists them
- What Restricted Support actually covers
- Why the IFS upgrade is two steps
- What drives the cost on each side
- Where ERPNext fits an IFS 9 site, and where it does not
- A fit test before you choose
- Migrating data from IFS Applications 9 to ERPNext
- What ERPNext costs to run
- Questions to put to both sides
- A phased plan
- 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 mid-size companies, often 100 to 1,000 people, still running IFS Applications 9 (or an earlier release) on their own servers or with a hosting partner. Many are manufacturers, distributors, engineering and service businesses that went live on IFS years ago, customised it, and then skipped Apps 10 because the upgrade looked like a project without enough business benefit.
We implement ERPNext, so read our view with that in mind. IFS builds a strong product for asset-intensive, project-based and field-service businesses, and for many Apps 9 sites the right move is to stay with IFS. This guide is meant to help you test that assumption, not to argue you out of it.
If you are on Apps 10 rather than Apps 9, read our IFS Applications 10 guide instead: Apps 10 still has Extended Support available to March 27, 2028 and a direct path to IFS Cloud. Other manufacturing guides in the series: Epicor 10 and 9 and older SyteLine on-premises. The legacy ERP end-of-support hub lists every vendor date we have confirmed.
Sources, checked on Nov 20, 2026: the IFS Global Support Policy (PDF, version 2023-01-13), IFS Cloud 26R1 technical documentation, “Technical changes related to IFS Cloud” and the IFS Cloud 25R1 edition of the same page, IFS Cloud 26R1 “Upgrading of IFS Cloud” documentation, the Frappe Cloud pricing page and Frappe Cloud server plans page, the ERPNext repository on GitHub, and the ERPNext documentation linked in each section.
The IFS dates, exactly as the policy lists them
| IFS product | Standard Support ends | Extended Support ends | Restricted Support | Update cadence |
|---|---|---|---|---|
| IFS Applications 9 | Expired | March 27, 2023 | Beyond March 27, 2023 | Quarterly updates |
| IFS Applications 10 | March 27, 2025 | March 27, 2028 | Beyond March 27, 2028 | Quarterly updates |
| IFS Cloud | Not applicable: service updates per release for 23 months from release to market | Not applicable | Not applicable | Two releases a year; monthly service updates |
The table reproduces the Product Release Lifecycle table in the IFS Global Support Policy (PDF, version 2023-01-13). For Apps 9 the policy does not print a Standard Support end date; it says “Expired”, so we do not give one. A footnote says Extended Support is offered for a maximum of three years, with additional terms and fees, and does not apply to IFS Cloud 2021 R1 and later releases.
Releases earlier than Apps 9 (Apps 8, Apps 7.5 and older) do not appear in the current policy table at all. If you are on one of those, assume you are at least as far out of support as Apps 9 and ask IFS to confirm your status in writing.
What Restricted Support actually covers
“Restricted” sounds softer than it is. The policy’s Support Services Overview compares the four support levels line by line. For Restricted Support:
| Service | Restricted Support |
|---|---|
| Accept cases for suspected security vulnerabilities | Yes |
| Accept cases for demonstrated errors | Yes |
| Diagnosis of accepted cases | Yes |
| Targeted response times | Not offered |
| Fix new security vulnerabilities | Not included |
| Fix new errors | Not included |
| Deliver Priority 1 and Priority 2 fixes | Not included |
| Deliver accumulated fixes | Not included |
| Right to new releases | Yes, as long as you have purchased support and maintenance |
| Improvements for legal changes in supported countries | Not included |
| Certify new platforms | Not included |
| Translations for supported languages | Not included |
Put simply: IFS will look at your problem, but if it is a new bug or a new security vulnerability, a fix is not part of the service, and there are no legal or tax updates. You keep the right to new releases, which is what makes the upgrade possible without buying new licences, subject to your contract.
Check the policy version you are relying on
The copy we cite is version 2023-01-13, issued January 13, 2023, “valid until superseded by a later version”. It is the copy IFS links publicly at the address above. Ask IFS whether a later version applies to your contract.
Why the IFS upgrade is two steps
IFS’s technical documentation for IFS Cloud 26R1 (IFS Cloud 26R1 technical documentation, “Technical changes related to IFS Cloud”) says: “IFS Cloud only supports direct upgrades from IFS Applications 10. Upgrades from IFS Applications 8 must be done in two steps.” The same note says the two-step upgrade path “is planned for IFS Applications 9 in a future release”. The 25R1 edition carries the same note.
There is one more signal in the same pages. In the 25R1 edition, the table of certified Oracle database versions for an upgrade still lists IFS Applications 9 as a starting point. In the 26R1 edition, that table lists only IFS Applications 10 and IFS Cloud 21R1 onwards, both to Oracle 19c Enterprise Edition. So on IFS’s current documentation, an in-place upgrade of an Apps 9 database to the current IFS Cloud release goes through Apps 10 first.
In practice that leaves Apps 9 sites three IFS routes:
| IFS route | What it means | Watch for |
|---|---|---|
| Two-step database upgrade | Upgrade the Apps 9 database to Apps 10 with IFS’s scripts, then from Apps 10 to IFS Cloud | Two sets of upgrade scripts, testing and customisation retrofits; ask IFS whether you go live on Apps 10 or pass straight through |
| Fresh IFS Cloud implementation | Install IFS Cloud new and migrate selected data from Apps 9 | A re-implementation: process design, data mapping and testing, but no carry-over of old customisations |
| Stay on Apps 9 | Continue under Restricted Support | No new fixes or legal updates; risk grows every year |
The same documentation notes two technical prerequisites worth knowing early: a byte (non-Unicode) database must be converted to Unicode before the IFS upgrade, and export and import of an IFS Cloud database must include objects outside the application owner schema. Neither is a reason not to upgrade; both belong in the plan and the quote.
What drives the cost on each side
IFS does not publish IFS Cloud subscription prices, Extended Support fees or upgrade project prices, and neither do its partners in a form we can cite. So we do not estimate them. What we can do is list what makes each project large or small, so you can read the proposals side by side.
| Cost driver | Two-step IFS upgrade | ERPNext migration |
|---|---|---|
| Customisations | Each one is retrofitted, rewritten or retired, and tested, potentially across two steps | Each one is rebuilt, replaced by standard function or dropped; nothing is carried over |
| Licences and subscription | IFS Cloud subscription or licence terms, quote-only | No licence fee (GPL-3.0); hosting from Frappe’s published prices |
| Data | Whole database carried forward, history included | Masters, open items and balances migrated; history archived |
| Process change | Lower: same vendor, same concepts, new user interface | Higher: new system, new screens, new terms |
| Integrations | Re-pointed to IFS Cloud APIs | Rebuilt against the Frappe Framework REST API documentation |
| Testing | Two upgrade passes plus regression of customisations | One implementation, tested end to end |
| People | Same IFS skills, updated to IFS Cloud | New skills: Frappe and ERPNext, in-house or through a partner |
| Infrastructure | Oracle 19c Enterprise Edition for on-premises IFS Cloud, per the upgrade table above, or IFS’s cloud service | Frappe Cloud or your own servers; MariaDB under Frappe |
The pattern we see when Apps 9 sites price both routes: if most customisations are still valuable and the business uses IFS’s deeper modules, the upgrade wins. If many customisations were workarounds for things the business no longer does, a fresh implementation, on IFS Cloud or on ERPNext, is a better use of the money, and then the licence model becomes the deciding factor.
Where ERPNext fits an IFS 9 site, and where it does not
| IFS area | ERPNext equivalent | Fit |
|---|---|---|
| Financials: GL, AP, AR, fixed assets | Chart of Accounts, Journal Entry, Purchase and Sales Invoices, Asset | Good for single and multi-company groups; see the ERPNext Chart of Accounts documentation and ERPNext Asset documentation |
| Code parts and analysis | Accounting dimensions and cost centres | Good; see the ERPNext accounting dimensions documentation |
| Inter-company trading | Inter-company invoices | Good within one ERPNext site; see the ERPNext inter-company invoices documentation |
| Inventory parts, sites, locations | Item, Warehouse (group warehouses), Batch, Serial No | Good for standard stock; see the ERPNext Warehouse documentation |
| Manufacturing: structures and routings, shop orders | Bill of Materials, Routing, Work Order, Job Card | Good for discrete make-to-stock and make-to-order; see the ERPNext Bill of Materials documentation and ERPNext Work Order documentation |
| Purchasing and customer orders | Purchase Order, Sales Order, Delivery Note, invoices | Good; see the ERPNext Purchase Order documentation and ERPNext Sales Order documentation |
| Project-based manufacturing, project accounting | Project, Timesheet, linked orders | Partial: simple project costing fits; deep project-driven planning does not |
| Enterprise asset management, maintenance | Asset, Maintenance Schedule | Partial: basic maintenance fits; asset-intensive EAM does not |
| Field service management | No equivalent of IFS FSM in standard ERPNext | Wrong fit if field service is core |
This is why IFS’s own target markets are the honest test. If your business looks like the asset-intensive, project-based or field-service companies IFS is built for, ERPNext will feel thin. If it looks like a standard manufacturer or distributor that happened to buy IFS, it will not.
A fit test before you choose
Run these with your own data
- List every IFS customisation with an owner and a yes or no on “would we build this again today?”
- Pick three representative products and rebuild their structures, routings and costing in ERPNext.
- Take one month of real orders and run them order to cash and purchase to pay in ERPNext.
- Run one month-end close with your real code parts mapped to dimensions and cost centres.
- Ask IFS, in writing, which upgrade route it proposes, whether you go live on Apps 10, and which customisations it expects to retrofit.
- Ask the ERPNext side to show your data loaded in a working system and to name every item that needs development.
If the IFS proposal retrofits most of your customisations and the ERPNext pilot shows serious gaps in your core processes, upgrade. If the IFS proposal is mostly a re-implementation anyway and the pilot shows your core processes running, price ERPNext seriously.
Migrating data from IFS Applications 9 to ERPNext
| Data | Approach |
|---|---|
| Company, sites, code parts | Map to companies, warehouses, accounting dimensions and cost centres |
| Chart of accounts and opening balances | Rebuild the chart; load balances at cutover with the ERPNext opening balance documentation |
| Inventory parts, structures, routings | Clean and import with the ERPNext Data Import documentation; review structures before loading |
| Customers and suppliers | Import with addresses, contacts, payment terms and tax settings |
| Open customer and supplier orders | Migrate open lines only |
| Open AR and AP | Opening invoices per document, or summarised by customer and supplier |
| Stock on hand | Stock Reconciliation per warehouse at cutover; see the ERPNext Stock Reconciliation documentation |
| Fixed assets | Assets with cost, accumulated depreciation and remaining life |
| Closed history | Archive: keep a read-only Apps 9 instance or export to a reporting database |
Apps 9 runs on an Oracle database, so the extraction is SQL work against well-understood tables, plus a reporting copy for history. Keep the old instance read-only for as long as your audit and statutory retention rules require, and check the Oracle licence terms for that read-only use.
What ERPNext costs to run
ERPNext has no licence fee under GPL-3.0. You pay for hosting and implementation. Frappe Cloud publishes USD prices: site plans from $5 a month (about £3.80) and servers from $40 a month (about £30.42), checked on Nov 20, 2026. The GBP figures are indicative conversions, not Frappe prices. For a 100 to 1,000 person business you would normally use a dedicated server plan or your own infrastructure rather than a shared site plan; the server plans on the Frappe Cloud server plans page are published in USD. Indicative GBP conversions use the Bank of England daily spot rate (series XUDLUSS) of US$1.3148 per £1 for 18 Nov 2026, the latest published figure when we checked on Nov 20, 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.
We give no IFS figure, and no implementation estimate for either side. Ask both proposals to break out licence or subscription, implementation, data migration, integrations, training and first-year support, so that you are comparing like with like.
Questions to put to both sides
Two proposals are only comparable if they answer the same questions. These are the ones we would ask, and the ones we expect to be asked ourselves.
For IFS or your IFS partner
- Which route do you propose for our Apps 9 database: two-step upgrade through Apps 10, or a fresh IFS Cloud implementation with data migration? Why?
- If two-step, do we go live on Apps 10 at any point, or pass straight through to IFS Cloud in one project?
- Which of our customisations do you expect to retrofit, which to replace with standard IFS Cloud function, and which to retire?
- Which deployment are you proposing (IFS’s cloud service or remote deployment on our infrastructure), and what database edition does it need?
- What does our support cost look like during the project, while we are still on Apps 9 in Restricted Support?
For the ERPNext side, including us
- Show our own items, structures and a month of orders running in a working ERPNext system, not a demo company.
- List every requirement that needs development, with who builds it and who maintains it after go-live.
- Explain how history will be archived and how auditors will reach it.
- Name the people who will support the system after go-live, and what happens if they leave.
A phased plan
| Phase | What happens |
|---|---|
| 1. Options review | Customisation inventory; IFS route confirmed in writing; ERPNext scoping |
| 2. Pilot | Three products, one month of orders and one close in ERPNext |
| 3. Decision | IFS upgrade, IFS Cloud re-implementation or ERPNext, on comparable proposals |
| 4. Build | Configuration, data mapping, integrations, reports |
| 5. Trial migrations | At least two full data loads with reconciliation |
| 6. Cutover | Go live at a period end; Apps 9 kept read-only for history |
Decision table
| If this is true for you | Lean towards | Why |
|---|---|---|
| Asset-intensive, field-service or project-driven business | IFS Cloud | Depth ERPNext does not match |
| Most customisations still valuable | Two-step IFS upgrade | Carries data and code forward |
| Customisations mostly obsolete; standard manufacturing or distribution | ERPNext worth pricing | Either way you re-implement; licence model differs |
| Want to self-host without Oracle Enterprise Edition | ERPNext | Runs on Frappe Cloud or your own servers |
| Business being sold or merged within a year | Stay on Apps 9, archive later | No new project worth starting |
Best for, and wrong choice when
The IFS route is best for
Apps 9 sites in IFS’s core markets (asset-intensive, project-based, service-heavy) whose customisations still matter, and which want to keep their data, processes and people on one platform.
ERPNext is best for
Mid-size manufacturers and distributors on Apps 9 with mostly standard processes, a long list of ageing customisations and no strong attachment to IFS’s deeper modules, who would rather spend the upgrade budget on a clean implementation without licence fees.
ERPNext is the wrong choice when
Field service, enterprise asset management or deep project-driven manufacturing is core to the business, the group mandates IFS, or nobody can own the new 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 IFS path is the better answer.
Frequently asked questions
When did IFS Applications 9 support end?
IFS’s Global Support Policy lists Standard Support for Apps 9 as expired and Extended Support as ended on March 27, 2023, with Restricted Support beyond that date (checked Nov 20, 2026).
What does Restricted Support include?
Case acceptance and diagnosis, and the right to new releases if you pay for support. It does not include new security or error fixes, legal-change updates, platform certification or targeted response times.
Can I upgrade IFS Applications 9 directly to IFS Cloud?
IFS’s IFS Cloud 26R1 documentation says IFS Cloud only supports direct upgrades from IFS Applications 10, so an in-place upgrade from Apps 9 goes through Apps 10 first. Confirm the exact route for your target release with IFS.
How much does IFS Cloud cost?
IFS does not publish prices; IFS Cloud and upgrade projects are quoted per customer. We give no estimate.
Can ERPNext replace IFS Applications 9?
For mid-size manufacturers and distributors with mostly standard processes, often yes. For asset-intensive, field-service or deep project-driven businesses, IFS is usually the better fit.
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.80 and £30.42 at the Bank of England rate for Nov 18, 2026; checked Nov 20, 2026). Implementation is separate.