# ERP Data Cutover Window Calculator

> Source: https://netray.co/tools/legacy-erp-data-cutover-window-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Estimates final load duration, window utilisation and total rehearsal time from record volume, throughput and validation overhead.

## Category

erp-migration

## Audience

- Migration lead
- DBA
- Project manager

## Tool

**Kind:** calculator

**Inputs:**

#### Records to load in cutover

**Key:** records

**Type:** number

**Default:** 5000000

**Min:** 0

**Step:** 100000

**Unit:** records

**Help:** Include open transactions, balances and any master data not loaded earlier.

#### Throughput per stream

**Key:** rpm

**Type:** number

**Default:** 3000

**Min:** 1

**Step:** 100

**Unit:** records/min

**Help:** Measure this in a rehearsal, not from a vendor brochure.

#### Parallel streams

**Key:** streams

**Type:** slider

**Default:** 2

**Min:** 1

**Max:** 8

**Step:** 1

**Unit:** streams

#### Validation and reconciliation overhead

**Key:** overhead

**Type:** slider

**Default:** 40

**Min:** 0

**Max:** 150

**Step:** 5

**Unit:** %

#### Planned full rehearsals

**Key:** mocks

**Type:** slider

**Default:** 3

**Min:** 1

**Max:** 8

**Step:** 1

**Unit:** runs

#### Business cutover window

**Key:** window

**Type:** number

**Default:** 48

**Min:** 1

**Step:** 4

**Unit:** hours

**Outputs:**

#### Raw load time

**Key:** load_minutes

**Expr:** records / (rpm * streams)

**Format:** minutes

#### Load plus validation

**Key:** load_hours

**Expr:** load_minutes * (1 + overhead / 100) / 60

**Format:** hours

**Primary:** true

#### Window headroom

**Key:** headroom

**Expr:** window - load_hours

**Format:** hours

**Primary:** true

**Description:** Negative means the plan does not fit.

#### Window utilisation

**Key:** utilisation

**Expr:** load_hours / window * 100

**Format:** percent

#### Total rehearsal machine time

**Key:** rehearsal_total

**Expr:** load_hours * mocks

**Format:** hours

**Chart:**

#### Load hours vs parallel streams

**Type:** line

**X:** streams

**From:** 1

**To:** 8

**Steps:** 8

**Series:**

- load_hours

**Disclaimer:** Assumes linear scaling across streams. Database locks and API limits usually flatten the gain, so confirm in a rehearsal.

## Content

**Intro:** Cutover plans fail when the final load takes longer than the weekend. This calculator checks whether your volume, throughput and validation time fit the window you have.

**Sections:**

#### How to use it

**Body:** Count only the records loaded during cutover. Master data, closed history and configuration should be loaded days earlier. Take throughput from your most recent rehearsal and enter the number of streams you actually ran. Keep utilisation under 70 percent so a failure can be rerun without missing go-live.

#### The method

**Body:** Raw load minutes equal records divided by throughput times streams. Validation overhead scales the result, then dividing by 60 gives hours. Headroom is the window minus load hours, and utilisation is load hours as a percentage of the window. Rehearsal time is load hours times the number of full runs.

#### Common mistakes

**Body:** Teams extrapolate from a small sample, forget validation, or assume eight streams give eight times the speed. Source system extract time, network transfer and index rebuilds also sit outside this formula, so add them as extra overhead. Treat a result near the window limit as a red flag.

**Bullets:**

- Measure real throughput
- Preload what you can
- Plan a rerun budget
- Include extract and index time

**Cta:** Netray can script and monitor migration loads with reconciliation checks. This tool works without any such help.

**Faq:**

#### How many rehearsals are enough?

**Answer:** Three full rehearsals is a common minimum: one to find errors, one to fix and time, one to prove the runbook. Complex multi-entity migrations may need more.

#### What counts as a record?

**Answer:** Any row you load as a unit, such as a journal line, open invoice or inventory balance. Use the same unit when measuring throughput.

#### Why keep utilisation below 70 percent?

**Answer:** Because failures happen. Spare time lets you rerun a failed step without moving the go-live decision.

#### Does this work for GP and AX?

**Answer:** Yes. The calculation is source-neutral. Only the throughput value differs by tooling and target.

## Search terms

erp cutover window, data migration load time estimate, gp to d365 data migration time, ax data migration cutover hours, erp go live cutover planning, mock migration rehearsal

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