# Oracle Fusion Cutover Plan Worksheet > Source: https://netray.co/tools/oracle-fusion-cutover-plan-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Plan a go-live weekend task by task, with start offsets, durations, owners and a calculated end hour for each step. ## Category oracle ## Erp Oracle Fusion Cloud SCM ## Audience - Cutover manager - Oracle Cloud consultant - ERP project manager ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Step **Key:** step **Type:** number #### Task **Key:** task **Type:** text #### Owner **Key:** owner **Type:** text #### Area **Key:** area **Type:** select **Options:** - Legacy freeze - Data extract - Data load - Reconciliation - Integration - Security - Go / no-go - Hypercare #### Start offset **Key:** start **Type:** number **Unit:** hours #### Duration **Key:** dur **Type:** number **Unit:** hours #### End offset **Key:** end **Type:** number **Expr:** start + dur **Format:** hours #### Rollback point **Key:** rollback **Type:** select **Options:** - No - Yes #### Status **Key:** status **Type:** select **Options:** - Planned - In progress - Done - Blocked **Rows:** **Step:** 1 **Task:** Freeze legacy transactions and close open receipts **Owner:** Ops lead **Area:** Legacy freeze **Start:** 0 **Dur:** 2 **Rollback:** Yes **Status:** Planned **Step:** 2 **Task:** Extract final item, supplier and on-hand files **Owner:** Data lead **Area:** Data extract **Start:** 2 **Dur:** 4 **Rollback:** No **Status:** Planned **Step:** 3 **Task:** Load items, then structures, then on-hand quantities **Owner:** Load team **Area:** Data load **Start:** 6 **Dur:** 10 **Rollback:** Yes **Status:** Planned **Step:** 4 **Task:** Reconcile on-hand value to the general ledger **Owner:** Finance lead **Area:** Reconciliation **Start:** 16 **Dur:** 3 **Rollback:** Yes **Status:** Planned **Step:** 5 **Task:** Enable integrations and run smoke test orders **Owner:** Integration lead **Area:** Integration **Start:** 19 **Dur:** 3 **Rollback:** No **Status:** Planned **Step:** 6 **Task:** Go / no-go decision **Owner:** Steering group **Area:** Go / no-go **Start:** 22 **Dur:** 1 **Rollback:** Yes **Status:** Planned **Totals:** #### Total task hours **Key:** dur **Agg:** sum **Format:** hours #### Latest end offset **Key:** end **Agg:** max **Format:** hours #### Tasks **Key:** task **Agg:** count **Format:** integer **Summary:** #### Cutover window **Key:** window_days **Expr:** max_end / 24 **Format:** days **Notes:** Start offsets are hours from the legacy freeze. Overlapping tasks are allowed, so the latest end offset, not the sum, sets the window. ## Content **Intro:** A cutover plan turns the go-live weekend into a sequence people can follow at two in the morning. This worksheet holds the step list, owners, durations and rollback points and calculates when each step ends. **Sections:** #### How to build the plan **Body:** Work backward from the point at which users must be able to transact. Add every task, including those that feel obvious such as disabling legacy logins, running scheduled processes, and confirming that integrations point at the correct environment. Give each task a start offset in hours from the freeze and a realistic duration taken from your mock cutovers, not from optimism. #### Rollback points **Body:** Mark steps after which reversing is cheap and steps after which it is not. The steering group should decide at each marked point with evidence in hand, such as reconciliation totals. Without marked points, teams drift past the last safe decision and then have to fix forward under pressure. **Bullets:** - Set the last rollback point before integrations go live - Write the rollback steps, not only the flag - Rehearse at least once - Record actual hours against plan #### Reading the window **Body:** The latest end offset and window in days tell you the real elapsed time even when tasks overlap. Compare it with the business downtime you negotiated. If the plan exceeds it, look for parallel work, such as loading master data while finance prepares reconciliation, and for steps that can move before the freeze, such as static data. #### Common mistakes **Body:** Plans often ignore the time to run reconciliation and fix variances, assume load durations from small test files, and leave out the people. Add owners for every step and a named backup. Include hypercare handover and a rule for who may approve emergency changes after go-live. **Cta:** If you want a second pair of eyes on a cutover runbook, we can review the sequence, rollback points and reconciliation approach. **Faq:** #### How many cutover rehearsals should we run? **Answer:** At least one full rehearsal, and for complex manufacturing scopes two. Each rehearsal gives real durations and exposes sequencing mistakes. Use rehearsal actuals to replace estimates in this worksheet. #### Who owns the go / no-go decision? **Answer:** A named steering group with authority over both business and IT, agreed before the weekend. The decision should rest on criteria such as reconciliation totals, open critical defects and integration status, written in advance. #### How do I handle open work orders and purchase orders? **Answer:** Decide per document type whether to complete them in the legacy system, migrate them as open balances, or recreate them. Write the rule down, because manufacturing teams care about work in process more than any other balance. #### What belongs in hypercare? **Answer:** A time boxed period after go-live with a daily defect triage, a named support rota, and a stable list of known issues. Include period end tasks if go-live is close to a close. ## Search terms oracle fusion cutover plan template, oracle cloud go live checklist excel, erp cutover plan example, oracle fusion go live runbook, cutover runbook template, oracle cloud cutover tasks, erp go live weekend plan --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json