Legacy ASP Classic to ASP.NET Modernization
Some production systems are too large and too embedded to replace. We have run a continuous ASP Classic to ASP.NET migration on a long-running US public sector case management platform for thirteen years, alongside the same extend-rather-replace pattern on a commercial ERP and an inherited multi-tenant SaaS platform.
SYSTEM
TRANSITION
LAYER
The scope, and what has to get right.
- Incremental ASP Classic to ASP.NET migration. Legacy pages and modules converted piece by piece against a live system, rather than a single all-at-once rewrite that risks the whole platform.
- Migration without downtime. A system in continuous public-sector use cannot go offline for a rewrite. Conversion happens against the running platform, verified at each step.
- Extending a commercial ERP instead of replacing it. The same extend-rather-replace discipline applied to a commercial ERP that could not be replaced, detailed in our AccountMate case study.
- Extending an inherited SaaS platform. The same pattern again, applied to a cloud SaaS product inherited mid-flight rather than built from scratch, detailed in our multi-tenant safety platform case study.
Inside the system, not bolted on.
Convert incrementally, verify continuously
Each converted piece is checked against the live system before the next piece begins, so the migration never risks the whole platform at once.
Confidentiality is part of the engagement
The specific systems, their code and their business logic are not discussed publicly, consistent with the confidentiality this kind of long-running public-sector engagement requires.
One principle, applied wherever it fits
Whether the system is legacy ASP Classic, a commercial ERP, or an inherited SaaS platform, the approach is the same: extend what already works rather than restart from zero.
A web layer and B2B portal over a commercial ERP
- AccountMate's functionality, in a browser: Order entry, invoicing, payments and reporting screens built directly against the same SQL Server data AccountMate uses, so both stay in step with no synchronization process to maintain.
- Customers place their own orders: Account-gated self-service ordering against the live product catalog, with every order written back into AccountMate as a real ERP order rather than a message someone re-keys, plus full order history per customer.
- Order shipping handled end to end: The shipping workflow that used to live partly outside the system now runs inside it, from order to dispatch.
- Incoming email filed automatically: Attached documents are extracted from incoming email, OCR-processed, identified and attached to the correct order record, removing manual filing and the risk of a document landing on the wrong order.
Also relevant: Maintaining and extending a lone worker safety SaaS platform
Common questions.
Can you name the client or the system?
No. This engagement is covered by a long-standing confidentiality arrangement, and we describe it only as a long-running US public sector case management platform, consistent with that agreement.
How many systems have been converted?
We do not state a specific count. What we can confirm is that the work covers multiple large production systems, and we would rather say that plainly than publish an invented number.
Is this the same discipline as your ERP extension work?
Yes. It is the same extend-rather-replace approach applied wherever a client is running on something that cannot simply be replaced, whether that is legacy ASP Classic, a commercial ERP, or an inherited SaaS platform.
Does this cover ASP.NET Core, or just ASP.NET MVC?
The migration work covers ASP Classic to ASP.NET generally. Which specific framework a given system lands on depends on that system's own constraints and timeline.
Can this happen without downtime?
Yes, and it has to. A platform in continuous public-sector use cannot go offline for a rewrite, so conversion happens incrementally against the live system.
Is there a system nobody wants to touch because it is too old to replace?
Tell us what it runs on today and we will tell you honestly whether extending it is realistic.