Application development

Legacy Application Modernization

An older application can still be the system of record. Modernization means reducing risk and adding what the business needs. It does not automatically mean a rewrite.

Choose the depth of change

Maintain

Keep the current application supported and stable.

Enhance

Add a capability the business is missing.

Integrate

Connect it to a newer system through an API or a data feed.

Modernize

Improve the interface, security, data access or structure where that pays off.

Rewrite

Replace the application only when the cost and risk of keeping it are higher than building again.

Where modernization usually lands

  • Legacy ASP.NET and Web Forms applications that still encode the business rules
  • SQL Server version upgrades behind the application
  • Authentication and security brought in line with how the company signs in today
  • A clearer interface, without throwing away the process
  • Performance work in both the application and the queries
  • Reporting moved to a maintained path, including SSRS or Power BI when that fits
  • An API in front of functions other systems need

If the immediate need is care and feeding rather than a roadmap, start with legacy ASP.NET support.

A roadmap before a rewrite

We look at the code, the database and the business process, then recommend the smallest change that removes the risk.