Find your version, see what it means
.NET Core 3.1, .NET 5, 6 and 7
Support ended by November 2024 at the latest
No security fixes for two years or more. Usually an upgrade, not a rewrite, but packages may need several version jumps.
.NET 8 and .NET 9
Support ended 10 November 2026
No more security patches. The smallest move on this list: retarget, update packages, test.
.NET Framework 4.8 / 4.8.1
No fixed end date
No deadline forces you to move. The reasons are practical: Windows-only hosting, no new features, and libraries and developers moving on.
.NET 10 (LTS)
Supported until 14 November 2028
The target for most modernisation work today, with a year of servicing releases behind it and wide package support.
Dates from Microsoft’s .NET support policy. .NET 11 (released 10 November 2026) is a standard-term release that ends on the same day as .NET 10. See our .NET 8 to .NET 10 checklist.
An upgrade or a migration?
.NET Core, .NET 5–9 → .NET 10
The code already runs on modern .NET, so the work is mostly mechanical, but it still needs care.
- Retarget projects and update packages together
- Work through Microsoft’s documented breaking changes
- Full regression testing before release
- Hosting updated: runtime, pipelines and containers
.NET Framework → .NET 10
A bigger move, done in slices so the business keeps running and each step can be rolled back.
- Tests added around critical business paths first
- Old and new running side by side, one module at a time
- Web Forms, WCF and EF6 replaced with modern equivalents
- Business logic carried across, not rewritten
When the platform starts slowing you down
- Web Forms, WCF or
System.Webdependencies block every attempt to move forward. - The application only runs on one Windows server under IIS, and nobody wants to touch that server.
- Releases are slow and nerve-racking because there are few automated tests.
- Key NuGet packages are abandoned or stuck on old versions.
- It is getting harder to hire developers who want to work on the codebase.
- A security review or customer questionnaire flagged an unsupported runtime.
Five stages, each one reversible
-
Assess
Review the code, dependencies, hosting and data. Write down the risks and agree the target architecture.
-
Protect
Add automated tests around critical business paths so we can prove behaviour has not changed.
-
Migrate in slices
Move one module or route at a time using the strangler-fig pattern, with old and new side by side until each slice is proven.
-
Re-host
Move to Azure App Service, containers or modern Windows or Linux hosting, with a CI/CD pipeline instead of manual deployments.
-
Hand over
Documentation, a runbook and a walkthrough for your team, plus optional support to keep the runtime current.
We use Microsoft’s upgrade tooling for the mechanical changes, but never treat a tool’s output as finished without testing.
Modernisation Assessment
What you get
- Code and dependency analysis: projects, NuGet packages, Web Forms, WCF, EF6, authentication and configuration
- A risk register with each risk rated and a suggested mitigation
- A target architecture and hosting recommendation
- A phased migration plan you can take to budget holders
- A fixed quote for phase one
- A 60-minute read-out with your team
What we need from you
- Read access to the source code, under NDA
- An hour or two with someone who knows how the system is used
- Details of the current hosting and deployment process
- Access to a non-production environment, if one exists
You can use the report with us, with your own team or with another supplier.
Our website: .NET 6 to .NET 10
One thing broke: removing an unused package also removed a library our CAPTCHA relied on without anyone knowing. That is the kind of surprise an assessment is designed to find early. We wrote up what changed, what broke and how we fixed it.
From what you have to what you need
ASP.NET Web FormsRazor Pages, MVC or Blazor
No automatic conversion exists. Pages are rebuilt, but business logic is usually reused.
WCF servicesWeb API, gRPC or CoreWCF
CoreWCF keeps existing clients working while new clients move to REST or gRPC.
Entity Framework 6EF Core
Mapping and query behaviour differ, so data access is tested carefully.
Membership / Identity 2ASP.NET Core Identity or Entra ID
Password hashes and sessions get a migration plan so users are not locked out.
Windows servicesWorker Services or Azure Functions
Often the simplest part of the migration.
IIS on a single serverApp Service, containers or modern hosting
With a CI/CD pipeline and separate test and production environments.
The parts that usually go wrong, planned for
Data
Schema changes and data migration rehearsed on a copy of production data, with a rollback plan for every step.
Sign-in and sessions
Authentication changes planned so existing users keep their accounts and are not forced through surprise resets.
Third-party libraries
Each dependency checked for a supported replacement. Where none exists, we isolate it or find another route.
Hidden behaviour
Differences in serialisation, date and culture handling, and configuration caught by tests rather than by users.
Need extra hands for your own migration team? We also provide dedicated .NET developers. For new builds and ongoing work, see our main .NET development page.
.NET modernisation questions
Do we have to move off .NET Framework 4.8?
Not by a fixed date. .NET Framework 4.8 is supported as part of Windows and follows the Windows lifecycle. The case for moving is about hosting options, performance, hiring and access to current libraries. The assessment helps you decide whether and when it is worth it.
We are on .NET 8. What happens if we wait?
The application keeps running, but it no longer receives security fixes, and security reviews and customer questionnaires increasingly flag unsupported runtimes. Moving to .NET 10 is normally a contained piece of work, so it is usually better planned now than done in a hurry later.
We are on .NET Core 3.1 or .NET 6. Is that a bigger job than .NET 8?
Somewhat. The code is already on modern .NET, so it is still an upgrade rather than a rewrite, but there are more breaking changes to work through and packages may need several version jumps. The assessment tells you how much.
Can we modernise without a full rewrite?
Usually, yes. Most business logic can be carried across. We migrate module by module with old and new running side by side, so there is no single big-bang release.
How long does a .NET Framework migration take?
It depends on size, test coverage and how much Web Forms or WCF is involved. Rather than guess, the two-week assessment produces a phased plan and a fixed quote for phase one.
Do we have to move to Azure?
No. Azure is a common choice for our clients, but modern .NET runs well on Linux or Windows servers, on AWS, or in containers on your own infrastructure.
Can you work alongside our own developers?
Yes. Many teams want to keep ownership of the codebase. We can lead the migration and pair with your developers, so the knowledge stays in-house when we finish.
Not sure where your application stands? Ask an engineer.
Thirty minutes to talk through your application, its dependencies and your constraints. If an assessment is not worth it for your situation, we will tell you.