How to hand a WordPress site over to a client
Last updated
To deliver a WordPress website to a client, you get their sign-off, move the site into the hosting account they'll own, give them their own logins, and send a note that lists everything you handed over. Do it in that order, so nothing goes live in the wrong account. What the client owns at the end turns on your contract, so check it before you start.
How do you deliver a WordPress website to a client?
You deliver a WordPress website to a client in four moves: sign-off, the move, the logins and the handover note. Each one closes a question the client would ask you later.
- Get the final sign-off in writing. Name the version of the site the client approved.
- Move the site. Put it in the hosting account the contract names, if it isn't there already.
- Hand over the logins. Give each person on the client's side an account of their own. Then you can remove one person's access without touching anyone else's.
- Send the handover note. List every account, login and file, and what you'll still look after, if anything.
Ownership of the site and its code, the domain name and each login should already be in writing with the client. For ownership terms in the contract, see what a web design contract should say about ownership.
How do you transfer a WordPress website to a client's account?
Agree on the client's hosting account first, then back up the site and move the files and the database into it. WordPress.org's Advanced Administration Handbook says you don't need to reinstall WordPress to move it to a new server, and that you start by backing up the WordPress folder, images, plugins and other files on the site, as well as the database.
Here are the steps:
- Settle the account. Ask whose name the hosting is in, who pays for it, and who can sign in. Get the client to set up the account in their own name, then add you as a user.
- Back up everything. Take a full copy of the files and the database before you touch anything.
- Check whether the address changes. The handbook says a move that keeps the domain and the site's web addresses is simple and can be done, in most cases, by moving the files. If the database and the address stay the same, copying the files and the database is enough. If the database name or user changes, it says to edit wp-config.php so it has the right values.
- Take care if the domain changes. The handbook warns that references to the old domain stay in the database when the address changes, and that this can cause problems with links or with how the theme shows. It also warns that a search and replace on the whole database can cause problems, because some themes and widgets save values that record how long the address is.
- Test the moved site. Go through every page, form and login before you tell the client it's done.
If you'd rather talk through a client build with someone, DeskTeam360 runs short calls that tie you to nothing.
What goes on a website handoff checklist?
The checklist names every account and file the client now holds, and how you checked it. Go down the list with the client on a call, or send it and ask them to confirm each line.
| Item | What to hand over | How to check it |
|---|---|---|
| WordPress admin login | The client's own user account, with the role you agreed | The client signs in with it while you watch |
| Other user accounts | One account for each person on the client's side who edits the site | Each person can sign in and sees what they need |
| Hosting account | The login, in the client's name | The client can sign in and sees the site |
| Domain name | Access to the registrar account, in the client's name | The domain shows in the client's account |
| Backups | Where the latest full backup sits, and how to get it | The client knows where to find it |
| Paid themes and plugins | The license keys, or the accounts that hold them | Each license is in an account the client can reach |
| Your own access | What you keep, and for how long, or a note that you've removed it | Your old logins are gone, or listed in the contract |
On the user accounts, WordPress.org's guide to roles gives an Administrator access to every administration feature on a single site. An Editor can publish and manage posts, other users' posts included, and an Author can publish and manage their own. Contributors can write and manage their own posts, though they can't publish them, and a Subscriber can only manage their profile. The guide adds that installing WordPress creates an Administrator account by itself, and that Settings > General holds the default role for new users. For the client's dashboard, see setting up a WordPress client dashboard.
What goes in a website handover email?
A website handover email tells the client the site is theirs and where everything lives. Keep it short enough to read in one sitting, and keep it somewhere you can both find it later.
Put these in it:
- a line that says the site is live and signed off, with the date
- the web address and the login page address
- each account the client now holds: WordPress, hosting and the domain
- how to reset a password, so they never need you for that
- where the backups are kept
- what you'll still look after, if anything, and how to ask for help
- the checklist of what you handed over, attached or pasted in
Send the logins themselves another way than the email, such as a password manager, so they don't sit in an inbox.
Once the site is handed over, the next build is waiting, and DeskTeam360 can talk it through with you on a short call that doesn't tie you down.
Nothing on this site is legal or tax advice.
More on Handover and ownership
- Web design contract: the parts that set who owns the site
- WordPress client dashboard: what to give a client when the site is done
- How to add a client portal to a WordPress site
- All guides
Sources
- WordPress.org, Advanced Administration Handbook, Moving WordPress, read October 15, 2026
- WordPress.org, Roles and Capabilities, read October 15, 2026
- DeskTeam360, booking page, deskteam360.com/book-a-call, read October 14, 2026
What changed
- : Page first published.