Migrated a 100k-row legacy system with zero downtime. Here's what actually worked. A client's ASP...Migrated a 100k-row legacy system with zero downtime. Here's what actually worked. A client's ASP...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Migrated a 100k-row legacy system with zero downtime. Here's what actually worked.
A client's ASP.NET WebForms app was crawling — pages taking 8+ seconds to load under real production data.
The problem wasn't the framework. It was unindexed queries and client-side pagination trying to handle six-figure row counts.
What I did:
Migrated the backend to .NET 8 Core in phases, not a big-bang rewrite
Rebuilt pagination server-side with proper SQL indexing and query profiling
Kept the app live for users the entire time — zero downtime
Result: load times dropped from 8s to under 1s, and the client's support tickets for "slow dashboard" complaints disappeared entirely.
The lesson? Full-stack developer work isn't just writing React components — it's knowing when the real fix lives in the database layer.
If you're dealing with a legacy .NET system that's aging badly, or a React frontend that feels fast until real data hits it, I'd love to compare notes.
What's the oldest legacy stack you've had to modernize — and what broke first?
More on how I approach these migrations is on my profile 👇

asp.net

ASP.NET Core | Open-source web framework for .NET

Build web apps and services that run on Windows, Linux, and macOS using C#, HTML, CSS, and JavaScript. Get started for free on Windows, Linux, or macOS.

Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started