System replacement

RedenkoConnect

The system field and office teams work with every day runs on a new foundation, without the work stopping for a day. New requests have gone live faster and more safely ever since.

role
Lead developer
stack
Laravel Livewire Flux UI Tailwind CSS Pest
RedenkoConnect
context

What was going on

RedenkoConnect is the web platform field and office teams work with every day. Over the years it had grown organically as custom PHP, with a lot of business-specific logic and practical knowledge inside. I rebuilt it completely on Laravel and have kept developing it since.

challenges

What made it hard

Understanding a large existing codebase and reconstructing it, business rules included

Moving production data out of the existing database without interrupting daily operations

Existing links and the data model had to keep working after the switch

Bringing security and privacy up to today's standard without touching functionality

Preparing the switch while the old system stayed in production

approach

How I approached it

The rebuild was split into documented phases: first the data model and authorisation, then the screens and the background tasks. Custom migration tooling made the data switch repeatable and testable, and the old system kept running until the new one was demonstrably complete. What used to be manual work or loose scripts now runs as queues, a scheduler and automated tests.

result

Rebuilt completely and live, with all existing functionality and data kept

From zero to a full automated test suite with static analysis

Existing links kept working after the switch

New functionality has gone live faster and more safely since, thanks to the framework's conventions and the tooling

intake

Need something like this?

One route: analysis, building and introducing, and maintenance if you want it. It starts with a thirty-minute intake.