Skip to content

Laravel development

Laravel upgrades and legacy rescue

An old version of Laravel, a PHP version that’s reached end of life, or code nobody wants to touch: it all works until it doesn’t. I audit what you have, add tests around the risky parts, then upgrade or stabilise it in safe stages while the business keeps running.

How I make legacy code safe

01

A health check first

I review the code, dependencies, hosting and process, and give you a plain-English report on what’s healthy, what’s risky and what to fix first.

02

Tests before refactoring

I add automated tests around the critical parts before changing anything, so we can prove the app still behaves the same afterwards.

03

Staged version upgrades

Laravel and PHP upgraded one safe step at a time, with each step released and verified, rather than one risky big bang.

04

Performance fixes

Slow queries, missing indexes, caching and background jobs: the common causes of a sluggish Laravel app, found and fixed.

05

Security and hosting hygiene

Updated dependencies, secrets handled properly, backups that actually restore and sensible deployment and monitoring.

06

Documentation and handover

Short, useful docs and a tidy repository, so the next developer (or you) isn’t starting from scratch.

Worth knowing

Upgrade or rebuild? I’ll tell you honestly

Most Laravel apps can be upgraded, and that’s usually cheaper and less risky. Occasionally the foundations are so weak that a rebuild is the better investment. I’ll show you the evidence either way, so the decision is yours and well informed.

How a rescue works

  1. Audit

    Read-only access to your code and hosting. You get a plain-English report with a prioritised plan and rough effort.

  2. Stabilise

    Fix the urgent risks, add tests around critical flows and set up safe, repeatable deployments.

  3. Upgrade

    Move Laravel and PHP forward in staged releases, checking behaviour at each step.

  4. Hand over or carry on

    Documented, tested and in good shape. I can keep looking after it, or you can take it in-house.

Ways to work together

Every business is different, so I keep this flexible. I’ll recommend the simplest option that gets you what you need.

Option 01

Laravel health check

A fixed-scope audit with a report and walkthrough call.

Best when: You want to know where you stand before deciding.

Option 02

Upgrade project

A scoped, staged upgrade of Laravel and PHP with tests.

Best when: You know the app needs bringing up to date.

Option 03

Ongoing care

Regular updates, monitoring and fixes after the rescue.

Best when: You want it to stay healthy.

FAQ

Laravel Upgrades & Legacy Rescue: your questions answered.

How do I know if my Laravel app is out of date?

Check your composer.lock for the Laravel version, and your hosting for the PHP version. If either is a few major versions behind, or no longer receiving security fixes, you’re accumulating risk. A short health check will tell you exactly where you stand.

Should we upgrade or rebuild?

Usually upgrade: it’s cheaper, faster and keeps the behaviour users rely on. Rebuild when the foundations are so tangled or untested that upgrading costs more than starting again. I’ll show you the trade-offs with evidence.

Will the site go down during the upgrade?

Not if it’s done properly. I work on a copy, test in staging and release each step with a rollback plan, so users shouldn’t notice anything other than improvements.

How long does an upgrade take?

It depends on how far behind you are and how much of the code is covered by tests. A modest app a version or two behind can be quick; a long-neglected one takes longer. The health check gives you a realistic estimate.

Can you take over code written by someone else?

Yes. I’ve worked with plenty of codebases I didn’t write. I’ll start by reading and testing it, and tell you honestly what I find.

What access do you need?

Usually read-only access to the repository and hosting to begin with, and I’m happy to sign an NDA first. I only need to change things once we’ve agreed a plan.

Get in touch

Tell me about your project.

No sales script and no pressure. Share a few details and I’ll reply personally, tell you honestly whether I can help and, if I can’t, point you to someone who can.

I’ll only use your details to reply. See the privacy policy.