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-2 quarters (often parallel with Phase 7)· advanced

Step 8: Migration of Consumption (BI, ML, Downstream Apps)

Switch consumers from legacy data sources to the new platform. Power BI, Tableau, ML pipelines, custom apps, Excel queries — each gets a different migration path.

What you're doing in this step

Per consumer: Power BI → rebuild on top of new semantic models or repoint data sources. Tableau → repoint. ML pipelines → redirect feature sources. Custom apps → redirect connection strings (often hardest). Excel users → educate + provide alternative. For each, validate query results match within tolerance, performance is acceptable, and functionality is complete.

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

Use this when: Per significant consumer cutover that needs a formal runbook

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 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
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 in-scope reports / dashboards migrated
  • Performance acceptable on the new platform
  • User acceptance validated
  • Legacy consumers redirected
  • Old report URLs / connection strings retired
Common pitfalls

What goes wrong at this step

  • "They'll figure it out" approach to migration — users don't; they complain or work around
  • No performance testing on new platform — new is slower than expected; users dislike
  • Forgetting Excel users — they have queries you don't know about
  • No training plan — new tools / patterns require user training
  • Big-bang cutover of many reports — phase by criticality
← Previous step

Command Palette

Search for a command to run...