← All field notes

A WordPress client handover checklist for the agency taking over

A handover is not complete when someone sends a WordPress administrator login. That login may let you edit pages while leaving domain renewal, hosting, email delivery and premium plugin updates under accounts your agency cannot reach.

Before agreeing that you now maintain the site, separate access from ownership. You need both a way to do the work and a clear record of who can authorize it.

Ask for the account map

List the domain registrar, DNS provider, host, CDN and business email service. Add the plugin and theme vendors that require paid licenses, plus services connected to forms, payments, booking or analytics. Record the legal account owner and an administrative contact for each.

Use invitations or a password manager’s sharing mechanism where supported. Avoid passing a single shared password around by email. Do not request a transfer of ownership when delegated access is the appropriate arrangement.

Confirm renewal dates and payment responsibility with the client. An agency can have working access to an extension today and still lose updates next month because the former supplier owns the license.

Inspect before changing the site

Capture the current software versions and the key workflows. Check the homepage, an important landing page and the main conversion journey. Record visible errors and missing access before applying updates. This gives everyone a baseline for what was inherited.

The WordPress role reference explains the capabilities attached to core roles. Use it to assess the access being offered, while remembering that installed plugins may add their own permissions. Being able to log in does not guarantee permission to install software or manage every integration.

  • Identify custom plugins, child themes and snippets, with their source location and maintainer.
  • Confirm the backup destination, retention policy and last restore exercise.
  • Find staging and check whether it is safely separated from live services.
  • Record scheduled jobs and integrations that can change external systems.
  • Ask for known problems, upcoming campaigns and unfinished work.

Agree the boundary of the maintenance service

Write down which installations and services you are accepting. Explain whether the agreement covers emergency response, content changes, malware investigation or work on external systems. A vague “website support” label is an invitation for both sides to assume different things.

Give inherited issues their own action list. The client should be able to distinguish an onboarding repair from routine monthly maintenance. If you cannot verify a critical integration because access is missing, keep that limitation visible rather than treating the check as passed.

Close old access deliberately

Once the incoming access has been tested and the transfer is agreed, review accounts held by the previous supplier. Confirm whether any are still needed for a defined piece of work. Remove or reduce access through an authorized process; do not lock people out while they are still responsible for an active migration.

Rotate shared secrets that should no longer be shared, with the relevant owners involved. Check application passwords, deployment keys and service tokens as well as interactive user accounts. A removed administrator account is not the whole access review.

Finish with a short acceptance note: what was transferred, what was verified, which issues remain and who owns them. Add the site to your fleet inventory and schedule its first maintenance window. Have the client acknowledge the open items, especially missing access and inherited faults. Keep that acceptance note with the service agreement so the starting position is easy to find later.


Have a correction or a workflow we should cover? Tell the IrmaWP team.