.NET Framework modernization
Your .NET Framework applications still work. That's the problem.
They run. They make money. And every quarter the cost of moving them goes up, the number of people who understand them goes down, and another auditor asks a question you'd rather not answer.
We migrate legacy .NET estates — WebForms, WCF, WinForms, VB.NET — to modern .NET and Azure. Without a rewrite, without a big-bang cutover, and without stopping your business.
The pressure
Why this is on your desk now
Windows Server 2016 support ends January 2027.
If your .NET Framework applications run on Server 2016, you have a hard deadline and a budget line whether you wanted one or not. Moving the OS without addressing the framework underneath just buys you a shorter reprieve.
The people who wrote it are leaving.
WebForms and WCF expertise is not being replenished. Every senior developer who leaves takes undocumented business logic with them, and the replacement market is thin and expensive.
Compliance and cyber-insurance now ask directly.
End-of-life software is an explicit question on renewal forms and audit checklists. “It still works” is no longer an acceptable answer to a risk committee.
Azure spend keeps climbing.
Framework applications on IIS VMs cost more to run than the same workloads on modern .NET, and the gap widens with every release.
Scope
What we migrate
| From | To |
|---|---|
| ASP.NET WebForms | ASP.NET Core MVC, Razor Pages, or Blazor |
| WCF services | ASP.NET Core Web API, gRPC, or CoreWCF where contracts must stay |
| WinForms / WPF desktop | Modern .NET desktop, or web-enabled where it makes sense |
| VB.NET | C# on modern .NET |
| .NET Framework 4.x | .NET 10 LTS |
| On-prem IIS | Azure App Service, Container Apps, or AKS |
| Entity Framework 6 | EF Core |
| Web.config / manual deploys | Bicep or Terraform, CI/CD in Azure DevOps or GitHub Actions |
How we do it
We use the strangler-fig approach by default. Your existing system stays live and stays authoritative while functionality moves across module by module, behind a routing layer. Each phase ships independently and can be rolled back on its own.
This is slower than a rewrite on paper. In practice it's the only approach that finishes, because it never requires the business to accept a feature freeze or a single terrifying cutover weekend.
Straight answers
What we tell clients before they hire us
Tooling handles the mechanical work. It doesn't handle the decisions.
AI-assisted migration genuinely does a large share of the syntactic conversion now, and we use it. What it doesn't do is decide which modules to move first, what to leave on Framework permanently, how to keep two systems consistent during a two-year transition, or which undocumented behaviour is load-bearing. That judgment is the work, and it's what you're paying senior engineers for.
Sometimes the answer is not to modernize.
If an application is stable, low-change, and behind a firewall, the right move may be a supported Framework version and proper documentation rather than a migration. We'll tell you that, and it costs you the assessment fee rather than a two-year programme.
Low-code is a real alternative, and sometimes the right one.
If your estate is simple enough to rebuild on Power Platform, that is cheaper than hiring us and we'll say so. We're the right choice when the estate is too complex, too regulated, or too integrated for that to work.
The entry point
Start with an assessment, not a contract
Two weeks. Fixed fee. €4,500
You get:
Dependency inventory
Every third-party component, framework binding, and integration point, flagged by migration difficulty. The ones with no modern equivalent are where projects die, and you'll know about them on day one instead of month eight.
Risk register
What breaks, what's undocumented, what has no test coverage, what nobody understands anymore.
Phased migration plan
Sequenced by business risk and dependency order, with a defensible reason for each phase boundary.
Effort and cost estimate
Ranged, with the assumptions written down.
A go / no-go recommendation
Including “don't do this,” if that's the answer.
The deliverable is a document you can take to your board. Most clients use it to get the migration funded, whether or not we're the ones who do it.
If you engage us for the migration, the assessment fee comes off the first invoice.
Proof
Selected work
Nodi — healthcare workflow platform, Netherlands
Azure-hosted .NET platform for personal alarm systems, home-access management, and B2B client portal workflows, supporting Dutch home care organizations. Regulated environment, operational software that cannot go down, integration-heavy backend.
Read the case study →Trust
Who you're working with
Brick Byte is an engineering company based in Belgrade, Serbia, working with clients across the Netherlands, Germany, and the UK.
How we contract:
- Direct B2B contract with your entity — no intermediary, no EOR overhead
- We invoice in EUR or USD
- IP assigns to you on payment, written into our standard MSA
FAQ
Questions we get asked
Can you migrate without stopping our development roadmap? +
That's the point of the phased approach. Your team keeps shipping features on the existing system while migration proceeds in parallel behind a routing layer. The two are decoupled by design.
We're a public-sector body. We can't move to cloud-native. +
Common, and fine. A large share of public-sector modernization is a lateral move to a supported Framework version with proper documentation and handover, not a cloud rewrite. We do that work and we scope it honestly as what it is.
What about our Telerik / DevExpress / Infragistics components? +
These are usually the hardest part of the estate, not the framework itself. Some have modern equivalents, some need replacement, some need a compatibility shim. The assessment tells you which category each one falls into before you commit budget.
Do we have to migrate everything? +
Almost never the right answer. Most estates have modules that should move, modules that should be retired, and modules that should stay exactly where they are.
How long does it take? +
A single module: weeks. Larger estates depend entirely on dependency structure and how much of the business logic is documented. The assessment produces a number for your specific case, which is the only number worth acting on.
Can we start small? +
Yes — the assessment is designed for exactly that. Two weeks, fixed fee, no commitment beyond it.
Find out what you're actually dealing with
Two weeks, fixed fee, and a document you can take to your board — whether or not you hire us for what comes next.
Or email ask@brick-byte.com with a description of your estate and we'll tell you whether it's worth a call.
