ASP.NET Web Forms → .NET 10

Your Web Forms app, moved to modern .NET.

Fixed price. Phased, so your team never faces a risky cutover weekend. AI-assisted conversion, with every page reviewed and tested by an experienced .NET developer.

  • VB.NET and C#
  • SQL Server stays as it is
  • You own all the code

Sound familiar?

The app runs the business. Nobody wants to touch it.

Web Forms apps built 10 or 20 years ago still handle orders, billing, scheduling and reporting at thousands of companies. They work, until they don't.

  • The person who built it left

    Knowledge of how it works lives in one head, or none. Every change is a guess.

  • Hiring for it is nearly impossible

    Few developers want Web Forms or VB.NET work, and the ones who do are expensive.

  • It's stuck on .NET Framework

    It can't use modern .NET, current libraries or modern hosting, and the gap grows every year.

  • A rewrite feels too risky

    Big-bang rewrites run over budget and break things nobody knew the old system did.

Services

Three steps, one clear price at each.

Start small with an assessment. You'll know the cost, the plan and the risks before you commit to anything bigger.

Then

Fixed-Price Migration

Quoted from your assessment

  • Web Forms pages rebuilt as .NET 10 Blazor components
  • Old and new run side by side; pages move in phases
  • Same behavior, same database, every page tested against the original
  • Scope changes are agreed in writing first

Ongoing

Support Retainer

From $1,500/month

  • Bug fixes, small features and report changes
  • A set number of hours each month with an agreed response time
  • Available for migrated apps and for legacy apps you're not ready to move yet

How it works

No big-bang cutover. Ever.

Your new app is put in front of the old one. Pages move over a group at a time, and anything not yet migrated is quietly passed through to the old app. Users keep one address and never notice the switch.

  1. 1

    Assess

    Under NDA, with read-only access, we inventory the whole application and deliver a phased plan and a fixed price.

  2. 2

    Build the foundation

    New .NET 10 solution, your layout and navigation, data access and authentication, running side by side with the old app.

  3. 3

    Migrate in phases

    Read-only pages first, then pages that change data. Each group is tested against the original before it goes live.

  4. 4

    Cut over and support

    When the last page moves, the old app is retired. Optional ongoing support keeps the new one healthy.

See exactly what you'd get

A real assessment, on a real app.

We ran our assessment on Microsoft's own open-source Web Forms sample application, eShopLegacyWebForms. The report is 9 pages: a plain-English summary for decision makers, a phased plan, the risks specific to the app, what we'd need from you, and the full estimate with every number explained.

Download the sample report (PDF)
  • Summary for decision makers. What the app is, the cost, the risks and our recommendation.
  • Phased plan. Which pages move when, and what each phase depends on.
  • Risks, named specifically. For example: two apps writing to one database during the transition.
  • Estimate you can audit. Hours by page and by shared component, from measured code, not guesswork.

Why it costs less

AI does the heavy lifting. A developer signs off on every page.

Our conversion tooling does the first pass on each page: it reads the markup, code-behind and the shared code it depends on, and produces modern Blazor code plus a written review. Then a .NET developer checks it, tests it against the original and fixes what the tool missed.

Same behavior

Formats, messages, defaults and quirks are preserved on purpose. Your users shouldn't have to relearn anything.

Same database

Your SQL Server schema and stored procedures stay as they are, so reports and integrations keep working.

Defects surfaced, not hidden

When we find a real bug or security issue in the old code, we tell you and fix it only with your agreement.

You own everything

All code lives in your repository, in standard .NET. No proprietary runtime, no lock-in.

FAQ

Questions we hear first.

Is our source code safe with you?

We sign an NDA before seeing any code, and we only need read-only access. Code is processed with a commercial AI service under terms that do not allow training on your data. If your policies require it, we can run the tooling under your own accounts.

Do we have to stop using the current app during the migration?

No. The old and new apps run side by side and pages move over in phases. Your team keeps working the whole time.

Will our database change?

No. We keep your SQL Server schema, stored procedures and data as they are. Any database improvements are a separate decision for later.

Our app is VB.NET. Is that a problem?

Not at all. VB.NET Web Forms is a core part of what we do. The new app is written in C#, and the assessment shows exactly how each VB page maps over.

We use Telerik, DevExpress or Crystal Reports controls.

The assessment finds every third-party control and prices its replacement, so there are no surprises later.

Why Blazor?

Blazor is Microsoft's component-based web framework for modern .NET. Its model is the closest to Web Forms, so pages map over cleanly, and .NET 10 is a long-term support release.

How long does a migration take?

A small app with a handful of pages can be done in a few weeks; large apps take months. Your assessment includes a phased timeline.

What if the work takes longer than estimated?

That's our risk. The price is fixed for the agreed scope. If you want to add or change scope, we agree the change in writing before doing it.

Get started

Tell us about your app.

A few lines is enough: what the app does, roughly how big it is, and what's worrying you about it. We'll reply within one business day to set up a short call.

Prefer email? hello@showmentech.com

We'll only use your details to reply to you.