Evaluate the move with clear eyes: understand what you gain, what staying on IFS Applications really costs, and how to plan a low-risk path to a modern, evergreen platform.

Contents

1. Why upgrade now — the case for moving

2. What’s new in IFS Cloud and why it matters

3. The cost and risk of staying on IFS Applications

4. The business value of upgrading (ROI)

5. Upgrade paths and options

6. How IFS de-risks the move

7. Migration approach and timeline

8. Cost, licensing, and commercial considerations

9. Common concerns and objections to pressure-test

10. Upgrade readiness checklist and questions to ask

11. Upgrade & migration terminology glossary

12. Frequently asked questions

Suggested next step

1. Why upgrade now — the case for moving

Since you first went live on IFS Applications, the ground has shifted. Enterprise software has moved decisively to the cloud, artificial intelligence has moved from pilot to production, and the security and compliance bar rises every year. The distance between an older release and the current platform now widens every six months rather than every few years — which changes the maths of waiting.

The question is no longer whether to modernize, but how to do it well. Global spending on cloud infrastructure and the pace of cloud-delivered innovation both continue to climb, and the organizations pulling ahead are the ones running on platforms built for continuous change rather than periodic catch-up.

What upgrading to IFS Cloud means

IFS Cloud is IFS’s single, composable, cloud-native platform for enterprise resource planning, enterprise asset management, service management, and supply chain — the successor to IFS Applications, delivered on an evergreen model that updates continuously. Moving to it is not simply a version bump. It is a shift onto modern, modular architecture, a unified and AI-assisted user experience, open APIs, and a release model where new capability arrives on a schedule you control — instead of being locked away until your next major upgrade project.

Why now, specifically

Several concrete triggers make the timing real rather than aspirational:

• Support is running down. Standard support for IFS Applications 10 ended on March 27, 2025, with extended support available to March 27, 2028 under IFS’s 5+3 lifecycle policy. IFS Applications 9 has been in restricted support since March 27, 2023, and earlier releases are further along the same path.
• The last Applications 10 update has shipped. Update 26 (January 2025) was the last planned release for IFS Applications 10; from March 2025, regulatory and legal updates are no longer delivered on a general basis, so compliance gaps accumulate over time.
• The capability gap compounds. IFS adds hundreds of enhancements to IFS Cloud every six months. Each release you skip widens the distance between what your business runs on and what it could run on.
• The cost of waiting rises. Extended support is structured to cost more year on year, and the pool of specialists experienced in legacy upgrades is finite — the longer you wait, the more you pay and the harder resourcing becomes.

What this guide will and won’t do

This guide will give you the value case, an honest view of the effort involved, and a practical plan for a low-risk move. It will not quote your price, promise a fixed timeline, or replace a formal upgrade assessment — those require your own data and a conversation with your IFS account team.

2. What’s new in IFS Cloud and why it matters

The value of upgrading is best understood not as a feature list but as capability you are currently missing. The table below contrasts where IFS Applications sits today with what IFS Cloud delivers, across the dimensions that matter most to an operational business.

Capability area	On IFS Applications today	With IFS Cloud
Architecture	Traditional, layered monolithic design	Cloud-native, modular microservices — easier to scale, maintain, and extend without disruption
Release model	Periodic, project-based upgrades	Evergreen: twice-yearly feature updates and monthly service updates, adopted on your schedule
User experience	Legacy UI with partial modernization	Unified, responsive experience with role-based home screens and AI interaction points
AI & automation	Limited or bolted-on AI	IFS.ai embedded in workflows — predictive maintenance, intelligent scheduling, real-time decisions
Integration & APIs	Legacy API framework, some REST	Fully open, REST-first API framework for faster, simpler integration
Extensibility	Customizations with higher maintenance	Low-code / no-code tailoring that reduces custom code and technical debt
Security & compliance	Depends on your hosting model	Built-in security and compliance frameworks with regular updates and monitoring by IFS
Service & asset management	Equipment-focused, less integrated	Unified customer-focused FSM, EAM, and ERP on one data model and one experience

Continuous innovation instead of periodic catch-up

On IFS Applications, new capability arrives when you run an upgrade project. On IFS Cloud, it arrives continuously — you choose when to switch features on. The practical effect is that your platform stops falling behind between projects and starts compounding value between releases.

Embedded Industrial AI, not an add-on

