Skip to main content

Keene Systems, Inc.

ASP.NET Web Forms and .NET Framework Migration Services

A .NET migration moves an application built on ASP.NET Web Forms or the .NET Framework to ASP.NET Core and modern .NET, keeping the business rules and the data while replacing the foundation. Keene Systems has built on ASP.NET since 2002, so we know both ends of the journey: the code you have and the platform you are moving to.

Why Web Forms applications need a plan

ASP.NET Web Forms was the standard way to build business web applications for more than a decade, and a huge number are still in daily use. They run on the .NET Framework, which is part of Windows.

Microsoft continues to patch the .NET Framework, but it stopped adding to it years ago. Everything new goes into modern .NET, and Web Forms was not brought across. The practical effects build up slowly:

  • New security features, performance gains and cloud hosting options arrive only on modern .NET.
  • Third-party components the application depends on stop being updated.
  • Fewer developers each year want to work in Web Forms, or know how.
  • Auditors and customers start asking how long the platform will be supported.

None of this is an emergency on any particular day. It is a risk that grows quietly, which is why it is better planned than rushed. Our page on whether an older .NET application is still safe covers how to check where you stand.

Two professionals planning a system at a whiteboard

Signs it is time to plan a migration

  • Your application’s pages end in .aspx and it has not had a major update in years.
  • A security review, insurer or customer has asked which version of .NET you run.
  • A component or reporting tool the application depends on is no longer sold or updated.
  • You cannot find developers willing to work on it.
  • The server it runs on is due for replacement.
  • Users need it on phones and tablets, and it was never designed for them.

What can be kept and what has to change

A migration is not a rewrite from a blank page. A well-run one keeps as much as possible.

  • Kept: the database and its data, the business rules, the reports people rely on, and usually a large share of the C# or VB.NET code that does calculations and data access.
  • Replaced: the screens. Web Forms pages, with their view state and postbacks, have no equivalent in ASP.NET Core and are rebuilt in Blazor, MVC or Razor Pages.
  • Updated: sign-in and security, configuration, and links to other systems, which all work differently on the new platform.
  • Reviewed: third-party controls, reporting tools and anything that depended on Windows-only features.

How we migrate without stopping the business

The safest migrations happen in pieces. We run the new ASP.NET Core application beside the old one and move one area at a time: a module, a group of screens, a set of reports. Users sign in once and move between old and new pages without noticing which is which. At every stage there is a working system, and at every stage you can pause.

Before any screen is rebuilt we separate the business logic from the pages it is tangled up in. That step alone makes the old system easier to maintain, and it means the rules are tested once and reused on the new platform.

The same staged approach applies to systems that started even earlier. See Classic ASP migration and VB6 modernization.

What you gain

  • A supported platform with a published support schedule, so the question “how long is this good for?” has an answer.
  • Speed. ASP.NET Core applications are typically much faster on the same hardware.
  • Hosting choice. Windows or Linux, your own servers or the cloud.
  • Screens that work on phones and tablets.
  • Easier hiring. Developers want to work on current technology.
  • A system that can be connected to other software through modern web APIs.

It is also the moment to fix the things users have complained about for years. Our ASP.NET development team will ask for that list at the start.

How a .NET migration works

  1. We talk first. You describe the system and what is prompting the move.
  2. We assess it. We read the code and the database and report what can be kept, what must change and what the risks are.
  3. We agree the order. The application is divided into stages, starting where the benefit is greatest or the risk is highest.
  4. We migrate in stages. Old and new run side by side, and each stage is tested and released before the next begins.
  5. We retire the old system. When the last piece has moved, the Web Forms application is switched off.
  6. We stay available. The same developers handle fixes and new features, with no minimums or monthly commitments.

The next step is a short, no-pressure conversation. Schedule an ASP.NET project exploration call or use the form on this page.

Frequently asked questions

Is ASP.NET Web Forms still supported?

Web Forms runs on the .NET Framework, which Microsoft still supports as part of Windows. It receives security fixes but no new features, and Web Forms was not carried over to modern .NET, so it has no upgrade path other than migration.

Can Web Forms be upgraded directly to ASP.NET Core?

No. There is no automatic conversion, because Web Forms pages work differently from anything in ASP.NET Core. The business logic and database can largely be kept, and the screens are rebuilt in Blazor, MVC or Razor Pages.

Do we have to rewrite everything at once?

No. The old and new applications can run side by side, and the system is moved across one area at a time while the business keeps running.

What happens to our data?

It stays where it is. In most migrations the SQL Server database is kept, with improvements made where they are needed.

Can you migrate an application written in VB.NET?

Yes. VB.NET business logic can often be kept as it is, or converted to C# as part of the work if you prefer one language going forward.

Should we migrate or replace the application?

If the application still fits the business, migrate it. If the business has changed so much that the system no longer fits, a replacement designed around how you work now may be the better investment. An assessment will tell you which.

Schedule a Project Exploration Call

This free session is your fastest path to improved business productivity.