This guide breaks down everything you need to know about the IFS Cloud upgrade; what it involves, which upgrade path suits your organisation, and how each stage of the process works.
Many organisations running IFS Apps 9 or IFS Applications 10 believe their ERP environment is modern enough. The Aurena interface looks current, updates arrive regularly, and day-to-day operations continue without disruption. However, this perception carries a meaningful risk: staying on legacy IFS is not the same as staying Evergreen, and the support timelines have already begun to close.
Standard support for IFS Applications 10, ended in March 2025, with only extended support remaining at progressively increasing cost. IFS Applications 9 has been in restricted support since 2023. For organisations yet to act, the window for a structured, well-resourced upgrade is narrowing.
This guide draws on the experience of Creative Software's, IFS Lead Technical Consultants to explain what an IFS Cloud upgrade involves, who needs it, how to choose the right upgrade path, and what each stage of the process requires. Our IFS services and support team works across upgrades, integrations, and ongoing operations and the guidance here reflects what we see on the ground across real client environments.
What Is an IFS Cloud Upgrade?
An IFS Cloud upgrade is the process of moving from a legacy IFS application (typically Apps 8, 9, or 10) and onto the modern IFS Cloud platform. It is not a version update or a patch cycle. It is a full modernisation of your ERP environment, including your business processes, custom code, integrations, security model, and data structures.
How Does an IFS Cloud Upgrade Differ from a Version Update?
On legacy IFS versions, organisations periodically apply version upgrades which refers to, moving from one major release to another, such as Apps 9 to Apps 10.
An IFS Cloud upgrade is categorically different from this. It is a deliberate migration to an architecturally different platform; one built on a single unified codebase that spans ERP, Enterprise Asset Management, and Field Service Management, with embedded AI capabilities and a composable, cloud-native architecture. Once on IFS Cloud, the equivalent ongoing updates are Service Updates (delivered monthly) and Release Updates (delivered every six months), which apply new capabilities and fixes without requiring a formal upgrade project.
The scope of change is broader than most organisations anticipate when they begin planning;
- Custom code must be uplifted to IFS Cloud standards.
- Integrations must be reviewed and rebuilt where necessary.
- Security and permissions cannot be migrated directly, they must be reconstructed for the cloud model.
What "Evergreen" Means and What It Does Not
The term "Evergreen" describes a software environment that receives continuous updates without requiring costly, disruptive upgrade projects. IFS Cloud delivers this through monthly service updates and major releases every six months, applied without interrupting daily operations.
A question that frequently arises is whether IFS Cloud is the only path to Evergreen, or whether staying current on IFS Applications 10 achieves the same outcome. The honest answer is that it does not entirely. Organisations can stay current on Apps 10 by applying the latest Updates (UPDs) and remain evergreen on that track. However, IFS Cloud is strongly recommended because it eliminates the need for multiple rounds of major upgrades that legacy versions require and deliver Monthly Service Updates and six-month Release Updates without disruption. More importantly, IFS Cloud is the latest platform from IFS and the only route to the newest features and capabilities developed by IFS R&D that are not available on Apps 10. Organisations on Apps 10 will need to move to IFS Cloud eventually; the question is when, and under what conditions.
Why Are Organisations Upgrading to IFS Cloud Now?
The Support Timeline Every IFS Customer Should Know
The commercial pressure to upgrade has become concrete. IFS Applications 9 went into restricted support in March 2023 which means new bug fixes, security vulnerability responses, and legal changes are no longer included in the standard support arrangement. For Apps 10, extended support costs are structured to increase year on year, rising significantly through to 2026. IFS Cloud, by contrast, remains on standard support indefinitely under the Evergreen model.
Organisations that delay are not simply deferring cost, they are accepting growing exposure on security, compliance, and performance, while paying more each year for a diminishing level of support.
What IFS Cloud Unlocks: AI, IoT, and Continuous Innovation
Beyond the support argument, IFS Cloud significantly advances the AI and IoT capabilities available to organisations. While Apps 9 and Apps 10 did offer AI and IoT functionality in earlier forms, IFS Cloud takes these considerably further through IFS.ai which is an embedded industrial AI layer that spans predictive maintenance, AI-driven scheduling, demand forecasting, and operational automation across ERP, EAM, and FSM. The depth of integration, the breadth of use cases, and the pace of new capability delivery are materially different from what legacy versions provide.
For organisations in service-intensive industrie such as; field service providers, asset-heavy manufacturers, or businesses investing in IoT or machine learning, these capabilities represent a meaningful shift in what the ERP platform can deliver and one that compounds in value with every release update.
Who Should Be Considering an IFS Cloud Upgrade?
Is My Organisation Ready to Upgrade to IFS Cloud?
The honest answer is that readiness is less about technical maturity and more about strategic intent. Any organisation currently on a legacy IFS version (Apps 8, 9, or 10) is a candidate. The practical question is whether the organisation has the internal capacity to sustain a structured upgrade programme alongside normal operations.
Organisations with the most to gain include service providers managing distributed or remote field teams, businesses investing in AI or IoT-powered innovation, and enterprises with complex multi-country operations where a unified, continuously updated ERP reduces operational risk. Organisations on Apps 7.5 or 8 should anticipate a more extensive re-implementation process, given the version distance involved.
The primary risk in delaying is not technical, it is resourcing. As more organisations approach their support deadlines simultaneously, the pool of experienced IFS Cloud consultants becomes constrained. Early movers have more choice in how they structure the project and who they bring in to support it.
What are the Three IFS Cloud Upgrade Paths?
Choosing the right path is one of the most consequential decisions in the upgrade planning process. Each path carries different trade-offs in speed, risk, change management burden, and post-go-live outcome.
- As-Is - Lift and Shift
The As-Is path prioritises speed. Existing processes are carried across to IFS Cloud with minimal change. Only critical fixes are addressed, and the emphasis is on moving fast with limited disruption. This path suits organisations with well-functioning processes that simply need to reach the Cloud platform quickly, and where change management capacity is limited.
The trade-off is that technical debt and process inefficiencies travel with the upgrade. Organisations using this path typically face more post-go-live optimisation work as they begin adopting Cloud-native features.
- Normal - Uplift and Optimise
The Normal path takes a balanced approach. Selected IFS Cloud capabilities are adopted where they clearly deliver value, and processes are tuned before go-live. This path suits organisations that want to arrive on IFS Cloud in a stronger operational position, without the full investment of a re-implementation.
It requires more planning and stakeholder engagement than the As-Is route, but the post-go-live environment is typically cleaner and more aligned with Cloud-native ways of working.
- Re-Implementation - Full Redesign
Re-implementation is a full redesign and relaunch of the IFS environment. Data is reloaded, structures are reworked from the ground up, and IFS Cloud is configured as a solid foundation for the future rather than a continuation of the existing system. This path is most appropriate for organisations upgrading from older versions such as IFS Apps 7.5 or 8, or those where the existing installation has accumulated significant complexity that would not travel well through a direct upgrade.
Re-implementation takes longer to reach go-live, but the resulting environment is typically more aligned with IFS Cloud's architecture and better positioned to adopt ongoing innovation.
How the Upgrade Process Works - Stage by Stage
What Happens During an IFS Cloud Technical Upgrade?
The upgrade follows four stages. Stages 2 and 3 may each require several iterations before the team is confident enough to proceed. This is a deliberate feature of the process and organisations should plan their timelines accordingly.
- Stage 1 - Initial Planning and Path Selection
Planning begins by translating the readiness assessment into a concrete project plan. This involves confirming the scope of customisations, locking the statement of work, setting milestones, and assembling the right team. The upgrade path (As-Is, Normal, or Re-Implementation) is confirmed at this stage based on the organisation's version, process maturity, and strategic objectives.
The quality of planning directly shapes the outcome. Organisations that invest time in this stage, particularly to understand their customisation landscape and integration dependencies, experience fewer surprises in later stages.
- Stage 2 - Technical Upgrade and Solution Validation
The technical upgrade covers a structured set of activities: setting up the IFS Lifecycle Experience (LCE) Build Studio and the customer solution repository, uplifting all custom code, configurations, reports, and integrations to IFS Cloud standards, and updating or replacing deprecated features.
For example, document storage requires migration from shared repositories to IFS Cloud File Storage. Security and permissions must be fully rebuilt for the cloud model since there is no automated migration path for these.
Data migration from the legacy IFS system is handled using the IFS Cloud Data Migration Toolkit, specifically the Data Migration Manager (DMM). Once the technical uplift is complete, validation begins thereby functionally testing all uplifted components against daily workflows, and conducting load, permission, and security testing. Each iteration of testing may reveal further work, and teams should expect multiple test cycles before the technical and functional leads are ready to proceed.
One area that is frequently underestimated is data quality. IFS Cloud maintains a single, shared master data model, which means duplicate records for customers, suppliers, or other master data entities can cause significant issues during and after migration. Organisations are strongly advised to conduct a thorough data cleansing exercise before the first trial migration run, rather than carrying duplicates and inconsistencies into the Cloud environment. Addressing this early reduces rework considerably and leads to a cleaner, more reliable go-live.
- Stage 3 - Rehearsal and Training
This entails a full dress rehearsal of the go-live process, conducted using cleansed data. This is where the organisation tests the upgraded environment under conditions that mirror production as closely as possible. End-user training also takes place during this phase, ensuring that teams are operationally prepared before the cutover. Any issues surfaced during rehearsal are resolved before proceeding making this stage a critical quality gate in the upgrade process.
- Stage 4 - Go-Live and Hypercare
Go-live execution switches production to IFS Cloud according to the agreed cutover plan. This is a high-stakes phase that requires careful coordination across technical and business teams. A defined hypercare period follows immediately, with named owners responsible for monitoring and stabilising the system. This phase is frequently underplanned but it is where the real-world performance of the upgrade is determined. Organisations with a structured hypercare plan, clear escalation paths, and dedicated post-launch capacity recover faster and establish a more stable foundation for ongoing Evergreen operations.
What Does a Successful IFS Cloud Upgrade Look Like in Practice?
The outcomes of a well-executed upgrade are both technical and operational. VT Industries worked with Creative Software to complete a seamless upgrade from IFS Applications 10 to IFS Cloud, achieving measurable improvements in operational efficiency and system reliability. The project is a practical illustration of what structured preparation and the right technical partnership can deliver.
The defining characteristic of upgrades that go well is not simply technical skill, it is the presence of a team that understands both the platform and the operational context of the business it is supporting. Upgrades are planned well, staffed correctly, and carried through by people who have navigated the process before.
Upgrading to IFS Cloud Is a Strategic Decision, Not Just a Technical One
The IFS Cloud upgrade represents a structural shift in how your ERP platform supports the business. It closes the technical debt accumulated on legacy versions, establishes a foundation for continuous innovation, and positions the organisation to adopt AI, IoT, and machine learning capabilities as they mature within the platform.
The three upgrade paths (As-Is, Normal, and Re-Implementation) give organisations genuine flexibility in how they approach the transition. But the choice of path, the quality of planning, and the capability of the technical team executing the upgrade will determine whether the outcome delivers lasting value or simply moves the problem forward.
If you are building or extending the technical team needed to support your IFS Cloud programme across the upgrade itself, integrations, or ongoing operations, our dedicated IFS technical consultants are experienced across the full upgrade lifecycle. Book a 15-minute call with our team to explore how we can support your upgrade programme.
Conclusion
Creative Software provides dedicated development and IFS technical teams to software enterprises across Scandinavia and Europe. Learn more about our IFS services or explore our customer stories.
