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 03 of 10 2-3 weeks· advanced

Step 3: Map the Data Model

Plan how data moves from on-prem SQL Server to cloud-hosted DB, including any schema reshape and stored-procedure migration.

What you're doing in this step

WinForms apps often share a SQL Server with the client connecting directly. The new architecture has APIs in between, which exposes schema issues that "worked because the client was right there." Inventory tables / procs / triggers / jobs, decide schema reshape vs as-is, plan migration strategy.

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

Data Migration Plan

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

View template
Template· Template 1 day

SQL Server to Modern Schema Translator

Translate SQL Server schemas to modernized SQL Server (Azure SQL) or Postgres, handling type differences, constraints, and stored procedure migration.

Use this when: Moving to a different DB engine (Azure SQL → Postgres, etc.) and need explicit type/feature mapping

postgressql
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: You have stored procedures whose business logic should move to .NET application code

dotnetsql
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

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

Database Migration Skill

Claude Code skill that generates safe forward and reverse migrations with transaction-wrapping, idempotency, and zero-downtime patterns.

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

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

  • Data migration plan at /docs/migration/data-plan.md
  • Schema mapping (source → target, with transformations)
  • Stored-procedure migration decisions per proc (translate / rewrite / view / decommission)
  • Migration strategy chosen (big-bang / dual-write / CDC / trickle)
  • Data quality audit completed (orphans, duplicates, NULL violations)
  • Validation queries written
Common pitfalls

What goes wrong at this step

  • "We'll use the same database" — sometimes the right answer; sometimes the schema needs reshape and skipping it forces it later
  • Missing stored-procedure logic — WinForms apps often delegate heavily to procs
  • Data-quality issues surfacing only at migration — audit BEFORE you're committed
  • Big-bang migration of large data — may exceed your downtime window; plan accordingly
← Previous step

Command Palette

Search for a command to run...