Other ERPsFree calculatorPDF, Excel, Word exportIFS ApplicationsAll IFS Applications tools

IFS Applications 9/10 to IFS Cloud Upgrade Effort Calculator

This calculator estimates the technical effort to move an IFS Applications 9 or 10 on-premises installation to IFS Cloud from a count of your customizations and integrations. It is meant for the first budget conversation, before a partner runs a formal upgrade analysis.

Your numbers

Changes to standard IFS code delivered in the customer layer (Cust), as opposed to configurations.

40 % of build

Upgrade run, data checks and fixes for one full rehearsal.

people

Your results

Total technical hours
1,924 hrs
Build plus testing plus rehearsals. Excludes functional training and business testing time.
Elapsed weeks for the team
18.3 weeks
Assumes 35 productive hours per person per week.
Rework and rebuild hours
1,203 hrs
Test hours
481 hrs
Migration rehearsal hours
240 hrs
Share of build from layered code
33.3%

All hour defaults are editable rules of thumb for scoping, not IFS figures. Replace them with your own partner's estimates once you have an upgrade analysis of your installation.

Save results:

Total hours vs number of layered code modifications

Sweeps Layered core code modifications from 0 to 100, holding your other inputs fixed.

Get your upgrade estimate sanity checked

Send your object counts and current Apps 9 or 10 update level and we will review the assumptions and flag the items most likely to move the number.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

How to use it

Count each type of object in your current installation. Custom fields, custom logical units and custom events can be listed from the Custom Objects and Custom Events windows; quick reports from the Quick Reports window; operational reports from the report definitions you actually print. Layered modifications are the changes your partner made to standard IFS code in the customer layer, which usually sit in a version-controlled build area. Then set hours per item. The defaults suit a typical mid-size site; raise them if your objects are poorly documented. Testing is a percentage of build effort, and each data migration rehearsal is a full upgrade run with reconciliation.

  • Count only objects still in use; retiring dead quick reports is free effort saved
  • Treat each changed core package as one layered modification
  • Count an integration once per external system and direction

Why layered code drives the cost

IFS Cloud ships on an evergreen model with regular service updates and release updates. IFS distinguishes configurations, which are made through the client (custom fields, custom LUs, events, page configurations, lobbies, quick reports) and are designed to carry forward, from customizations, which change code and must be re-applied and re-tested on every update. Layered core modifications are the most expensive item twice: once to re-implement against the new code base, and again on each later update. Aurena page configurations from late Apps 10 updates generally carry over better than Enterprise Explorer window customizations, which do not carry over to the Cloud web client and must be redone as page configurations.

Worked example and how to read the result

With the defaults: 120 custom fields at 0.5 hours is 60, 15 custom LUs at 6 is 90, 40 events at 2 is 80, 30 page configurations at 1.5 is 45, 60 quick reports at 0.5 is 30, 35 reports at 6 is 210, 25 layered modifications at 16 is 400 and 12 integrations at 24 is 288. Build is 1,203 hours, testing at 40% adds 481, three rehearsals at 80 add 240, so the total is about 1,924 hours, or roughly 18 weeks for a team of three. Layered code is a third of build. The chart shows how quickly the total climbs as layered changes grow, which is the case for replacing them with configuration where you can.

Common mistakes

Do not forget the reports: operational reports built for Enterprise Explorer layouts often need layout rework in IFS Cloud. Do not count functional training or business user testing in these hours; add them separately. Integrations built on direct database views or PL/SQL calls usually need to move to the Cloud projections and REST APIs, so price them as rebuilds, not re-points. Finally, decide early which layered modifications can become configurations; every one removed cuts both upgrade cost and the cost of each future service update.

Frequently Asked Questions

Can I upgrade directly from IFS Applications 9 or 10 to IFS Cloud?

IFS provides upgrade paths from Apps 9 and Apps 10 to IFS Cloud, usually run by IFS or a partner with database upgrade scripts plus re-implementation of customizations. The data upgrade is mechanical; the effort sits in customizations, reports and integrations, which is what this calculator counts. Confirm the supported source update level with IFS for your installation.

What is IFS Aurena compared with IFS Applications?

Aurena is the browser client that IFS introduced during the Apps 10 update cycle and that became the main client in IFS Cloud. IFS Applications 10 could run both Enterprise Explorer and Aurena. Page configurations made in Aurena on Apps 10 are closer to the IFS Cloud model than Enterprise Explorer customizations.

Are the hour defaults from IFS?

No. They are editable planning assumptions for a typical mid-size installation. IFS and partners produce their own estimates after analysing your actual code and configuration. Use this tool to see which object types dominate and to sanity check a quote, then replace the defaults with real figures.

How many data migration rehearsals should we plan?

Many teams plan at least two full rehearsals, often three: one to find problems, one to prove fixes, and a final timed dress rehearsal that sets the cutover window. Large databases or heavy layered code justify a fourth. Each rehearsal includes the upgrade run, reconciliation reports and fix time.

If you want a private AI assistant that answers questions over your IFS data before, during and after the move to IFS Cloud, we can run it on your own servers.

ArchRay builder
Design the on-prem AI stack for IFS Applications: model, GPUs, RAG pipeline, guardrails
See memory, speed and cost as you swap parts, then export the diagram. Free, in your browser.
Open the builder

Keep exploring

Free tools

ERP fixes and how-tos

Guides

AI on your ERP

Integrations

Software