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

Step 6: Mass Migration

Migrate the bulk of pipelines in batches using the established patterns. Common batching: by source system, by consumer, by complexity, or by owner.

What you're doing in this step

Pipeline by pipeline, in batches. For each: migrate following established patterns, reconcile against legacy output, run shadow for N days, cut over consumers, document new patterns, retire the legacy pipeline. Track % pipelines migrated, % consumers cut over, DQ pass rate, cost trajectory.

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 reference document; 1 day for initial setup

PySpark Transformation Standards

Standards for PySpark transformations in Bronze/Silver/Gold pipelines: idempotency, partitioning, Delta Lake patterns, and code organization.

Use this when: Adding new patterns or refining existing ones during the mass migration

azurepysparkfabricdatabricks
View template
Template· Template 1-2 days per dimension

Slowly Changing Dimensions (SCD) Implementation in PySpark

Implement SCD Type 1, 2, 3, and 6 patterns in PySpark with Delta Lake MERGE — for dimensional modeling in modern data platforms.

Use this when: A batch contains slowly-changing-dimension migrations

azurepysparkdelta-lakefabric
View template
Template· Template 1-2 days for initial setup

Data Quality Test Suite

Generate comprehensive data quality tests for ETL pipelines: schema validation, freshness checks, null/duplicate/range checks, and business invariants.

Use this when: Adding DQ tests as new pipelines come online

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

Data Validation Skill

Claude Code skill that compares old and new system outputs for parity — running validation queries on both DBs and reporting drift.

claude-codesql
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 pipelines migrated
  • All consumers cut over to new pipelines
  • Legacy pipelines disabled (not yet deleted)
  • Reconciliation continues for monitoring period
  • DQ acceptable across new pipelines
Common pitfalls

What goes wrong at this step

  • Long tail of "weird" pipelines — they take 50% of the time. Budget for it
  • Burnout — multi-quarter projects need rotation and small wins
  • Pattern divergence — each engineer reinvents patterns; maintain code review
  • Skipping reconciliation in batch — discovers issues after consumer cutover
  • No retire step — old pipelines linger; legacy ETL tool licenses persist
← Previous step

Command Palette

Search for a command to run...