# JD Edwards World Parallel Run Cost Calculator

> Source: https://netray.co/tools/jde-world-parallel-run-cost-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Add up the cost of running the old and new systems together, including reconciliation and slippage, and see the true incremental cost of the overlap.

## Category

erp-migration

## Erp

Oracle JD Edwards World

## Audience

- Project manager
- CFO
- CIO

## Tool

**Kind:** calculator

**Currency:** $

**Inputs:**

#### Planned parallel period

**Key:** months

**Type:** slider

**Default:** 3

**Min:** 1

**Max:** 12

**Step:** 1

**Unit:** months

#### Schedule slip

**Key:** slip

**Type:** slider

**Default:** 1

**Min:** 0

**Max:** 6

**Step:** 1

**Unit:** months

**Help:** Months of overlap beyond plan. Include a realistic figure; most cutovers slip.

#### Legacy monthly run cost

**Key:** world_monthly

**Type:** number

**Default:** 22000

**Min:** 0

**Step:** 500

**Unit:** $/month

**Help:** Hardware, software support, hosting and the legacy support team.

#### New system monthly cost

**Key:** new_monthly

**Type:** number

**Default:** 18000

**Min:** 0

**Step:** 500

**Unit:** $/month

**Help:** Subscription or licence and hosting for the new ERP, once it is live.

#### Staff doing dual entry or checking

**Key:** dual_fte

**Type:** number

**Default:** 3

**Min:** 0

**Step:** 0.5

**Unit:** FTE

#### Monthly cost per FTE

**Key:** fte_cost

**Type:** number

**Default:** 7500

**Min:** 0

**Step:** 250

**Unit:** $/month

#### Reconciliation hours per month

**Key:** recon_hours

**Type:** number

**Default:** 120

**Min:** 0

**Step:** 10

**Unit:** hours

#### Hourly rate for reconciliation

**Key:** recon_rate

**Type:** number

**Default:** 70

**Min:** 0

**Step:** 5

**Unit:** $/hour

**Outputs:**

#### Dual-working people cost per month

**Key:** people

**Expr:** dual_fte * fte_cost + recon_hours * recon_rate

**Format:** currency

#### Total monthly cost during overlap

**Key:** monthly

**Expr:** world_monthly + new_monthly + people

**Format:** currency

#### Overlap months including slip

**Key:** span

**Expr:** months + slip

**Format:** months

#### Total cost of the overlap period

**Key:** total

**Expr:** monthly * span

**Format:** currency

**Primary:** true

#### Extra cost over legacy-only running

**Key:** incremental

**Expr:** total - world_monthly * span

**Format:** currency

**Primary:** true

**Description:** What the overlap costs beyond what you would have spent keeping the old system anyway.

#### Cost of the slip alone

**Key:** slip_cost

**Expr:** monthly * slip

**Format:** currency

**Chart:**

#### Overlap cost vs planned parallel months

**Type:** line

**X:** months

**From:** 1

**To:** 12

**Steps:** 12

**Series:**

- total
- incremental

**Disclaimer:** Excludes implementation fees, data conversion and training. Use it only for the cost of the overlap itself.

## Content

**Intro:** Parallel running is a safety net with a monthly bill. Finance teams often budget for the new system but not for what it costs to keep JD Edwards World alive and reconciled while the new one proves itself. This calculator makes that bill visible.

**Sections:**

#### How to use it

**Body:** Enter the cost of running the legacy IBM i system for one month, including hardware support, software maintenance, hosting and the people who support it. Enter the new system's monthly cost for the same period. Then add the human cost of working in parallel: dual entry, checking and daily reconciliation of balances, open orders and inventory. Finally add a realistic slip, since parallel periods tend to be extended once reconciliation finds differences.

#### The method

**Body:** Monthly overlap cost is the legacy cost plus the new cost plus people cost. Total overlap cost is that monthly figure times planned months plus slip. The incremental figure subtracts what the legacy system would have cost anyway over the same months, so it shows the genuine price of the overlap decision. The chart sweeps planned months from one to twelve.

**Bullets:**

- Include contract termination notice periods in the legacy monthly cost if they apply
- Dual-entry cost drops sharply if only a subset of transactions is run in parallel
- A shorter parallel period with strong reconciliation often beats a long one

#### How to read it

**Body:** If the incremental cost is a few percent of the project budget, a longer parallel period is cheap insurance. If it is a large fraction, consider a phased cutover by site or business unit, or a limited parallel run over one month end. The slip line tells you the value of getting data conversion and testing right before go-live: every month saved is a number you can quote.

#### Common mistakes

**Body:** Leaving out the reconciliation effort, assuming the legacy system can be switched off the day after go-live when finance needs it for year-end and audit queries, and forgetting read-only retention. Plan for archive access after shutdown, and decide what evidence auditors will need before you turn the machine off.

**Cta:** If you would like a reconciliation approach that compares balances and open items between systems automatically, Netray can scope that with you.

**Faq:**

#### Should every transaction run in parallel?

**Answer:** Usually not. Many teams choose key flows such as one month end close, a sample of orders and inventory counts. Full parallel running doubles workload and often masks errors through fatigue.

#### What does the incremental figure mean?

**Answer:** It is the total overlap cost minus the legacy-only cost for the same months. It is the real extra money spent because you chose to overlap, which is the number to compare with the risk reduction.

#### How much slip should I enter?

**Answer:** Use your own history. If past projects slipped by a month or more, assume at least one month here. It is better to over-budget than to ask for more later.

#### Does this cover the licence for the old system?

**Answer:** Include it in legacy monthly cost. If the contract allows early termination or a reduced read-only tier, model that as a lower figure.

## Search terms

erp parallel run cost, jd edwards world cutover cost, legacy system retirement cost, dual running erp cost, erp go-live overlap, as400 decommission cost, erp migration budget

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