How-To & Tutorials
Freelance Website Handoff Checklist: Transfer Ownership Without Locking Yourself Out

☰ Table of Contents
A freelance website handoff can go wrong even when the site itself is finished. A client may not know which account owns the domain, the freelancer may still be the only administrator, or a shared password may be sitting in an old email. This checklist helps you transfer control deliberately, prove what changed, and avoid locking either person out.
The key is to transfer ownership and access, not to send a bundle of passwords. Work through the account map first, make the client an administrator where appropriate, test their access, and only then remove your own access if the agreement calls for it. For wider project delivery, pair this with our freelancer proof-of-delivery pack.
Start with the account map, not the files
Before touching permissions, list every service the project relies on. A website is rarely one account: domain registrar, DNS, hosting, CMS, analytics, form delivery, email, stock assets and paid plugins can all have separate owners. Make a simple map with the service, current owner, billing contact, client’s intended role and transfer action.
Ask the client which email address should own each account. Do not assume the address used for project correspondence is the right long-term administrator. If they use an agency or IT provider, confirm who should receive ownership before sending invitations.
| Asset or service | What to confirm | Typical transfer action |
|---|---|---|
| Domain registrar | Registrant, renewal payer, recovery email | Invite client as account user or update registrant after approval |
| Hosting and DNS | Billing owner, nameservers, recovery path | Add a named client user; keep DNS change details documented |
| Website CMS | Client admin email and role | Create an individual administrator account and have client sign in |
| Analytics and forms | Who needs reports and lead notifications | Grant least-privilege access and test delivery |
Decide what the client should own
For a lasting business asset, the client should normally control the domain, hosting account and primary site administrator. That does not mean you must surrender your personal account or disclose your own master password. The client can own the service while granting you a separate collaborator account for agreed maintenance.
Check the contract, proposal and platform terms before transferring a paid licence, theme or third-party account. Some products permit moving a site but not transferring an individual subscription. If a licence cannot move, explain the renewal cost and the practical consequence of letting it expire.

Transfer access without sharing passwords
Use the provider’s invitation or user-management feature wherever possible. Each person should have their own login, protected with multifactor authentication. A password copied into a document, email or chat is hard to revoke and makes it unclear who used it.
- Invite, don’t impersonate: use a named client account with the smallest role that supports their work.
- Let the client accept it: ask them to sign in while you are available, then verify the access works.
- Use a password manager for exceptions: only when the service has no user roles, share through an approved secure vault and rotate the secret after transfer.
- Keep recovery details current: confirm the client controls the email and phone used for account recovery.
For WordPress, create the client’s account using their email and the administrator role if they are taking full site ownership. They should set their own password from the invitation. Keep your own account separate until the client confirms access and any contracted support period is clear.
Run a clean handoff in the right order
Sequence matters. Removing your access before the client tests theirs can turn a routine delivery into an urgent recovery job. Transfer first, verify second, clean up last.
- Back up the site and note its current working state.
- Invite the client to the relevant services using the agreed email.
- Have the client accept invitations and sign in independently.
- Verify that key actions work: edit a page, view analytics, receive a test form, and access billing or renewal details as agreed.
- Send the account map, renewal dates, support terms and any non-secret operating instructions.
- Remove temporary users and rotate shared credentials only after the client confirms access.
Record the date and what was transferred. If the work includes a scope change or additional cleanup, agree on that separately rather than silently adding it to the handoff. Our guide to a freelance change-order system can help keep those extra tasks explicit.
Use this handoff checklist
Use the list as a working record rather than a claim that every project needs every service. Mark each row complete, not applicable, or waiting on the client.
| Check | Done when… | Owner |
|---|---|---|
| Domain and renewal | Client knows registrar, renewal date and recovery email | Client / freelancer |
| Hosting and backups | Client can sign in and knows where backups are kept | Client / freelancer |
| CMS administration | Client’s separate administrator login has been tested | Client |
| Forms and notifications | A test submission reaches the agreed inbox | Both |
| Licences and renewals | Paid tools, payer and renewal responsibility are documented | Both |
| Freelancer access | Retained, downgraded or removed as agreed in writing | Both |
Set a clear support boundary
Clients often interpret “handoff complete” differently. Say what is included: for example, a short walkthrough, a defined bug-fix window for defects in the delivered work, or a separate maintenance plan. Be precise about what is not included, such as new features, content changes, hosting support or problems caused by later edits.
Set one route for requests and a reasonable response window. Avoid promising that you will remain the permanent emergency contact unless you have priced and agreed to that service. A written boundary protects the client too: they know where to go when something needs attention.

A handoff message you can adapt
“The website handoff is ready. I’ve invited [client email] to the domain, hosting and website accounts listed in the attached access map. Please accept the invitations and confirm you can sign in before [date]. I’ve included the renewal dates, backup location and a test form result. I’ll keep my collaborator access through [date] for the agreed support period, then remove it unless we arrange ongoing maintenance. No passwords are included in this email.”
Change the wording to match the actual services and contract. Never say ownership has transferred until the client has accepted the relevant account invitation or the provider confirms the transfer.
Frequently asked questions
Should I transfer the domain before the website launches?
Not automatically. Confirm the contract and launch plan. If the client is meant to own it, add them with the registrar’s supported role or complete the transfer when both sides can verify access. Avoid changing nameservers during the ownership step unless the launch requires it.
Should the client get the WordPress administrator role?
If they are taking ownership or need full site control, create a separate administrator account for them. If they only need routine content edits, a lower role may be safer. Never hand over your own personal login.
Can I keep access after delivery?
Yes, if the client agrees and the contract or maintenance plan defines why and for how long. Use an individual account with only the access needed. Otherwise remove it after the client confirms they can access the services.
What if a hosting account cannot be transferred?
Ask the host about adding the client as an account owner or moving the site to a client-owned account. Explain any downtime, migration fee or licence change before doing it, and preserve a backup until the client verifies the new site.
Is it safe to email a password?
No. Use named invitations where available. If a service forces shared credentials, send them through a reputable password manager’s secure sharing feature and rotate them after the client takes control.
When is the handoff actually complete?
When the client has accepted access, tested the important tasks, received the agreed documentation and confirmed the support boundary. Sending a zip file or an invitation alone does not prove the client can operate the site.

