Who Changed It/Guides

WordPress Agency-to-Client Handover: A Security Checklist

A handover is the moment a site's security is most likely to degrade without anyone noticing: accounts nobody owns, licences in the wrong name, alerts going to a mailbox that will be closed. This checklist covers what to transfer, what to revoke and what to write down. It works in both directions, whether you are handing a site over or receiving one.

The short version
  • The client should own the domain, the hosting account and every licence in their own name before the project ends.
  • Rotate every shared credential at handover, including salts, database and SFTP passwords and API keys.
  • Decide explicitly what access the agency keeps, under which named accounts, and until when.
  • Hand over a baseline: an export of the activity log and a list of accounts as they stood on the day.

1. Ownership: the things that are not in WordPress

The most damaging handover failures are outside the site.

2. Accounts and roles inside WordPress

3. Credentials to rotate on the day

Anything the build team knew, treat as known. Rotate, in this order so that nothing locks you out half way:

  1. Hosting control panel password, and its two-factor setup moved to the client.
  2. SFTP and SSH: remove agency keys that are no longer needed, change passwords.
  3. Database password, updating wp-config.php to match.
  4. Authentication keys and salts in wp-config.php. This signs everyone out.
  5. WordPress passwords for every remaining administrator.
  6. Third-party API keys stored in plugin settings: payment gateway, email service, maps, CRM.

Hand credentials over through a password manager's sharing feature, never by email or chat.

4. What the agency keeps

Ongoing maintenance is normal. Unstated ongoing access is the problem. Write down:

If there is no retainer, the answer is that the agency keeps nothing, and its accounts are deleted at handover.

5. Hardening that should already be in place

6. Backups the client can actually use

7. Logs and alerts: who hears about it now

During a build, every notification goes to the agency. After handover, somebody else has to be listening.

8. Data protection loose ends

9. The handover document

One page, dated, signed off by both sides. It lists the hosting, domain and DNS providers and who owns each account; every administrator account on the day; the plugins and themes installed, with licence owner and renewal date; where backups are and how to restore; who to contact for what; and what access the agency retains. Attach the log export and the user list. In two years, when nobody remembers the project, this page is what answers the questions.

If you use Who Changed It on client sites

The plugin this site documents fits steps 4 and 7 specifically. Log access is its own capability, so a client contact can read the history without being an administrator, or the log can be kept to agency accounts. Alerts go to email, Slack, Discord or Telegram. Exports are signed, so the baseline you hand over can be shown later to be unaltered. The agency page has a setup kit for retainers, and the plugin is free on WordPress.org.