⬆️ OasisPro · IFS Cloud Upgrade · Apps 10 · Evergreen · CrystalWorks · PermissionWorks
The IFS Cloud upgrade clock is running.
Extended support ends March 2028.
IFS Cloud upgrade planning has moved from strategic option to calendar problem for IFS Applications 10 customers. Standard support for Apps 10 ended on 27 March 2025, the final planned update was Update 26, and extended support runs only until 27 March 2028, at rising cost and without general regulatory updates. That leaves a shrinking window in which hundreds of businesses will compete for the same specialist IFS Cloud resource. The businesses that start in 2026 will get the calm version of this project.
This guide sets out the IFS Cloud upgrade decision for Apps 10 customers: the support timeline, the technical upgrade versus reimplementation choice, and the 6 steps that make the move succeed.
It draws on OasisPro's decade-plus of IFS consulting across Apps 10 and IFS Cloud, and the tooling we built specifically for upgrade pain points.
An IFS Cloud upgrade is not a version upgrade. It is a move to an architecturally different, evergreen platform. That is exactly why it is the last big upgrade you should ever need to do.
Apps 10 customers periodically absorbed major version upgrades. IFS Cloud replaces that cycle with an evergreen model: two release updates a year, monthly service updates, and one unified codebase spanning ERP, EAM, and FSM. The upgrade project is real work, but it ends the era of multi-year upgrade programmes. The strategic question is not whether to move, it is how to move well and when to start.
Why the IFS Cloud upgrade window matters more than the deadline
Extended support is designed to be a bridge, not a home. Costs step up year on year, and regulatory capabilities are no longer implemented on a general basis.
For businesses in regulated or fast-moving compliance environments, that second point is the sharp one. EU eInvoicing mandates, tax changes, and payment standards keep arriving whether Apps 10 receives updates or not.
The resource squeeze is the other quiet risk. IFS has a large installed base still on Apps 10, and a limited pool of experienced IFS Cloud upgrade consultants.
Every quarter closer to March 2028 concentrates more projects into fewer available teams. Starting early is the cheapest risk reduction available.
The IFS Community support timeline discussion confirms the Apps 10 dates, and IFS publishes the release cadence for IFS Cloud itself.
IFS Cloud upgrade routes: technical upgrade versus reimplementation
Apps 10 has a direct upgrade path to IFS Cloud, which makes the route decision a genuine choice rather than a forced reimplementation. The right answer depends on what you are carrying.
Technical upgrade
Carries your data estate and configuration forward on the supported Apps 10 to IFS Cloud path. Fastest route, least business disruption, and the right default for well-run Apps 10 environments. Customisations still need individual assessment, because the platform underneath them has changed.
Reimplementation
Deploys IFS Cloud fresh and migrates selected data. Slower and more expensive, but the honest choice when customisation debt is heavy, processes have drifted far from standard, or the business wants the reset. Data cleansing becomes an opportunity instead of an obstacle.
Most Apps 10 customers land on a hybrid, and the CRIM inventory decides the mix.
Upgrade the core, redesign the areas the business has outgrown, and retire every customisation that IFS Cloud now covers as standard. In OasisPro upgrade assessments, a substantial share of Apps 10 CRIMs map to standard IFS Cloud capability, configuration, or low-code extension. The customisations you do not carry forward are the ones that never cost you in an update again.
The 6-step IFS Cloud upgrade approach that works
- Step 1: Assessment and route decision. Inventory CRIMs, integrations, reports, and data quality. Score each customisation against IFS Cloud standard capability. The output is a costed route decision: technical upgrade, reimplementation, or hybrid, with a realistic timeline.
- Step 2: Rationalise before you migrate. Retire dead customisations, archive stale data, and standardise processes where the business allows. Every object you do not carry forward removes cost from the project and from every future release update.
- Step 3: Solve reporting deliberately. Crystal Reports is removed from IFS Cloud, completely from 26R2. Rebuilding hundreds of reports in new tooling is a project in itself, which is why OasisPro built CrystalWorks to keep existing Crystal Reports running in IFS Cloud without redevelopment.
- Step 4: Rebuild integrations on projections. IFS Cloud exposes REST APIs through OData projections, and legacy integration methods need reworking against them. Treat the integration layer as an upgrade workstream in its own right, not a cutover-weekend surprise.
- Step 5: Redesign permissions once, properly. Apps 10 permission structures rarely translate cleanly. Rebuilding security by hand takes months, which is why PermissionWorks uses AI-driven analysis to cut permission setup effort by up to 80% and deploy in days.
- Step 6: Cutover, then stay evergreen. Test with real business scenarios, train by role, and go live with a rollback plan. Then adopt the evergreen rhythm: monthly service updates and twice-yearly release updates, absorbed as routine instead of saved up as the next big bang.
The best IFS Cloud upgrade is the one you never repeat. Evergreen means this is the last major upgrade, provided the move is done properly the first time.
For the integration workstream in depth, see our IFS Cloud integration guide covering REST APIs, projections, and the patterns that work in production.
OasisPro brings the upgrade team and the upgrade tooling.
Senior IFS consultants across functional and technical workstreams, plus CrystalWorks for reporting continuity and PermissionWorks for security rebuild. That combination removes the two workstreams that most often blow up Apps 10 upgrade timelines.
Read how CrystalWorks keeps Crystal Reports running in IFS CloudOn Apps 10? Get your upgrade assessment done while the calendar is still your friend.
Talk to OasisPro about your Apps 10 estate. We will inventory your CRIMs, reports, and integrations, give you a costed route decision, and show you what the move to evergreen IFS Cloud looks like for your business specifically.
When does support for IFS Applications 10 end?
Standard support for IFS Applications 10 ended on 27 March 2025, with the final planned update being Update 26. Apps 10 then moved into extended support, which runs until 27 March 2028 at progressively increasing cost and without regulatory capabilities being implemented on a general basis. IFS Applications 9 has been in restricted support since 2023.
Should we do a technical upgrade or a reimplementation?
A technical upgrade carries your existing data and configuration forward on the direct Apps 10 path and is typically faster. A reimplementation deploys IFS Cloud fresh and migrates selected data, which suits businesses with heavy customisation debt or processes they want to redesign. Most Apps 10 customers land on a hybrid: upgrade the core, redesign where the business has outgrown its setup, and retire customisations that IFS Cloud covers as standard.
What happens to our customisations and Crystal Reports?
Customisations (CRIMs) are assessed individually: many are replaced by standard IFS Cloud capability, some become configurations or low-code extensions, and a minority need rebuilding. Crystal Reports is being removed from IFS Cloud, with complete removal in 26R2, so report strategy is part of every upgrade. OasisPro's CrystalWorks keeps existing Crystal Reports running in IFS Cloud without redevelopment, protecting years of report investment.
How long does an IFS Cloud upgrade take?
Timelines depend on scope, customisation volume, and data quality. A focused technical upgrade for a mid-sized business typically runs months rather than years, while reimplementations take longer. The stronger driver is the calendar: with extended support ending in March 2028 and specialist resource in high demand, upgrades started in 2026 get better resourcing and calmer timelines than those started later.
The IFS Cloud upgrade question is when, not whether. Choose your when.
Apps 10 served its era well. That era has a published end date, and every business still on it will make this move before March 2028, either on their own schedule or on the calendar's.
OasisPro delivers IFS Cloud upgrades with the consultants, the method, and the tooling to make it the last major ERP upgrade your business does.
Start with the assessment.