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 4-8 weeks for decommission, ongoing for optimization· advanced

Step 9: Decommission Legacy + Optimize

Turn off old systems. Run cost optimization (typically 30%+ savings opportunity). Tune performance. Mature governance.

What you're doing in this step

Decommission: verify zero traffic on legacy DW + ETL tools for 30+ days, take final backup / archive, decommission infrastructure, cancel licenses. Cost optimization: right-size compute, lifecycle storage to cool / archive tiers, pause non-prod outside business hours, reserve capacity for predictable workloads. Performance: OPTIMIZE + ZORDER Delta tables, review partitioning, add materialized views. Governance: deploy Purview, formalize data contracts, document schema-evolution policies, formalize DQ SLOs.

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
Skill· Skill 5 min setup

Performance Profiler Skill

Claude Code skill that diagnoses performance issues — slow queries, slow renders, memory leaks — with measurement-first methodology.

Use this when: Optimization phase needs systematic profiling of hot pipelines / queries

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.

Use this when: Driving the post-migration retrospective and the optimization roadmap

claude-code
View skill
Template· Template 20 min initial assembly + ongoing additions

Regression Test Bed — Master Suite

Assemble per-program / per-component test cases into a single master regression suite — coverage summary, critical path, domain sections, end-to-end scenarios, run instructions.

Use this when: Standing up a permanent regression suite for the new platform

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

Performance Profiler Skill

Claude Code skill that diagnoses performance issues — slow queries, slow renders, memory leaks — with measurement-first methodology.

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
Skill· Skill 5 min setup

Code Reviewer Skill

Claude Code skill that performs comprehensive code review on PRs and diffs, prioritized by severity with concrete fixes.

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

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
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 systems decommissioned
  • Final backup / archive complete
  • Cost optimization round-1 complete (target: 30% reduction)
  • Performance optimization on hot paths
  • Governance tooling deployed
  • Migration retrospective complete
Common pitfalls

What goes wrong at this step

  • Decommissioning too fast — 30+ days of zero traffic before pulling the plug
  • Skipping cost optimization — costs sneak up if not actively managed
  • No performance baseline — can't optimize what you don't measure
  • No retrospective — lessons not captured = repeated mistakes
  • Treating governance as bureaucracy — it's an enabler, not overhead
← Previous step

Command Palette

Search for a command to run...