IFS Applications 10 Extended Support: What to Plan Now

Three dates frame the Apps 10 support position, and they sit on one timeline. The dates come from the IFS Extended Support Terms as summarised in public commentary of October 2026. I have not seen the contract wording for your site, so check this section against your contract and ask your IFS account team to confirm each date in writing.

The three dates give each customer who has purchased IFS Cloud and is upgrading one of two positions on 27 March 2027. Either you hold an active plan and may extend to 27 March 2028, or you hold a new Order Form for support beyond the default date. A customer with neither has no documented support position after 27 March 2027, and that is the situation this article helps you avoid. Any other Apps 10 customer should ask IFS for their own position in writing.

The published summaries of the terms do not define "active IFS Cloud upgrade and migration plan", so anything I write about its content is a question to ask and not a fact. The date 27 March 2028 depends on that phrase, and a phrase without a definition is a contract risk for the finance sponsor.

These are the questions I would put to the IFS account team. Ask for the answers in an email you can file with the contract:

1. Form of the plan. Is it a document, a signed project plan, a statement of work with a start date, or an executed IFS Cloud order?
2. Evidence of activity. Does IFS expect milestones to be met, and who confirms that the plan is still active?
3. Timing of acceptance. Must the plan exist before 27 March 2027, and who at IFS accepts it?
4. Loss of status. What happens to the extension if a milestone slips or the scope changes?
5. Cost. What additional terms and fees apply to Extended Support at each stage, in euros or your contract currency?
6. Interaction with the order. Which IFS Cloud order or subscription must be signed before the plan counts, and from which date does the subscription term run?
7. Go-live and support. Does go-live on IFS Cloud change your Extended Support position, and from which date does the change apply?
8. Order Form. If the plan is not accepted, what does a new Order Form for support after 27 March 2027 contain, and what is its term?

If the account team does not reply within a week, send the same questions again, copy your contract manager and keep the thread with the contract file. Question 7 covers a situation the summaries do not address, and question 8 one they describe only in outline, so they are the ones I would not leave to a phone call. For the wider decision between upgrade approaches, see strategies in ERP upgrade planning.

From 15 October 2026 to 27 March 2027 is 5 months and 12 days, or 163 days, which is about 23 weeks. To 27 March 2028 it is about 17 months. IFS says migrations typically take 6 to 12 months. The time left to the 2027 date is therefore already shorter than the low end of IFS's own range.

The table below is plain calendar arithmetic, offered as an illustration. Your project's duration comes from your own plan. The table assumes go-live happens at the end of the stated duration with no overrun, and the 2028 column assumes the extension is granted.

Two readings follow from the table. Every row ends after 27 March 2027, including the fastest one, so every project needs either the plan-based extension or a new Order Form. And the 2028 date leaves real room only for a project that starts by early 2027.

The September 2027 start is the case I would not accept. It leaves a 6-month project with 26 days of margin and anything longer with none, and it relies on a plan IFS has not defined in writing. Whatever the duration, the go-live has to land in a cutover window your business can tolerate, so check the date against your financial period close. Why ERP upgrades fail lists the planning gaps that sink projects in this phase, and being prepared for an ERP upgrade covers the sponsor-side preparation.

The first 30 days after reading the dates are best spent on a written position with IFS and a named budget owner. The schedule below is the author's practice and uses dates from today, 15 October 2026.

1. By 22 October 2026: find the Apps 10 support and subscription clauses in your contract and note the term end date and any renewal date.
2. By 29 October 2026: send the eight questions about the active plan to your IFS account team in one email.
3. By 5 November 2026: name the budget owner for the upgrade. The extension decision needs a budget owner and not only a project lead, because the answers to the cost questions change the budget.
4. By 13 November 2026: count your customisations and integrations, choose a start month and write down the matching go-live date. The counts feed the duration estimate, and the rows of the countdown table are the model for the dates.

With these four items done you can judge whether an extension to 27 March 2028 is realistic or whether a new Order Form is the safer route.

A plan document that can carry a support extension names an owner, a budget and dated phases for every workstream of the move to IFS Cloud. This list is the author's practice from upgrade projects, and it may differ from what IFS accepts as an active plan.

The data migration row deserves its own planning, and the articles on the IFS Cloud data migration plan and IFS DMM step by step go into the mechanics. Assign each process in the validation row an owner by name before the document goes to IFS. The IFS Cloud upgrade readiness checklist on ifs-erp.com turns these workstreams into questions you can score. If you want the plan reviewed or written with you, I do that work as part of IFS Cloud services.

Book a 30-minute fit call

The destination is IFS Cloud, which receives updates continuously, as service update vs release update explains, so in my reading the move also changes how you take updates after go-live. The cost of that change depends on how you tailor the system. Tailoring through supported extension mechanisms keeps your changes outside the standard code, which is the idea described in the clean core.

That choice belongs in the plan document, because each customisation you rebuild now is a change you will test again at every update. For a project with a data-heavy scope, professional data migration services cover the migration work on its own. The implementation documentation kit offers templates for the update strategy and the handover, and the SCM Automation Pack adds purchasing exception monitoring after go-live, with nothing installed in your IFS Cloud.

Dariusz Myśliwiec brings 18 years of hands-on work with IFS (Apps 7.5–10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Based in Kraków, delivering remotely across Europe and globally as an independent practice, so you talk to the consultant who builds it.

Selected clients: Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm.

Source for the IFS statements on fees, access and migration time: IFS customer success page, read on 15 October 2026. The support dates come from published summaries of the terms and are not legal advice. IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.