Laravel upgrades

We move Laravel apps to the current version, one major version at a time, while your team keeps shipping. We took a US nonprofit’s two platforms from Laravel 10 to 12.

We start with an audit: we read the code, the dependencies and the deploy, and list what stands between your app and the next version. Then each major version lands in its own pull request, with the tests passing, through your review process. We’re an official Laravel Partner and have worked in Laravel since 2016.

  • Packages stuck on an old version

    One abandoned or pinned package can hold the whole app back. We update or replace them before the upgrade, so it doesn’t stall halfway.

  • No tests to lean on

    We add tests around the parts the upgrade touches first, so every step can be checked before it ships.

  • A PHP version behind

    New Laravel versions need a newer PHP. We move PHP and the server along with the app, not after it.

How an upgrade runs

  1. Step 01

    We audit the app

    The code, the Composer dependencies, the PHP version and the deploy. You get the list of what blocks the next version.

  2. Step 02

    One version at a time

    Each major version lands in its own pull request that you review and release on your calendar.

  3. Step 03

    It stays current

    Stop at the version you need, or keep us on a monthly retainer so the next upgrade never slips.

An upgrade we shipped

  • A US nonprofit

    Two web platforms on Laravel and October CMS, one of them a tablet app for residents of correctional facilities. Nerdify engineers work alongside the nonprofit’s developers and moved both from Laravel 10 to Laravel 12. Name withheld by agreement.

    Nonprofit · Laravel · October CMS

    [ Read the case → ]

Laravel upgrade · Both platforms

10 → 12

Both platforms, one major version at a time, shipped through its staging, QA and automated GitHub checks.

When teams call us

Your Laravel version is out of support.

An audit first, then the upgrade, one version at a time.

A package forces the move.

A dependency drops your version, and the upgrade can’t wait.

A big feature is about to land on old code.

We upgrade first, so the feature is built on the current version.

Model · Audit, then the upgrade

Scoped after the audit.

The price depends on the codebase and how far behind it is. We quote after a 30-minute call.

Alejandro Galo

Head of Sales, Nerdify

Book a free 30-minute call to talk through your team, stack and timeline.