Replace the old app without losing what it does.

Your old system still runs the business, but nobody wants to touch it. We rebuild it on a current framework, prove the new version behaves the same, and switch you over with every record intact.

Sound familiar?

  • It runs on PHP 5 or 7, and your host keeps warning you about upgrades
  • It’s built on CodeIgniter, an old Laravel or custom PHP nobody else understands
  • The developer who built it has left, and every change breaks something else
  • There are no tests, so nobody can say what “working” means
  • It holds years of data you can’t afford to lose or retype

How a rebuild works

The old app keeps running until the new one has proven itself. You’re never without a working system.

  1. Map the old app

    We read the code and the database and write down every screen, rule and calculation it really uses.

  2. Rebuild on the same data

    A new Laravel or Next.js app, working against a copy of your real database from day one.

  3. Run both side by side

    The same actions go through both apps, and the results are compared until they match.

  4. Switch over with proof

    Records are reconciled before the switch. You get the test suite and the docs.

Rebuilds we’ve finished

On ledgerlift, the side-by-side tests found two real problems in the original app, both now documented in the project.

A ledgerlift invoice with three line items, taxes, two payments and the balance

ledgerlift

An open-source rebuild of InvoicePlane, a PHP invoicing app, on Laravel 13. Same database, same screens, proven equal by side-by-side tests. Fixed a security hole the original still has.

View on GitHub
10,143attendance rows checked against the old system before the switch

HR platform rebuild

Replaced an international foundation’s decade-old PHP HR system with a Next.js app. Staff, leave and attendance records were reconciled row for row before cutover. It is now the live system of record.

Fixed price

Quoted after a free written review of your app.

  • One price for the agreed scope, not an hourly meter
  • Paid in milestones, not up front
  • 30 days of fixes after the switch, included
What do you need from us for the review?

Read access to the code and a copy of the database with anything sensitive removed. If that’s not possible yet, a 20-minute walkthrough of the app is enough for a first estimate.

Will the new app look different?

Only if you want it to. A rebuild can keep the same screens so nobody needs retraining, or tidy them up as part of the work. We agree on that in the scope.

What happens to our data?

It moves across in full. Before the switch we compare old and new records table by table and show you the result.

How long does it take?

A small app takes three to six weeks. The review tells you the real number for yours.

Tell us what you’re stuck on.

A short email is enough. You’ll get a reply within one working day.