Website Handover Checklist: What to Get From Your Developer
By Nemanja Vukmirović, Lizzard Solutions. Last updated 13 November 2026.
Your developer is leaving, the agency contract is ending, or the freelancer who built your site stopped answering email. Then you discover the domain is in their name, the hosting bill goes to their card and nobody knows the admin password.
A website handover checklist prevents that. Below you get 28 checks grouped by area, a ready-to-copy handover register, the red flags that mean you do not really own your site yet, and what to put in your next development contract so the next handover takes an afternoon.
TL;DR
- A website handover is complete only when the business, not a person, owns the domain, hosting, code, data and every admin account.
- Ask for access first, then documentation, then a test: someone other than the developer must be able to log in and restore a backup.
- Write the handover list into the contract at the start of a project. It is much harder to negotiate at the end.
What is a website handover checklist?
A website handover checklist is a list of every account, file, credential and document a business needs to run and change its website without the person who built it. It covers the domain, DNS, hosting, source code, CMS admin, third-party services, analytics, backups and legal rights, and each item is confirmed as transferred and tested.
It is different from a website launch checklist. The launch list checks that the site works. The handover list checks that you control it.
Key takeaway
If one person can lock you out of your website by changing a password or stopping a payment, the handover is not finished.
1. Domain and DNS: who really owns your address?
The domain is the one asset you cannot rebuild. A new site can be built in weeks. A lost domain may be gone for good.
- ☐ The registrant (holder) of the domain is your company, with a company email address as contact.
- ☐ You have your own login at the registrar, with two-factor authentication on a company device.
- ☐ Auto-renew is on and the payment card belongs to the company.
- ☐ You know where DNS is managed (registrar, Cloudflare or hosting) and have admin access there too.
- ☐ You have an export or screenshot of all DNS records, including email records (MX, SPF, DKIM, DMARC).
For generic domains such as .com, ICANN’s Transfer Policy sets the rules for moving a domain between registrars, including the authorization code the current registrar must give the holder. For .rs domains, our guide to .rs domain registration explains how holders and registrars work in Serbia.
Action for today: look up who is listed as the holder of your domain and which email gets the renewal notices.
2. Hosting, server and cloud accounts
- ☐ The hosting or cloud account is in the company’s name and paid by the company.
- ☐ If the developer must keep the account for now, you are added as an owner or admin user, not just a viewer.
- ☐ You have the server, database and SSH or FTP access details, stored in a company password vault.
- ☐ Billing alerts or spend limits are set on cloud accounts.
- ☐ You know the renewal date and the plan you are paying for.
Action for today: find the last hosting invoice. If it is not addressed to your company, put this area first.
3. Source code: do you have it, and do you own it?
Having a copy of the code and owning the rights to it are two different things. You need both.
- ☐ The code is in a repository owned by your organization (GitHub, GitLab or similar), not in the developer’s personal account. GitHub documents how to transfer a repository to another account or organization.
- ☐ The repository contains everything needed to build the site, including the database structure (migrations) and a sample configuration file without real secrets.
- ☐ A README explains how to run the project locally and how to deploy it.
- ☐ You have a list of paid themes, plugins and libraries, and the licences are in the company’s name.
- ☐ Your contract states that the rights to the custom code pass to your company on payment. Ask a lawyer to check the wording.
Example
A typical case: a WordPress site where the theme licence and a premium form plugin were bought on the agency’s account. When the agency leaves, updates stop. The fix is simple: buy the licences on your own account before the handover date.
4. Admin accounts, integrations and API keys
- ☐ CMS admin (WordPress, Webflow, custom panel): at least two admin accounts owned by the company.
- ☐ Email sending service, payment provider, booking tool, maps and chat widgets: you are the account owner.
- ☐ Every API key used by the site is listed, with where it lives and who can rotate it.
- ☐ The developer’s personal accounts are downgraded or removed after the handover, and shared passwords are changed.
- ☐ All credentials go into a shared vault. Our password manager setup guide for small business shows how to organize one for a team.
5. Analytics, Search Console and marketing tools
These accounts hold years of data about your visitors. If they belong to the agency, that history leaves with them.
- ☐ Google Search Console: your company account is an owner of the property. Google’s help page on managing Search Console users explains the owner and user roles.
- ☐ Google Analytics: your account has the Administrator role. See Google’s guide to Analytics access and roles.
- ☐ Tag Manager, ad accounts, Google Business Profile and social pages: the company is the primary owner.
- ☐ Cookie consent tool and newsletter platform: the company holds the account and the subscriber list export.
Action for today: open Search Console and check the list of users and owners. Remove anyone who no longer works with you.
6. Backups, documentation and the restore test
- ☐ Backups run automatically, are stored outside the hosting server, and you can download them yourself.
- ☐ You have a recent full backup of files and database taken on handover day.
- ☐ A short document lists the tech stack, hosting, domain, integrations, scheduled tasks and known issues.
- ☐ Someone other than the outgoing developer has restored a backup to a test copy and the site worked.
The restore test is the one most teams skip, and it is the one that proves the rest. Our 3-2-1 data backup guide explains how to set up copies you can rely on.
A handover register you can copy
Put every item in one table and fill it in together with the developer. Here is a worked example for a small company site:
| Item | Where | Owner after handover | Checked |
|---|---|---|---|
| Domain example.rs | Registrar account | Company, office@ contact, 2FA on company phone | Holder confirmed |
| DNS | Cloudflare | Company account, developer removed | Records exported |
| Hosting | VPS provider | Company card, two admin users | Invoice on company |
| Source code | GitHub organization | Company organization, developer as outside collaborator until handover ends | Repo transferred |
| CMS admin | /admin | Two company admins | Logins tested |
| Analytics and Search Console | Company Google account as owner and Administrator | Roles checked | |
| Backups | Off-server storage | Company, restore tested | Test restore done |
Red flags: you do not own your website yet
| What you hear | What it usually means |
|---|---|
| “The domain is on our account, it is easier that way.” | The agency is the holder. You need a holder change, not just access. |
| “We will send the code if you ever need it.” | There is no repository you control. Ask for it now. |
| “The theme is on our licence.” | Updates and support stop when the relationship ends. |
| “Only I know how to deploy it.” | No documentation exists. Ask for a README and a test deploy by someone else. |
Not sure which of these applies to you? Our free website audit guide shows what to check, or you can request a free website audit and we will flag ownership and access risks along with speed, SEO and security.
What to put in your next development contract
- The domain, hosting and all third-party accounts are opened in the client’s name from day one.
- Code lives in the client’s repository, and rights to custom code transfer on payment.
- The handover includes a README, a full backup, a credentials list in a shared vault and a test restore.
- Notice period and handover support (for example, a set number of hours) are agreed in advance.
After the handover, a website maintenance checklist keeps everything renewed and updated, whoever does the work.
FAQ
Who owns a website, the developer or the client?
It depends on the contract. The domain belongs to whoever is registered as its holder, accounts belong to whoever opened them, and rights to custom code follow what you signed. Without a clear clause, the developer may keep rights to the code. Put ownership in writing at the start.
What should I ask for when changing web developers?
Ask for registrar and DNS access, hosting admin access, the code repository, CMS admin accounts, a list of plugins and licences, API keys, analytics and Search Console ownership, a fresh backup and short documentation. Then test that a new person can log in and deploy.
How long does a website handover take?
For a simple site with good records, access and documentation can be sorted in a day or two. Domain holder changes and registrar transfers can take longer because they depend on the registrar’s process. Start early and keep the old developer’s access until the new team has tested everything.
Can I get my domain back if the developer registered it?
Often yes, if you can show the domain was bought for your business. First ask the developer to change the holder or give you the transfer code. If that fails, contact the registrar. Disputes over domains have formal procedures, so keep invoices and emails that prove it is yours.
Taking over a website from another developer?
We run the handover with you: domain, hosting, code and accounts moved to your company and tested, so nothing depends on one person.
Talk to Lizzard Solutions