IE-5: Cutover Weekend Runbook | NetSuite Implementation Guide

Cutover Weekend Runbook

A minute-by-minute execution checklist for the critical go-live weekend. Covers data extraction, validation, loading, smoke testing, and the official transition to production NetSuite.

6

Phases

45

Checklist Items

72

Hour Window

Overview

Cutover Weekend Timeline

The typical cutover spans Friday evening through Monday morning.

Standard 72-Hour Cutover Window

Friday 6PM

Freeze legacy system, begin extraction

Saturday

Data loading & reconciliation

Sunday

Testing & validation

Monday 8AM

GO-LIVE & Hypercare begins

Cutover Flow Diagram

                gantt
                    title Cutover Weekend Timeline
                    dateFormat HH:mm
                    axisFormat %H:%M

                    section Friday
                    Legacy System Freeze       :fri1, 18:00, 1h
                    Final Data Extract         :fri2, after fri1, 3h
                    Extract Validation         :fri3, after fri2, 2h

                    section Saturday
                    Load Master Data          :sat1, 08:00, 4h
                    Load Transactions         :sat2, after sat1, 4h
                    Balance Reconciliation    :sat3, after sat2, 3h

                    section Sunday
                    Smoke Testing             :sun1, 08:00, 4h
                    UAT Validation            :sun2, after sun1, 4h
                    Go/No-Go Decision         :sun3, after sun2, 2h

                    section Monday
                    GO-LIVE                   :mon1, 08:00, 1h
                    Hypercare Support         :mon2, after mon1, 8h

Decision Framework

Go/No-Go Criteria

Critical checkpoints that must pass before declaring go-live.

Mandatory Go Criteria

Category	Criteria	Tolerance
Data Integrity	Trial Balance matches legacy within tolerance	+/- $1.00
Data Integrity	AR/AP aging matches legacy subledger	100% match
Data Integrity	Inventory quantities match physical count	100% match
Functionality	All P0 (critical) smoke tests pass	100% pass
Functionality	P1 (high priority) smoke tests pass	≥95% pass
Integration	All critical integrations verified	100% operational
Access	Key users can log in and perform core tasks	100% verified

🚨 No-Go Triggers

Any of these conditions require immediate escalation and potential rollback: Trial Balance variance >$100, missing customer/vendor records affecting AR/AP, inability to create transactions, integration failures to banking or payroll, or key decision-makers unavailable.

Phase 1

Pre-Cutover Preparation T-7 Days

Final preparations in the week before cutover weekend.

Stakeholder Readiness

Distribute final cutover schedule to all stakeholders — Include executive sponsors, IT, department heads, and external partners
Confirm War Room location and access (physical or virtual) — Ensure video conferencing, whiteboards, and power available
Verify all team members have emergency contact information
Confirm executive sponsor availability for Go/No-Go decision (Sunday)

Technical Readiness

Complete final mock cutover rehearsal — Document timing for each step; identify bottlenecks
Verify Sandbox is refreshed and matches Production configuration
Confirm all CSV import templates are final and tested
Test rollback procedures in Sandbox environment — Ensure you can restore to pre-cutover state if needed

Phase 2

Friday Night - Cutover Start T-0

System freeze and final data extraction from legacy system.

⚠️ Point of No Return

Once the legacy system is frozen, all business transactions must stop until NetSuite is live. Communicate widely that NO transactions should be entered in the legacy system after the freeze time.

Legacy System Freeze

Send 'System Freeze' notification to all users — Email, Slack, and verbal confirmation to key users
Disable user write access in legacy system — Set to read-only or disable logins
Document freeze timestamp: __________ (record actual time)

Final Data Extraction

Extract final Trial Balance from legacy system — This is your reconciliation baseline - store securely
Extract AR Aging report (by customer, by invoice)
Extract AP Aging report (by vendor, by bill)
Extract Inventory valuation report (by item, by location)

Phase 3

Saturday Morning - Data Loading SAT AM

Load master data and validate before proceeding to transactions.

Master Data Load

Load/update Customer records (delta from last load) — Verify count matches expected; spot-check 10 records
Load/update Vendor records (delta from last load)
Load/update Item records (delta from last load) — Verify pricing, costing method, and inventory settings
Validate Employee records and access levels

Opening Balance Entry

Enter Opening Balance Journal Entry for GL accounts — Debit assets, credit liabilities and equity
Verify Trial Balance in NetSuite matches legacy extract — Run comparison; document any variances >$1
Load Inventory Adjustment for opening quantities — Use Inventory Adjustment transaction type
Verify Inventory Valuation matches legacy extract

