1. Home
  2. Enterprise care
  3. .NET & Web Forms migration

Web Forms migration: move to modern .NET section by section, without a big-bang rewrite

We upgrade .NET Framework, Web Forms, MVC 5 and WCF applications to modern .NET one section at a time, with old and new running side by side behind the same URLs. Typical programmes take six to sixteen weeks.

Typical timeline
6–16 weeks
Your quote
Fixed, in writing
Good for
Web Forms, MVC 5, WCF and Classic ASP applications running on IIS.

Who it’s for, and who it isn’t

A good fit
  • Web Forms, MVC 5, WCF and Classic ASP applications running on IIS.
  • The app only runs on Windows Server and IIS
  • Web Forms or WCF are central to the codebase
Probably not for you
  • Applications due to be retired within a year (keep them secure instead; see Web Forms support)
  • Teams wanting a full product redesign at the same time

What changes

✕BeforeA .NET Framework or Web Forms app that is getting harder to patch and host.
✓AfterThe same app on supported .NET 10, moved section by section while it stays live.
For the people using it
  • Faster pages and fewer errors
  • Screens that still work the way they did
For your business
  • Off end-of-life frameworks and Windows-only hosting
  • Lower hosting bills and easier hiring
The guide

Modernising .NET Framework applications to .NET 10

Many corporate applications still run on .NET Framework 4.x, Web Forms or WCF. They work, but they are tied to Windows hosting, harder to hire for and miss the performance gains of modern .NET.

We upgrade section by section using the strangler-fig pattern: new .NET 10 modules sit alongside the old app behind the same URLs until everything has moved. Users see the same screens, only faster.

Signs you need this

  • The app only runs on Windows Server and IIS
  • Web Forms or WCF are central to the codebase
  • Hosting costs are high for the traffic you have
  • Developers are reluctant to touch the code
Try it · Upgrade check

How complex is your .NET upgrade?

Tick what applies to your application.

How complex is your .NET upgrade?
Low
upgrade complexity
In place
recommended approach
6–8 wk
typical timeline
A direct upgrade is realistic

Most of the code should port directly. We would start with an automated analysis and a short spike.

What’s included

Scope, price and timeline are fixed in writing before work starts.

  1. 01Code and dependency audit
  2. 02Upgrade plan by section
  3. 03.NET 10 rebuild of each module
  4. 04Old and new running side by side
  5. 05Performance and security testing

How it works

  1. Weeks 1–2

    Audit

    Inventory of content, data, integrations and every live URL.

  2. Weeks 2–3

    Map

    Every page, field and redirect mapped to the new platform.

  3. Build

    Rehearse

    Full trial migrations on staging until the numbers reconcile.

  4. Cutover

    Switch over

    A planned window with a tested rollback, agreed in advance.

  5. 30 days

    Hypercare

    Daily checks on traffic, errors and data after launch.

Risks we remove

What usually goes wrong with .net & web forms migration projects, and what we do about it.

01

A failed big-bang cutover

Routes move across one at a time behind the same domain.

02

Hidden business rules lost

Behaviour is captured in tests before each section is rewritten.

03

New code that only runs on Windows

Windows-only dependencies are flagged in the audit so you can choose Linux hosting later.

Worked example

A typical upgrade

An internal claims application runs on Web Forms and WCF on .NET Framework 4.8. Weeks one and two audit every page, service and dependency, and rank sections by risk and value.

A modern .NET application is placed in front of the old one. Each sprint moves one section across, with tests capturing existing behaviour first. Users keep the same address throughout.

An illustrative example of how we would run this kind of project, not a client case study.

Technology we use
.NET Framework 4.xWeb FormsMVC 5.NET 10BlazorAzure App Service
Have a project like this?

Options for a Web Forms application

Keep and supportIncremental migrationFull rewrite
RiskLow now, growingLowHigh
Disruption to usersNoneMinimalOne large cutover
Time to first benefitImmediateWeeksMonths
End state.NET Framework on IISModern .NETModern .NET or another stack
Free quote · no obligation

Talk to a .NET and Web Forms migration specialist this week.

Leave your email and a line about what you need. We reply with questions or a price range. Prefer to talk? Book a free 30-minute call.

No spam. One reply from a real person.

.NET & Web Forms migration: questions, answered

Do we need to rewrite everything?
No. Most business logic ports across. UI layers such as Web Forms are rebuilt one section at a time.
Can the app stay live during the upgrade?
Yes. Old and new run side by side behind the same domain, so there is no big-bang cutover.
Can we move to Linux hosting afterwards?
Yes. Modern .NET runs on Linux and in containers, which often lowers hosting costs.
How does pricing work?
After a free scoping call you get a written proposal setting out the scope, the cost and a planned timeline, so you know what you are agreeing to before work starts.
Do I own what you build?
Yes. Code, designs, content and accounts are yours from day one, in accounts you control.

Another question? Email us or book a free call.

Often paired with

All services →