contact@neural.com.do Monday to Friday, 8:00 AM to 5:00 PM (GMT-4)
Santo Domingo, Dominican Republic +1 (809) 545-5185
Back to Case Studies
Reference project Β· Legacy modernization

Visual Basic 6 Library System β†’ React + .NET 8 + PostgreSQL

A Visual Basic 6 desktop library system with flat-file storage and unsalted MD5 passwords, rebuilt as a modern React, .NET 8 and PostgreSQL web application. First production release on day 4, full delivery in 13 days, 94.7% test coverage.

This open-source legacy application was migrated by the Neural team as a reference project using the same engineering practices, tooling and acceptance criteria applied to client engagements.

Visual Basic 6 to React, .NET 8 and PostgreSQL reference migration
Classification
Legacy Modernization
Technologies
Visual Basic 6 (source), React 19, .NET 8, PostgreSQL
Project type
Reference Project, Legacy Modernization
Delivery year
2026
Engagement model
Reference project (Legacy Modernization)
Platform
Web application
The Challenge

A desktop system with flat files and unsalted passwords

The starting point was a Visual Basic 6 desktop application of approximately 9,400 lines of VB6, storing its data in flat files and protecting user passwords with unsalted MD5 hashes. It could not be run in a browser, shared safely between users or extended without touching fragile legacy code.

The objective was a modern web application that preserves the library's functionality while replacing the storage, security and user-interface foundations entirely.

The Process

From day-4 release to full delivery in 13 days

The team mapped the VB6 code base before writing new code: dependency graph, data model, security posture and a risk register. The target architecture, design decisions and a task-level plan were written down and reviewed before implementation started.

The three reference migrations were executed in parallel between September 21 and October 3, 2026, with approximately 70 logged engineering hours combined, following one shared process.

What the team delivered

  • React 19 front end replacing the VB6 forms
  • Backend services on .NET 8 with typed API contracts
  • Flat-file storage migrated to a PostgreSQL schema with migration evidence and reconciliation
  • Password handling rebuilt with modern hashing in place of unsalted MD5
  • Automated test suite reaching 94.7% coverage
  • Runbook, rollback triggers, monitoring and operations documentation delivered with the release
Project Details

How the migration was run

Shared modernization process

The three reference migrations were executed in parallel between September 21 and October 3, 2026, with approximately 70 logged engineering hours combined, following one shared process.

01 Β· Scan and map

Dependency graph, data model, security posture and risk register built from the legacy code base before any decision is made.

02 Β· Design and plan

Target architecture, written design decisions and a task-level implementation plan reviewed by the engineers who own delivery.

03 Β· Build with evidence

Code, tests, infrastructure, documentation, migration or ETL evidence and reconciliation produced together, so every increment can be verified.

04 Β· Cut over and hand over

Runbook, rollback triggers, monitoring, operations documentation and a credentials package delivered with the release.

The Result

A modern web application with evidence behind every step

The first production release went live on day 4 and full delivery was completed in 13 days, with a 94.7% automated test coverage on the modernized code base.

Day 4

First production release.

13 days

Full delivery.

94.7%

Automated test coverage.

Capabilities

  • Legacy modernization
  • Desktop-to-web migration
  • Data migration and reconciliation
  • Secure software design
  • QA automation
  • DevOps and documentation

Process

Scan and map, design and plan, build with evidence, cut over and hand over: the shared four-step modernization process, executed in parallel with two other reference migrations.

AI role

AI-enabled, human-led delivery: experienced engineers led the migration, AI coding agents supported reading the legacy code, drafting, generation and documentation, and the engineers retained ownership of architecture, security, validation and every important delivery decision.

Ready to talk about your next project?

Let's Talk