Visual FoxPro migration Available Immediately
Visual FoxPro Migration to .NET
I have taken a legacy Visual FoxPro system to C#, .NET and SQL Server, from the first workflow to retiring the old system. As the sole engineer on a 2.5-year engagement I migrated 42 financial workflows carrying two decades of business logic, with no existing specification, onto a .NET Core domain layer with Entity Framework Core and 42 T-SQL stored procedures, and replaced the FoxPro reports in Blazor. Based in Lahore, five years fully remote with US, UK and German teams, and available immediately for the next one.
01 Experience
What I did, by team
Taken from my CV. Only the work that belongs to this role is listed.
- Benington Financials CanadaFreelance Full-Stack Developer · Feb 2023 - Sep 2025Independently migrated 42 financial workflows from a legacy Visual FoxPro system carrying two decades of business logic to C#/.NET Core, delivering Angular and Blazor frontend features as the sole engineer responsible for end-to-end development.Redesigned legacy data models and business logic with no existing specification into a maintainable .NET Core domain layer on Entity Framework Core and 42 T-SQL stored procedures against SQL Server, with a testable data access layer, preserving all 42 financial workflows.Replaced the legacy Visual FoxPro reports with reporting workflows in the new Blazor application, retiring the old system over a 2.5-year engagement.
02 Skills
What I work with
- Backend & APIsC# · .NET 6 · .NET 8 · .NET Core · ASP.NET Core Web APIs · Node.js · Express.js · Blazor Server · Entity Framework Core · REST / RESTful APIs · API Design (OpenAPI / Swagger) · GraphQL · WebSockets · SignalR · Webhooks · Microservices · Message Queues (Kafka, RabbitMQ) · Full-Stack Development (Full Stack) · PHP Integration · Python
- DatabasesSQL · Microsoft SQL Server (T-SQL, Stored Procedures) · PostgreSQL · MySQL · NoSQL (MongoDB) · Redis (Caching) · Prisma ORM
03 Case studies
The work in detail
- Migrating 42 financial workflows from Visual FoxPro to .NETIndependently migrated 42 financial workflows from a legacy Visual FoxPro system carrying two decades of business logic to C#/.NET Core, delivering Angular and Blazor frontend features as the sole engineer responsible for end-to-end development.
04 Articles
How I approach it
- Visual FoxPro to .NET and C#: a step-by-step migration guideHow to convert a legacy Visual FoxPro app to C#, .NET and SQL Server when the old code is the only spec: inventory, data, domain rules, reports, cutover.
- Visual FoxPro to SQL Server: a repeatable data migrationMoving Visual FoxPro tables into SQL Server: a mapping for every field type, deleted rows, code pages, and a staging load with control totals you can rehearse.
- Replacing Visual FoxPro reports with Blazor and SQL ServerHow to retire FoxPro .frx reports without losing a number: inventory, totals in T-SQL, a Blazor QuickGrid screen, CSV and PDF exports, and parity tests.
- Stored procedures in Entity Framework Core: call, map, testWhen a stored procedure belongs in an EF Core app, how to call one with FromSql and ExecuteSql, read output parameters, map saves, and test the data layer.
05 Quick answers
Asked before you ask
Who can migrate a Visual FoxPro application to .NET?
I can. As the sole engineer I migrated 42 financial workflows from a legacy Visual FoxPro system to C# and .NET Core for a client in Canada, over a 2.5-year engagement, and retired the old system. I work remotely and have spent five years with US, UK and German teams.
Do you take on Visual FoxPro migration projects?
Yes. I am available immediately and work remotely from Lahore. My last FoxPro migration ran as a part-time independent contract.
Can you migrate a FoxPro system that has no specification?
Yes. The system I migrated carried two decades of business logic and had no specification. I redesigned its data models and business logic into a maintainable .NET Core domain layer and preserved all 42 financial workflows.
What does a FoxPro system become after the migration?
In mine: C# and .NET Core with a domain layer on Entity Framework Core, 42 T-SQL stored procedures on SQL Server with a testable data access layer, and Angular and Blazor on the frontend.
Do you redesign the data model and replace the reports as well as the code?
Yes. I redesigned the legacy data models on SQL Server with Entity Framework Core and 42 T-SQL stored procedures, and replaced the legacy Visual FoxPro reports with reporting workflows in the new Blazor application.
How long does a Visual FoxPro to .NET migration take?
It depends on the number of workflows and on how much of the knowledge is written down. Mine covered 42 workflows in two and a half years as a part-time engagement, with one engineer and no specification.
Hiring for this role?
Check the fit in ten seconds
Paste your job description and see which of its technologies are on my CV.