Why move at all
.NET Framework 4.8 is still supported as part of Windows, but it receives fixes, not new features. Modern .NET runs on Linux and in containers, which usually makes hosting cheaper and more flexible. Most new libraries, tools and developers target modern .NET first. Modern .NET is significantly faster for typical web and API workloads.
Which version to target
What usually ports easily, and what does not
Business logic and class libraries: usually straightforward, often a project-file change plus fixes. ASP.NET MVC and Web API: move to ASP.NET Core; controllers carry over, but startup, configuration and middleware change. Entity Framework 6: move to EF Core, and test queries carefully. Web Forms: has no direct equivalent in ASP.NET Core, so pages are rebuilt, for example in Razor Pages, Blazor or a React or Angular frontend. WCF services: CoreWCF exists for the server side, or the service can be replaced with REST or gRPC. Windows-only APIs and old third-party components: each needs a replacement or a wrapper.
Migrate in stages, not in one big rewrite
A practical plan
Inventory the solution: projects, dependencies, third-party packages and Windows-only features. Add automated tests around the most important workflows before changing anything. Move shared class libraries first, then APIs, then the user interface. Containerize the new parts and deploy them next to the old system. Retire the old application once the last route has moved.
What drives the cost
Frequently asked questions
Do we have to stop adding features during a migration?
No. With an incremental migration, new features can be built in the new application while older parts keep running, so the business keeps moving.
Is .NET Framework 4.8 going out of support?
It is supported as a component of the Windows versions it ships with, so there is no single end date to panic about. The bigger costs are hosting, hiring and the libraries that no longer target it.