IFS Cloud service updates and release upgrades, done routinely

← All services

IFS Cloud is evergreen. IFS ships two major releases a year (25R1 and 25R2, for example) and regular service updates between them with fixes and improvements. Staying current keeps you supported and gives you the new functionality you are paying for. Falling behind makes every later jump bigger, riskier and more expensive. The organisations that find updates easy are the ones that take them on a steady rhythm.

A service update, step by step

1. Impact review. We read the release notes against your CRIMs and flag anything that touches your modifications, reports or integrations.
2. Rebuild. We bring your customer solution up to the new service update in the Build Place, resolve any conflicts and build a new delivery.
3. Deploy to test. The delivery goes to a test environment first, never straight to production.
4. Regression testing. We test your custom code, reports and integrations. Your key users test the business processes, with scripts we keep up to date with you.
5. Production. We deploy in a window agreed with you, check the result, and record what was applied.

Release upgrades

Moving to a new release is a bigger step than a service update. Features are deprecated, APIs change and data structures move. Crystal Reports, for example, is being retired from IFS Cloud by release 26R2 (read what that means). We plan release upgrades early: what changes for you, what needs rework, and a timeline that keeps you inside IFS's support window.

Coming from IFS Applications

If you are still on IFS Applications 8, 9 or 10, the move to IFS Cloud is a larger upgrade. It starts with a review of your customisations (see IFS customisation and CRIMs) and usually includes data migration. We support IFS Applications estates in the meantime, so the timing is your choice.

Frequently asked questions

How often should we take IFS Cloud service updates?

On a regular, planned cadence rather than when something forces it. IFS supports each release for a limited period, so a steady schedule agreed in advance keeps you supported and keeps each update small.

Who tests a service update?

We test the technical side: modifications, reports and integrations. Your key users test the business processes they own, using test scripts we maintain with you.

What is the difference between a service update and a release?

A service update applies fixes and small improvements within a release. A release, such as 25R1 or 25R2, brings new functionality and can deprecate old features, so it needs more planning and testing.

Related services

• IFS consultancy from people who do the technical work
• IFS customisation and modifications that survive upgrades
• IFS Cloud Build Place administration
• IFS data migration, planned and reconciled
• IFS integration with the rest of your estate