Upgrading to IFS Cloud and migrating from IFS Applications 10
Eqeep plans your move from IFS Applications 10 to IFS Cloud and the release updates that follow. As an IFS Specialized Partner, we assess the route, test in a shadow environment and prepare your team for the go-live decision.
IFS Cloud has two release updates a year and monthly service updates. Your release and service-update position affect which support conditions apply. We plan the work around business priorities, test capacity and those requirements.
Moving from IFS Applications 10 to IFS Cloud
IFS lists Extended Support for IFS Applications 10 through 27 March 2028, followed by Restricted Support. A technical upgrade carries forward your existing configuration; reimplementation starts from the IFS Cloud standard. Your route depends on customisations, data quality and changes to your processes. We compare the work and risks before you choose.
During analysis and design, we compare the technical work with the processes your team wants to improve. You decide which route fits. A reimplementation follows our implementation approach. For more detail, see our IFS Applications 10 migration guide.
How do you plan an IFS Cloud upgrade around daily operations?
Start with tests that cover your processes, customisations and integrations. Eqeep prepares a shadow environment and fallback plan; key users review the test results. Your team approves the go-live timing and any planned interruption to operations.
Scheduling IFS service updates and security patches
We assess service updates and security patches for your environment, including their urgency and testing needs. Your team agrees the installation and approval route within the applicable support requirements. Ongoing monitoring helps identify issues that need attention.
Which new IFS features fit your business?
We review new functionality against your processes and configuration, including industrial AI capabilities, planning tools and reporting. You receive advice on relevance, effort and priorities before deciding what to adopt.
How an IFS upgrade works
- Fit-gap assessment: compare new features with your processes and roadmap.
- Test plan: regression tests for your processes, customisations and integrations in a shadow environment.
- Planned go-live: your team approves the timing, acceptance criteria and fallback route.
- Hypercare: agreed support during the first days after the upgrade.
- Documentation: a record of the changes and decisions your team needs to manage the upgraded environment.
Emergya Wind Technologies moved from IFS Applications 8.2 to 9 in an earlier project. IFS carried out the technical upgrade; Eqeep handled functional verification and testing. Read the EWT story.
IFS Upgrade Journeys
Explore upgrade routes and the choices involved in moving to a newer IFS environment.
Frequently asked questions about IFS Cloud upgrades and IFS Applications 10
Define the release gap, customisations, test ownership and customer approval before planning the upgrade.
When does support end for IFS Applications 10?
IFS lists Extended Support through 27 March 2028 and Restricted Support from 28 March 2028 to 27 March 2030. Restricted Support allows case submission but includes no new updates, fixes or target response times. Check your agreement and plan the next step through analysis and design.
Technical upgrade or reimplementation: how do we choose?
Compare custom code, data quality and the fit of your current processes. A technical upgrade carries forward the existing setup; reimplementation starts from the standard. We assess the trade-offs with your team. You choose the route before implementation begins.
How long does an upgrade take?
The duration depends on the chosen route, release gap, customisations, integrations, data and test capacity. We assess those dependencies during analysis and design. Your team can then review the scope and planning before committing.
What is the difference between a release update and a service update?
A release update introduces a new IFS Cloud release with new functionality. A service update supplies cumulative fixes for your current release. Plan both against your environment’s requirements and the applicable IFS support policy.
How far behind can we fall on IFS Cloud?
IFS defines a current environment as the latest release or one of its three predecessors. Stay no more than three service updates behind the latest update for your release. Consequences depend on deployment and support terms. We check your version and agree the update plan against the applicable IFS policy.
What does Eqeep assess before an upgrade?
We assess service-update currency, customisations, integrations, test coverage and critical business processes. Your team identifies priorities, dependencies and who will accept the test results.
Who gives final approval?
Your team gives final go-live approval. Eqeep prepares test results, remaining issues and the fallback plan so you can make that decision.
Discuss your IFS question
Tell us where you stand with IFS. You get one conversation and a clear next step.
Tell us which release you run, what needs attention and which business processes depend on it.