To take over an abandoned software project: secure access to code, servers and accounts, back everything up, run it on a safe copy, list problems by risk, decide whether to fix, finish or rebuild, stabilize first, and document as you go.
In this article
1. Secure access first
Before anything else, collect everything the project touches: the source code repository, the server or hosting account, the database, domain and DNS, and any third-party accounts such as payments, email and analytics. Move ownership of these accounts to you. If you cannot get the source code, ask for a copy of the deployed application and a database backup.
2. Make a safe copy
Take a full backup of the code, the database and the uploaded files before anyone changes anything. Store it somewhere you control.
3. Run it and see what is really there
An engineer should get the project running on a separate environment. This shows what works, what is broken and what is missing. It also reveals hidden problems such as outdated libraries, hard-coded passwords or missing configuration.
4. List the problems by risk
Not everything needs fixing at once. Sort the findings into three groups:
- Critical: security holes, data loss risks and anything that stops the app from working.
- Important: bugs that hurt users or block new features.
- Later: cleanup, style and nice-to-have improvements.
5. Decide: fix, finish or rebuild
Most projects do not need a full rewrite. A useful rule of thumb: if the core design is sound and the code can be understood, fix and finish it. If the foundation is unsafe or so tangled that every change breaks something else, rebuild the weak parts, or all of it, in small steps.
6. Stabilize before adding features
Fix the critical issues, set up backups and a repeatable deployment, and add basic tests around the main features. Only then continue building. This keeps you from stacking new work on a shaky base.
7. Document as you go
Write down how to run, test and deploy the project, and where each account and secret lives. This is what protects you the next time a developer leaves.
Not sure what state your project is in? Our free assessment gives you a plain-English report of what works, what is risky and what we would do first.
Related solutions
- Abandoned project takeover: The developer stopped replying, the agency closed, or the project simply ran out of steam. We take over the code, the servers and the plan, and get you moving again.
- Finish an unfinished app: You paid for something that stopped at 60%. We work out what is really done, what is missing, and the fastest safe way to launch.
- Move off an old developer's server: If your software runs on a server or account you do not control, we move it to hosting that is yours, safely and with documentation.
Prefer a quick answer? Try the free fix-or-rebuild self-check.