Fix It or Rebuild It? How to Decide What to Do With an Old Web Application

A system that has run your business for ten years is rarely as bad as it feels. Before paying for a full rebuild, it is worth answering a few questions honestly.

Signs a fix is enough

• The problems are specific: a few bugs, slow pages, a broken integration.
• The data model still matches how the business works.
• The framework has a supported upgrade path.

In these cases we fix the urgent issues first, then upgrade PHP and the framework, and add tests around the flows that make money.

Signs a step-by-step modernisation is better

• The code runs on an unsupported PHP version.
• Nobody wants to touch certain modules.
• You need a mobile app or API that the old system cannot provide.

Here we put a modern API next to the old system and move one module at a time. The business keeps running throughout.

Signs a rebuild is justified

• The data model no longer fits the business.
• Security problems are structural, not isolated.
• Every small change takes weeks.

Start with a review

Our debugging and bug-fixing service usually starts with a short paid code review. You get a written report that says which of the three paths fits — and what each would cost.