Phase 4

Saturday Afternoon - Transactions SAT PM

Load open transactions and perform balance reconciliation.

Open Transaction Load

Load Open AR Invoices using clearing account methodology — Reference IE-3 for GAAP-compliant approach
Load Open AP Bills using clearing account methodology — Reference IE-4 for GAAP-compliant approach
Load Open Sales Orders (if maintaining order history)
Load Open Purchase Orders (if maintaining order history)

Balance Reconciliation

Run AR Aging in NetSuite - compare to legacy extract — Must match 100% by customer
Run AP Aging in NetSuite - compare to legacy extract — Must match 100% by vendor
Verify clearing accounts net to zero — Any balance indicates a data error

Phase 5

Sunday - Testing & Validation SUNDAY

Comprehensive testing before the Go/No-Go decision.

Smoke Testing - Critical Paths

Create a new Sales Order and fulfill to Invoice — Verify pricing, tax, and inventory reduction
Record a Customer Payment and apply to invoice
Create a Purchase Order and receive to Vendor Bill — Verify costing and inventory increase
Record a Vendor Payment (bill payment)
Run key financial reports (P&L, Balance Sheet, Cash Flow) — Verify data appears correctly

Integration Verification

Verify bank feed connection (if using bank feeds)
Test payment processing integration (credit cards, ACH)
Verify eCommerce/CRM integrations are syncing

Phase 6

Monday - Go-Live Day MONDAY

Official go-live and transition to hypercare support.

💡 Go-Live Declaration

Once Go/No-Go passes on Sunday evening, send the official "We Are Live" communication to all stakeholders. Include support contact information and the hypercare schedule.

Go-Live Morning

Send 'NetSuite is Live' announcement to all users — Include login URL, support hotline, and FAQ link
Staff hypercare support desk (War Room active) — Ensure all functional leads are available
Monitor first real transactions closely — Watch for errors, unusual behavior, or user confusion
Decommission legacy system write access permanently

End of Day 1 Validation

Review all issues logged during Day 1 — Categorize by severity; assign owners
Run end-of-day reports to verify transaction integrity
Conduct Day 1 retrospective with core team — Document lessons learned; plan for Day 2 focus areas

Reference

Rollback Plan

Emergency procedures if cutover cannot proceed.

Rollback Decision Points

Timing	Decision Point	Rollback Action
Saturday AM	Data load fails repeatedly	Re-enable legacy system; schedule retry for next weekend
Saturday PM	Balance reconciliation fails	Delete imported transactions; restore from pre-cutover backup
Sunday PM	Go/No-Go fails critical criteria	Re-enable legacy system; communicate delay to users
Monday (Live)	Critical system failure	Emergency: Re-enable legacy; manually reconcile any NetSuite transactions

🎯 Consultant Insight

The rollback plan should be tested during mock cutover. If you haven't practiced restoring to pre-cutover state, you're not ready for go-live. "Hope for the best, plan for the worst."

Reference

War Room Setup

Command center configuration for the cutover weekend.

War Room Requirements

Category	Requirements
Physical Space	Conference room with whiteboard, projector, power strips, WiFi
Virtual Space	Dedicated Zoom/Teams room open 24/7 during cutover
Communication	Slack/Teams channel for real-time updates; email distribution list
Documentation	Shared folder for cutover artifacts; issue log spreadsheet
Staffing	Project Manager, Technical Lead, each functional lead on rotation
Supplies	Snacks, coffee, meals planned for extended hours

Reference

Cutover Weekend Runbook

Cutover Weekend Timeline

Standard 72-Hour Cutover Window

Cutover Flow Diagram

Go/No-Go Criteria

Mandatory Go Criteria

Pre-Cutover Preparation T-7 Days

Stakeholder Readiness

Technical Readiness

Friday Night - Cutover Start T-0

Legacy System Freeze

Final Data Extraction

Saturday Morning - Data Loading SAT AM

Master Data Load

Opening Balance Entry

Saturday Afternoon - Transactions SAT PM

Open Transaction Load

Balance Reconciliation

Sunday - Testing & Validation SUNDAY

Smoke Testing - Critical Paths

Integration Verification

Monday - Go-Live Day MONDAY

Go-Live Morning

End of Day 1 Validation

Rollback Plan

Rollback Decision Points

War Room Setup

War Room Requirements

Sources & Further Reading

Primary Sources