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

Step 2: Translate the Schema

Map every source object to a target equivalent — types, constraints, indexes, identity columns, computed columns.

What you're doing in this step

Produce a target schema script. For each table, design the target equivalent. For each constraint, decide whether it translates as-is, needs adjustment, or doesn't translate. For each type, map to the target type with explicit attention to precision and behavior differences.

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

postgressql
View template
Template· Template 20 min

PostgreSQL Schema Designer

Design a normalized PostgreSQL schema with indexes, constraints, and migration files.

Use this when: Target is PostgreSQL and you want to design the new schema fresh rather than translate 1:1

postgressql
View template
Template· Template 20 min

MongoDB Schema Designer

Design a denormalized MongoDB schema with proper indexes, embedded vs referenced choices, and validation rules.

Use this when: Target is MongoDB (rare for cross-engine but covers it)

mongodb
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

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.

  • Type mapping table (every source type → target type)
  • Schema migration script generated
  • Constraint translation documented (especially defaults using engine-specific functions like GETDATE() vs now())
  • Identity columns translated (SQL Server IDENTITY → Postgres GENERATED AS IDENTITY or SERIAL)
  • Computed columns translated (SQL Server PERSISTED → Postgres GENERATED ALWAYS STORED)
  • Indexes translated (with attention to clustered indexes — no equivalent in Postgres)
  • Validation queries written (run on both DBs once schema is in place)
Common pitfalls

What goes wrong at this step

  • Datetime confusion — SQL Server datetime (no tz) → Postgres timestamptz (always UTC) is a behavior change; affects every app touching dates
  • Decimal precision drift — money type → numeric(19,4) is precision-equal but type-different; app code may break
  • Clustered index loss — Postgres has no clustered indexes; query patterns may change behavior
  • Missing Postgres-specific opportunities — JSONB, arrays, partial indexes are usable where they fit
← Previous step

Command Palette

Search for a command to run...