Skip to content
Shahid Malla

Laravel Web Apps

Laravel Version Upgrade

Move an older Laravel app to the current release, one supported version at a time, with tests run at each step.

Shahid Malla

Shahid Malla · Top Rated on Fiverr and Upwork
600+ Fiverr reviews, 4.9 average · 13+ years · 900+ projects

LaravelPHP 8Composer

About this package

This package upgrades an older Laravel app, stuck on Laravel 6, 7, 8 or 9 or even 5.x on Premium, to a supported release that receives security fixes again and runs on a current PHP version. Apps in that state usually block a server PHP upgrade, fail new security scans, or cannot install the package a new feature needs.

The upgrade path

I upgrade one major version at a time, following the official upgrade guide for each, because jumping straight to the latest release hides which change broke what. At each step Composer dependencies are updated, deprecated calls replaced, and the tests run before moving on. Business and Premium also replace abandoned packages with maintained ones and bring config and route files up to the current structure.

  • If the app has no tests, I first write smoke tests for login and the main pages, so there is a baseline to compare against.
  • Every breaking change I handle is written down with the file it touched, on Business and Premium.
  • Premium moves the frontend build from Laravel Mix to Vite and adds feature tests for your main flows.

Keeping the live app safe

All work happens on its own branch in your repository. On Business and Premium the upgraded version runs on staging for you to click through with real accounts, while your live app keeps serving users. Premium includes the production release itself with a written rollback plan, plus two weeks of fixes afterwards.

Acceptance

The upgrade is complete when composer audit is clean or every remaining advisory is explained, the test suite passes on the new versions, and you confirm the pages on your own checklist behave as before. New features and redesigns are separate work; this package keeps behavior the same on newer foundations.

Compare packages

Package Starter$349 Business$899 Premium$1,899
Major versions upgraded 1Up to 3From 5.x to current
Composer dependencies updated
Smoke tests for key pages
PHP version upgrade –
Abandoned packages replaced –
Staging copy for your review –
Mix to Vite migration ––
Production release and rollback ––
Fixes after release ––2 weeks
Delivery time 5 days10 days20 days
Revisions 235

What I need from you

After you pay, a project opens for your order. Send these there and the delivery clock starts.

  • Repository access and the branch that runs in production
  • Your current composer.json and composer.lock
  • The .env file with production secrets removed
  • A database dump with personal data anonymized
  • How you deploy today and where the server is hosted
  • Test logins for each user role

About the developer

Shahid Malla

Shahid Malla

AI agent and AI chat developer, full-stack developer

Top Rated on Fiverr and Upwork

Based in
Kashmir, India
Experience
13+ years
Projects
900+ delivered
Languages
English, Hindi

I have built websites, WHMCS modules and web apps for clients since before AI coding tools existed. Today I build with AI-assisted tools and review every change myself, which is why fixed prices here are lower than an agency's for the same scope. I work while the US, Canada and Australia sleep, so each morning there is progress on your staging link.

Read my 600+ Fiverr reviews · Upwork profile · Portfolio · About me

Questions about this package

What if a package I depend on has no version for the new Laravel?

I check this before starting, using the package's release history and issues. Usually there is a maintained fork or a replacement with a similar API, and on Business and Premium the swap is part of the work. If a package has no path forward at all, I tell you up front and quote the rewrite separately.

Will my site go offline during the upgrade?

No. The upgrade happens on a branch and a staging copy, and your live app keeps running untouched. Only the final release touches production, which on Premium I do with a tested rollback, at a time you choose when traffic is low.

Why not jump straight to the newest Laravel version?

Because each major release has its own breaking changes, and stacking several at once makes it hard to see which one caused a failure. Stepping through versions, with tests at each step, is slower on paper and faster in practice, since problems are found and fixed in small pieces.

How ordering a package works

  1. 1

    Choose a plan

    Pick Starter, Business or Premium and pay once by card, PayPal or crypto. The price on the page is the price.

  2. 2

    Send your content

    A project opens for your order. Send your text, logo, photos and any logins I need there.

  3. 3

    I build it

    I build on a private staging link you can open on your phone, with updates as I go.

  4. 4

    Launch and handover

    After your approval the site goes live on your domain, and every login is yours.

One-time price, no monthly fee from me

You pay for the build once. Your domain and hosting are registered in your name and renewed with your hosting provider, who bills you directly. I add nothing on top, and the site keeps running whether or not you hire me again.

What I do not build

Gambling and adult websites, and sites that sell content without the rights to it. Need something not listed? Ask for a custom quote.

All laravel web apps · All package categories