← All dispatches
Laravel8 Oct 2026 · 4 min read

Our Laravel Developer Has Left. What Should We Do First?

Your developer has gone and the application still runs the business. What to do in the first week, in the right order.

▲ SHIFT UP

Your Laravel developer has gone. Maybe they took a full-time job, maybe the agency that built the system folded, maybe they've just stopped answering emails. The application still runs the business, and now nobody knows how it works.

This happens a lot more than people think, and it's usually less of a disaster than it feels in the first week. But the order you do things in matters. Here's what I'd do, roughly in this order.

1. Secure access before anything else

Before you worry about the code, make sure you can actually get to it. Make a list and tick each one off:

  • The code repository. GitHub, GitLab or Bitbucket. Is it in your company's account, or the developer's personal one?
  • The server or hosting account. Forge, Ploi, a VPS, Cloudways, AWS. Who's the account owner?
  • The database. Can someone log in, and is it being backed up?
  • The domain and DNS. Registrar login, and where the DNS is hosted (often Cloudflare).
  • Email sending. Mailgun, Postmark, SES or similar.
  • Every third-party service the app talks to: payment providers, accounting software, APIs.

If any of these sit in the old developer's personal accounts, ask for them to be transferred now, while they're still replying. It's a polite, reasonable request, and it's much harder six months later. If you've lost contact completely, most providers have an ownership recovery process if you can prove the business is yours.

The website takeover checklist builds this list from your site's domain and DNS records, so you can see who holds what.

2. Don't change anything yet

The instinct is to fix whatever's annoying people. Resist it for a few days.

Inherited Laravel systems often have quirks that the business depends on without realising. A scheduled job that tidies up data every night. A queue worker that sends invoices. A bit of code edited directly on the server and never committed. Change the wrong thing and something important quietly stops.

3. Take a proper backup

A full copy of the database, the code exactly as it runs on the server (not just what's in the repository), the .env file and any uploaded files in storage. Keep it somewhere that isn't the same server.

If something goes wrong in the next few months, this is what gets you out of it.

4. Find out what you're running

A developer can tell you this in an hour:

  • Which Laravel and PHP versions it uses, and whether they still get security fixes
  • Whether the code on the server matches the repository
  • What runs on a schedule, and whether the scheduler is actually running
  • What queues and workers it relies on
  • What's in the error logs

If you're comfortable on the command line, paste the output of php artisan about into the Laravel version checker and it'll show what's out of support. The .env checker flags risky settings like debug mode left on, without the file leaving your browser.

5. Get it documented

The real problem with a developer leaving isn't the code. It's that the knowledge left with them. So the first piece of work should produce a short written document covering:

  • How it's hosted and deployed
  • What the scheduled jobs and queues do
  • Which external services it depends on
  • The known problems, ranked by risk
  • What it would take to bring it up to date

That document is useful whoever works on it next, whether that's me, another freelancer or an agency.

6. Decide: maintain, upgrade or rebuild

Once you understand what you've got, there are three realistic options.

Maintain it as it is. If it's on a supported Laravel version and works well, the cheapest answer is often a small monthly support arrangement: someone who knows the system, keeps it patched and fixes things when they break.

Upgrade it. If it's on an old version, it can usually be brought up to date in stages without rewriting it. That's normally far cheaper than people expect, and you keep everything that already works.

Rebuild it. Occasionally the honest answer is that it's cheaper to start again. That's rare. Most systems that feel like a mess are fixable, and a rebuild throws away years of business rules that someone has to rediscover.

What this usually costs

A focused review of an inherited Laravel application, with a written report and a plan, is a fixed fee, and on my own work it starts at £295, credited against any follow-on work booked within 30 days. Ongoing support is quoted to fit, from a few hours a month upwards.

If you're in this position now

Taking over Laravel applications from other developers is most of what I do, and I've seen the same patterns many times. If your developer has gone and you need someone to work out what you've got, have a look at Laravel rescue or get in touch with a short description of the system. I'll tell you honestly whether it needs a rescue or just a bit of looking after.

Stuck with something like this?

I take on the awkward Laravel, WooCommerce and tracking problems.

Tell me what's broken