Playbook
0 / 8 complete0%
  1. 01
  2. 02
  3. 03
  4. 04
  5. 05
  6. 06
  7. 07
  8. 08
Step 08 of 8 30-90 days post-cutover· advanced

Step 8: Decommission the Source

After 30+ days of zero source traffic, take the final backup, shut it down, decommission the infrastructure, write the retro.

What you're doing in this step

Source DB stays read-only for 30+ days post-cutover. Watch for any apps / reports still pointing at it. After zero-traffic confirmation, take the final backup, shut down source, decommission infrastructure, and write the migration retro.

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: Document the formal decommission rollback path in case a critical issue surfaces in the first 30 days

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

Postgres MCP for Evoke

Pre-configured Postgres MCP server for Claude Code — schema inspection and read-only queries to make database work safer and faster.

claude-codemcppostgres
View config
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 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.

  • 30+ days of zero source traffic confirmed (verified by query log)
  • All apps verified pointing at target
  • All reports updated
  • Final backup taken (cold archive)
  • Source DB shut down
  • Source license / infrastructure costs eliminated
  • Migration retrospective complete
  • Lessons documented
Common pitfalls

What goes wrong at this step

  • Decommissioning too fast — 30 days is the minimum; some teams keep source read-only for 6+ months
  • No final backup — you may need to read source data again for a compliance audit
  • Forgetting infrastructure costs — VM, license, storage all keep billing until explicitly stopped
  • No retrospective — the next DB migration won't benefit from this one's lessons
← Previous step

Command Palette

Search for a command to run...