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

MantisBT Bug Tracker β†’ React + Nest.js + PostgreSQL

A PHP legacy bug-tracking application with 57 of its 70 core modules in one dependency cycle and 461 global configuration switches, rebuilt as a modular TypeScript application on React, Nest.js and PostgreSQL with 79 typed API routes. First production release on day 10, full delivery in 13 days.

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.

MantisBT PHP bug tracker to React, Nest.js and PostgreSQL reference migration
Classification
Legacy Modernization
Technologies
PHP (source), React, Nest.js, TypeScript, PostgreSQL
Project type
Reference Project, Legacy Modernization
Delivery year
2026
Engagement model
Reference project (Legacy Modernization)
Platform
Web application
The Challenge

One dependency cycle holding 57 of 70 modules together

MantisBT is a PHP legacy bug-tracking application in which 57 of the 70 core modules sit inside a single dependency cycle, behaviour is governed by 461 global configuration switches, and automated UI testing is very limited. Changing one part safely meant understanding almost all of it.

The objective was a modular, typed architecture that keeps the tracker's functionality while making the code base understandable, testable and safe to change.

The Process

A modular TypeScript architecture with 79 typed API routes

The dependency graph was mapped first, which made the cycle and the configuration surface visible and measurable. The target architecture separated the modules into typed boundaries, and the plan sequenced the rebuild so that each module could be verified against the legacy behaviour.

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 bug-tracking workflows
  • Nest.js backend in TypeScript with a modular architecture replacing the dependency cycle
  • 79 typed API routes
  • PostgreSQL data layer migrated from the legacy schema
  • Global configuration switches replaced by explicit, typed configuration
  • Automated tests where the legacy application had almost none
  • 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

From a dependency cycle to typed, modular boundaries

The first production release went live on day 10 and full delivery was completed in 13 days, with 79 typed API routes replacing the legacy module tangle.

Day 10

First production release.

13 days

Full delivery.

79

Typed API routes.

Capabilities

  • Legacy modernization
  • PHP-to-TypeScript migration
  • Modular architecture design
  • API design
  • QA automation
  • DevOps and documentation

Process

Scan and map, design and plan, build with evidence, cut over and hand over, with the dependency graph as the starting point for the architecture.

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