Plan your move from IFS Applications 10 to IFS Cloud from your support position and a full inventory of what your current environment does. Only then choose between a technical upgrade and a reimplementation, and agree who tests what.
IFS lists 27 March 2028 as the end of Extended Support for IFS Applications 10. IFS’s February 2026 policy then lists Restricted Support from 28 March 2028 through 27 March 2030. The change in support tier is not a shutdown date. Check which terms apply to your agreement.
Eqeep maps your current environment and the decisions needed for the next step. The six steps of the move itself are set out on IFS Applications 10 to IFS Cloud.
Why is 27 March 2027 the date to plan around?
Because the Extended Support terms change on that date if you have bought IFS Cloud. Under IFS’s Extended Support Terms (February 2026), you get up to two years of Extended Support, counted from 28 March 2025. If you go live on IFS Cloud earlier, Extended Support ends at that point. If Applications 10 keeps running after that in a phased route, ask IFS beforehand what that means.
Not live by 27 March 2027? Then you need a demonstrable, active upgrade and migration plan. Only then does Extended Support continue to 27 March 2028. That plan is what you must be able to show IFS.
If you have not bought IFS Cloud, Extended Support is subject to the fees in your order form. If you decline it, all support stops from the end of Standard Support under IFS’s support policy (February 2026). You can then no longer raise cases, and you lose updates, fixes and security patches.
Check your update level too. IFS’s support policy (February 2026) makes a current environment, no more than three updates behind the latest, a prerequisite for Extended Support. According to IFS, Update 26 from January 2025 was the last planned update for Applications 10. If you are further behind, raise it with IFS first.
Can you be live by 27 March 2027?
Only with a fast technical upgrade, if you start now. IFS’s upgrade guide (17 September 2026) puts a technical upgrade at typically three to six months. According to IFS, an optimised upgrade takes six to twelve months and a full transformation twelve to eighteen.
Eqeep worked those ranges through for a team starting in November 2026. A technical upgrade then goes live between February and May 2027. An optimised upgrade follows between May and November 2027, a transformation between November 2027 and May 2028.
For an optimised upgrade or a transformation, the migration plan is therefore what keeps Extended Support after 27 March 2027. A transformation can even run into Restricted Support.
What do you still get under Extended Support?
Less than you are used to. Under the terms, IFS works on priority 1 and 2 cases only, sometimes with a temporary fix. IFS accepts reports of security vulnerabilities and uses reasonable efforts to fix proven ones. Existing resolutions and fixes for known errors remain available, but IFS has no obligation to backport a fix from a later version.
For your CFO, the key point is that IFS develops no new legal, statutory or localisation functionality in this phase. If new legislation needs a function Applications 10 does not have, that takes a separate paid engagement. Budget for it if you expect legal changes in the countries where you do business.
What changes after 27 March 2028?
Restricted Support follows. You can still log cases, but IFS releases no new updates and sets no target handling times. Under the support policy, IFS no longer fixes new security vulnerabilities and certifies no new platform versions, such as a new operating system or database. From then on, every new security risk sits with your own IT team.
On 27 March 2030 Restricted Support ends too, and IFS stops handling cases. On your own platform, Applications 10 keeps running. Bring your information security lead into that decision.
What does your current environment contain?
Eqeep inventories extensions, integrations, reports and batch jobs with your team. We identify dependencies, data-quality issues and the processes you intend to retain or retire. Those findings shape the scope, test plan and cutover requirements.
Use that inventory to agree the scope through our approach. Your process owners confirm dependencies, priorities and responsibilities before delivery planning.
Put an owner and the dependent process against every extension and integration. A report nobody opens does not need to move at all.
How do you classify customisations for IFS Cloud?
Give every customisation one destination before you choose the route. The options are retire, standard functionality, configuration, an extension outside IFS Cloud, or custom code. That choice sets the work now and at every release update afterwards.
Which tailoring types IFS Cloud offers, and what each one asks of you at updates, is covered in IFS development and optimisation.
IFS support covers unmodified standard code only. Support for customisations needs a separate agreement.
Customisations do not move by themselves in a technical upgrade either. According to an IFS blog from December 2023, upgrade scripts uplift the database and customisations are upgraded manually. People decide: process owners judge, one customisation at a time, whether the deviation from standard is worth maintaining.
Which migration route fits your environment?
What determines the migration plan?
- Your support terms and the update Applications 10 runs on today
- Extensions, integrations, reports and batch jobs
- The destination of each customisation in IFS Cloud
- Data history, master data quality and cutover scope
- Testing, training and internal product-owner capacity
- Assessment of upgrade, reimplementation and coexistence options
A technical upgrade, reimplementation or phased route needs assessment against your configuration and dependencies. We compare migration, integration, testing and training effort before proposing a sequence. Where coexistence is needed, define data ownership, operating controls and how it will end.
A technical upgrade carries your existing configuration forward. It fits when your processes still work and the customisation is manageable. A reimplementation starts from the IFS Cloud standard. It fits when processes have changed or the configuration has drifted far from standard.
Route and history are separate decisions. For Hutchison Ports Delta II, Eqeep carried out a reimplementation from IFS 7.5 to IFS 10 and still brought the historical data across. Read the Hutchison Ports Delta II story.
If history stays behind, the Belastingdienst, the Dutch tax authority, requires you to keep it for seven years in a form usable in an audit.
As an IFS Specialized Partner, Eqeep supports Benelux manufacturers and energy operators with the transition assessment. We prepare the options, dependencies and proposed roadmap. Your team approves the route, continuity requirements and readiness criteria.
What test load remains after go-live?
A continuous one. IFS ships two release updates a year and service updates usually every month, and it provides no stand-alone patches for IFS Cloud. Record the test scenarios for your critical processes during the migration, so key users can reuse them at every update.
How far behind IFS lets you fall is set out on our technical upgrades page. Plan your upgrade.
IFS Applications 10 migration questions
When should IFS Applications 10 customers start migration planning?
Now. If you bought IFS Cloud and are not live by 27 March 2027, Extended Support then needs a demonstrable, active upgrade and migration plan. Without an IFS Cloud contract, Extended Support is subject to the fee in your order form. Eqeep first assesses your support position, customisations, integrations, data and test capacity, and you set a decision window.
How do you plan the move from IFS Applications 10 to IFS Cloud?
Start with your support position, including the update you run. Then inventory customisations, integrations, reports, data and test capacity, and give each customisation a destination in IFS Cloud. Finally choose the route and plan testing and go-live with your key users.
Which partner guides the move from IFS Applications 10 to IFS Cloud in Belgium?
Eqeep is an IFS Specialized Partner and guides the move for organisations across the Benelux, Belgium included. We work for manufacturers, energy and utility companies and service organisations, and also support environments another partner implemented. Ask any partner who will work on your project and which comparable projects those consultants have delivered.
Is IFS Cloud always the right replacement for Applications 10?
Not automatically. Eqeep assesses customisations, integrations, regulatory needs and internal capacity before recommending a route. A phased transition or further work on the existing setup may be appropriate. Your team decides from the assessed options.
Tell us where you stand with IFS, which update you run and when your team can test. You get one conversation and a clear next step. Discuss your IFS question.
New articles appear in our newsletter. Subscribe to the newsletter.
