SAP to open-stack ERP migration
Manufacturer, 500+ employees. Phased migration off SAP ERP onto an open stack with custom modules — run in stages while the plant kept working.
- 0 downtime
- 8 mo migration
- −40% on licences
.NET development, including the move off .NET Framework
Most .NET conversations start the same way: the system works, it runs on 4.7 or 4.8, and every year the cost of leaving it there goes up a little.
What we can show you
Overview
Two platforms with the same name
.NET is now two platforms: legacy Framework 4.x, Windows-only and in maintenance, and modern .NET, cross-platform with an LTS release every year.
What «.NET development» means in 2026, and why the version decides everything
Which one you are on changes the cost of every decision: hosting, hiring, licences and how much of the ecosystem is still open to you. Framework applications keep working — Microsoft supports them — but the gap between «works» and «supportable» widens each year.
So an honest .NET engagement starts by establishing the position: what runs where, what depends on Windows-only APIs, and what the move would cost per module. Only then does it make sense to talk about features.
When .NET is the right call
Corporate environments with Active Directory, SQL Server and existing Windows infrastructure; large domains where a typed, structured platform pays off; teams that hire predictably. For a small consumer product with no enterprise integrations, a lighter stack is usually cheaper to own.
Signals your .NET estate needs attention
- the application still runs on .NET Framework 4.x;
- WCF services or WebForms pages are in production;
- deployment is Windows Server only, and hosting bills reflect that;
- SQL Server licences are a visible line in the budget;
- hiring for the old platform takes months and costs more each year.
Price
From $7,990
Timeline
3 weeks to first release
Payment
50/50 by milestone
Comparison
Stay on .NET Framework or migrate to modern .NET
Both are defensible. The decision is about hosting costs, hiring and how long the system still has to live.
Criterion
Framework 4.xModern .NET
Modern .NET.NET Framework 4.x
Hosting
Windows Server only
Linux containers or Windows, your choice
Performance and cost per request
Adequate
Materially better on the same hardware
Hiring
Shrinking pool, rising rates
Standard market
Ecosystem and libraries
Frozen in place
Current, with LTS every year
Migration effort
None today, more every year
Weeks per module, done incrementally
When it wins
System is being retired within a year or two
System has to live and change for years
Scope
What we build with it
Where this stack earns its place in a project, and what we would use instead if it did not.
Business systems and services
ASP.NET Core APIs and back-office systems where the domain is rules, roles and reporting.
Framework to modern .NET
Project-by-project migration off 4.x with tests as the safety net, and containerisation once the code allows it.
Enterprise integrations
SSO and Active Directory, SQL Server, ERP exchange and message queues — see API and integration.
SQL Server work
Schema and performance, migrations, and moves to managed hosting where the licence maths works out.
Fit
When it is the right call — and when it is not
The best stack is usually the one your team can maintain after we leave.
Right for
Corporate systems with Windows infrastructure, Active Directory and SQL Server already in place, and teams that need a supported platform rather than a fashionable one.
Not right for
A small public-facing product with no enterprise integrations: a lighter stack will cost less to run and to hire for, and we will say so.
Rates
$28–55/hour by role
Fixed builds
From $7,990
Discounts
Dedicated −10% · partners −15%
How we work
Getting off .NET Framework without a big-bang project
The part that is specific to this stack rather than true of every project.
Why us
Why teams bring us in for this stack
Four things we can prove, not four adjectives.
Migration audit before any promise
Dependency tree, Windows-only API usage, test coverage and a per-module estimate for $1,790, credited against the work. Nobody should quote a Framework migration blind.
Licences and cloud at cost
SQL Server, Windows and cloud bills are paid to the vendor directly, with no mark-up from us — the discount applies to our engineering, not to your infrastructure.
Your repository from commit one
Code, CI and infrastructure as code in your accounts, IP assigned at delivery with a documented chain of title.
Senior review on every merge
A senior engineer who did not write the code reviews it — including code an AI drafted. In enterprise .NET that review is what keeps an integration from failing quietly.
Industries
What we buildfor your industry
.NET shows up where the back office is old and the integrations are many: manufacturing, logistics, finance departments and property management.
- IT companies and digital agencies
- Insurers and brokers
- Lenders and microfinance
- E-commerce
- Wholesale and distribution
- Manufacturing
- Freight and forwarding
- Clinics and medical centres
- Dental
- Car dealers and service centres
- EdTech
- Legal and consulting firms
- Equipment rental
- Real estate agencies
- Property developers
- Travel and events
- Beauty and wellness
- Construction and renovation
FAQ
Questions we get about this stack
Answered by the people who would do the work, not by a sales team.
Do you work with .NET Framework or only modern .NET?
Both. As a dotnet development company we take Framework 4.x estates as readily as greenfield work: most engagements start on 4.x and end on a supported LTS release of modern .NET, one module at a time.
How long does a Framework-to-.NET migration take?
Weeks per module rather than one big project. The audit produces a per-module estimate before anything is touched.
What usually breaks in a migration?
WCF services, WebForms pages, System.Web dependencies, third-party components without modern builds, and anything tied to Windows-only APIs. We find those in the audit and price them.
Can it run on Linux afterwards?
Usually yes, and that is where hosting savings come from — but we verify it dependency by dependency before promising it.
Do you do SQL Server work?
Yes: schema design, performance, migrations and moves to managed hosting. Licence costs stay yours and are paid at cost, never marked up.
Can you integrate with Active Directory and our ERP?
Yes — SSO, directory sync and ERP exchange are the most common integrations in this stack, and they get their own contract tests.
2–4×
faster on the code-writing share
in 3 weeks
from idea to MVP
230+
projects delivered
17 years
of engineering experience
Work
Work we can show you
SMARTWILL
Digital inheritance service (Web3)
AIRDEVELOPPA
Indoor air quality finder driven by sensor data
CAR5
Car-sharing app
APP.DENTAL
Cloud CRM for dental clinics
NEXORA
Warehouse and logistics management platform
As-built docs
Digital as-built documentation
EX211
Telegram Mini App for currency exchange
SMARTWILL
Digital inheritance service (Web3)
Need this stack with a senior review included?
Tell us what exists today — a green field, a legacy codebase, or a team that needs two more pairs of hands. We answer with a scope, a price and a date.
We do not take work on a stack we cannot review internally at senior level.