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

GnuCash Desktop Accounting → React + .NET 8 + PostgreSQL

A C/C++/GTK desktop accounting application with a 24-table legacy schema and no multi-user permission model, rebuilt as a multi-user React, .NET 8 and PostgreSQL web application with a reconciled general ledger. First production release on day 8, full delivery in 13 days, approximately 890 automated tests.

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.

GnuCash desktop accounting to React, .NET 8 and PostgreSQL reference migration
Classification
Legacy Modernization
Technologies
C / C++ / GTK (source), React, .NET 8, PostgreSQL
Project type
Reference Project, Legacy Modernization
Delivery year
2026
Engagement model
Reference project (Legacy Modernization)
Platform
Web application
The Challenge

Desktop accounting with no multi-user model

GnuCash is a C, C++ and GTK desktop accounting application built around a 24-table legacy schema and a desktop-focused architecture, with no multi-user permission model. Moving it to the web meant more than a new interface: the data model, the ledger logic and the access model all had to be rebuilt for several users working at once.

The objective was a multi-user web application with a reconciled general ledger, delivered with the evidence needed to trust the migrated financial data.

The Process

A reconciled, multi-user accounting web application

The team mapped the 24-table schema, the dependency graph and the security posture, then designed a target architecture and a permission model before implementation. Data migration was treated as a first-class deliverable, with ETL evidence and reconciliation of the general ledger against the source.

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 front end for the accounting workflows
  • Backend services on .NET 8
  • Legacy 24-table schema migrated to PostgreSQL with migration evidence
  • Multi-user permission model that the desktop application did not have
  • Reconciled general ledger validated against the source data
  • Approximately 890 automated tests
  • Runbook, rollback triggers, monitoring and operations documentation
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

Multi-user accounting on a modern stack, with the ledger reconciled

The first production release went live on day 8 and full delivery was completed in 13 days, backed by approximately 890 automated tests and a reconciled general ledger.

Day 8

First production release.

13 days

Full delivery.

~890

Automated tests.

Capabilities

  • Legacy modernization
  • Data and database modernization
  • Desktop-to-web migration
  • Data migration, ETL evidence and reconciliation
  • QA automation
  • DevOps and documentation

Process

Scan and map, design and plan, build with evidence, cut over and hand over, with reconciliation of the general ledger as the central acceptance criterion.

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