Playbook
0 / 9 complete0%
  1. 01
  2. 02
  3. 03
  4. 04
  5. 05
  6. 06
  7. 07
  8. 08
  9. 09
Step 09 of 9 2-3 weeks· advanced

Step 9: Cutover and Decommission

Turn off the legacy system. By this point traffic should already be zero — this phase is the formal teardown plus the post-migration write-up.

What you're doing in this step

Execute the formal cutover runbook: remove DNS routes, decommission legacy infrastructure, archive code, run a post-migration retrospective, document lessons for the next migration. Celebrate.

Recommended prompts

Use one of these to do the work in your IDE

Open the template to read it in full. Click Copy prompt to grab it (with your stack values pre-filled where they apply) — then paste into Claude Code, Cursor, or wherever you build.

Primary recommendation 1 day to write

Migration Cutover Runbook

Detailed step-by-step runbook for the actual cutover from legacy to new system, including verification, communication, and rollback.

View template
Template· Template 0.5-1 day

Migration Rollback Plan

Plan recovery procedures for when migrations fail at any stage — from pre-cutover bugs to post-cutover production incidents.

Use this when: You want a fallback documented before pulling the plug, just in case

View template
Recommended skills

Drop these into Claude Code for this phase

Skills auto-trigger on the right kind of request. Install once; they apply to every prompt that fits.

Skill· Skill 5 min setup

Migration Planner Skill

Flagship migration skill that walks Claude Code through audit → strategy → slicing → cutover for any legacy system migration.

claude-code
View skill
Skill· Skill 5 min setup

Documentation Skill

Claude Code skill that generates README, API docs, JSDoc, ADRs, and other docs that match the project's existing voice and depth.

claude-code
View skill
Recommended MCP configs

Wire these tools into Claude Code first

MCP servers give Claude Code direct access to external systems (Jira, browsers, databases). Configure once.

MCP config· MCP config 10 min setup

Azure DevOps MCP for Evoke

Pre-configured Azure DevOps MCP server for Claude Code — work items, repos, PRs, and pipelines from chat.

claude-codemcp
View config
MCP config· MCP config 5 min setup

Filesystem MCP for Evoke

Pre-configured filesystem MCP server for Claude Code — safe, scoped read/write access to project files.

claude-codemcp
View config
MCP config· MCP config 10 min setup

Confluence MCP for Evoke

Pre-configured Atlassian Confluence MCP server for Claude Code — search, read, and write internal documentation pages from chat.

claude-codemcp
View config
When you're done

Verify these in your own work before moving on

This is a checklist for you to mentally tick off in your repo and IDE — the site doesn't track it, you do.

  • Legacy traffic = 0% for 30 consecutive days
  • No critical alerts from legacy in that window
  • All scheduled jobs migrated
  • All integrations updated to point at the new system
  • DNS / proxy routes to legacy removed
  • Legacy infrastructure decommissioned (compute, DB, etc.)
  • Legacy code archived (don't delete; archive)
  • Post-migration retrospective completed
  • Lessons documented for future migrations
  • Team celebration
Common pitfalls

What goes wrong at this step

  • Decommissioning too fast — keep legacy in cold standby for 30+ days post-cutover
  • Forgetting integrations — the partner still calling legacy; the report tool still pointing at the legacy DB
  • No retrospective — the next migration won't benefit from this one's lessons
  • No celebration — the team did hard work; recognize it
← Previous step

Command Palette

Search for a command to run...