The D365 Finance Cutover Rehearsal Playbook: The 2 Dry Runs That Save Your Go-Live

If a D365 Finance go-live fails, the root cause is rarely “the system.” It’s usually cutover discipline: unclear owners, missing timings, no rollback, and no throughput data. Here’s the two-rehearsal playbook I use to prevent that.

Outcome: two full dress rehearsals with measured timings, clear RACI, signed acceptance criteria, and a rollback you’ve actually tested.

Why most cutovers fail (and how to avoid it)

• No named owners per domain → fix with a RACI and sign-off points.
• Scope creep on history → freeze decisions early in a log.
• One token dry run → do two rehearsals with full volumes.
• No throughput metrics → measure every step (mins, records/min, error%).

The Playbook Overview

• Rehearsal #1 (T-6 to T-4 weeks): full-volume import with known defects allowed, objective is timings + bottlenecks.
• Rehearsal #2 (T-2 weeks): full-volume import with go/no-go criteria (quality + timings). This is your go-live rehearsal.

RACI for cutover (core roles)

(A=Accountable, R=Responsible, C=Consulted, I=Informed)

Rehearsal #1 — timings & bottlenecks

Goal: benchmark duration + throughput and surface blockers.

Scope checklist

• Full volumes for: Vendors, Customers, Items, Projects, opening balances, open AP/AR/bank, project WIP as applicable.
• “Happy path” smoke tests only (posting profiles, dimension entry, tax calc, vendor payment proposal, bank recon import).

What to capture (minimum)

Deliverables: a one-page timing sheet, a list of bottlenecks with owners, and revised targets.

Rehearsal #2 — go/no-go criteria

Goal: prove the go-live is repeatable, within time, and reversible.

Pass criteria (example)

• All imports within ±10% of targets from Rehearsal #1 (after optimizations).
• Error rate ≤ 0.5% across master & open items (known exceptions listed).
• End-to-end duration ≤ 6 hours (fits your window).
• Rollback tested: one import intentionally fails; team executes rollback and re-run within 45 minutes.

Sign-offs required

• AP, AR, GL, Projects each sign “numbers reconcile” against legacy/source.
• PMO signs “cutover book” with timings, owners, acceptance checkpoints.

The war-room (minute-by-minute)

• Single channel (Teams/Slack) with pinned run-sheet + decision log.
• Timekeeper calls each step start/finish; posts timestamps.
• Red/Amber/Green board for each workstream; only PMO can change status.
• Decision log lines: Decision, Impact, Owner, Time, Reversal Path.

Rollback policy (you must test it)

• Define rollback triggers (e.g., error > X%, duration > target + Y minutes).
• For each step, specify reversal (delete batch, restore backup, revert security).
• Assign rollback captain separate from the step owner.

Common pitfalls & quick fixes

• “Data” as one line item → split by domain and name the owner.
• Late change to scope/history → push to data warehouse, not ERP.
• Under-estimating security → rehearse role toggles and approvals.
• No clock → appoint a timekeeper and publish a wall clock in the channel.

Copy/paste mini-checklist

• [ ] Owners + RACI named and briefed
• [ ] Decision log template ready
• [ ] Two rehearsals scheduled (T-6/T-4 and T-2)
• [ ] Timing sheet prepared + throughput targets set
• [ ] Rollback steps written and tested
• [ ] Smoke tests list agreed + acceptance criteria signed

Related reads

• EN: Financial dimensions — better insight without a bloated COA
  https://www.fitgapfinance.com/the-strategic-role-of-financial-dimensions-better-insight-without-a-bloated-chart-of-accounts/
• FR: 10 bonnes pratiques pour le plan comptable
  https://www.fitgapfinance.com/plan-comptable-charte-de-comptes-d365-finance/

Get the 1-page ERP checklist (guardrails for governance, data, and security) from the homepage.