Taking over a system from another developer: how to do it safely
The developer ended the cooperation, the programmer left the company, or contact simply stopped. The system is still needed, and nobody knows exactly how it works. It is a difficult situation, but a manageable one.
Step 1: secure access
- source code and repository,
- servers, hosting and domains,
- databases and backups,
- accounts in external services: email, payments, maps, calendars.
Without this access, every next step is guesswork. If some of it is registered to the previous developer, transfer it to the company as soon as possible.
Step 2: back up everything
Before anyone changes anything, make a full copy of the code and data, and check that the system can actually be restored from it.
Step 3: assess the state of the system
- whether the system can be started in a new environment,
- how outdated the libraries and the server are,
- whether documentation and tests exist,
- which parts are most critical for the company,
- where the known bugs and workarounds are.
Step 4: set priorities
Security and stability first, then fixes, and development only at the end. It is tempting to start adding new features straight away, but until the basics are in order, every change carries risk.
Rewrite from scratch or keep developing?
Rewriting a system from scratch is rarely the best first step. It is usually safer to stabilise what works and gradually replace the weakest parts. The decision to rebuild is best made only after the system has been assessed.
For the future
After the takeover, make sure the situation does not happen again: access registered to the company, documentation, backups and a maintenance contract. If you are taking over a system from another developer, book a consultation.
Have a question on this topic? Let’s talk →