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.
By G. Schad · Updated 20 November 2026 · 4 min read
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.
Domain registration is in the client's own registrar account, with the client's email as the registrant contact and renewal on their card.
DNS is in an account the client controls. The agency may have delegated access.
Hosting is billed to the client and the account owner is a client address, not a developer's.
Email sending service, CDN, analytics, tag manager, search console, payment gateway: each has an owner, and it should be the client.
Premium plugin and theme licences are registered to the client. A licence on the agency's bulk account stops updating the day the relationship ends, and outdated plugins are the most common way WordPress sites are compromised.
2. Accounts and roles inside WordPress
List every user with the Administrator role and confirm each one with the client by name. wp user list --role=administrator
Remove build-phase accounts: test users, the staging importer, the freelancer who did the migration.
No shared logins. Each person has their own account.
The site's administration email address, under Settings → General, is a client mailbox that is read. It receives password resets and update notices.
Client staff have the lowest role that does their job. Most need Editor.
Two-factor authentication is on for every administrator.
Revoke application passwords created during the build, on every user's profile.
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:
Hosting control panel password, and its two-factor setup moved to the client.
SFTP and SSH: remove agency keys that are no longer needed, change passwords.
Database password, updating wp-config.php to match.
Authentication keys and salts in wp-config.php. This signs everyone out.
WordPress passwords for every remaining administrator.
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:
which named agency accounts remain, at which role;
what they are for: updates, emergency fixes, content support;
when the access is reviewed or ends;
how the client revokes it without the agency's help.
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
The file editor is disabled: define( 'DISALLOW_FILE_EDIT', true );
Automatic updates are configured deliberately, and someone is named as responsible for the updates that are not automatic.
Debugging is off, and no debug.log, database dump or backup archive is sitting in the web root.
Staging and development copies are deleted or locked behind authentication. Forgotten staging sites are indexed, outdated and full of real data.
The site is not set to discourage search engines, a setting that routinely survives the move from staging to live.
6. Backups the client can actually use
Backups run on a schedule and are stored off the server, in an account the client owns.
A restore has been tested, and the client has seen it done or has written steps.
The client knows the retention: how far back they can go.
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.
Security and uptime alerts are re-pointed to the client, or to both parties if there is a retainer.
If an activity log is installed, agree who can read it and who can change its settings. Both sides have an interest in the answer.
Export the log as it stands at handover and give the client a copy. It is the baseline: every later dispute about "who broke it" starts from a known state on a known date.
Server access logs are kept for a stated period, ideally 90 days or more.
8. Data protection loose ends
If the agency processed personal data for the client, the processing agreement says what happens at the end: return or deletion. Do it, and confirm in writing.
Delete local copies of the production database from developers' machines.
Remove the client's data from the agency's staging servers, backups and shared drives, or state when it will expire.
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.