Blog / Web management /
A client onboarding checklist for website handovers
The previous developer has moved on. The client has a login to “the website”, a vague memory of who set up the domain, and an invoice from a hosting company they’ve never logged into. Now the site is yours to look after.
Taking over a site someone else built is a big part of managing client websites, and it’s where problems hide. Nobody hands over a perfect site. The trick is to find out what you’ve inherited before something breaks, not after.
The short version: confirm who owns what, get your own access, take a backup you control, set up monitoring, record a baseline, and only then start changing things. Here’s the full checklist I work through.
1. Ownership: who holds the keys?
Before anything technical, find out who owns each account. Ideally the business owns all of them, in its own name, with its own email.
- Domain registrar. Which company, which account, when it renews, whether auto-renew is on.
- DNS. Often not the same place as the registrar. Cloudflare, the host, or the registrar’s own DNS.
- Hosting. Provider, plan, who pays, and whose email the account is under.
- Platform account. For Shopify, who’s the store owner. For WordPress.com or a managed host, the same question.
- Email. Does business email depend on the same DNS? (It usually does, so DNS mistakes take email down too.)
- Third-party services. Payment gateways, form tools, CDNs, premium plugin and theme licences.
If an old agency or ex-employee owns the domain or hosting account, sort that out first, politely and quickly. When I pick up a client site, the DNS login is the first thing I ask for. A business that doesn’t control its own domain doesn’t control its website. I covered the basics in DNS, SSL and Cloudflare: what site owners should know.
2. Access: your own accounts, not shared ones
- Your own named user on the CMS (WordPress admin, Shopify staff account), not the owner’s login.
- Delegated access to hosting, DNS and Cloudflare where the service allows it, rather than a shared password.
- Search Console and analytics access added as a user, not via someone else’s account.
- Everything into a password manager, not an email thread.
- Two-factor authentication turned on wherever it’s offered.
Then the less comfortable part: list who else has access and agree with the client who should keep it. Old agency accounts, former staff, test users, and plugins with API keys from years ago all count.
3. A backup you control
Before you touch anything, take a full backup (files and database for WordPress) and store it somewhere that isn’t the same server. If the previous setup had backups, find out where they go and whether anyone has ever restored one.
On Shopify, there’s no server to back up, but export products, customers and theme files, and duplicate the live theme before editing it.
My backup setup is in WordPress backups: a setup that saves you on the worst day.
4. Monitoring from day one
Add an uptime monitor with alerts that reach you. If the site goes down in week one, you want to know before the client does. You also want to know whether it was flaky before you arrived. (Details in the uptime monitoring setup I use for client sites.)
5. A baseline, written down
This protects you as much as the client. Record how the site is before you change it:
- Platform and versions: WordPress core, PHP, theme (and whether it’s a child theme), plugins with versions; or Shopify theme and installed apps.
- What’s out of date or abandoned.
- Speed: a PageSpeed Insights run on the homepage and one or two key pages.
- Search: Search Console indexing status, any manual actions or security issues, the last few months of clicks.
- Errors: broken links, failing forms, console errors, expired SSL warnings.
- Customisations: code snippets in
functions.php, custom plugins, theme edits, tracking scripts.
If something was already broken, the baseline shows it was already broken. If traffic was already falling, the baseline shows that too.
6. Forms, email and checkout: test them
The things that make money or bring in enquiries are the likeliest to be quietly broken. I’d rather find that out myself than from the client. Submit every contact form. Check where the emails land. On a store, place a test order. On WordPress, check that site emails actually send (many don’t, without an SMTP setup).
7. The conversation
A checklist only covers the technical side. The onboarding call covers the rest:
- What does the site need to do for the business? Sell, generate leads, inform?
- Who edits what? Who’s allowed to install plugins or apps?
- What happened before? Hacks, outages, big redesigns, migrations, traffic drops.
- What’s coming? Launches, campaigns, seasonal peaks you shouldn’t break things before.
- How do they want to hear from you, and how often?
Write the answers down next to the inventory. They’ll shape what you work on first.
8. Only then: change things
Once all that’s done, start with the safest wins: updates (with a backup and, ideally, on staging), security basics and obvious fixes. I leave big changes until I understand the site, which is never the first week.
Everything above goes into the site’s row in the inventory I described in managing several client websites at once. That way, the next person to take over, maybe you in a year, doesn’t start from scratch.
The checklist, short form
- Ownership of domain, DNS, hosting, platform, email
- Own named access, password manager, 2FA, access review
- Full backup stored off the server
- Uptime monitoring
- Written baseline: versions, speed, Search Console, errors, customisations
- Forms, email and checkout tested
- Onboarding conversation, answers recorded
- Safe changes first
Related reading
- Managing several client websites at once: the system I use
- DNS, SSL and Cloudflare: what site owners should know
- Training clients to manage their own websites
- The uptime monitoring setup I use for client sites
If you’re about to take over a site, copy the short list into a document before the first call. Every gap you can’t fill on day one is a question to ask.