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

Step 9: Cutover with Rollback Plan

Move the remaining 90% of users to the new app — usually a phased rollout over weeks, not a single cutover day.

What you're doing in this step

Disable the WinForms client for users in waves (10% / 25% / 50% / 75% / 100%). Each wave gets support resources and stop conditions. Keep WinForms available as an emergency fallback throughout.

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: Pre-flight check — make sure rollback is documented and rehearsed before the first wave

View template
Template· Template 0.5 day

Feature Flag Rollout Strategy for Migrations

Use feature flags to safely route traffic between legacy and new systems during migration with controlled rollout and instant rollback.

Use this when: Each wave is gated by a feature flag rather than a hard cutover

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

Performance Profiler Skill

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

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
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.

  • Cutover runbook completed
  • All users migrated
  • Support volume returned to baseline
  • No critical issues outstanding
Common pitfalls

What goes wrong at this step

  • Big-bang final cutover — even after months of incremental migration, going from 50% to 100% in one day is risky
  • No support escalation plan — the cutover wave will produce a support ticket spike
  • Disabling old before new is proven — keep WinForms client available for emergencies for at least 30 days post-cutover
← Previous step

Command Palette

Search for a command to run...