Shawn Mervin

Replacing a legacy ERP with no downtime: a case study

A 50-second case study: how a rental operation's legacy CodeIgniter system was replaced screen by screen with a React web app and React Native field app while it kept running, and switched off in October 2026 with no downtime.

0:50October 14, 2026

About this video

Told over animated diagrams — no customer or payroll screens are shown, because Rental Pilot's real screens hold live customer and payroll data.

Chapters

  1. 0:00 The problem: a system you can't switch off
  2. 0:11 Side by side, screen by screen
  3. 0:25 The data has to keep reconciling
  4. 0:32 Switching the old one off
  5. 0:40 What it looks like now

Transcript

No narration; on-screen captions, in order:

Replacing a legacy ERP with no downtime — a case study.

A rental operation running since 2008 had everything in one old PHP system — and it could not be switched off, not even for a weekend.

So it was never rewritten in one go. New React web and React Native apps were built next to it, on the same data.

Then they took over one workflow at a time.

The test for each step was not a green build. It was whether every invoice, agreement and audit row still added up.

When the last workflow had moved, the old interface was switched off — October 2026, with no downtime. The old address now sends people to the new app.

Today it runs as Rental Pilot, white-labelled for other rental businesses, and watched on a public status board.

1,400,000 audit-trail rows that had to keep adding up after every step.

Have a system like that? The answer is rarely a rewrite from scratch. mervinc.com.

Want this for your business?

Get in touch — I reply myself, usually the same day.

Got an operation that's outgrown its spreadsheets?

Tell me what your business does and where it's jamming up. If I'm not the right person for it, I'll say so and point you somewhere better.

What to send, and what happens next