IFS.ai is built into IFS Cloud workflows rather than layered on afterwards, so intelligence shows up where people already work — in scheduling, maintenance, and service. Real customers already rely on it: Transport for London uses it to help meet a 45-minute on-site response SLA, and Cheer Pack anticipates around $1.5 million in annual savings from it. To use AI at this depth, you need to be on IFS Cloud.

One platform across service, assets, and the back office

IFS Cloud brings ERP, EAM, and service management onto a single data model, removing the silos and point-to-point integrations that accumulate on older estates. That unified view is what lets leaders see what is happening — and what happens next — in real time.

3. The cost and risk of staying on IFS Applications

“Our current version still works” is true today. The difficulty is that staying is not a neutral, cost-free choice — it is an active decision whose price and risk grow every quarter. Making those hidden costs visible is the honest counterweight to the comfort of the familiar.

Risk area	What happens if you stay on IFS Applications
Support & lifecycle	Applications 10 is in extended support only (to March 27, 2028); Applications 9 is in restricted support. Fewer fixes, no general regulatory updates, and rising extended-support fees.
Security & patching	Older architecture receives progressively less security attention. Newer threats and hardening land in IFS Cloud, not in legacy releases.
Compliance & audit	Regulatory and legal changes are no longer delivered generally for Applications 10, so compliance gaps accumulate — a growing risk in regulated and government-contract work.
Compatibility drift	Browsers, operating systems, databases, and integrated third-party systems keep moving. Legacy releases fall out of certified compatibility over time.
Technical debt	Customizations built to work around old limitations keep costing maintenance — often to solve problems IFS Cloud no longer has.
Skills scarcity	The pool of specialists for legacy upgrades is finite and shrinking, so resourcing a later move becomes harder and more expensive.
Innovation gap	No access to embedded AI, evergreen updates, or modern cloud capability — while competitors on current platforms move faster.

The compounding cost of deferral

Delay does not hold cost steady — it raises it on both sides. Every six months, IFS adds hundreds of enhancements to IFS Cloud, so the capability gap you would eventually close gets larger. At the same time, extended-support fees rise, compliance exposure grows, and the demand for scarce upgrade specialists intensifies as more customers move at once. Waiting turns a manageable, well-resourced project into a larger, more urgent one.

4. The business value of upgrading (ROI)

The case to move is the sum of value gained and risk avoided. IDC’s 2025 study, The Business Value of IFS Cloud, interviewed organizations across sectors and quantified the return; the headline findings give you a credible starting point for your own business case.

Beyond the headlines, IDC reported an average of $5.5 million in annual benefits per organization, a 24.9% productivity improvement, 50% faster resolution of equipment or site outages, 37% more efficient capital-assets teams, and a 27% reduction in time spent per budget cycle. The table below maps the main value levers to how IFS Cloud delivers them and a KPI you can track.

Value lever	How IFS Cloud delivers it	KPI to track
Staff productivity & UX	Unified, AI-assisted experience reduces manual effort and clicks	Hours saved per user; efficiency benefit ($)
Automation & AI	IFS.ai embedded in scheduling, maintenance, and service	First-time fix rate; outage resolution time
IT cost & consolidation	Retire on-prem hardware; reduce integrations and upgrade projects	Infrastructure spend; capex avoided
Faster innovation	Evergreen updates every six months, adopted on your schedule	Time-to-value for new features
Reduced downtime & risk	Modern security, monitoring, and resilience	Revenue loss avoided from outages ($)
Better decisions	Embedded, real-time analytics and dashboards	Cycle time to insight; forecast accuracy

Treat these figures as evidence of what is achievable, not a promise of your result. The single most useful thing you can do is baseline your current metrics before you upgrade — outage times, cycle times, support effort, infrastructure spend — so the value is provable in your own numbers. Your account team can help model a business case against your data.

5. Upgrade paths and options 

There is no single right way to move. The best path depends on your appetite for change, the state of your customizations, and your timeline. The three shapes below are the common routes; most organizations blend them.

Path	Best for	Typical effort	What you keep / change
Technical (lift-and-shift)	A fast move to a supported, evergreen platform with minimal process change	~3–6 months	Keep existing footprint and most customizations; carry forward some technical debt
Optimized upgrade	Moving to the current release while selectively modernizing high-value areas	~6–12 months	Rationalize customizations; adopt standard processes where they add value
Transformation	Re-basing on standard IFS Cloud processes and driving major improvement with cloud and AI	~12–18 months	Adopt standard processes; retire most custom code; lowest ongoing debt

Deployment options

IFS Cloud offers a choice of deployment — IFS-managed cloud, customer-managed cloud, or on-premises — with the same functionality across all three and the ability to move between them. This means the move to IFS Cloud does not force a hosting decision you are not ready for: you can adopt the evergreen platform now and choose the operating model that fits your control, data-sovereignty, and cost requirements.

Choosing your path

A simple rule works well: match the path to your appetite for change, the real value of your customizations, and your timeline. A phased approach — upgrade first, optimize afterwards — is common and lets you reduce risk while still capturing quick wins. Many customers reach go-live in as little as 6–9 months on a focused scope.

6. How IFS de-risks the move

“This sounds hard” is a fair reaction, and the honest answer is that a platform move takes real work. What changes the risk profile is that you are not doing it alone or from scratch. IFS Upgrade Services, delivered by Global Customer Services, exist specifically to plan and execute upgrades with a proven, repeatable approach.

• Assessment and discovery. Structured readiness assessments and discovery tooling map your current version, customizations, integrations, and technical debt before you commit — so there are fewer surprises.
• A proven methodology. A well-documented, tried-and-tested upgrade journey that reduces the likelihood of issues and keeps the focus on outcomes.
• Data migration tooling. Established tools and patterns for extracting, transforming, and validating your data, so migration is managed rather than improvised.
• Business continuity by design. The approach is built to keep daily operations running through the transition, with rehearsal and staged cutover rather than a risky big bang.
• IFS Success and the partner ecosystem. Outcome-focused partnership to translate goals into work packages, plus a global network of experienced implementation partners.
• Hypercare after go-live. Intensive support in the first weeks after cutover — extended hours and rapid response — to stabilize quickly.
• Evergreen means this is the last one. Because IFS Cloud updates continuously, this is the last disruptive, big-bang upgrade your organization needs to do. Future capability arrives in small, controlled steps.

7. Migration approach and timeline

An upgrade is a finite journey with recognizable phases. Knowing the shape of it makes the effort concrete and plannable.

Phase	What happens
1. Assess	Confirm current version and configuration; inventory customizations and integrations; spot technical debt and build the baseline.
2. Plan & design	Define objectives and success metrics; choose the path; agree scope, roadmap, and governance.
3. Build & migrate	Configure IFS Cloud; rationalize customizations; re-platform integrations onto modern APIs; extract, transform, and validate data.
4. Test	Validate connectivity, data, business processes, performance, and failure scenarios — combining automated checks with business-user verification.
5. Cutover	Confirm readiness, disable legacy access, complete final sync, and go live.
6. Hypercare & optimize	Stabilize with intensive support, monitor performance against baselines, then adopt further capability over time.

Handling customizations, integrations, and data

The move is the ideal moment to reduce technical debt rather than carry it forward. Categorize every customization — business-critical (upgrade it), productivity (evaluate alternatives), workaround (often replaceable by standard capability), and irrelevant (retire it) — and apply the 80/20 rule to the 20% of customizations creating 80% of the burden. Many were built to work around limitations that no longer exist in IFS Cloud’s modern architecture. Re-platform integrations onto open REST APIs and webhooks, and use the move to cleanse data: legacy databases often carry 30–40% unused data that need not migrate at all.

Done well, this is barely felt by the business. In IDC’s study, one engineering customer described a transition so smooth that, apart from the CEO, CFO, and a few testers, the wider business was only told a week beforehand — it felt like a technical upgrade rather than a process change. Schoeller Allibert reported needing only a handful of customizations, none of which affected its future path to IFS Cloud.

What it takes from your team

Plan to resource an executive sponsor, application owners, subject-matter experts for each process area, testers, and a change lead. The time commitment is real but bounded, and it is front-loaded into assessment, design, and testing. Naming these roles early is the difference between a smooth project and a stretched one.

8. Cost, licensing, and commercial considerations

How IFS Cloud is licensed

IFS Cloud is licensed as a subscription — by module and user, plus services and support — replacing the large, periodic capital cost of on-premises upgrades with a more predictable operating cost. This shifts spending from unpredictable upgrade projects and infrastructure refreshes toward a steady subscription, and folds regular, non-disruptive updates into what you already pay.

