Fixed-price project

Laravel upgrade service: move an old Laravel app to the latest version

I move a Laravel app to the newest release and a supported PHP version in small steps, checking it after each one. It fits teams whose app is on an old version, from $350 for an audit and plan in 3 days.

Price
From $350
Delivery
3 days
at the Upgrade audit and plan tier
Packages
3 tiers

Who it is for

Who this helps

  • Owners of a Laravel app that is two or more versions behind
  • Teams on a Laravel or PHP version that no longer gets security fixes
  • Businesses that run sales or billing on the app and cannot afford a broken release
  • Developers who want a senior second opinion before they start the upgrade

Signs

Signs you need this

  • Composer will not install a new package because it needs a newer Laravel or PHP.
  • Your host or a security review has warned you about an old PHP version.
  • Nobody wants to touch the framework because the last upgrade broke something.
  • The docs, tutorials and packages you find no longer match your code.
  • Your Laravel version no longer gets bug fixes or security fixes.

Scope

What I do

  • The audit I start with

    I read your code, your composer.json and your hosting setup. I note your Laravel and PHP versions, every package and how old it is, and the code that newer versions break. The Laravel upgrade guide labels each breaking change by likelihood of impact. I use that guide as the base, then check what only your app can show.

  • One version at a time

    If you are several releases behind, I move up one major version at a time. Each release has its own list of breaking changes. A small step is easier to test, so I can check the app after every step.

  • Old packages

    Packages are often the slowest part of an upgrade. I update the ones that have a newer release and look for a replacement for the ones that nobody maintains. I tell you what I replace and why.

  • Your key flows

    After each step I check the parts of the app that cost you money when they fail: login, payments and queues. I run your existing tests if you have them. I also tell you about anything I could not test.

  • What I need from you

    A way to read your code (a GitHub or GitLab invite, or a zip file), your current Laravel and PHP versions, and the flows that matter most. A staging copy of the app helps. I do not need live passwords or keys for the code work.

  • What is not included

    New features, a redesign, and rewrites of code that works fine are not part of these packages. I point out other problems I see, and we can agree them separately. A second app needs its own package.

Packages

Pick a package

Fixed price in US dollars. Each package lists what is included.

Upgrade audit and plan

$350

3 days · 1 revision

You want to know the size of the job before you commit to it.

  • Review of your code, packages and hosting
  • Written list of what will break and why
  • Step-by-step upgrade plan in the right order

One app upgraded

$1,200

10 days · 2 revisions

One app needs to reach the latest version and keep working.

  • Upgrade of one Laravel app to the latest version
  • Fixes for deprecated and broken code
  • List of what changed, for your team

Upgrade plus handover

$2,800

21 days · 3 revisions

The app is critical, and you want package fixes, deploy checks and notes for the next developer.

  • Full upgrade of your app
  • Package fixes: old packages updated or replaced
  • Checks of your deploy steps, so the new version goes live safely
  • Handover guide for your team

Process

How it works

  1. Step 1

    You send access

    You give me read access to the code and tell me your current versions and the flows that matter most.

  2. Step 2

    I audit the app

    I check code, packages and hosting. You get the findings and the order of work.

  3. Step 3

    I upgrade in steps

    I move up one version at a time, fix what breaks, and check your key flows after each step.

  4. Step 4

    You get the result

    You receive the upgraded code, a clear list of what changed, and notes for your team.

Proof

Related work and reading

FAQ

Questions about this project

The latest major release at the time we start, together with a PHP version that release supports. If your app is several versions behind, I go up one version at a time and check it after each step.

The first is a written audit and plan, with no code changes. The second is the upgrade itself, with fixes, for one app. The third adds package fixes, deploy checks and a handover guide for your team. Send me your repository and versions, and I will tell you which package fits.

I do not change your live app while I work. I work on a separate copy of your code, so your live app is not touched until you release. The release is the risky moment, so the largest package includes deploy checks. I suggest releasing at a quiet hour for your users.

Yes, to a version that your new Laravel release supports. Each Laravel release lists the PHP versions it works with, and the support policy sets how long it gets fixes. I check your hosting for the PHP version and tell you what must change on the server.

I look for a maintained replacement and tell you what changes for your app before I swap it. If there is no good replacement, I list the options, such as a small patch or a rewrite of that part. You choose which way to go.

A tool helps with the mechanical changes, but it does not replace testing. The Laravel docs point to Shift, a community-run service that automates upgrades. A tool changes code by fixed rules. It does not know what your billing or login must still do afterwards. I check that part.

Yes. I have been the only engineer on one client platform since 2016, and I am now moving it to Laravel 13 while the business keeps running. The case study describes the system. Long-lived apps are where upgrades break, because old code and old packages pile up.

Need something different?

If your work does not fit these packages, tell me what you need and I will reply with a plan.

More projects

From $300

Laravel performance

Find why your Laravel app is slow, fix the biggest causes, and measure the result.

  • Measured before and after
  • N+1, indexes, cache, queues
  • Written, ranked fix plan

From $300

HubSpot integration

Contacts, companies and deals kept in step between Laravel and HubSpot.

  • Two-way sync with retries
  • Failed records logged and retried
  • Code in your repository

From $250

Stripe integration

Checkout, subscriptions and webhooks that keep your records in step with Stripe.

  • Verified, queued webhooks
  • Duplicate events handled
  • Code in your repository

See all services