Step 01 of 8 1-2 weeks· advanced
Step 1: Schema Audit
Inventory every object in the source database — tables, procs, functions, triggers, jobs — plus app code that references the schema.
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.
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.
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.
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.
- Inventory at /docs/migration/db-audit.md
- All tables documented with row counts, sizes, and indexes
- All stored procs catalogued with line counts, complexity score, and current callers
- All triggers documented with their purpose
- Data quality issues identified (orphans, NULLs in NOT NULL columns, duplicates)
- App code search done: every place SQL is generated, called, or schema-referenced is listed
Common pitfalls
What goes wrong at this step
- Ignoring CLR types — SQL Server allows .NET types in DB; these don't translate
- Missing SQL Agent jobs — they're outside the DB but tied to it; document them
- Not searching app code — every place the app generates SQL needs review
- Underestimating stored-procedure count — easy to find 50 in `dbo` and miss 150 more buried in other schemas