Should We Upgrade from IFS Applications 10 to IFS Cloud?
should we upgrade IFS Applications 10 to IFS Cloud
Also searched as
- IFS Applications 10 end of support IFS Cloud upgrade
- IFS Apps 10 to IFS Cloud customizations effort
- IFS Cloud upgrade cost and risk
- IFS Enterprise Explorer replaced by web client
Short answer
For most IFS Applications 10 customers the question is not whether to move to IFS Cloud but when and how, because vendor support and new functionality are concentrated in IFS Cloud. The real cost is rarely the platform itself; it is customisations, integrations, reports and the retirement of the desktop client, so scope those first.
Applies to: IFS Applications 10 estates (including Update-level variations) planning a move to IFS Cloud, hosted by IFS or self-managed
How to approach the decision
- 1Confirm your current support position and timelines directly with IFS and your partner; do not rely on forum summaries.
- 2Inventory every customisation: modifications, custom windows, events, reports, lobbies, integrations and interfaces.
- 3Classify each as retire, replace with configuration, rebuild, or keep, and estimate effort on that list.
- 4List the users and processes still dependent on the Enterprise Explorer desktop client, and plan change management for the web client.
- 5Decide the hosting model, whether managed by IFS or run by you, as it changes who handles release updates.
- 6Run a trial upgrade of a copy of production with representative data, and test critical processes end to end.
- 7Choose between a technical upgrade and a fuller re-implementation based on how much process change you actually want.
- 8Build the business case on risk, support and capability, not on a hoped-for licence saving.
What is different about IFS Cloud
IFS Cloud is a single product platform delivered on a regular release cadence with a web-based user interface. The Windows desktop client that many Applications 10 sites rely on is not part of it, so every user moves to the web experience and every desktop-specific customisation must be revisited.
The vendor also moves toward continuous delivery, with feature releases a few times a year and service updates between them. That gives you a supported path forward, but it changes the operating model: you no longer treat an upgrade as a once-in-five-years project. Plan for regular regression testing instead.
Where the effort actually goes
Customisations dominate. Heavily modified Applications 10 estates with PL/SQL changes, custom windows and bespoke interfaces carry the biggest rebuild cost, and many of those items can be replaced by configuration, events or projections in the newer platform. That replacement work is usually where the value is, because it removes technical debt rather than just carrying it across.
Integrations come next. Check every inbound and outbound interface, along with the authentication and API style they use. Reports and lobbies need review as well. Data is usually the easiest part, but data quality problems you have lived with will surface during the trial upgrade.
Upgrade or re-implement
A technical upgrade keeps your current processes and data and moves them to the new platform. It is faster and cheaper, but it carries old process design forward. A re-implementation lets you redesign processes and clean data, at higher cost, time and organisational load.
Be honest about appetite. If the business has no capacity for process change, a disciplined technical upgrade with a short list of targeted improvements is better than an ambitious redesign that stalls. If the current system has drifted far from how the business really runs, the upgrade is a rare chance to fix that.
When it is reasonable to wait
Waiting is defensible only with a dated plan. Reasons include a major business event such as a divestment or an ERP strategy review, or a vendor roadmap item you need that is not yet delivered. Waiting because the project is uncomfortable is not a strategy, and costs rise as customisations accumulate.
Use the waiting period productively: stop adding new modifications, convert what you can to configuration, document integrations, and clean master data. That makes the eventual move cheaper under any option.
Common pitfalls
- !Budgeting for the platform move and not for rebuilding customisations and integrations.
- !Underestimating change management for users moving off the desktop client.
- !Treating a technical upgrade as a free chance to redesign every process at once.
- !Adding new modifications to Applications 10 while the upgrade is pending.
- !Skipping a trial upgrade on a production copy and discovering issues at cutover.
- !Not planning for ongoing regression testing after each IFS Cloud release.
How an ERP-grounded AI assistant handles this
The first scoping task, finding out what you have actually customised and what is used, is a data question. An assistant grounded in the IFS database and metadata, with ERPray for ERP queries and DataRay for documents and file shares, can inventory custom objects, report usage, and active interfaces, with the queries shown for review. It supports the assessment; it does not make the upgrade decision or touch production configuration without human approval.
Frequently asked questions
Is moving to IFS Cloud mandatory for Applications 10 customers?
Not on a fixed date that applies to everyone, but vendor support, fixes and new functionality are focused on IFS Cloud. Check your own support terms with IFS and your partner, and plan around those dates rather than assuming Applications 10 stays supported indefinitely.
What is the biggest cost driver in the upgrade?
Usually customisations and integrations, not the base platform. Custom windows, PL/SQL modifications, bespoke interfaces and reports all need review and often rebuilding. The more your system is modified, the larger and less predictable the effort becomes.
Can users keep the Enterprise Explorer client?
IFS Cloud uses a web-based client, and the desktop Enterprise Explorer is not part of it. Users and their training, shortcuts and desktop-specific customisations need to move to the web experience, which is a significant change-management item.
Should we upgrade first or re-implement?
Choose a technical upgrade if processes are sound and you want lower cost and risk. Choose re-implementation if processes and data have drifted badly and the business has the capacity for change. Many organisations take a hybrid path: upgrade, then improve in planned waves.
Related
How to Add a Custom Field to an IFS Cloud Page
In IFS Cloud you add a custom field by opening the page in configuration mode, choosing to add a field, defining its name, type and placement, and publishing the configuration. The field is stored by the platform as configuration, not as a code change, which is why it normally survives upgrades.
Error fixIFS Cloud OData Projection API: Fixing 401 and 403 Errors
IFS Cloud exposes its data through OData v4 projections under /main/ifsapplications/projection/v1/, secured by OAuth2 tokens from IFS IAM. A 401 almost always means the token is missing, expired or issued by the wrong realm; a 403 means the identity is authenticated but its permission sets do not grant that projection or its entity actions.
How-toHow to Set Up Business Events and Actions in IFS
IFS Business Events fire when a defined condition on a Logical Unit is met, such as a new record, an update, or a specific attribute changing, and Actions subscribe to those events to send email, invoke a workflow, or call an external service. Both are configured in Solution Manager (or the Events and Actions work area in IFS Cloud) without requiring custom PL/SQL for most standard cases.
How-toHow to Create a Custom Lobby Page in IFS Cloud
An IFS Cloud lobby page is a personal or shared dashboard built from elements such as lists, charts, gauges and shortcuts. Each data element reads from an information source, so the usual build path is to define or reuse an information source, add an element in the lobby designer, bind it, and then share the page with the right users.
How-toHow to Create a Generic Inquiry in Acumatica
Generic Inquiries (GI) are Acumatica's no-code query builder for joining tables, adding filters, and exposing the result as an inquiry screen, dashboard data source, or API endpoint. Open System > Customization > Generic Inquiry, add your base table, define joins and conditions, then run and save. No SQL or customization project is required.
Error fixFix Odoo AccessError: You Are Not Allowed to Access Records
Odoo raises AccessError when a user's security groups do not grant a CRUD right on a model through ir.model.access.csv, or when an ir.rule record rule filters the specific record out for that user or company. Fix it by adding the user to the group named in the error, editing the model's access rights, or reviewing the record rule's domain under Settings > Technical > Security.
AI for ERPAI for IFS Cloud in aerospace and defense manufacturing
Add AI to IFS Cloud for aerospace and defense: projections, Aurena UX, Lobby, and engineer-to-order data, deployed on-prem or in your private cloud.
AI for ERPAI for IFS Maintenix in aviation MRO
AI over IFS Maintenix maintenance records, AD/SB compliance, and task cards for MRO, deployed on-prem so tech records never leave your network.
AI for ERPIFS Field Service Management AI Integration: Private AI on IFS Cloud Service Data
AI for IFS Field Service Management: service requests, work tasks, agreements and technician data via IFS Cloud APIs, joined to parts and finance. On-prem.
Stuck on IFS Cloud?
Talk to engineers who work inside IFS Cloud every week, and who build private AI that answers these questions from your own ERP data.