Explainer
IFS Cloud is the platform IFS has sold since 2021 for ERP, asset management and field service. Here is what it actually is, how it got here, how it is priced, and what moving onto it demands, written from the client side of the table.
By Christopher Fagan, Managing Partner, PEF Consulting Partners
Delivered for and alongside
















IFS Cloud is one product rather than a family. When IFS launched it in London on 10 March 2021, the pitch was a single platform with one data model, one user experience and one support arrangement, covering enterprise resource planning, enterprise asset management, field service management, customer relationship management and human capital management. Before that, customers bought IFS Applications for the ERP and asset side and a separate field service product, and lived with the join between them.
The company behind it was founded in 1983 in Sweden by five university friends, employs more than 7,000 people across 80 countries and said in April 2025 that annual recurring revenue had passed EUR 1 billion, growing at more than 30 per cent a year, with 2024 revenue above EUR 1.2 billion. The same announcement valued the business at over EUR 15 billion, with Hg becoming a co control shareholder alongside EQT and TA Associates staying as a minority investor. I mention the ownership because it matters: a vendor owned by private equity funds has a horizon, and its pricing and partner behaviour follow that horizon.
IFS built the product for the cloud but will deploy it on your own infrastructure, with a choice of where data lives, and says the functionality is identical either way. That matters to defence and utility customers who cannot put certain data in a public cloud, and I come back to it below.
Most UK organisations that talk to me about IFS are not choosing it fresh. They already run IFS Applications 9 or 10 and are being told to move. It helps to know the lifecycle facts rather than the sales version of them.
The IFS support policy, in its May 2024 edition, sets out three phases for the Applications generation: standard support, an optional paid extended support period of up to three years, and a restricted phase that runs until the release is retired. For Applications 10, standard support ended on 27 March 2025 and extended support runs from 28 March 2025 to 27 March 2028. Applications 9 and 8 were already down to restricted support, and that ended on 27 March 2026. Applications 7.5 and earlier dropped out of restricted support in March 2025. Field Service Management 6, the separate field service product, left standard support on 31 January 2026 with extended support available until 31 January 2029.
IFS Cloud sits under a different model, which IFS calls continuous support. There is no extended or restricted phase. Each release gets the equivalent of standard support for 24 months after general availability and then stops. If you are coming from Applications, that is the cultural change: you are moving from a system you upgraded when you chose to one that expects you to keep up. The question for every modification you ever wrote becomes whether it can survive two releases a year, and the ones that cannot have to go. In my experience the organisations that struggle are the ones that treat the move as a technical upgrade and try to carry everything across. Our guide to implementation timelines explains why that habit adds months.
IFS groups the product by capability: enterprise resource planning covering finance, supply chain, manufacturing and projects, enterprise asset management, field service management and enterprise service management. Within field service sits planning, scheduling and optimisation, the scheduling engine, and a scenario tool IFS calls the What If Scenario Explorer.
The industries IFS leads with are aerospace and defence, energy, utilities and resources, construction and engineering, manufacturing, transportation, telecoms and service. Note what is missing: retail, banking, professional services and the public sector are not where IFS competes, and a finance only buyer will find the ERP module competent but not the reason to choose it.
Several customers are a matter of public record. Rolls Royce Power Systems, the Friedrichshafen based division that includes the mtu brand, announced in October 2024 that it would run IFS Cloud for service operations covering 1,000 users, 1,200 locations and 175 countries, using the scheduling module and scenario modelling to test maintenance and capacity options. IFS has named Exelon, which uses it for grid asset maintenance, and TotalEnergies, which took it as the single platform for its operated assets worldwide. At the 2021 launch the quoted customer was Cimcorp, a robotics and automation manufacturer. IFS also said in April 2025 that it had added 350 customers in the previous year and that the average deal size among its largest customers had grown by 64 per cent. These are vendor announcements and I treat them as such, but they show the pattern: asset heavy, service heavy, global.
IFS Cloud gets two feature releases a year, labelled YYR1 and YYR2, so 25R1, 25R2 and onwards, with service updates issued roughly monthly for the 24 months each release is supported. IFS keeps four releases in support at once and promises at least a year’s notice before one leaves support. You can skip a release; you cannot sit still.
Deployment is a choice between the IFS managed cloud service and what IFS calls remote deployment. IFS staff describe the managed service as the default that needs no customer infrastructure, and remote deployment as an option for special cases that asks a great deal more of the customer’s IT team. Microsoft is named by IFS as a strategic technology partner, IFS Cloud can be deployed on Microsoft Azure, and it can be bought through the Microsoft commercial marketplace. For defence and critical infrastructure customers the remote route is the one that keeps data on premises, and its cost in people belongs in the business case.
The 25R2 release in autumn 2025 introduced what IFS calls Loops Digital Workers, agents that act across systems inside workflows, under the IFS.ai banner. I am wary of vendor AI claims in general. I would test any digital worker against a real work order backlog, with your own data quality, before paying for it. But the direction is clear, and the pricing change described next was designed around it.
IFS does not publish list prices. Every IFS Cloud deal is quoted, and the quote is driven by the modules you take, the deployment route, the services attached and, historically, the number and type of users.
That last part changed in April 2026. At its event in Paris, IFS announced that it was moving away from per user licensing to pricing based on the operational assets a customer manufactures, manages or maintains: vessels, components, infrastructure, production assets. The example IFS gave was an energy company managing 400 offshore assets paying for those 400 assets rather than for the 12,000 people and machines that touch the data. The chief executive’s line was that IFS is pricing the work, not the workers.
My reading, after 19 years on the buying side of software contracts, is this. For an asset heavy, people light operator the new metric is attractive and probably cheaper over time, because it stops penalising wide adoption. For a service business with many engineers and relatively few countable assets the arithmetic could go the other way. Before you sign, get the definition of an asset written into the contract, understand how growth in the asset base reprices the deal, and ask what happens to the metric if you divest a site or mothball a plant. None of that is on the price list, because there is no price list, and all of it belongs in the business case before the board sees a number.
The strengths are real. Depth in asset management and field service, one data model across finance, assets and service, an industry focus that shows in the configuration, and a vendor that is growing and investing. The limits are equally real. The finance and group reporting side is competent rather than exceptional, so a group that chooses IFS for its assets often keeps a separate consolidation tool. The partner pool in the UK is smaller than for SAP or Dynamics, which affects price and availability. The release model imposes a permanent testing overhead. And asset based pricing will suit some operating models far better than others.
A move to IFS Cloud, whether from Applications or from another system, has five parts I would not skip. First, a modification inventory with a verdict on every item. Second, data: asset registers, hierarchies, maintenance history and spares, which are always worse than anyone admits. On one programme I directed, the asset base passed 22 million items, and the register was the critical path from the first week to the last. Third, integration to the systems that stay, from payroll to telemetry, which is where our data migration and integration work usually begins. Fourth, a release adoption and regression testing regime designed before go live, not after. Fifth, a contract that pins down the asset metric, the partner’s obligations and the exit.
If you want the independent version of that conversation, our IFS consultancy page explains how we work on selection, assurance and delivery, and the vendor selection service is where IFS gets compared against the alternatives on your requirements rather than the vendor’s.
Related reading: Independent IFS consultancy, ERP vendor selection, How long an ERP implementation really takes, Best ERP software in the UK, ERP systems for manufacturing, Data migration consultancy.
IFS Cloud is a single platform for enterprise resource planning, enterprise asset management, field service management, customer relationship management and human capital management. It is used most in asset and service heavy industries: aerospace and defence, energy and utilities, construction and engineering, manufacturing, transportation, telecoms and service businesses. Finance is included, but the asset and field service modules are usually the reason it is chosen.
Both. IFS built IFS Cloud for the cloud and offers it as a managed service, which IFS staff recommend as the default, deployable on Microsoft Azure. It also offers remote deployment on a customer’s own infrastructure with a choice of data residency, which IFS says is for special cases and places much heavier demands on the customer’s IT team. Functionality is the same either way.
IFS does not publish prices, so every deal is quoted. In April 2026 IFS announced a move away from per user licensing towards pricing based on the operational assets a customer manufactures, manages or maintains, giving the example of an energy company paying for 400 offshore assets rather than 12,000 users. Modules, deployment route and implementation services drive the rest of the quote.
IFS Applications 10 is the last release of the previous generation. Under the IFS support policy its standard support ended on 27 March 2025, paid extended support runs from 28 March 2025 to 27 March 2028, and restricted support follows. Applications 9 and 8 lost restricted support on 27 March 2026. IFS Cloud replaced the Applications line as the product IFS develops and sells.
IFS has publicly announced Rolls Royce Power Systems, which chose IFS Cloud in October 2024 for service operations across 1,000 users, 1,200 locations and 175 countries, along with Exelon for grid asset maintenance and TotalEnergies as a single platform for its operated assets. Cimcorp, a robotics manufacturer, was quoted at the 2021 launch. IFS said in April 2025 that it had added 350 customers in a year.
Weighing up IFS Cloud? Bring the quote, the modification list and the asset register. We will tell you plainly what the move involves and whether to make it.
Book a confidential conversation
Independent, client side help across ERP implementation: vendor selection, project management, testing and go live, health checks and programme recovery, on SAP, Oracle, NetSuite, Dynamics 365, Sage, IFS, Odoo, Epicor, Infor and more. Fees are shown plainly on our pricing page.
Written by Christopher Fagan
Managing Partner, PEF Consulting Partners
Christopher has led systems and transformation delivery for 19 years, including the National Grid separation, the £9bn Energy Bills Support Scheme and the BP Pulse EV charging rollout.
Where next