Website handover for WordPress projects: What your clients should have in place after the launch

Whether it’s a new website or a relaunch, once the site goes live, your clients should be familiar with every account on their WordPress website and be able to access them themselves. You’ll learn which accounts should be in their name when handing over the website, how to pass on login details securely, and how to retain responsibility for maintenance. At the end, you’ll find a handover checklist to tick off.

Why handover is an integral part of every launch and relaunch

Every WordPress project culminates in a launch. A new website goes live for the first time; in the case of a relaunch – that is, the redesign of an existing website – the new version replaces the old one. Whether your clients then have all the necessary access details will become clear by the next relaunch at the latest.

When websites are relaunched, I often end up with sites created by third parties. In such cases, login details are almost always missing – most commonly for the hosting account, the WordPress login and the newsletter tool.

I often have to contact the agency I used back then, and it may no longer exist. This applies, for example, to the transfer code needed to move the domain. Or it isn’t even clear who the domain is registered to in the first place.

One of my clients had been given his WordPress website by an acquaintance 15 years ago. The two were no longer in contact. However, the client was still able to give me the acquaintance’s contact details. So I got in touch with him, finalised the transfer with him and then transferred everything into the client’s name.

In most cases, clients receive too little information from the agency or provider responsible for their website. As a result, they do not know which accounts exist, who they are registered to, or how to access them. As an agency or freelancer, you can prevent this by ensuring that the website handover is factored into the planning for every launch and relaunch.

Who the domain should be registered to

To transfer a .de or .at domain to another provider, you need a transfer code, known as the AuthInfo. You can usually obtain this from the current domain registrar.

If no one there responds, there is a fallback option via the organisation that allocates all domains with that extension. For .de domains, the new provider then requests the AuthInfo directly from DENIC. DENIC sends it by registered post to the address listed in the domain details. For .at domains, nic.at has a similar exceptional procedure, whereby a confirmation code valid for a limited period is sent by email to the domain holder.

So your customers will only receive the code if the domain details list them, with a current address and a postbox that someone actually checks. If you’re listed there instead, it will be sent to you.

Register domains in your clients’ names right from the start. Even if you manage them collectively via your agency account, you should still list their company as the registrant there.

The handover list will then specify which registrar the domain is registered with and who can request the transfer code. It also states who manages the DNS records. These are the settings that determine where a domain’s website and emails point to.

Hosting and backups in your clients’ accounts

The files and database for the WordPress website are hosted by the hosting provider. If the hosting package is set up through your account, your customers won’t be able to access either the server or the hosting provider’s backups without you.

Instead, have the package registered in their name and keep your own access for maintenance. Some hosting providers have a ‘change of ownership’ feature for this purpose. You transfer the package to your client’s account; they then select a plan themselves, whilst you retain access to the hosting settings. The hosting provider remains the same – only the account changes.

It’s not enough simply to have backups. Your clients should know where the backups are stored, how long the hosting provider keeps them and who can restore them. If the backups are carried out via a backup plugin that saves copies to cloud storage, separate access to this storage must be included in the handover.

One admin account for you, one for your customers

In WordPress, the Administrator role has access to all of a website’s administrative functions, as WordPress itself explains. Set up a separate administrator account in your clients’ names and create a second one for yourself for maintenance and updates.

If your clients switch to another agency later on, nobody will have to change a password that others know. They’ll simply delete your account, and everything else will stay as it is.

Anyone on your clients’ team who only manages text and images does not need an administrator role. A role that allows them to edit content but not install plugins is sufficient.

In the general settings of WordPress, there is also an email address for managing the website. WordPress sends notifications about updates to this address and, in the event of serious errors, a link to recovery mode, which allows you to access the admin area again even if a plugin is causing problems.

For websites you have set up for others, the WordPress documentation explicitly advises you to check whether your clients can access this address. If someone changes the entry, the new address will only take effect once they have clicked on the confirmation link sent to them.

Plugin licences and linked services

Premium plugins that you pay for, and purchased themes, usually receive their updates via a licence key. If you use an agency licence for multiple projects, the key is registered to you. If your collaboration ends, your clients’ websites will no longer be able to receive updates for the plugin. They may then miss out on security updates that the developer has already released.

