Services

Relicbridge is a consulting practice for the legacy Microsoft stacks the automated migration tools skip: ASP.NET WebForms, Visual Basic 6, Classic ASP, Microsoft Access and Visual FoxPro, moving to .NET 8. Senior US-based engineers work in your repository, billed hourly on a time-and-materials basis, as scoped project engagements or as staff augmentation inside your team.

What we do

• Legacy codebase assessment. A short first engagement, typically about two weeks, that maps the system, builds a characterization-test harness on the riskiest paths, and migrates one real module, so the plan that follows rests on measurement instead of guesswork.
• Strangler migrations. One bounded slice at a time rebuilt on .NET 8, routed behind the old front door, verified against the harness, and cut over with a rollback path while the rest of the system keeps running.
• Agent access layers. A documented API and an MCP server in front of a legacy module, with authentication, per-operation scoping and an audit log, so AI agents and modern services can use it safely without waiting for the rewrite.
• Ongoing support and staff augmentation. After a slice ships, the same engineers can stay on: keeping the harness green as the business changes, handling the runtime and dependency patches the old stack can no longer get, taking the next slice, or simply adding senior .NET capacity to your team for as long as the work needs.

Who this is for

• Mid-market companies whose line-of-business system runs on WebForms, VB6, Classic ASP, Access or FoxPro, typically with one to three internal developers who know it.
• Teams facing a trigger: an unsupported runtime, a retiring developer, a security or audit finding, an integration nobody can build, or an AI initiative blocked by the legacy system.
• Owners who have seen the alternatives, the automated converters that do not cover these stacks and the offshore rewrite quotes, and want the system handled by engineers who will be accountable for it.

How we work with you

• Hourly, time and materials. You pay for the hours senior engineers work. Scope is agreed through an initial conversation, revisited as the code teaches us more, and reported against, so you always know where the hours went.
• Tests before code. Every engagement starts with characterization tests that capture what the system does today, including the bugs users depend on. AI drafts them in bulk; engineers decide which behaviors are contracts.
• Your repository, from day one. Source, tests, dependency maps and runbooks all land in a repository you own. No proprietary framework, no license fees on anything we deliver.
• Project or embedded. Work runs as a scoped project with a named engagement lead, or as staff augmentation with our engineers inside your team and your process. Remote by default, onsite when the work needs it.

Next step

Most engagements begin with the assessment, because the only honest estimate comes from migrating something. If you already have an equivalent map and harness, we will review it and start from there.

Contact us with the stack, the rough size, and what is forcing the question now. A senior engineer replies within one business day.