How to hand over a website to a new agency without losing anything
List every account, move each into your company's name, collect the code, backups and documentation, then give the new agency access and revoke the old.
By Sohail Hussain21 November 20266 min read
To hand over a website to a new agency, first list every account and system the site depends on, then make sure each one is owned by your company rather than the old agency. Collect the code, a full backup and a short document on how the site works. Then give the new agency its own access, let it confirm that it can restore, deploy and test the site, and only then remove the old agency's access. Done in that order, nothing is lost and the site never goes down. Done in the reverse order, which happens more than it should, you can end up with a site nobody can update.
A handover is mostly an ownership exercise. If your company already holds every account, it takes days. If the old agency holds some of them, those transfers set the timeline.
What needs to be handed over?
More than the website files. This is the list we work through when we take over a site:
| Item | What you need | Who should own it |
|---|---|---|
| Domain | Registrar account access, or a transfer into your account | Your company, as registrant |
| DNS | Login to wherever the records are hosted, plus an export of all records | Your company |
| Hosting | Account access, or a full migration if it is the agency's server | Your company |
| Code | A Git repository with full history, transferred to your account | Your company |
| CMS | An administrator login on a company address | Your company |
| Backups | A recent full backup of files and database, and where older ones are stored | Your company |
| Admin access to Google Workspace or Microsoft 365 | Your company | |
| Analytics and Tag Manager | Administrator access at account level | Your company |
| Search Console | Verified owner on your company account | Your company |
| Google Business Profile | Primary owner | Your company |
| Third-party services | Form handlers, transactional email, CRM links, payment gateway, map and reCAPTCHA keys | Your company, with keys rotated after handover |
| Licences | Premium plugins, themes, fonts, stock images, with renewal dates | Your company, or moved to it |
| Design files | Figma or similar, plus brand assets | Your company |
The third-party row is where things go missing. A contact form that sends through the old agency's email service account, or a map key on the agency's billing, keeps working until the agency closes that account. Then it stops, months later, and nobody connects the two.
When a site comes to us for website care and maintenance, this list is the first week's work. Who owns your website explains why each row matters.
In what order should the handover happen?
- List every account and system, using the table above, with who holds each one and when it renews.
- Move each account into your company's name. The domain first, because it can take days and everything else depends on it. How to get control of your domain back covers the transfer.
- Get the code, content and backups. Ask for the repository to be transferred to your account; GitHub's guide to transferring a repository shows the steps, and the history comes with it. Take a full backup of files and database as well, and an export of the DNS records.
- Get the site documented. A short written note from the old agency, covered below.
- Give the new agency access as a user on each account, with its own logins, rather than sharing yours.
- Check everything works, then revoke the old agency. Only after the new agency has proved it can restore and deploy.
Keep the old agency's contract running for a month of overlap if you can. Questions always come up, and they are easier to answer while the old team is still being paid to answer them.
How do you get the code if the old agency is slow to cooperate?
Start with the contract. A good one says the code transfers to you on payment and the agency hands over credentials and documentation at the end. What a website development contract should include has the clauses. Send a written request that lists each item, quotes the clause, and gives a date.
If the repository does not arrive, a full backup from the server is the fallback. For WordPress, that backup is effectively the whole site: theme, plugins, uploads and database. For a site that is built before deployment, such as Next.js, or for a mobile app, the server only holds compiled output, and you need the source code itself. Without it, the new agency will rebuild rather than continue.
What documentation should you ask for?
One or two pages is enough. Ask the old agency to cover:
- How the site is deployed, and where staging lives, if there is one.
- The names of the environment variables and API keys the site needs. The values themselves belong in a password manager, not in a document.
- Scheduled jobs: backups, feed imports, cache clearing, anything that runs on a timer.
- Integrations: where form submissions go, what connects to the CRM, payment and shipping setup.
- Custom code worth knowing about, and anything unusual about the setup.
- Known issues and work in progress.
An agency that cannot produce this in a day or two probably does not have it written down anywhere, which is useful to know too.
How do you hand over passwords and two-factor access safely?
Do not email passwords or paste them into chat. Use a shared vault in a password manager, or better, have the old agency invite the new one as a user on each service so nobody shares a login at all.
Two-factor authentication is the part that catches people. If an account's second factor is on a former agency developer's phone, you cannot log in without them. Move every second factor to something your company controls, such as an authenticator in the company password manager or a company phone, and save the recovery codes. After the handover, change every password the old agency knew, using new ones from the password generator, and rotate the API keys it had access to.
Search Console needs one extra step. A verified owner keeps owner access for as long as their verification token stays in place, so removing the old agency means removing its DNS record or HTML verification file as well. Google's guide to managing Search Console users explains how.
How does the new agency confirm nothing is missing?
Before the old agency loses access, the new one should run four checks:
- Restore the backup to a staging site and confirm it works. This proves the backup is complete. Website backups: what good looks like covers what a complete backup contains.
- Deploy a small, harmless change to the live site through the normal process. This proves the code and access work end to end.
- Submit every form and confirm each one arrives where it should.
- List every renewal date for the domain, certificates, licences and paid services, and put them in a calendar owned by your company.
If all four pass, revoke the old agency's access everywhere on the list, in one sitting, and note the date. For a larger codebase, taking over an existing codebase covers the deeper technical review, and the website maintenance guide covers the routine the new agency should run from then on.
Was this guide useful?