# JD Edwards Go-Live Cutover Plan Worksheet

> Source: https://netray.co/tools/jde-cutover-plan-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Plan each cutover task with an owner, start hour and duration, and see end times and total window length before the weekend arrives.

## Category

oracle

## Erp

Oracle JD Edwards EnterpriseOne

## Audience

- JDE project manager
- JDE CNC administrator
- ERP cutover lead

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Task

**Key:** task

**Type:** text

#### Owner

**Key:** owner

**Type:** text

#### Phase

**Key:** phase

**Type:** select

**Options:**

- Freeze
- Data
- Technical
- Validation
- Release

#### Start

**Key:** start

**Type:** number

**Unit:** hours from T0

#### Duration

**Key:** dur

**Type:** number

**Unit:** hours

#### End

**Key:** end

**Type:** number

**Expr:** start + dur

**Format:** hours

#### Status

**Key:** status

**Type:** select

**Options:**

- Not started
- In progress
- Done
- Blocked

#### Rollback point

**Key:** rollback

**Type:** select

**Options:**

- Yes
- No

**Rows:**

#### Freeze

**Task:** Freeze transactions and hold batch queues

**Owner:** Operations

**Start:** 0

**Dur:** 1

**Status:** Not started

**Rollback:** No

#### Technical

**Task:** Final database backup

**Owner:** DBA

**Start:** 1

**Dur:** 3

**Status:** Not started

**Rollback:** Yes

#### Data

**Task:** Load final data conversion files

**Owner:** Data lead

**Start:** 4

**Dur:** 6

**Status:** Not started

**Rollback:** Yes

#### Technical

**Task:** Deploy full package to enterprise and web servers

**Owner:** CNC admin

**Start:** 10

**Dur:** 4

**Status:** Not started

**Rollback:** No

#### Validation

**Task:** Smoke test: order entry, receipt, GL post

**Owner:** Functional leads

**Start:** 14

**Dur:** 3

**Status:** Not started

**Rollback:** No

#### Release

**Task:** Go or no-go decision and user release

**Owner:** Project manager

**Start:** 17

**Dur:** 1

**Status:** Not started

**Rollback:** No

**Totals:**

#### Total task hours

**Key:** dur

**Agg:** sum

**Format:** hours

#### Window length (latest end)

**Key:** end

**Agg:** max

**Format:** hours

#### Tasks

**Key:** task

**Agg:** count

**Format:** integer

**Summary:**

#### Task hours per window hour (1.0 means fully sequential)

**Key:** parallel

**Expr:** sum_dur / max_end

**Format:** decimal

**Notes:** Hours are measured from T0, the moment of the freeze. Overlapping tasks are fine, but check the dependencies yourself: the worksheet adds start and duration only. Durations here are examples, so use timings from your rehearsal runs.

## Content

**Intro:** Go-live weekends rarely fail on big surprises. They fail because a four hour task takes eight and nobody had a view of what it pushed back. This worksheet turns the cutover list into a simple timeline you can rehearse and adjust.

**Sections:**

#### How to use the worksheet

**Body:** List each cutover task, its owner and phase, the start hour counted from T0 and the expected duration. The worksheet calculates each end hour, the total task hours and the length of the window. Mark rollback points so everyone knows the last safe moment to step back. Update the status live during the weekend and export to share.

**Bullets:**

- Base durations on rehearsal timings.
- Mark each rollback point.
- Keep decision tasks in the list.

#### Reading the window length

**Body:** The window length is the latest end hour of any task. Compare it with the downtime the business agreed. The task-hours to window ratio shows how much work overlaps: a value near 1 means the plan is nearly sequential, a higher value means more parallel work and more coordination risk. If the window exceeds the agreed downtime, shorten the longest tasks or move work before T0.

#### JD Edwards specifics

**Body:** Typical JDE cutover items include holding batch queues and integrations, taking final backups, loading conversion data, building or deploying a full package, checking server and web services, running cache clears, validating next numbers and UDCs, and smoke testing key transactions such as sales orders, receipts and posting. Add your own interfaces, printers and scheduled UBEs, which are often forgotten.

#### Common mistakes

**Body:** Planning on best-case durations, leaving out the decision meeting, and not defining a point of no return are common. Another is hiding long, sequential tasks inside one line, so no one sees the real critical path. Split long tasks and rehearse them.

**Cta:** If you are preparing a JDE upgrade or migration cutover, Netray can review your plan and help script validation checks against your data.

**Faq:**

#### What is T0?

**Answer:** T0 is the reference moment from which all start times are counted, usually when users are frozen out of the system. Using hours from T0 keeps the plan independent of the calendar date and easy to reuse for rehearsals.

#### Does the worksheet calculate dependencies?

**Answer:** No. It adds start and duration to give an end hour. You choose the start hours based on your dependencies, so check that a task does not start before its predecessor ends.

#### How many rehearsals should we run?

**Answer:** Enough to get stable timings. Many teams do at least two full rehearsals on a production-sized copy. Use the measured durations in the worksheet instead of estimates.

#### Can I use this for non-JDE projects?

**Answer:** Yes. The structure fits any ERP cutover. The JDE-specific tasks are only examples, so replace them with your own.

## Search terms

jde go live cutover plan, jd edwards cutover checklist excel, erp cutover plan template, jde upgrade cutover schedule, jde production cutover tasks, jde go live weekend plan, jde cutover runbook

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