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

Step 8: Continue Migrating Remaining Slices

Repeat the slice migration pattern for everything else. By the end of this phase, all user-facing capabilities should run on the new system.

What you're doing in this step

Migrate every remaining slice using the established pattern. Each one gets faster. Document edge cases (the report run quarterly, the integration with the partner system nobody mentioned). Address them, keep going.

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

View template
Template· Template varies (per procedure)

Stored Procedure to Service Migration

Convert business logic embedded in T-SQL stored procedures into testable, observable application services.

Use this when: A slice involves moving SQL business logic to .NET application code

dotnetsql
View template
Template· Template 1-2 days

Data Migration Plan

Plan a safe data migration: schema mapping, ETL strategy, dual-write or one-shot, validation, and cutover with rollback.

Use this when: A slice requires per-feature data movement

View template
Template· Template 1 day

Authentication Migration Strategy (.NET Forms Auth → JWT/OAuth)

Migrate from legacy .NET authentication (Forms Auth, Windows Auth, custom) to modern JWT/OAuth without breaking existing users.

Use this when: Completing the auth migration started in Phase 5

dotnet
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

Spec-Driven Builder Skill

Tool-neutral skill that walks developers through PRD → stories → schema → API → tests for any new feature, producing real artifacts at each step. The methodology is identical on every supported tool.

claude-codecopilotcursor
View skill
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

Test Generator Skill

Claude Code skill that picks the right test type (unit/integration/E2E) based on context and applies Evoke's testing patterns automatically.

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 10 min setup

GitHub MCP for Evoke

Pre-configured GitHub MCP server for Claude Code — issues, PRs, code search, and Actions 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.

  • All user-facing slices migrated
  • All slices ramped to 100% on the new system
  • Legacy serves only background / admin (or nothing at all)
  • Stakeholder sign-off captured per slice
  • Decommissioning criteria documented for each legacy component
Common pitfalls

What goes wrong at this step

  • The long tail — last 10% of capabilities take 50% of the time. Budget for it
  • Burnout — migrations are grueling. Rotate engineers, celebrate slice completions
  • Scope creep across slices — the temptation to "fix" things in legacy that are about to be deleted is huge
  • Stalling — at some point the team gets bored of migration; push through to decommission
← Previous step

Command Palette

Search for a command to run...