0 / 10 complete0%

Step 01 of 10 2-3 weeks· advanced

Step 1: Audit the WinForms App

Inventory every form, local-resource dependency, and single-user assumption. WinForms apps hide a lot in code-behind and stored procs.

What you're doing in this step

Generate a comprehensive audit. Beyond the standard fields, focus on: forms inventory (every form, role, frequency), local-resource dependencies (file system, registry, COM, printers, scanners), single-user assumptions, modal-dialog patterns, and background-thread work.

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

Legacy System Audit

Reverse-engineer an existing application: structure, dependencies, integrations, business logic, hidden risks. The starting point for any migration.

View template

Template· Template 30-60 min per program

COBOL Program → Functional Specification

Reverse-engineer a COBOL program into a structured 10-section functional spec — inputs, processing logic, business rules, calculations, outputs, customizations, dependencies.

Use this when: You're auditing COBOL programs alongside VB.NET (some hybrid systems)

cobolmainframedb2vsamcics

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

Legacy Code Analyzer Skill

Claude Code skill that reads legacy .NET code (WebForms, VB.NET, classic ASP) and explains what it does — the foundation for any migration.

claude-codedotnet

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

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

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

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.

Audit document at /docs/migration/audit.md
Form inventory: every form, its purpose, user role, complexity
Local-resource dependencies catalogued (files, registry, COM, printers)
Single-user assumptions identified (concurrency hot spots)
Modal-dialog patterns identified (which workflows depend on blocking UI)
Background work catalogued (threads, timers, scheduled tasks within the app)
Reporting / printing requirements documented

Common pitfalls

What goes wrong at this step

Underestimating form count — "we have 50 forms" usually turns out to be 200 when you actually count user controls too
Missing user controls — .ascx-style controls are reused across forms and easy to overlook
Ignoring keyboard shortcuts and power-user flows — desktop users build muscle memory; web app must replicate or have a transition plan
Skipping the printing audit — printing is often more complex than realized (custom drivers, label printers, multi-tray printers)

← Back to intake