Setup & site building · Guide
How to Hand Over a WordPress Site to a Client

Short answer
Create the client as an Administrator, change the site admin email to their address and confirm it, hand over hosting, domain and billing details, reassign your posts and pages to them, and leave a one-page document listing every login, plugin and renewal date. Remove your own account only after they have logged in and the site has run for a few days.
Key takeaways
- WordPress has six default roles, and only Administrator gives full control of a single site.
- A new admin email stays pending until the client clicks the confirmation link in their inbox.
- The site admin email and a user account email are separate, and changing one does not change the other.
- Editors cannot install themes or plugins or change site settings, so the client needs Administrator.
- Hosting, domain and WordPress are three separate accounts, and each needs its own handover.
- Remove your own account only after the client has logged in and the site has run for a few days.
What does a proper WordPress handover include?
A proper handover gives the client full control of the site, the hosting, the domain and the billing, plus a written record of logins, settings and support terms.
A handover is not one password in an email. It moves four things: WordPress admin access, hosting and domain control, the site's content and settings, and the knowledge to run it. Miss one, and the client will be locked out of their own site within weeks.
| Handover item | What the client receives |
|---|---|
| WordPress admin account | Their own Administrator login |
| Site admin email | Their email address in Settings → General |
| Hosting account | Login, or a move to their own host |
| Domain | Registrar login and DNS control |
| Backups | A full backup file and the backup routine |
| Documentation | Logins, plugins, settings and support terms |
Agree the scope before you start. Decide who owns the hosting bill, who pays for premium plugins, and how long you will answer questions after the handover. Put those answers in writing so neither side has to guess later.
The guide to how to run a WordPress security audit is a good final check before you hand the keys over, since it catches open issues while you still have access.
How do you create the client as an administrator?
Add the client as a new user with the Administrator role, let them set their own password, and confirm they can log in before you remove your own access.
Follow these steps:
- Go to “Users → Add New” in the dashboard.
- Enter the client's username and email address.
- Set the role to Administrator.
- Send them the login link and ask them to set a password.
- Ask them to log in while you watch, or confirm by message that they are in.
WordPress has six pre-defined roles: Super Admin, Administrator, Editor, Author, Contributor and Subscriber, as the Roles and Capabilities documentation states. Only Administrator gives full control of a single site, so the client needs that role to own the site.
The same documentation states that an Administrator account is created automatically when WordPress is installed, and that the default role for new users is set under “Settings → General”. Check that default before you add the client, so a wrong default does not give them a weaker role.
Do not share your own admin account with the client. The Learn WordPress User management lesson states that an administrator can publish, edit and delete posts and pages, edit code, and manage media, plugins, themes, other accounts and settings. A shared account hides who changed what, and it leaves your email on the account.
The guide to how to add users in WordPress covers the add-user screen in full.
The guide to how to manage user roles securely in WordPress covers which role fits each person on the team.
How do you move the admin email and ownership of content?
Change the site admin email to the client's address in “Settings → General”, then reassign your posts and pages to the client's account.
The administration email is the address WordPress uses for site notices, such as update failures and new user registrations. The Settings General screen documentation states that the Administration Email Address is different from the email address tied to a user account, and changing it does not change the email used to log in.
To change it, go to “Settings → General”, type the client's address in the Administration Email Address field, and click “Save Changes”.
WordPress then sends a confirmation email to the new address. The Settings General screen documentation states that the new address does not become active until the confirmation link in that email is clicked, and the old address stays active until then.
That confirmation step is the most common handover snag. Ask the client to open their inbox, click the link, and confirm the change shows on the settings screen. The documentation page for this screen was updated on 3 July 2026 with this confirmation wording, so the flow above matches current WordPress.
Next, move the content. Open “Posts → All Posts”, select your posts, pick “Edit” from Bulk Actions, and change the author to the client. Do the same for pages.
The guide to how to change the admin email in WordPress covers the email change in detail if the confirmation mail goes missing.
How do you hand over hosting, domain and billing?
Move the hosting account into the client's name or move the site to their host, hand over the domain registrar login, and list every paid service with its renewal date.
Hosting, domain and WordPress are three separate accounts, and each one needs its own handover. A client who owns WordPress but not the hosting cannot restore a backup or fix a server error. A client who owns the hosting but not the domain cannot point the site at a new server.
Work through this list:
- Hosting: transfer the account to the client, or move the site to a host they own. If you move it, the content export alone is not enough, since it leaves the theme, plugins and settings behind. The Learn WordPress Tools: Import and Export lesson states that a migration plugin can move the whole site, and that is the route to use for a host move.
- Domain: hand over the registrar login and confirm the client can see the domain and its DNS records. Note the renewal date and whether auto-renew is on.
- Billing: list every paid service, such as hosting, domain, premium plugins and email, with the price, the renewal date and who pays it.
- Email: note where the site's email lives and who controls that account, since password resets depend on it.
If the client wants the site on their own host, the WordPress.com import guide notes that importing content does not delete or overwrite what is already on the new site, so a test import will not wipe their fresh install.
The Importing Content handbook adds that a failed import may leave partial content behind, so check the counts before you call the move done.
The guide to how to choose hosting for agency client sites helps when the client asks which host to pick for the next term.
How do you document the site for the client?
Write a one-page handover document that lists every login, every plugin, the theme, the backup routine, and who to call when something breaks.
A good handover document has six parts:
- Logins: WordPress admin, hosting, domain registrar and email, with the username and where each password lives.
- Site facts: the domain, the host, the WordPress version and the theme name.
- Plugins: each plugin, what it does, whether it is free or paid, and its renewal date.
- Backups: where backups live, how often they run, and how to restore one.
- Routine jobs: updates, spam checks and comment moderation, with how often each runs.
- Support terms: what you will still answer, for how long, and what counts as paid work.
Keep it to one or two pages. Store it where the client can find it, such as a shared folder, and send a copy by email.
Note any custom code or settings that are easy to break, such as redirect rules, custom fields or a child theme. If a plugin needs a licence key to get updates, write down which account holds the licence and when it renews.
How do you check the site still works after handover?
Log in as the client, open the home page and three key pages, submit the contact form, and confirm a backup runs on the new setup.
Run these checks with the client's account, not yours. That proves the client account has the access it needs, and it catches a role mistake before you leave.
- Log in with the client account and open the dashboard.
- Open the home page, a service page and the contact page on the front end.
- Submit the contact form and confirm the message arrives at the client's email.
- Create a test post, then delete it, to confirm the client can publish.
- Run a manual backup and confirm the file appears where backups live.
Take a full backup before the handover and keep a copy for 30 days. The guide to how to back up WordPress covers a full backup of files and database. If anything breaks in the first week, that copy is the fastest way back.
Check the site admin email one more time after the client confirms the new address. If the confirmation link was never clicked, the old address still receives the site notices, and the client will miss update failures and new user alerts.
When should you remove your own access?
Remove your own admin account only after the client has logged in, confirmed the admin email, and the site has run for a few days without your help.
Do not remove yourself on the same day you create the client account. A missed confirmation email, a wrong role, or a lost password will lock the client out, and you will have no way back in without host access.
Follow this order:
- Create the client Administrator account and confirm they can log in.
- Change the site admin email and confirm the new address is active.
- Hand over hosting, domain and billing details.
- Wait a few days while the client uses the site.
- Ask the client to remove your account, or remove it yourself with their written OK.
Editors cannot install themes or plugins or approve updates, as the Learn WordPress User management lesson states, so do not drop the client to Editor and call it a handover. The client needs Administrator to run their own site.
If you will keep doing maintenance for the client, keep a named account of your own with the Administrator role, and agree that in writing. A named account keeps a clear record of who changed what, and it is easy to remove later.
What mistakes should you avoid?
Do not share one admin account, do not leave your email on the site, and do not hand over a site with no backup and no written record.
Other mistakes to avoid:
- Creating the client as Editor or Author, which blocks them from installing plugins and changing settings.
- Forgetting the site admin email, so update and security notices keep coming to you.
- Leaving your personal email on plugin licences, which stops the client renewing them.
- Handing over hosting access but not the domain, or the domain but not the hosting.
- Deleting your account before the client has logged in even once.
- Skipping the backup, so a mistake in the first week has no way back.
A clean handover takes about an hour of checks and one page of notes.
Frequently asked questions
Can I just share my own admin account with the client?
No. Give the client their own Administrator account. WordPress has six roles, and only Administrator has full control of a single site. A shared account hides who changed what, and it leaves your email on the account after you leave.
What is the difference between the site admin email and my user email?
The site admin email is the address for site notices, while the user email is the address tied to one login. Change the site address in Settings, then General, and update the client user account under Users. Each change is confirmed by email.
What if the client never gets the admin email confirmation?
Ask the client to check their spam folder and confirm the address was typed right. Until the link is clicked, the old address stays active. If mail never arrives, the host or email service may not be set up to send WordPress mail.
Is an Editor account enough for the client to run the site?
No. An Editor can publish and manage posts, including those of other users, but cannot install themes or plugins or change site settings. The client needs the Administrator role to run their own site.
How do I move the site to the client's own hosting?
Move the hosting account into their name, or move the site to a host they own with a migration plugin. The built-in export moves content only, so it leaves the theme, plugins and settings behind. Hand over the domain registrar login as well.
Should I keep an account if I will still maintain the site?
Keep a named account of your own with the Administrator role, and agree that in writing. A named account keeps a clear record of who changed what, and the client can remove it later when the work ends.
Sources
- Roles and Capabilities WordPress.org
- Settings General screen WordPress.org
- User management Learn WordPress
- Importing Content WordPress Developer Resources
- Import content to WordPress from another site WordPress.com Support
- Tools: Import and Export Learn WordPress
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


