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
Fixed-price project
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.
Who it is for
Signs
Scope
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.
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.
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.
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.
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.
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
Fixed price in US dollars. Each package lists what is included.
$350
3 days · 1 revision
You want to know the size of the job before you commit to it.
$1,200
10 days · 2 revisions
One app needs to reach the latest version and keep working.
$2,800
21 days · 3 revisions
The app is critical, and you want package fixes, deploy checks and notes for the next developer.
Process
Step 1
You give me read access to the code and tell me your current versions and the flows that matter most.
Step 2
I check code, packages and hosting. You get the findings and the order of work.
Step 3
I move up one version at a time, fix what breaks, and check your key flows after each step.
Step 4
You receive the upgraded code, a clear list of what changed, and notes for your team.
Proof
Case study
Global Express Limited is a Caribbean freight-forwarding and virtual mailbox business. Customers across Barbados, the Cayman Islands, Guyana...
Article
Article
FAQ
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.
If your work does not fit these packages, tell me what you need and I will reply with a plan.
More projects
From $300
Find why your Laravel app is slow, fix the biggest causes, and measure the result.
From $300
Contacts, companies and deals kept in step between Laravel and HubSpot.
From $250
Checkout, subscriptions and webhooks that keep your records in step with Stripe.