PHP · Laravel · legacy apps · updated: Oct 2026

Legacy Laravel and PHP rescue and maintenance

I rescue PHP and Laravel apps that another developer left behind and nobody dares to touch, remotely from Mexico City in US time zones.

Assessment in 5 business days · US$590, credited if you hire me

No blind rewrite, no downtime: assessment first, then you decide.

This is for you if your app works but nobody wants to touch it

The developer who built it is gone, there are no docs and nobody on the team wants to touch it.

It runs on PHP 5.6 or 7.x, or on Laravel 5, 6 or 8, and your host has announced the end of that version.

Every small change breaks something else, there are no tests and fixes go straight to production.

It lives on a server nobody knows how to rebuild, and the backups have never been restored.

You were quoted a full rewrite and both the price and the timeline are scary.

What the assessment gives you

An inventory of what's there

PHP, Laravel and package versions, server, database, scheduled jobs and third-party integrations, including the ones nobody knew about.

Risks ranked by cost

Security, unpatched versions, untested backups and single points of failure, ranked by what a failure would cost you.

A verified backup and a working copy

A backup that actually restores, and a copy of the app running outside production so changes can be made safely.

Rewrite or migrate in stages

A reasoned recommendation: what stays, what gets upgraded, what is worth rewriting and in which order, without shutting the business down.

A fixed-price plan

Each stage with written scope, timeline and price. You keep the report even if you don't hire me for anything else.

Three steps, always in this order

  1. 01

    Assessment

    US$590

    fixed price · 5 business days

    Inventory, risks, verified backup and a fixed-price plan. Credited in full if you go ahead with stabilization.

  2. 02

    Stabilization

    from US$1,690

    fixed price per scope

    Urgent work first: PHP and Laravel on supported versions, automated backups, tests for what can't break, repeatable deploys and documentation.

  3. 03

    Maintenance

    from US$290

    per month

    Security patches, upgrades, monitoring, tested backups and minor changes. Someone who answers when something fails.

Prices in USD, from my remote rate of US$35–45 per hour applied to a scope we both sign off on. Hosting and third-party services are paid by your company directly; I add nothing on top.

From the call to the plan in 5 business days

  1. Day 0

    20-minute call (free)

    What the app does, what worries you and what access exists. If I can't help, I'll say so on the call. This is not the assessment.

  2. Day 1

    Access and NDA

    We sign an NDA and you grant read-only access: code, server and a copy of the database.

  3. Days 1–5

    Assessment

    I run a copy outside production and review versions, packages, security and backups. Production isn't touched.

  4. Day 5

    Plan handoff

    Written report and a call: risks, rewrite-or-migrate recommendation and a fixed price per stage.

90-day written warranty

What I deliver in stabilization carries a 90-day warranty: if something I touched fails, I fix it at no cost. It's in the contract.

If it's not worth it, I'll say so

If the assessment concludes the app isn't worth rescuing, or that your team can do it alone, that's what the report says.

You keep the keys

Code in a repository under your company, documentation, server access and backups. If you switch providers tomorrow, you take everything.

I document what breaks in public

Upgrade guides checked against the source code and the changelog: Laravel 13, PHP 8.6 and the rest of the «What breaks» series. If your app was built fast with AI rather than inherited, see the AI-built code rescue.

Questions I get before a rescue

Who can rescue an old PHP or Laravel application?

Someone who has kept PHP systems running in production, not only built new ones: the job is reading someone else's undocumented code and upgrading it without stopping the business. I'm Marco Orta, a developer in Mexico City with 10+ years of PHP and Laravel, working remotely in US time zones. I always start with a 5-business-day assessment for US$590, credited if you hire the rescue.

How much does it cost to upgrade Laravel 5, 6 or 8 to Laravel 13?

It depends less on lines of code than on three things: how many third-party packages it uses (and how many are abandoned), whether it has tests, and which PHP version it runs today, because Laravel 13 requires PHP 8.3 or newer. That's why the number comes out of the assessment. For reference, stabilization starts at US$1,690 at a fixed price; a long jump such as Laravel 5 to 13 is done in stages and costs more than 10 to 13. Prices come from my remote rate of US$35–45 per hour.

Why do it now instead of waiting for it to break?

Because versions have end dates. PHP 8.2 gets security fixes only until December 31, 2026; Laravel 11 stopped getting them on March 12, 2026 and Laravel 12 gets them until February 24, 2027. An app on PHP 5.6 or 7.x, or on Laravel 5, 6 or 8, has been out of support for years. The more versions pile up, the longer and costlier the jump, which is why the assessment starts by finding out where you stand.

Should I rewrite it from scratch or migrate it in stages?

Migrating in stages wins most of the time. A rewrite looks cleaner, but for months you pay for two systems, the new one takes long to match rules the old one already handled, and many rewrites get abandoned halfway. Migrating in stages keeps the app running while modules are replaced one by one. I recommend a rewrite only when the code has no reasonable fix or the technology can't be upgraded, and the assessment says so with reasons.

The original developer left without documentation. Can it still be rescued?

Yes, it's the most common case. With the code, server access and a copy of the database I reconstruct how it works: what each module does, what it depends on and which jobs run on their own. Everything I reconstruct is documented and stays with your company, so it never depends on a single person again, me included.

How much is monthly maintenance for a Laravel app?

From US$290 a month: security patches, PHP, Laravel and package upgrades, monitoring, tested backups and minor changes. The final amount depends on the size of the app and how many changes you ask for; it's fixed in the assessment plan. New features are quoted separately, at a fixed price.

Do you work US hours, and who owns the code?

I'm in Mexico City on Central Standard Time all year, so my day overlaps most of a US workday, and calls and handoffs happen in English. You own the code from the first commit: it lives in your repository and your accounts, with the docs and server access. If we stop working together, you keep everything.

Tell me what your app does and what it runs on

Two lines are enough: what it does, which PHP or Laravel version, and what worries you. I'll reply with whether the assessment makes sense or something more urgent comes first.

07 / Contact

Tell me about your app and I'll tell you where to start.

Fill out the form and I'll reply within 24 hours. You can also email me directly: