All posts

Your developer has moved on. Here's how to take back control of your software

When the person who built your software leaves, the risk isn't just bugs. It's lost logins, untested backups and code nobody understands. A practical checklist to get back in control.

It happens to a lot of businesses. The freelancer who built your system takes a full-time job. The agency stops replying. The one person on your team who understood the database leaves.

Everything still works, for now. But nobody is quite sure how, and that's a risk worth dealing with before something goes wrong.

Step 1: Get the keys back

Before anything else, make sure your business controls every account the software depends on. Make a list and check each one:

  • Code repository (GitHub, GitLab, Bitbucket): is it under your organisation, or someone's personal account?
  • Hosting (AWS, Azure, Google Cloud, a hosting provider): who's the account owner and who gets the bills?
  • Domain name and DNS: registered to your business, with renewal set up?
  • Database: can you access it, and who has admin rights?
  • Third-party services: email sending, payments, maps, AI APIs, analytics.
  • App store accounts if you have a mobile app.

Step 2: Check the backups actually work

Many businesses believe they have backups. Fewer have tested restoring one. Ask for a test restore to a separate environment. If it works, you've confirmed your safety net. If it doesn't, you've found the most important problem on the list.

Step 3: Look at security updates

Software depends on frameworks and libraries that receive security fixes. If nothing has been updated in a year or more, there's likely work to do. Outdated dependencies are one of the most common ways small business systems get compromised.

Step 4: Get an honest review

A read-only health check of the code and hosting tells you what you're dealing with:

FindingWhat it usually means
Clean, documented, tested codeEasy to maintain and improve
Working but messy codeMaintain, and tidy up gradually
Fragile code that breaks with every changeRebuild the weakest parts first
Unsupported technologyPlan a migration before it becomes urgent

Most systems land somewhere in the middle. The point is to know, so you can make decisions calmly rather than in an emergency.

Step 5: Decide how it'll be looked after

You have three realistic options: hire someone in-house, find another freelancer, or put the system on a maintenance retainer with a team that knows it. Whichever you choose, insist on documentation, everything in your name, and direct access to the person doing the work.

This is exactly what our software maintenance service is for: a health check first, a careful handover, then steady monthly improvements.

Common questions

What if we can't get access to the hosting account?

Start with the hosting provider's ownership-recovery process, using proof that your business pays the bills. It's slower than a friendly handover, but it's usually possible.

Do we need to rebuild everything?

Rarely. Most systems can be stabilised and improved in place. A rebuild only makes sense where part of the system genuinely can't be maintained.

How long does a handover take?

Getting access and backups sorted can often be done within a few weeks. Ongoing improvements continue from there at whatever pace suits you.

Can you take over software someone else built?

Yes, that's a common starting point for us. Tell us what you've got and what worries you about it.

Want this looked at for your business?

A short call, no pitch. Tell us how things run today and we'll tell you honestly what's worth doing first.