IFS
Client side advice on IFS Cloud: whether IFS is the right fit, what the move from IFS Applications 9 or 10 involves, how to hold your implementation partner to account, and how to get the asset, service and finance modules live without surprises.
Delivered for and alongside
































IFS Cloud is the single platform IFS launched in March 2021 to connect everything it sells. It carries enterprise resource planning, enterprise asset management and field service management on one data model, with customer relationship management, human capital management and supply chain alongside. IFS names its focus industries as aerospace and defence, energy, utilities and resources, construction and engineering, manufacturing, transportation, telecoms and service businesses.
That list tells you where the product earns its keep. IFS ERP is a capable finance and supply chain system, but the reason organisations choose it over Oracle, SAP or Dynamics is usually the asset and service side: long lived assets with maintenance histories, field engineers who need scheduling and parts, defence programmes with configuration control, and service contracts that have to be priced and honoured. Rolls Royce Power Systems chose IFS Cloud in 2024 to run service operations for 1,000 users across 1,200 locations in 175 countries, with the planning, scheduling and optimisation module and scenario modelling at the heart of the case. Exelon and TotalEnergies are among the other customers IFS names publicly.
IFS itself was founded in 1983 in Sweden, employs more than 7,000 people in 80 countries and reported revenue above EUR 1.2 billion for 2024. It is a serious vendor with a growing book. It is not the right answer for every organisation that gets a demonstration. A professional services firm replacing its finance system, or a group whose real problem is consolidation and statutory reporting, will often find a better fit elsewhere, and our vendor selection work is where that gets settled on evidence rather than on the quality of the presentation.
IFS Cloud ships two feature releases a year, named for the year and half, such as 25R1 and 25R2, with service updates roughly monthly in between. Under the IFS support policy each release is supported for 24 months from general availability, four releases are in support at any time, and IFS gives at least 12 months' notice before one drops out. In practice a programme has to plan release adoption as a standing activity, with regression testing that is repeatable rather than heroic. The vendor's cadence does not bend to your go live date, so the plan has to.
For organisations still on IFS Applications the clock is already running. Standard support for Applications 10 ended on 27 March 2025. Extended support, which is a paid arrangement, runs to 27 March 2028, after which only restricted support remains. Restricted support for Applications 9 and 8 ended on 27 March 2026. If you are on Applications 9 today you are running without a safety net; if you are on 10 you have a little over a year to decide how to use the paid window.
The move itself is more than an upgrade. Every modification written against Applications 9 or 10 needs a verdict: retire it, replace it with standard configuration, or rebuild it in a form that survives each release. Data has to be cleansed and loaded, with asset registers and work order history usually the hardest part, which is why we treat data migration as a workstream with its own owner from day one. Deployment is a choice too. IFS runs a managed cloud service, which its own staff recommend as the default, and IFS Cloud can be deployed on Microsoft Azure through the IFS partnership with Microsoft. Remote deployment on your own infrastructure exists for cases where that is not an option, and IFS is candid that it demands much more of your IT team.
IFS sells and implements through its own services organisation and a partner network of services, resell and independent software vendor partners, with Microsoft listed as a strategic technology partner and the UK business run from Staines. Partners are rewarded by the vendor for the licences they influence and paid by you for the implementation. That is not a criticism; it is simply the commercial structure, and you should read every piece of advice you receive through it.
We sit on the other side of the table. PEF holds no reseller, referral or alliance agreement with IFS or any other software vendor, earns no commissions and takes no implementation revenue from vendors. When we say IFS Cloud is the right product for you, or that it is not, nothing in our business depends on the answer. Independence is the whole point of hiring us rather than a firm that also resells the software.
What we bring to IFS specifically is a bench rather than a badge. PEF's consultants have steered the decisions made ahead of, during and after platform migrations and implementations, and analysed the ones that went wrong, which is exactly the experience an IFS Cloud move draws on. Christopher Fagan, our Managing Partner, ran the procurement of every software provider on the National Grid separation, a programme with more than 22 million assets under management, from tender through to implementation. Buying asset and finance software at that scale, and holding vendors to what they sold, is the discipline we bring to an IFS negotiation. Fees are shown plainly on our pricing page.
There are two ways to use us, and clients take one or both.
Part A, independent assurance. We work alongside your team and your IFS partner. On selection that means a requirements baseline built from your processes, scripted demonstrations rather than showcases, reference calls we run ourselves, and a commercial review of the licence metric, the release adoption obligations and the exit terms before anything is signed. During implementation it means stage gates with teeth: is the data migration rehearsed and measured, has field service scheduling been tested with real engineer rosters, are the integrations to finance, payroll and asset data proven, and is the cutover plan rehearsed rather than described. We report to your sponsor, not to the partner.
Part B, delivery led by our practitioners. We take the client side programme role: programme director, PMO, data migration lead, test lead and change lead, working with your people and the partner's configuration team. You keep ownership of the decisions; we make sure they get made on time and stick.
Both routes start with an honest view of readiness. Our readiness assessment tells you whether the organisation, the data and the budget are in shape before the partner's clock starts. If a programme is already live and struggling, our recovery service is built for that moment. And if you are not yet sure IFS is the answer at all, start with the ERP implementation consulting hub and the guides there.
IFS Cloud is the single platform IFS launched in March 2021, combining ERP, enterprise asset management and field service management on one data model with twice yearly releases. IFS Applications 9 and 10 are the older generation, sold as separate products with a slower upgrade cycle. Moving between them is a project in its own right, because modifications, integrations and data all have to be reworked for the new platform.
Under the IFS support policy, standard support for IFS Applications 10 ended on 27 March 2025. Paid extended support runs until 27 March 2028, after which only restricted support is available. Restricted support for Applications 9 and 8 ended on 27 March 2026. Organisations still on Applications 10 should treat the extended support window as time to plan and run a controlled move, not as a reason to wait.
IFS Cloud has two feature releases a year, named like 25R1 and 25R2, plus service updates issued roughly monthly. Each release is supported for 24 months after general availability and four releases are supported at any time, so you can skip a release but cannot fall more than two years behind. Plan release adoption as a routine activity with a repeatable regression test pack.
No, but that is where it is strongest. IFS targets aerospace and defence, energy and utilities, construction and engineering, manufacturing, telecoms and service businesses, and the asset management and field service modules are the usual reason it wins. A finance led organisation with no assets or field workforce should compare it carefully against Oracle, SAP, Dynamics and NetSuite before committing.
Both. Part A is independent assurance, where we work alongside your team and your IFS partner on selection, contract, stage gates and cutover. Part B is delivery led by our own practitioners in the client side roles: programme director, PMO, data migration, testing and change. We hold no agreement of any kind with IFS or any vendor, so our advice on either route is not tied to a sale.
Where next
Talk to us before you sign with IFS or an implementation partner. One conversation now can change the shape of the whole programme.