The developer left and nobody knows how the software works
It happens more than you think: the person who built or maintained your application retires, changes jobs or stops answering, and nobody else knows how it works. It is not the end. A few ordered steps in the first days prevent data loss and let you regain control of the software.
What to do in the first 48 hours
Do not touch what works
Do not reinstall, do not update the server or the Windows it runs on, and do not move the program to another machine until you have copies.
Copy everything, twice
The application folder, the database and the configuration files, on an external disk and in the cloud, with the date in the name.
Gather the access
Passwords for the server, the database, the hosting, the domain and the cloud accounts. Note who holds each one.
Look for the source code
On the developer's machine, in repositories (GitHub, GitLab, Bitbucket), in old copies, in emails or by asking the previous vendor.
Review contracts and ownership
Check whether the software belongs to the company and whether any contract requires handing over the code and documentation.
Write down what the program does
Which processes depend on it, who uses it, which automatic tasks it performs (closings, invoices, exports) and on which dates.
Identify the technology
Analyse the executable with the free analyser to find out what it is built with and whether its code is recoverable.
Decide with a plan
Maintain, stabilise or migrate. The worst thing is to make blind changes to a system nobody understands.
Signs that it is urgent
There is no backup
If the machine or server fails, everything is lost.
It runs on a single machine
An old PC or server the whole company depends on.
Errors are starting to appear
And nobody knows whether they come from the program, the data or the machine.
A mandatory change is coming
A regulatory, tax or system change that forces the program to be modified.
Nobody has the passwords
Neither for the server nor for the database.
It has to be integrated with something new
An ERP, an online shop or e-invoicing.
How I help
Quick assessment
An inventory of what exists, the risks and what can be recovered.
Recover the code
If only the executable is left, we reconstruct the logic when the technology allows it.
Stabilise and document
Backups, organised access and documentation so you never depend on a single person again.
Maintain or migrate
Keep going safely with what you have or move to current technology, in phases.
If the former developer or vendor does not hand over the code, ownership and contracts are key: consult a lawyer. We only work on software the company owns or has the right to act on.
Frequently asked questions when the developer leaves
Can we keep using the program in the meantime?
Yes, as long as it works and you have recent copies. The important thing is not to make changes to the machine it runs on until you have a plan.
What if the former developer will not hand over the code?
It depends on the contracts and on who owns the software, and you should consult a lawyer. Meanwhile, if the company is the owner, recovering the logic from the executable can be considered.
How long does it take to regain control?
An initial assessment usually takes a few days. From there it depends on the size of the application and on what can be recovered.
What if the program stops working before then?
With copies of the folder and the database you can almost always get it running again on another machine. That is why the first step is to copy everything.
Related
Contact
Email: jmoreno@stellariscode.com · Phone: +34 654 51 63 65