For each licence, make a note of who it’s registered to, when it expires, and what happens if your clients switch agencies. It’s neater if they purchase the licences for their website themselves and you simply register them. It’s best to check which licence models and ongoing costs a plugin entails when you’re selecting it. Katharina Brozek demonstrates this using the example of event plugins for WordPress.

The situation is similar for services that link a plugin or form to the website. A newsletter sign-up form sends new email addresses to the newsletter tool via an interface that connects the two programmes directly. If the account for this tool is in your name, your customers’ mailing list will be stored in your account. It’s best to set up such accounts in their names straight away and only then link them to the website.

Transferring login details securely

Passwords should not be included in plain text in a normal email, as they will remain in several inboxes. Use the sharing function of a password manager or an encrypted document, the password for which you can share via another channel, such as over the phone.

Your customers should then know which accounts they have been given and how to log in to each one. A table showing the service, login address, username and contact person is sufficient for this. The passwords themselves are not included. A brief joint session, during which your clients log in to each account themselves, will confirm that everything has been set up correctly.

If two-factor authentication is enabled for an account – i.e. a second code in addition to the password – this code must be sent to your customers. If the app for this is running on your smartphone, they will not be able to log in, even if they enter the correct login details.

How to keep the maintenance anyway

In my projects, everything is registered in my clients’ names. I send them all login details in encrypted form. This means they can switch agencies at any time without needing my help. I retain my own admin account for maintenance and updates.

You’ll also just need a clear agreement on which tasks you’ll be taking on. It’s best to clarify before the launch exactly what services are included in ongoing WordPress maintenance – from updates and backups to monitoring site availability.

The handover checklist for your next website handover

You can go through the following list before every launch or relaunch and then provide it to your clients as a handover checklist. They can then use it later to check for themselves whether anything is missing.

Domain and hosting

  • The domain is registered in your customers’ names, with their current address and a postbox that someone actually checks.
  • It is known which registrar the domain is registered with and who can request the transfer code.
  • It is clear who manages the DNS records.
  • The hosting package is set up for your clients, with their own login details.
  • With backups, it is clear where they are stored, how long they are kept and who restores them. Each storage location has its own access point.

WordPress

  • Your customers have their own administrator account; you have a second one for maintenance and updates.
  • Anyone who only manages content has a role without access to plugins and settings.
  • The email address in the general settings links to one of your customers’ email accounts.
  • For every Premium plugin and theme, it is clearly stated who the licence is issued to and when it expires.

Accounts and login details

  • The newsletter tool and other linked services are registered in your customers’ names.
  • All login details were received in encrypted form; none were sent in plain text by email.
  • A table lists each account, along with the service, login address and contact person.
  • Nobody needs your smartphone for two-factor authentication.
  • Your customers have each logged in to their account once themselves.
  • They know which tasks you’ll be taking on after the launch.

Migrating taken-on and older WordPress projects

This list is useful for taking stock when you’re taking over a third-party website as part of a relaunch or tidying up your own older projects. Mark anything that isn’t yet live for your clients and switch it over bit by bit.

For the domain, ask your current provider how the change of ownership works and what documents are required. For hosting, check whether your current hosting provider can transfer the package to one of your customers’ accounts.

The easiest way to handle licences that are in your name or in the name of your previous agency is to switch them to your own licences on the next renewal date. When doing so, briefly explain to your clients what will change for them.

Conclusion

A smooth website handover starts with registering the domain. If the domain, hosting, licences and associated services are in your clients’ names from the outset, all that’s left to do at launch is to provide the login details and an overview of all accounts. You’ll continue to manage maintenance via your own admin account.

My advice, therefore, is to be transparent. This often pays off more than restricting access in order to retain customers. Take the handover list with you to the next launch or relaunch and go through it with your customers.

Alexander Leeb avatar
Alexander Leeb

Share on social media

Alexander Leeb avatar
Alexander Leeb

Leave a Reply

Your email address will not be published. Required fields are marked *