How to take over a web project abandoned by a former developer?
The developer no longer answers, the website shows an error and nobody knows where the code is. The situation is more common than you might think. It can almost always be resolved, provided you proceed in the right order.
1. Recover access
First of all, list and recover: domain name, hosting, database, code repository, accounts for third-party services (payment, email, APIs). The domain name comes first: if it is in the former provider’s name, have it transferred to yours.
2. Back up and secure
Make a full backup of the files and the database before touching anything. Then change all passwords and remove the former developer’s access. Check that no known vulnerability is being exploited.
3. Audit the code
- versions of the language, framework and dependencies;
- presence of tests and documentation;
- changes made directly on the server;
- fragile or poorly understood parts.
4. Decide: fix, take over or rebuild
A full rebuild is rarely the best first decision: you lose business rules that are invisible in the code. Most often, you stabilise first, then modernise piece by piece. A complete rebuild is justified when the technology is no longer maintained or every change breaks something else. See our migration and upgrade page.
5. Prevent it from happening again
Require the code to be in a repository in your name, access to be documented and code ownership to be written into the contract. A maintenance contract also ensures a project is never left without anyone watching over it.
A project to take over?
Tell us what still works and what is blocked: we will start by securing it.