01
Codebase and database audit
What you have, in plain terms, with the parts that matter marked.
- Framework versions, dependencies and dead code
- Database schema, stored procedures and data flows
- Integrations: what talks to what, and how
Legacy .NET Modernization Assessment
KNOW BEFORE
YOU MIGRATE.
Ten working days on your legacy .NET, VB6 or Visual FoxPro system. Fixed price. Written report. A plan your team can run.
What you get
FOUR DOCUMENTS.
ONE DECISION.
Fixed price, quoted on the call. 10 working days. Half to start, half on delivery.
02
Risk register
What breaks, what blocks, what can wait. Ranked.
- Technical risks: unsupported libraries, hidden coupling, data integrity
- Business risks: downtime windows, compliance gaps, key-person dependencies
- A severity and effort rating for each item
03
Migration plan
Phases, order and cutover. Written for your team to execute.
- What to migrate, what to wrap, what to retire
- Phase by phase, with old and new running side by side until cutover
- Team shape, tooling and the CI/CD you need before phase one
04
Estimate and options
Numbers you can take to a budget meeting.
- Effort range per phase, with the assumptions stated
- Two or three delivery options, with trade-offs
- A recommendation, and the reason for it
Ten working days
KICKOFF TO
FINAL REPORT.
Day 1
Kickoff call. Access to a read-only repository or mirror. Questions answered.
Days 2–7
Audit and risk register. Short written questions to your team as they come up.
Day 8
Draft review call. You see the findings before they are final.
Day 10
Final report and plan delivered. Closing call to walk through it.
Who it is for
THIS FITS IF
YOU HAVE…
01 A .NET Framework 2.0 to 4.8 application that still earns revenue
02 A VB6 or Visual FoxPro system that nobody wants to touch
03 A SQL Server database with logic in stored procedures
04 A software company or a healthcare software team with 5 to 50 engineers
Book a 20-minute callIt does not fit if you have…
01 A greenfield product with no legacy system
02 A request for an estimate without access to the code
03 A migration that must finish before the assessment does
Done before
TWO MIGRATIONS.
BOTH IN PRODUCTION.
Hospital platform, Danish health department
.NET Framework 4.8 to .NET Core, Angular retained, codebase restructured to a layered architecture. Delivered solo in two months. Test coverage to 95%.
Fintech back office and client portal
Visual FoxPro to .NET Core and Angular. 200 internal users and a portal serving 5,000+ clients. Target architecture designed for performance, security and reliability.
Enterprise architecture, US healthcare
Introduced .NET into a Python and React organization. HIPAA and SOC 2 technical controls. CI/CD that tripled deployment frequency.
Why a fixed price?
Because an estimate from a call is a guess, and you deserve better than a guess before you commit a year of engineering.
What access do you need?
Read-only access to the repository or a mirror, a database schema export, and two hours of your team’s time across the ten days. Under your NDA or mine.
What if the plan says “do not migrate”?
Then the report says so, with the reasons. That outcome has value too, and you still own the audit and the risk register.
Do I have to hire you for the migration?
No. The plan is yours. Your team can run it, another vendor can run it, or I can. That is a separate decision after you have read the report.
How do we pay?
Half to start, half on delivery of the final report. Bank transfer or Wise.