0 / 8 complete0%

Step 02 of 8 2-3 weeks· advanced

Step 2: Strategy Decision (per Pipeline Category)

Not every pipeline needs the same approach. Categorize each into rewrite, tool-assisted translation, redesign, retire, or replace-with-platform-feature.

What you're doing in this step

For each pipeline, pick a strategy: (A) direct rewrite in ADF + PySpark, (B) tool-assisted translation (Informatica IICS, AWS SCT, SSMA), (C) rethink and redesign (for pipelines that were bad anyway), (D) retire (for dead or duplicated work — 20-40% of inventory), (E) replace with platform feature (Fabric Mirroring, Fivetran, Debezium CDC). Document the categorization.

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 4 hours

Migration Risk Register

Comprehensive risk inventory for migration projects with likelihood, impact, mitigations, and triggers.

View template

Template· Template 1 day

Coexistence Architecture ADR

Document the architecture decisions for running legacy and new systems in parallel during migration: routing, auth, data, and sessions.

Use this when: Capturing the strategy decisions as architecture decision records alongside the risk register

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

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

Confluence MCP for Evoke

Pre-configured Atlassian Confluence MCP server for Claude Code — search, read, and write internal documentation pages from chat.

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.

Every pipeline categorized into a strategy (A/B/C/D/E)
Retirement list confirmed — pipelines NOT migrating
Tool-assisted translation tooling chosen (if applicable)
Replace-with-platform candidates identified
High-level effort estimate per strategy
Risk register updated

Common pitfalls

What goes wrong at this step

One-size-fits-all strategy — different pipelines need different approaches
Skipping the retirement list — migrating dead pipelines is the easiest waste to eliminate
Picking automated translation without piloting — tools vary in quality
Underestimating "rethink" pipelines — "while we're modernizing, let's also..." is a project killer

← Previous step