IFS Cloud cost depends on licences, implementation scope and the work needed to run the environment. Eqeep separates programme costs from recurring costs, with assumptions your finance and operations teams can review.
The estimate covers modules, integrations, migration and your team’s capacity for change. A licence quote alone cannot establish the full cost. Eqeep prepares an estimate after the analysis, once scope, data and integrations are known.
What should the cost estimate include?
Include implementation services, internal time, infrastructure changes, reporting and support after go-live. Separate one-off programme work from recurring licences, hosting and application management. Confirm what each supplier quote includes so costs are counted once.
Equipment records, project structures and service processes can add data and integration work. Map those requirements before presenting an estimate to sponsors.
How is IFS Cloud licensed?
Licence costs depend on users, modules and the deployment model.
On 2 April 2026, IFS announced a pricing model in which customers pay per asset instead of per user. IFS presented it as a way to use AI across the whole organisation. In IFS’s example, an energy company managing 400 offshore assets pays for those 400 assets. The 12,000 people and machines that need access to the data do not set the price.
The announcement names neither IFS Cloud nor any other product, and gives no contract terms or start date. Nor does it say whether per-user pricing will remain.
On 13 October 2026, IFS also launched IFS Intelligence. IFS offers it as one enterprise-wide licence without feature tiers, with an entitlement of AI executions as a fair-usage cap. IFS has not said how the two announcements relate to each other or to existing IFS Cloud contracts. So ask which basis your quote uses and how AI is covered.
IFS Cloud is offered in a cloud model managed by IFS and in a remote model. According to IFS, in the cloud model IFS handles installation and technical operations as part of the service. You still schedule with IFS when an update is deployed.
In the remote model you run technical operations yourself or through a partner, from back-ups and database monitoring to deploying updates. In both models you keep end-user support, training, user accounts and the configuration of security and the application. So keep those lines in the estimate.
Which scope gaps can change the estimate?
Cost lines to make explicit
- User and module licensing
- Integrations, reporting and infrastructure changes
- Data migration, testing and training
- Internal ownership, support and temporary coexistence
Review undocumented integrations, duplicate master data, custom reports and systems that may run in parallel. Give each cost an owner and state what the estimate assumes. Set an expected end point for temporary coexistence and include its running costs.
Eqeep maps modules, interfaces and rollout choices with Benelux industrial teams. Finance and operations review the costs and expected benefits together. A smaller change to the existing setup may be the better option. Your sponsors decide whether the case justifies the investment.
Which costs are missing from a supplier’s quote?
Your own people’s time. In its implementation methodology (2020), IFS calls the people assigned to the project a key success factor. According to IFS, the project team needs the time and support to succeed.
Key users join workshops, decide on fit-gaps together with the process owner and test the solution before go-live. They also check the migrated data. Include those hours in the estimate, even though nobody sends an invoice for them. You decide how much time each key user frees up and who covers their day-to-day work.
Data migration is not a single move either. In the same methodology, data goes into a migration test environment first and again into the environment for the Solution Acceptance Test. A cutover rehearsal and the real cutover at go-live follow later.
Your organisation checks the data during the tests and the cutover rehearsal. In IFS’s methodology, the data scope and the need for cleansing and harmonisation are settled before the solution is built. Ask how many migration rounds a quote includes and who cleanses the data.
What does IFS Cloud cost after go-live?
After go-live you pay for licences, application management and keeping up with updates.
IFS publishes two release updates a year and a service update, usually monthly. Under IFS’s February 2026 support policy, IFS supports each IFS Cloud release for 24 months after it becomes available. The latest release and the three before it count as current, and you may be no more than three service updates behind. With monthly service updates, we read that as about three months of slack.
If you fall further behind, IFS treats your environment as non-current. In the cloud model, service levels then lapse and remediation may require you to buy Extended Support. If remediation is not achieved in time, IFS may start offboarding you from the cloud service at your own cost. A remote environment may then stop receiving updates, fixes and security patches.
If you ask IFS to install and implement a release or update, IFS charges for it under the same policy. Every update also means testing your processes, integrations and customisations. Budget that test capacity as a recurring cost, and see how Eqeep plans technical upgrades.
Customisations make every update bigger. IFS’s documentation says invasive changes create extra work, such as impact analysis and uplifting code, whenever you apply a future release. With a so-called overtake you copy standard code, and IFS says you must then keep that copy updated, even for service updates. Read how to bring customisations back to the standard in development and optimisation.
Licences nobody uses still cost money. Eqeep reviews usage reports with you so your contract stays right-sized. See what maintenance and support covers.
How do you make IFS Cloud quotes comparable?
Check every quote against the same set of questions. Where a quote gives no answer, write down the assumption and check it with the supplier.
- Is the licence priced per user or per asset, and for which modules?
- Does the cloud model or the remote model apply, and who installs, runs and applies service updates?
- Which data moves, who cleanses it and how many migration rounds are included?
- Which integrations and reports are built, and who maintains them after go-live?
- How many test cycles are included, and who writes and runs the tests?
- How many key-user hours does the quote assume?
A line that appears in one quote and is missing from another is not a saving. The work moves to your own organisation or to a later date. For the questions to ask a partner about design, key users and go-live, read the article on implementation and realisation.
Where do reliable figures for the business case come from?
From your own processes and data. In analysis and design, the Business Value Overview records the expected value and dependencies of the possible improvements. Your team uses the priority matrix to decide what comes first. Read what analysis and design delivers.
Where transaction data is available, process insight shows where work waits, repeats or takes a different route. That gives you a baseline you can measure again after go-live. A value check then puts the business case next to how IFS Cloud is actually used.
If you still run IFS Applications 10, include the support date as well. According to IFS, Extended Support ends on 27 March 2028. The IFS Applications 10 migration guide explains what that means for your planning.
IFS Cloud cost questions
What are the main IFS Cloud cost drivers?
Licences, integrations, data migration, testing, training and internal ownership all affect the estimate. Eqeep maps the required work and responsibilities for each. Phasing can spread expenditure but may add temporary coexistence costs.
How should we calculate the return on an IFS Cloud investment?
Compare expected benefits with the full costs over an agreed period. Eqeep records the baseline, assumptions and benefit owners with your team. Separate cash savings from capacity gains and risk estimates to avoid double-counting. Review the assumptions as scope and evidence change.
Can IFS Cloud be licensed per asset instead of per user?
Not yet clear. On 2 April 2026 IFS announced a pricing model per asset, but it did not name IFS Cloud or any other product. IFS gives vessels, components, infrastructure and production assets as examples of assets.
Which costs continue after go-live?
Licences, application management and keeping up with release and service updates, including the testing they need. Eqeep plans those updates with your team within IFS support periods.
Tell us where you stand with IFS. You get one conversation and a clear next step. Bring your quotes and the assumptions behind them. Discuss your IFS question.
New articles appear in our newsletter. Subscribe to the newsletter.
