Legacy .NET migration
Moving an older .NET application to a supported platform, with the data and history intact and the business running throughout.
What we migrate
.NET Framework to modern .NET. Dependencies, configuration, Windows-specific code and the testing that proves it behaves the same.
WebForms. There is no direct path, so the choice is a rewrite or an incremental replacement. An assessment tells you which.
Umbraco. Version 7 and 8 sites moved to current Umbraco, including the Minnesota Secretary of State's move from 7 to 14.
On-premises to Azure. Applications and SQL Server databases, with the identity and security setup your IT team requires.
What it costs
Ranges from completed engagements. Test coverage moves the number more than size does.
.NET Framework to modern .NET
| Size | Timeline | Range | Profile |
|---|---|---|---|
| Small | 2 to 4 weeks | $10,000–$13,000 | Under 50k lines, minimal System.Web usage, current dependencies, reasonable test coverage |
| Medium | 1 to 3 months | $15,000–$25,000 | Active business logic, some System.Web usage, a mix of current and dated dependencies |
| Large | 3 to 6 months | $35,000 and up | Heavy System.Web usage, legacy packages, Windows-specific integrations, substantial manual testing |
Umbraco 7 to 13+
| Size | Range | Profile |
|---|---|---|
| Small | $15,000–$30,000 | Under 20 document types, simple templates, minimal custom code, no member functionality |
| Medium | $35,000–$75,000 | 20 to 50 document types, custom features, package dependencies, basic member functionality |
| Large | $80,000 and up | Extensive custom development, member portals, many package dependencies, high content volume |
Three things drive the estimate: components with no modern version, integrations that haven't been inventoried, and how much test coverage exists. An assessment measures all three and turns the range into a figure.
What are you running?
The runtime version, roughly what the application does and what's forcing the move.
Get in touch