The TCO view: staying vs moving

A fair commercial comparison looks at the whole picture over three to five years — not just the price of moving, but the accumulating cost of staying.

Cost of staying on IFS Applications	Cost of moving to IFS Cloud
Rising extended-support fees, year on year	Predictable subscription (by module and user)
On-prem hardware, hosting, and maintenance	Reduced or eliminated infrastructure spend
Growing security and compliance exposure	Built-in, continuously updated security and compliance
Recurring cost of custom-code maintenance	Lower technical debt via low-code extensibility
A larger, more urgent forced upgrade later	One managed move, then evergreen — no more big-bang upgrades
Opportunity cost of missed AI and cloud capability	One-off implementation services + change effort

Upgrade programs and incentives

IFS and its partners offer structured upgrade services and commercial models designed to de-risk the investment and give you a predictable cost. The specifics — including any migration incentives or phased commercials — depend on your contract and region, so treat them as a conversation with your account team rather than a fixed menu.

9. Common concerns and objections to pressure-test 

A credible upgrade case names the real worries rather than dodging them. Here is a balanced way to think through the objections we hear most often.

You may be thinking…	A balanced way to think about it
“Our current version still works.”	It works today — but support is winding down, compliance updates have stopped for Applications 10, and the capability gap widens every release. Staying is an accumulating cost, not a saving.
“It’s too expensive.”	Compare the whole picture: rising extended-support fees, on-prem costs, and a larger forced move later, against a predictable subscription and IDC-measured returns. The business case is built on your own numbers with your account team.
“We can’t afford the disruption.”	Modern migration tooling, rehearsal, staged cutover, and hypercare are designed to protect operations. Many customers go live in 6–9 months; some report the business barely noticed the change.
“We’ll lose our customizations.”	The move is a chance to rationalize, not just recreate. Low-code extensibility and open APIs replace much old custom code, and many customizations solved problems IFS Cloud no longer has. Business-critical ones are carried forward.
“Our team is already stretched.”	The commitment is real but bounded and front-loaded. IFS Upgrade Services, partners, and a clear governance model share the load so it doesn’t fall entirely on your people.
“We just upgraded a few years ago.”	That investment is exactly what you protect by moving to evergreen — this is the last big-bang upgrade. From here, capability arrives continuously, on your schedule.
“Why not re-evaluate the whole market instead?”	That’s a fair question. Weigh it honestly: staying in a platform your people know, keeping your data and process investment, and gaining modern cloud and AI capability — against the cost and risk of a full rip-and-replace to an unfamiliar vendor.
“The timing isn’t right for our cycle.”	Extended-support costs rise and specialist capacity tightens as more customers move at once. Starting the assessment now keeps you in control of timing rather than reacting to a deadline.

10. Upgrade readiness checklist and questions to ask 

Use this as a practical starting point to turn intent into action.

Business readiness

• Executive sponsor named and accountable
• Clear objectives tied to measurable business goals, not vague aspirations
• Current metrics baselined so value can be proven after go-live

Technical readiness

• Current version and patch level confirmed
• Integrations inventoried and cloud connectivity tested early
• Customizations catalogued and categorized (upgrade / evaluate / replace / retire)

Data readiness

• Data quality assessed; obsolete and unused data identified for archive rather than migration
• Decision made on what to migrate versus archive

People & change

• Subject-matter experts and testers available for each process area
• Training and change-management approach planned; champions identified

Commercial

• Budget approach and timeline agreed; account team engaged early

Questions to ask IFS or your partner

• Which upgrade path fits our profile, and why?
• What is a realistic timeline for our scope?
• Which reference customers made the same move from our version?
• What support do we get during and after cutover?

11. Upgrade & migration terminology glossary

Lifecycle terms

Standard support — the primary support phase for a release, with the full scope of fixes and regulatory updates. For IFS Applications 10 this ended March 27, 2025.

Extended support — a paid phase after standard support with a similar scope, typically time-limited and rising in cost. Available for Applications 10 to March 27, 2028.

Restricted support — a reduced phase in which new fixes, security responses, and legal updates are no longer generally provided. Applications 9 has been here since March 27, 2023.

5+3 policy — IFS’s lifecycle pattern of five years of standard support followed by three years of extended support before a release enters restricted support.

