Taking over software from a previous developer: a checklist
A handover checklist for inheriting a website or system: access, code ownership, hosting, backups, documentation and a risk review before you change anything.
By AM-IT Solution · Published · 4 min read

In short
Secure access first: domain, hosting, source code, database and third-party accounts should all be in your name or your control. Then confirm who owns the code, get a working backup, and review the system for risk before changing anything. Do not start new features until you know how the system is built, where it runs and whether it can be restored.
Inheriting a website or business system is rarely a clean handover. The developer may have moved on, a freelancer may have stopped replying, or an agency relationship may have ended badly. Whatever the reason, the risk is the same: you depend on software you cannot fully see. This checklist puts the order of work right, so you secure what matters before you change anything.
What access should you secure first?
Make a list of every account the system touches and check who is the owner of each one. In many inherited projects, the previous developer is the registered owner of something important.
- Domain registrar and DNS, including where email records are managed.
- Hosting or cloud account, and any deployment platform.
- Source code repository, with the full history if it exists.
- Database, file storage and backup storage.
- Email-sending service, payment provider, analytics and any other third-party service the system calls.
- Licences and subscriptions for paid tools or plugins.
- Administrator accounts inside the application itself.
Where an account is in the developer’s name, ask for it to be transferred to you or add you as an owner. Do this early, while the relationship is still cooperative. Change shared passwords afterwards and use individual logins from then on.
Who owns the code?
Do not assume you do. In the UK, the person who creates a work is normally its first owner. GOV.UK guidance on commissioned work says the first owner of copyright is the creator and not the commissioner, unless it is agreed otherwise in writing, and that a freelancer will usually keep copyright unless a contract says differently. A commissioner without a written agreement may only have an implied licence to use the work for its original purpose.
So look for the original contract or statement of work. Check whether it assigns ownership to you, grants a licence, or says nothing. If it says nothing, ask the developer to confirm in writing what you may do with the code, including modifying it and passing it to another developer. This is a legal question for your own adviser rather than something to settle by assumption.
What should you check about hosting and backups?
- Where does the system run, and who pays for it? Find the invoices.
- Is there a backup of the database and uploaded files? When was the last one taken?
- Has a restore ever been tested? A backup that has never been restored is an assumption, not a safeguard.
- Are the server, runtime and framework versions still supported by their makers?
- Is there a staging copy, or is everything changed live?
- Where are secrets such as API keys and database passwords kept, and who can read them?
Take your own copy of the code, the database and the files before anyone changes anything, and store it somewhere you control. That copy is your starting point if a later change goes wrong.
What documentation do you need, and what if there is none?
Ask for whatever exists: setup notes, architecture diagrams, a list of integrations, scheduled jobs, deployment steps and known problems. Much of it is often missing. When it is, the first piece of work is to write it as you learn the system, which is part of what a takeover review produces: how it is built, how it is deployed, what depends on what and what would break if a component stopped working.
How do you review the system for risk?
Before planning improvements, assess what you have. A useful review covers:
- Security: outdated dependencies, exposed credentials, weak access controls, unprotected admin pages.
- Reliability: error handling, monitoring, what happens when a third-party service is unavailable.
- Data: where personal or financial data is stored, who can reach it and how it is backed up.
- Maintainability: whether the code is understandable, tested and consistent enough for someone new to change safely.
- Fit: whether the system still matches how the organisation works, or is being held together with workarounds.
The outcome should be a ranked list: what must be fixed now, what can wait and what is not worth touching. Sometimes the finding is that a rebuild would cost less than years of repairs, but you should see that as a conclusion supported by the review, not a starting assumption.
How does AM-IT handle a takeover?
Our system takeover service audits the code and hosting, documents how the system works and stabilises it, then supports it or advises whether to improve or replace it. Hosting management and essential maintenance keep it supported afterwards, and a paid discovery from £750 can scope what comes next. If the review points to moving data to a new system, our data migration checklist shows how that is done safely.
Common questions
What if the previous developer will not cooperate?
Start with what you can prove: invoices, contracts and your own admin access. Registrars and hosting providers have their own processes for confirming account ownership. For disputes about the code itself, take legal advice.
Can a new developer work without documentation?
Yes, but it takes longer and costs more at the start. Reading the code, the database and the live behaviour is how a missing manual gets written.
Should we change anything straight away?
Only security fixes that cannot wait. Secure access, take a backup and review the system first, then plan changes in small steps.