# IFS Applications 9/10 to IFS Cloud Upgrade Effort Calculator

> Source: https://netray.co/tools/ifs-applications-10-to-ifs-cloud-upgrade-effort-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Estimate the hours and weeks to move an IFS Applications 9 or 10 installation to IFS Cloud, driven by how many custom objects, reports, layered code changes and integrations you carry.

## Category

other-erp

## Erp

IFS Applications

## Audience

- IFS project manager
- IFS technical consultant
- IT manager

## Tool

**Kind:** calculator

**Inputs:**

#### Custom fields

**Key:** custom_fields

**Type:** number

**Default:** 120

**Min:** 0

**Step:** 5

#### Custom logical units

**Key:** custom_lus

**Type:** number

**Default:** 15

**Min:** 0

**Step:** 1

#### Custom events and event actions

**Key:** custom_events

**Type:** number

**Default:** 40

**Min:** 0

**Step:** 1

#### Aurena page configurations / custom pages

**Key:** page_configs

**Type:** number

**Default:** 30

**Min:** 0

**Step:** 1

#### Quick reports

**Key:** quick_reports

**Type:** number

**Default:** 60

**Min:** 0

**Step:** 5

#### Crystal or Report Designer (operational) reports

**Key:** reports

**Type:** number

**Default:** 35

**Min:** 0

**Step:** 1

#### Layered core code modifications

**Key:** layered_mods

**Type:** number

**Default:** 25

**Min:** 0

**Step:** 1

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

#### Integrations

**Key:** integrations

**Type:** number

**Default:** 12

**Min:** 0

**Step:** 1

#### Hours per custom field

**Key:** h_cf

**Type:** number

**Default:** 0.5

**Min:** 0

**Step:** 0.25

#### Hours per custom LU

**Key:** h_lu

**Type:** number

**Default:** 6

**Min:** 0

**Step:** 0.5

#### Hours per event

**Key:** h_ev

**Type:** number

**Default:** 2

**Min:** 0

**Step:** 0.5

#### Hours per page configuration

**Key:** h_pc

**Type:** number

**Default:** 1.5

**Min:** 0

**Step:** 0.5

#### Hours per quick report

**Key:** h_qr

**Type:** number

**Default:** 0.5

**Min:** 0

**Step:** 0.25

#### Hours per operational report

**Key:** h_rep

**Type:** number

**Default:** 6

**Min:** 0

**Step:** 0.5

#### Hours per layered modification

**Key:** h_lm

**Type:** number

**Default:** 16

**Min:** 0

**Step:** 1

#### Hours per integration

**Key:** h_int

**Type:** number

**Default:** 24

**Min:** 0

**Step:** 1

#### Testing effort

**Key:** test_pct

**Type:** slider

**Default:** 40

**Min:** 20

**Max:** 60

**Step:** 5

**Unit:** % of build

#### Data migration rehearsals

**Key:** rehearsals

**Type:** select

**Default:** 3

**Options:**

##### 2

**Value:** 2

##### 3

**Value:** 3

##### 4

**Value:** 4

#### Hours per rehearsal

**Key:** mig_hours

**Type:** number

**Default:** 80

**Min:** 0

**Step:** 10

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

#### Technical team size

**Key:** team_size

**Type:** number

**Default:** 3

**Min:** 1

**Step:** 1

**Unit:** people

**Outputs:**

#### Rework and rebuild hours

**Key:** build_hours

**Expr:** custom_fields * h_cf + custom_lus * h_lu + custom_events * h_ev + page_configs * h_pc + quick_reports * h_qr + reports * h_rep + layered_mods * h_lm + integrations * h_int

**Format:** hours

#### Test hours

**Key:** test_hours

**Expr:** build_hours * test_pct / 100

**Format:** hours

#### Migration rehearsal hours

**Key:** rehearsal_hours

**Expr:** rehearsals * mig_hours

**Format:** hours

#### Total technical hours

**Key:** total_hours

**Expr:** build_hours + test_hours + rehearsal_hours

**Format:** hours

**Primary:** true

**Description:** Build plus testing plus rehearsals. Excludes functional training and business testing time.

#### Elapsed weeks for the team

**Key:** weeks

**Expr:** total_hours / (team_size * 35)

**Format:** weeks

**Primary:** true

**Description:** Assumes 35 productive hours per person per week.

#### Share of build from layered code

**Key:** layered_share

**Expr:** layered_mods * h_lm / build_hours * 100

**Format:** percent

**Chart:**

#### Total hours vs number of layered code modifications

**Type:** line

**X:** layered_mods

**From:** 0

**To:** 100

**Steps:** 21

**Series:**

- total_hours

**Disclaimer:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How to use it

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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

**Body:** 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.

**Cta:** 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.

**Faq:**

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

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

ifs applications 10 upgrade, ifs applications - metrix apps 10 upgrade, ifs apps 10 to ifs cloud, ifs cloud upgrade effort, ifs applications 9, ifs aurena - ifs applications, what is ifs applications 10, ifs cloud migration estimate

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json