WordPress Maintenance Client Offboarding Checklist

Offboarding should leave the client able to operate the website and leave the maintenance provider with a clear end to access, billing, renewals, and responsibility. Start the checklist before the contract ends, especially when agency-owned licenses or recurring services are involved.

1. Confirm scope, dates, and decision makers

• Contract end date and the last day of active maintenance
• Client contact authorized to accept the handoff
• New provider contact, if the client has appointed one
• Work included before the end date and work requiring a separate quote
• A written acceptance or issue window for the delivered handoff

2. Create a complete service and renewal inventory

List domains, DNS, hosting, SSL, email delivery, CDN, backups, monitoring, premium plugins, themes, stock assets, analytics, and maintenance contracts. Record the vendor account owner, payer, renewal date, auto-renew status, and next action for each item.

3. Separate access transfer from credential sharing

Use vendor-supported ownership transfer, collaborator, or delegated-access features where available. Create named accounts for the client or new provider. Do not send a shared password in an ordinary email or place secrets in the renewal tracker.

• Transfer client-owned accounts to a client-controlled email address.
• Remove agency staff only after the client confirms replacement access.
• Rotate credentials and recovery methods that were shared during the engagement.
• Remove API tokens, deployment keys, and integrations no longer required.
• Keep an access-removal record without retaining the secret itself.

4. Resolve every premium plugin and theme license

Classify each license as client-owned, client-owned but agency-managed, or agency-provided. Then choose a supported handoff: retain client ownership, transfer the vendor subscription, have the client purchase a replacement, or remove a no-longer-needed product after testing.

Do not promise that an agency license can be transferred. WooCommerce, for example, documents that transferring a subscription moves ownership and billing, while sharing access retains ownership. Multi-site products can have additional limits. See WooCommerce subscription transfer documentation.

5. Deliver a maintainable technical handoff

• Current production and staging URLs
• Hosting, DNS, repository, deployment, and backup ownership
• WordPress administrator accounts and least-privilege guidance
• Theme, custom plugin, build, and deployment instructions
• Known defects, temporary workarounds, and pending updates
• Backup restoration procedure and the most recent verified backup date
• Monitoring, analytics, cache, email, and security-service ownership

6. Close billing and future renewals

1. Issue the final agreed invoice and identify any disputed items.
2. Cancel agency-billed services that should not continue.
3. Transfer or update payment methods before the next renewal.
4. Remove the client site from agency plans when the replacement is active.
5. Confirm which upcoming charges the client will receive directly.
6. Record the last responsibility date so later expiry notices have an owner.

7. Protect data without keeping unnecessary access

Retain only what the contract, accounting requirements, dispute handling, and applicable law require. Delete unnecessary copies of credentials and client data, document any retained backup window, and tell the client what will be deleted and when. This checklist is operational guidance, not legal advice.

8. Obtain a simple sign-off

Send a final handoff summary listing transferred items, outstanding client actions, removed access, unresolved risks, and support arrangements after the end date. Ask the authorized client contact to confirm receipt. A clear sign-off prevents an expired license six months later from becoming an argument about an old care plan.