- Article
- 2 minutes read
- Reviewed August 4, 2026
- WordPress maintenance and troubleshooting
A WordPress handover transfers operational control from one person or team to another.
A complete handover includes ownership, access, documentation, training, known issues and ongoing responsibilities.
Ownership Inventory
Transfer or document:
- Domain registrar.
- DNS.
- hosting.
- WordPress administrator accounts.
- source repository.
- deployment platform.
- email service.
- analytics and Search Console.
- CDN and security services.
- payment accounts.
- licences.
- external storage.
- monitoring.
- backup storage.
Prefer organization-owned accounts over personal accounts.
Access Transfer
Create named accounts for the receiving team.
Avoid sending passwords in plain text. Use a password manager or secure invitation process.
Remove or reduce outgoing-team access after acceptance and record emergency access separately.
Technical Documentation
Provide:
- Architecture overview.
- environments.
- version inventory.
- custom code.
- plugin and theme purpose.
- content model.
- deployment process.
- update workflow.
- backup and restore process.
- cron and queues.
- integrations.
- monitoring.
- known limitations.
- support contacts.
Editorial Training
Demonstrate the actual tasks the owner will perform:
- Publishing.
- media.
- users.
- forms.
- products or events.
- updates.
- staging.
- recovery.
- requesting support.
Record sessions where appropriate and provide written procedures.
Acceptance and Support
Agree:
- Handover date.
- tested credentials.
- outstanding work.
- warranty or support window.
- maintenance ownership.
- renewal responsibility.
- response expectations.
- final backup.
- acceptance record.
Frequently Asked Questions
Should the client receive every administrator credential?
They should receive or control all accounts required to own and operate the website, with privileges assigned appropriately.
Is a list of plugins enough documentation?
No. The receiving team needs purpose, configuration, dependencies, licences and maintenance procedures.
Continue Learning
Previous: WordPress Disaster Recovery
Next section: Advanced WordPress and Integrations