Step 03 of 8 4-8 weeks (depends on volume + complexity)· advanced
Step 3: Migrate Stored Procedures and Functions
Decide what to do with each proc — translate, rewrite in app code, downgrade to a view, or decommission. This is usually the longest phase.
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.
- Every proc has a decision: translate / rewrite / view / decommission
- Translated procs work in the target dialect with tests
- Rewritten logic has unit tests
- Original procs marked deprecated with logging (not yet dropped)
- App code updated to call new locations
Common pitfalls
What goes wrong at this step
- Translating procs that should be rewritten — putting business logic back in DB is just moving the problem
- Skipping the decommission step — orphaned procs accumulate; track callers
- Rewriting without tests — proc behavior is not always documented; tests prevent regressions
- Forgetting cursors — they often hide what should be set-based queries
- Forgetting transaction boundaries — implicit in procs, must be explicit in app code