Taking over a website from another developer is one of the riskiest moments in the life of a business website. The previous developer may be unreachable, the code may have few notes, and the site may still be live and taking orders. The safe approach is to check access, back up everything, and understand the system before you change a single line.
Step one: secure access before anything else
Most handover problems start with accounts. Before you look at the code, make a list of every place the website or app lives and who controls it. Common places include:
- The domain registrar, where the domain name is registered
- The hosting account and any server or cloud dashboard
- The code repository, such as GitHub or GitLab
- The database and any file storage
- Payment gateways, email services, and analytics tools
- Third-party plugins, APIs, and app store developer accounts
For each one, confirm that the account is registered in your business name or an email address you control. If the previous developer set up accounts under their own email, ask them to transfer ownership now, while they are still reachable. Remove access for people who no longer work with you, and turn on two-factor authentication wherever it is offered.
Make a full backup before you touch anything
Before you make any change, take a complete copy of the live site: the code, the database, uploaded files, and configuration. Store the copy somewhere separate from the hosting account. A backup you cannot restore is not a backup, so test the restore on a separate environment if you can. Our guide on website backup for small business explains a simple routine you can keep afterwards.
Map the stack and what it depends on
Next, find out what the website is built with. You need to know the language, the framework, the database, and the hosting setup. Look for a file that lists dependencies, such as package.json for JavaScript projects, composer.json for PHP, or pubspec.yaml for Flutter apps. Note the versions. Old frameworks and libraries that no longer receive security updates are a common source of trouble.
Also check for things that are easy to forget:
- Environment variables and secret keys stored on the server
- Scheduled jobs, cron tasks, and webhooks
- Email sending and SMS setups
- SSL certificates and when they renew
- Custom domains, redirects, and subdomains
Read the code, the tests, and the gaps
Ask whether the code is in version control with a clear history. A repository with commit messages gives you a timeline of changes. If there is no repository, that is a finding in itself, and you should plan for it.
Then look at how the code is organised. You are not trying to judge the developer's style. You are trying to answer practical questions:
- Can someone new run the project on their own computer by following the setup steps?
- Are there automated tests, and do they pass?
- Is business logic, such as pricing, order status, or payment handling, in one place or scattered across pages?
- Are passwords, keys, or tokens written directly into the code?
- Are there error logs, and does anyone read them?
If the answers are mostly no, that does not mean the project is lost. It means the first months will be spent understanding the system rather than adding features.
Find the open bugs and security risks
Write down what is broken now. Ask customers, staff, or anyone who uses the site what goes wrong. Check the error logs and the hosting dashboard for failed payments, slow pages, or repeated crashes. Run the site through the main journeys yourself: browsing, signing up, checking out, booking, and contacting you.
Security needs its own check. Confirm that admin pages are protected, that user passwords are hashed rather than stored as plain text, and that the software and its libraries have recent updates. If you handle customer data, review what is collected and where it is kept. Our article on how to keep customer data safe for your business covers the basics.
Decide whether to fix, extend, or rebuild
Once you understand the system, you have three realistic options:
- Fix and stabilise. The foundation is sound, but there are bugs, outdated packages, or missing backups. Start with the problems that cost you money or expose data.
- Extend. The code works well enough, and you want new features. Add them only after the risky parts are stable, and write tests for the areas you change.
- Rebuild. The code is hard to run, insecure in ways that cannot be patched, or built on a platform you no longer want. A rebuild costs more up front, but it can be cheaper than years of patching.
Most businesses end up with a mix. They fix the urgent problems, then move one part at a time. Whatever you choose, agree the order of work in writing so that you can see progress.
Plan ongoing upkeep from the first week
A website or app is never finished. Frameworks release security updates, payment providers change their APIs, and phones update their operating systems. Without a maintenance plan, the code you just inherited will drift out of date again.
A practical upkeep plan covers regular updates, backups, uptime monitoring, error alerts, and a named person who receives them. If you need help with bug fixing or ongoing care, our technical support service covers code repair and maintenance. If the project needs a new interface or a rebuilt front end, look at our web development service.
Frequently asked questions
Can another developer take over my website without the original developer?
Yes, in most cases. A competent developer can study the code, the hosting setup, and the database to understand how the site works. The original developer's notes and access to accounts make the job faster, so ask for them if you can.
What if the previous developer will not hand over the code?
Start by confirming who owns the domain, hosting, and repository, because those accounts are usually in your name. If the code is locked up under someone else's account, get advice on your contract and written agreements before taking further steps. Keep records of every request you make.
How much of the code should I review myself?
As the business owner, you should review access, accounts, backups, and the list of open issues. The technical review of the code is better left to a developer, who can run the project and test it properly.
Should I rebuild the website instead of taking it over?
Rebuild only when the existing code cannot be secured or maintained at a reasonable effort, or when the platform no longer fits your business. A short technical audit gives you the evidence to make that decision rather than guessing.
If you have a website or app that was left half-finished, or you are about to take over one, send us a project brief or get in touch and we will explain what a review would involve.




