IFS Upgrade — Apps 10 to IFS Cloud
Upgrading IFS Applications 10 before end of support, or planning an IFS Cloud migration? Move to IFS Cloud the right way: a functional transformation, not a lift-and-shift. As an IFS Gold Partner, ESS re-maps your processes to IFS Cloud and migrates your data with proprietary, idempotent tooling — for a short cutover and a cleaner system on the other side.
A functional transformation to IFS Cloud — parallel validation, idempotent loads, and high success on complex data.
Not a Version Bump
What Actually Changes in IFS Cloud
Apps 10 to IFS Cloud replaces the client, the architecture, the identity model, the database bar, the reporting stack and the integration surface — all at once. That's why the upgrade is planned as a platform transformation.
New user interface
The IEE desktop client is retired for the Aurena web client — and its permission model has no automatic migration path. Every role is redesigned as Projection Grants.
New architecture
The monolithic install becomes containers on Kubernetes with a Linux middle tier — modern operations, but a different infrastructure discipline.
New identity model
Database and LDAP logins give way to IFS IAM with OpenID Connect and OAuth2 — every SSO connection and API client re-authenticates.
New database bar
Oracle 19c container database with Unicode mandatory — single-byte Apps 10 databases are converted and validated before anything else happens.
New reporting stack
XSL report layouts are retired (they error in IFS Cloud) and SSRS is deprecated — reports migrate to RDL and Report Studio on a planned path.
New integration surface
REST integrations re-map to Projection API endpoints with new URLs and auth — every interface is inventoried, re-pointed and regression-tested.
On Apps 8 or 9? IFS Cloud only supports a direct upgrade from Apps 10, so older releases take a planned two-step path — Apps 8/9 to Apps 10 first, then to IFS Cloud. ESS runs both steps and keeps you supported in between.
Our Process
From Apps 10 to IFS Cloud in Five Steps
A controlled, reviewable path that retires workarounds instead of carrying them forward.
01Assess & Re-Map
Compare your Apps 10 configuration to IFS Cloud capabilities and design the target — a functional transformation, not a copy.
02Extract & Stage
Pull master and transactional data; model complex structures like parent-child explicitly.
03Validate in Parallel
Review and sign off on data in a portal against the live business — before anything posts.
04Migrate (Idempotent)
Re-runnable batches load into IFS Cloud with idempotent commits — zero duplicate posts.
05Cutover & Stabilize
Short, controlled cutover, then we stay on to stabilize and optimize on IFS Cloud.
Land on IFS Cloud Better Off — Not Just Current
A lift-and-shift carries your old workarounds and data problems into IFS Cloud. ESS re-maps functionally, so the upgrade is a chance to clean up, adopt newer IFS capabilities and simplify — with the data risk engineered out through parallel validation and idempotent loads.
- Functional transformation to IFS Cloud — not a lift-and-shift
- Upgrade paths from IFS 8, 9 and 10
- Proprietary, portal-driven migration tooling
- Parallel validation with real-time status
- Idempotent loads — re-run safely, zero duplicates
- Handles complex data (e.g. parent-child) at high success rates
Transformation
Not a lift-and-shift
Less Downtime
Short, controlled cutover
Idempotent
Re-run, no duplicates
De-Risked
Validated before posting
Planning a broader program? See IFS Cloud implementation programs, IFS consulting & implementation and IFS integration & API. Comparing partners? Take the IFS partner evaluation kit into your RFI.
The Playbook
Eight Phases, Each With a Go/No-Go Gate
The migration approach above sits inside a full engineering program. Depending on customization and integration complexity, the whole journey runs 6–18 months — and every phase ends with a decision gate, not a hope.
- 01
Assessment & Discovery
3–6 weeksInventory every customization, integration and report, then cross-reference them against IFS's catalog of 2,125 entity changes across 84 components. The output is a formal gap analysis with a verdict per object: compatible, rework, rewrite or obsolete.
- 02
Environment & Infrastructure
2–4 weeksOracle 19c container database stood up, Unicode conversion run and validated where needed, the Linux/Kubernetes middle tier prepared — including the one-shot installer settings that can never be changed after install day.
- 03
Customization & Integration Remediation
4–8 weeksCustom PL/SQL reworked against the changed schema and unit-tested in a sandbox, XSL reports bulk-converted to RDL, IFS Connect configurations merged, the IEE-to-Aurena permission model redesigned, and every API integration re-mapped.
- 04
Pre-Upgrade Preparation
1–2 weeksComponent-specific pre-scripts evaluated one by one for your installation — not blindly executed — hold-table vouchers posted, legacy batch and connect servers decommissioned, and verified backups taken at every gate.
- 05
Main Upgrade Execution
1–3 daysThe rehearsed maintenance window: installer run against the prepared database, invalid objects worked systematically, custom fields and configuration items migrated onto their changed parent entities.
- 06
Post-Upgrade Remediation
3–6 weeksPost-, clean- and drop-scripts executed in the correct order — with obsolete-table data backed up first — reporting objects and materialized views rebuilt, and every integration re-authenticated and retested end to end.
- 07
UAT & Performance Testing
3–6 weeksBusiness-led test scripts across finance, orders, maintenance, reporting, integrations and mobile, plus load testing on the new stack, ending in a formal sign-off from the business owners.
- 08
Go-Live & Hypercare
1–2 weeks + hypercareTransaction freeze, final backup, the production run of the exact procedure validated in UAT, smoke tests — then a 2–4 week war-room hypercare with daily triage until the system is boring again.
Related Reading
Go Deeper
FAQ
IFS Upgrade — FAQ
ESS runs the IFS Apps 10 to IFS Cloud upgrade as a functional transformation, not a lift-and-shift: we re-map your processes to IFS Cloud capabilities, migrate master and transactional data with proprietary migration tooling, validate everything in parallel against the live business, and cut over in a short, controlled window. The five-step path — assess and re-map, extract and stage, validate in parallel, migrate with idempotent loads, then cutover and stabilize — keeps the IFS Cloud migration reviewable at every stage. Because ESS is an IFS Gold Partner with 15+ years of IFS expertise, the target design uses current IFS Cloud capabilities instead of copying your old configuration forward. The result is a cleaner system on the other side, not your Apps 10 workarounds re-hosted.
ESS upgrades and migrates from IFS Applications 8, 9 and 10 to IFS Cloud, and provides support along the way if go-live is still months out. One technical fact shapes the plan: IFS Cloud only supports a direct upgrade from Apps 10, so customers on Apps 8 or 9 take a two-step path — up to Apps 10 first, then to IFS Cloud — which ESS runs as one planned program rather than two surprise projects. The same proprietary, portal-driven tooling, parallel validation and idempotent loads apply across versions, with the depth of re-mapping scaled to how far your release sits from IFS Cloud. Older versions typically carry more workarounds and data debt — exactly what a functional transformation is designed to retire. As an IFS Gold Partner, ESS can also keep maintaining IFS 8 or 9 while the IFS Cloud upgrade is planned, so you don't have to rush the move to stay supported.
Far less than a traditional big-bang load — ESS's incremental, portal-driven approach keeps the IFS Cloud cutover window short. The key is doing the risky work before go-live: data is staged and validated in parallel against the live business while you keep running on Apps 10, so the cutover itself is a controlled, pre-rehearsed event rather than a leap. Idempotent batches add a second layer of protection — any load can be re-run safely without creating duplicates, which removes the classic reason upgrade weekends overrun. On complex IFS data migration work, this approach has cut downtime dramatically versus conventional loads. Tell ESS your current version, data volumes and integration count, and we'll size a realistic cutover window for your upgrade.
Complex relationships such as parent-child master data are modeled explicitly in the migration rather than flattened into generic templates — because these structures are exactly where a typical IFS data migration goes wrong. ESS's proprietary tooling stages them in a portal where they're validated and signed off before anything posts to IFS Cloud, and loads run with idempotent commits so a re-run never creates duplicate records. That combination — explicit modeling, parallel validation, safe re-runs — is how ESS achieves very high migration success rates on difficult data during an IFS Apps 10 to IFS Cloud upgrade. If your Apps 10 environment carries deep structures, custom fields or years of history, that's a reason to engineer the migration properly, not to delay the move.
Typically 6 to 18 months, driven almost entirely by how much you've customized and integrated — the main upgrade itself is only a 1-to-3-day maintenance window at the end of a much longer preparation arc. ESS structures the program into eight phases, each with a go/no-go gate: assessment and gap analysis (3–6 weeks), environment preparation (2–4 weeks), customization and integration remediation (4–8 weeks, usually the long pole), pre-upgrade preparation, the main execution window, post-upgrade remediation (3–6 weeks), UAT and performance testing (3–6 weeks), and a 1–2 week cutover followed by hypercare. The honest answer to "how long" comes out of phase 1: once your customizations are cross-referenced against IFS's entity-change catalog — 2,125 changes across 84 components — the remediation effort, and therefore the timeline, stops being a guess.
They're inventoried, given a verdict, and remediated on a plan — not discovered broken after go-live. Custom PL/SQL is analyzed against the IFS Cloud schema and reworked where entities changed; database triggers behind history logging and custom events are re-validated after the upgrade invalidates them; custom fields and information cards are migrated onto their changed parent entities. Reports follow a defined path: XSL layouts are bulk-converted to RDL (unconverted XSL hard-errors in IFS Cloud), Business Reporter reports go through the upgrade utility, and SSRS users plan a move to Report Studio or Power BI since SSRS is deprecated. The biggest single effort is permissions: there is no automatic migration from IEE Presentation Objects to Aurena Projection Grants, so ESS starts that mapping in phase 1 with your business owners — starting it late is the most common cause of a slipped go-live.
Both — and that's the point of treating the move as a functional transformation. Because ESS re-maps your processes to IFS Cloud capabilities instead of copying the old configuration forward, the upgrade becomes the natural moment to retire workarounds, clean up data and adopt newer capabilities like embedded AI, analytics and the modern interface. Once live, the platform's evergreen cadence keeps you current through routine IFS Cloud release updates instead of another big-bang project years from now. Clients land better off than before — not just on a newer version number. As an IFS Gold Partner, ESS can show what this looked like on a real project; see the Apps 10 to Cloud case study linked on this page.
Ready to Move to IFS Cloud?
Tell us your current IFS version and data complexity. We'll outline a functional-transformation upgrade with a short, predictable cutover.









