// services / legacy-modernization

From VB6 to .NET 10 — step by step, modernized.

We migrate Visual Basic 6, Delphi, classic ASP, Access applications and aging WinForms software to modern .NET 10 architectures — no big-bang, no downtime, with a functionally identical transition phase.

VB6 has been alive since 1998. It was not built for the cloud, not for multi-user web access, not for modern security requirements. We dissolve the risk step by step — and you keep your business logic.

Request code audit See the migration

// status-quo

Software that delivers — and slowly turns into a mortgage.

— problem

The problem

VB6 runs. It has been running for twenty years. But no vendor support, no 64-bit future, no multi-user web interface, no modern authentication. Every personnel change on the team increases the risk that critical business logic becomes unmaintainable.

— fix

The fix

We separate the application into layers, rebuild the business logic in modern C# 12, run old and new in parallel, and switch over module by module. Your data stays consistent, your users keep their workflow, your risk drops with every sprint.

// transformation

Watch the migration.

Scroll through — code, IDE and UI morph from VB6 to .NET 10 / Blazor.

Microsoft Visual Basic 6.0 — Project1 - frmMain (Code) _ ▢ ×

' frmMain.frm  —  Project1
' Microsoft Visual Basic 6.0
Option Explicit

Private Sub cmdSave_Click()
    Dim rs As ADODB.Recordset
    Set rs = New ADODB.Recordset
    rs.Open "SELECT * FROM Orders", _
            cn, adOpenStatic, adLockOptimistic
    rs.AddNew
    rs!CustomerID = txtCust.Text
    rs!Total = CDbl(txtTotal.Text)
    rs.Update
    MsgBox "Gespeichert.", vbInformation
End Sub

Order entry

Kunde:

Betrag:

Frame1

Bar Rechnung

VS Code — Modernized.cs · .NET 10 .NET 10

// MainView.razor.cs · .NET 10
public partial class MainView : ComponentBase
{
    [Inject] private IOrderService Orders { get; set; } = default!;
    [Inject] private ILogger<MainView> Log { get; set; } = default!;

    private OrderModel Model { get; set; } = new();

    private async Task OnSaveAsync()
    {
        await Orders.CreateAsync(Model);
        Log.LogInformation("Order saved: {Customer}", Model.Customer);
    }
}

Order capture

Customer

Amount

↓ scroll

// supported-stack

Sources we migrate.

Over 25 years of Microsoft, Borland and Sybase stacks — we know the quirks, the gotchas and the productive migration paths.

— from

Source stacks

×

Visual Basic 6.0

COM components, OCX controls, MS DataGrid
×

Visual Basic .NET 1.1 / 2.0

early .NET Framework apps with WinForms
×

Delphi 7 / XE

VCL applications, BDE and FireDAC
×

Classic ASP / VBScript

ASP 3.0 with COM backends
×

Microsoft Access (VBA)

forms, reports, JET/ACE databases
×

Legacy WinForms (.NET 2.0–4.8)

older LOB applications
×

Sybase PowerBuilder

DataWindow-centric business apps
×

FoxPro / FoxBASE

DBF-based in-house solutions

— to

Target platform

✓

.NET 10 / C# 12

long-term support, modern language, high performance
✓

Blazor United

one model for server, WebAssembly and hybrid
✓

WPF / WinUI 3

modern desktop UI with XAML
✓

.NET MAUI

desktop and mobile from one codebase
✓

ASP.NET Core 10

web APIs, minimal APIs, gRPC, OpenAPI
✓

Entity Framework Core 10

clean migration paths from ADO.NET, BDE, JET
✓

PostgreSQL / SQL Server 2022

modern, supported database platforms
✓

Docker · Kubernetes

containerization as a migration step

A tidy workspace with a modern monitor, mechanical keyboard and notebook.

// migration in practice · createIF labs

// migration-plan

Five steps. Reversible until the last moment.

Code audit

We scan the VB6/Delphi codebase: modules, dependencies, third-party components, OCX/COM DLLs. Clear statement on risks, effort and migration order.

Layer split

Decouple UI, business logic and data layer — even where they are originally entangled. Business rules end up as pure C# 12, testable and neutral.

Parallel run

New .NET 10 modules run alongside the existing system. Identical tests against both sides, identical data paths, identical results — as the prerequisite for every switch.

Module migration

Module by module: lowest risk first, business-critical last. Every step is reversible. Your users only notice the migration through a better interface.

Cutover & decommissioning

VB6 is shut down once both sides have delivered identical results for weeks. With runbook, backup plan and clean documentation. No vendor lock-in.

// good-fit

When we're the right partner.

You run critical business logic on VB6, Delphi, Access or classic ASP — and can no longer change it without risk.
You've lost the original developers, and the remaining team only knows parts of the codebase.
You need a web interface, multi-user access or mobile usage — the old software does not provide it.
You have to meet compliance requirements (BSI, ISO 27001, GDPR) that get harder with unsupported software.
You want to migrate — but without a multi-year big-bang that puts the running business at risk.
You have a database that needs to move along (Access, BDE, Sybase, old SQL Server versions).

// free code audit

Request a code audit.

60 minutes, free. We look at your codebase — VB6, Delphi, Access or classic ASP — and deliver an honest assessment: what's feasible, what isn't, what it costs.

— Response within one business day.

hosted in germany
on-prem · byollm
gdpr by default