Upgrade inventory
PHP, Laravel, Composer package, extension, and deployment inventory, including abandoned or pinned dependencies that block the target version.
The Laravel upgrade keeps slipping. The old PHP version keeps running.
An unsupported runtime is not just a version number. Composer conflicts, abandoned packages, missing tests, and deployment assumptions turn a small bump into a risk the team cannot schedule. We assess the real upgrade path, then run a scoped sprint from it.
Fees
Assessment$1,000
Upgrade sprintfrom $6,000
The assessment fee is credited toward the matching approved sprint. You get a written scope and quote after the assessment; work starts only after you approve it.
Prices are in USD. The sprint is quoted from the assessment findings; the amount shown is the starting point, not a fixed total.
Every month on the old runtime makes the next upgrade larger.
Security patches stop, hosting providers move on, and new packages assume a runtime you do not have. The team knows the upgrade is needed; what it does not have is a credible view of what will break, what must be replaced, and how to get through it without freezing feature work.
A version bump is the smallest part
Framework upgrades, PHP behavior changes, Composer constraints, and custom patches travel together. Missing one turns the release into a production surprise.
Tests that do not exist cannot catch regressions
If the app has thin coverage, the upgrade plan has to include how the important flows will be checked before and after the cutover.
Deployment assumptions surface late
Queue workers, cron jobs, PHP extensions, and hosting configuration can fail after the code passes locally.
What you get
An upgrade plan grounded in the repository, not a generic estimate.
The assessment is a fixed-fee first step. The sprint is scoped from the evidence it produces.
Risk map
The changes that are mechanical, the ones that need code work, and the ones that need a product decision. Each has evidence, not a generic estimate.
Step plan and quote
A proposed upgrade path with checkpoints and acceptance checks, then a fixed scope for the sprint. The $1,000 assessment is credited toward it.
Scoped upgrade sprint
Dependency and framework changes, compatibility fixes, regression coverage for agreed flows, and a staged cutover with rollback notes.
What this is not
The assessment is meant to expose the real work before anyone commits to a date. These items stay outside the sprint unless they are separately scoped.
- A feature roadmap or unrelated product work.
- Rewriting custom packages from scratch unless scoped separately.
- Hosting migration, new infrastructure, or vendor contract changes.
- A guarantee of zero downtime or a fixed calendar duration before the assessment.
- Every PHP framework; the sprint is scoped to the Laravel/PHP application assessed.
How it works
Assess the path, then move the application.
You approve the written scope and quote before the upgrade sprint begins.
- 1
Intake
You tell us the current versions, the target if you have one, the business impact, and the deadline. Do not send credentials through this form.
- 2
Inventory and reproduce
We inspect the repository and dependency metadata through the access process you approve, then identify the blockers that actually affect the target versions.
- 3
Plan and quote
You get the upgrade path, the risk map, the regression checks, and a written quote. The assessment fee is credited toward the approved sprint.
- 4
Upgrade and verify
We make the approved changes, run the agreed checks, and document the cutover and rollback. Remaining risks are handed over explicitly.
Requirement
The assessment starts with evidence.
We inspect the repository and dependency metadata through the access process you approve. Do not send credentials, secrets, or production data through this form.
Related rescue services
PostgreSQL performance
Diagnose slow queries, lock contention, and unstable load before changing production.
View service →Security remediation
Turn a confirmed finding into a scoped fix, with verification and an independent review before completion.
View service →Cloud cost optimization
Find the cost drivers in your cloud bill before changing infrastructure. Qualification first, implementation only where the evidence supports it.
View service →Questions about PHP and Laravel upgrades.
Do you upgrade Laravel across major versions?
Yes, when the assessment shows a workable path. The exact source and target versions are part of the assessment; we do not quote a major upgrade blind.
What if we have no tests?
We will not pretend the tests exist. The plan includes the smallest regression checks for the flows that matter, and we agree those before the sprint.
What happens with abandoned packages?
We identify them in the assessment and give options: replace, pin, patch, or remove. Replacing a package can become a separate scope.
Is $6,000 the total?
No. It is the starting point for the upgrade sprint. The assessment produces the scope and written quote; the $1,000 is credited toward the approved sprint.
Will features change?
No. The sprint is for the upgrade. Behavior changes and new features are separate work.
Can you work alongside our team?
Yes. The scope names who changes what, and the handover notes go to whoever maintains the application.
PHP and Laravel upgrades
Is the old runtime holding the roadmap hostage?
Send the current PHP and Laravel versions, the target if you have one, and the deadline. We will reply with the assessment next step.