Evergreen — a model in which the platform is kept continuously current through regular updates, removing the need for periodic major upgrades. IFS Cloud remains on standard support indefinitely under this model.

Upgrade-approach terms

Technical upgrade (lift-and-shift) — moving the existing footprint to IFS Cloud with minimal process change; fastest and least disruptive.

Re-implementation / transformation — adopting standard IFS Cloud processes and rationalizing customizations; more effort, greatest long-term payoff.

Cutover — the point at which you switch from IFS Applications to IFS Cloud in production.

Hypercare — the period of intensive, elevated support immediately after go-live to stabilize the solution.

Data migration — the process of extracting, transforming, cleansing, and loading data from IFS Applications into IFS Cloud.

Platform terms

Configuration vs customization — configuration tailors the system using supported settings and low-code tools; customization changes underlying code and carries higher maintenance cost.

Technical debt — the accumulated cost of legacy customizations and workarounds that must be maintained over time.

Deployment model — how IFS Cloud is run: IFS-managed cloud, customer-managed cloud, or on-premises, with the ability to move between them.

12. Frequently asked questions

What does upgrading from IFS Applications to IFS Cloud actually involve?

It means moving from a periodic, project-based release onto IFS Cloud’s cloud-native, evergreen platform. In practice you assess your current environment, choose an upgrade path, rationalize customizations, migrate and validate data, test thoroughly, cut over, then stabilize with hypercare. From there, updates arrive continuously rather than as future big-bang projects.

Do we have to upgrade — what happens when support ends?

Standard support for IFS Applications 10 ended in March 2025, with extended support only to March 2028; Applications 9 is already in restricted support. As support winds down you receive fewer fixes, no general regulatory updates, and rising fees, while security and compliance exposure grows. Confirm your specific dates with your account team.

How long does an upgrade take?

It depends on scope and path. A technical (lift-and-shift) move is typically around 3–6 months, an optimized upgrade 6–12 months, and a full transformation 12–18 months. Many customers reach go-live in as little as 6–9 months on a focused scope.

Will we lose our customizations?

No — business-critical customizations are carried forward, and the move is a chance to rationalize the rest. Low-code extensibility and open APIs in IFS Cloud replace much of the old custom code, and many customizations were built to work around limitations that no longer exist.

Technical upgrade or re-implementation — which is right for us?

Match the choice to your appetite for change, the value of your customizations, and your timeline. Choose a technical upgrade for speed and minimal disruption; choose transformation to adopt standard processes and maximize long-term value. A phased approach — upgrade first, optimize later — is a common middle ground.

Is now the right time, or should we wait?

Waiting rarely reduces cost. Extended-support fees rise year on year, compliance gaps accumulate, the capability gap widens every six months, and specialist capacity tightens as more customers move at once. Starting the assessment now keeps timing in your control.

What will it cost?

There is no fixed price. Cost depends on your modules, users, chosen path, and services. IFS Cloud replaces large periodic upgrade costs with a predictable subscription; model the full three-to-five-year TCO with your account team and your own finance team.

What’s new in IFS Cloud that we can’t get on IFS Applications?

Cloud-native architecture, a unified and responsive user experience, embedded IFS.ai, open REST APIs, low-code extensibility, built-in security and compliance, and evergreen updates every six months. Crucially, embedded Industrial AI requires IFS Cloud — it cannot be delivered on legacy releases.

How does IFS help us reduce the risk?

IFS Upgrade Services, delivered by Global Customer Services, provide readiness assessments, discovery and data-migration tooling, a proven methodology, rehearsal and staged cutover, IFS Success, a partner ecosystem, and hypercare after go-live.

Is this the last big upgrade we’ll have to do?

Yes. Because IFS Cloud is evergreen, this is the last disruptive, big-bang upgrade your organization needs. After it, capability arrives in small, controlled updates you adopt on your own schedule.

Suggested next step

The most useful next move is small and concrete: ask your IFS account team or customer success contact for an upgrade assessment. It maps your current version, customizations, integrations, and data, recommends the right path for your profile, and gives you a realistic timeline and business case built on your own numbers — with no obligation to commit.

---

About this guide. This guide is published by IFS to help existing customers evaluate an upgrade from IFS Applications to IFS Cloud. It is based on current product and lifecycle information, which changes over time — validate all dates, capabilities, and commercial terms with your IFS account team. It is not a substitute for a formal upgrade assessment or for your own planning and professional advice.