All Guides

Website Management

Website Handover Checklist

By TC Timebomb, Moonvine

Everything to transfer when changing hands.

What this covers: The complete website handover package: credentials transfer, technical documentation, content editing guides, source file delivery, maintenance schedules, training sessions, and a post-handover support period.

Who it’s for: Agencies, developers, or site owners transferring website ownership or management to a new team or client.

Key outcome: You’ll have a structured handover package with all credentials transferred, documentation delivered, training completed, and a support period defined so the new owner can operate independently.

Time to read: 4 minutes

Part of: Website Management series

Jump to Quick Questions ↓

Handing off a website? Here’s the complete checklist: credentials, documentation, training, and the often-forgotten items that cause emergencies later.

The Handover Package

1. Credentials Document

Transfer all credentials to their password manager or create a secure document with:

? WordPress admin accounts (create one for them, don’t share yours)
? Hosting account access
? Domain registrar access
? DNS management (if separate)
? SSL certificate details (if manual renewal needed)
? Email service logins
? Analytics access (add them to Google Analytics property)
? Any API keys or third-party service accounts

2. Technical Documentation

See our documentation guide for the full template. At minimum:

? Site architecture overview
? Theme information (custom or purchased, how to update)
? Critical plugins list with descriptions
? Custom functionality documentation
? Backup procedures
? How to clear cache

3. Content Editing Guide

Non-technical team members need:

? How to log in to WordPress
? How to create/edit pages and posts
? How to upload and insert images
? How to update menus
? How to edit contact forms
? Style guide for content (if applicable)

4. Source Files

Transfer all design and development assets:

? Original design files (Figma, Sketch, PSD)
? Logo files in all formats (SVG, PNG, etc.)
? Brand assets (fonts, colors, icons)
? Original photography/imagery
? Custom code repository access (if applicable)

5. Maintenance Schedule

Document what needs to happen and when:

? Plugin updates (weekly check recommended)
? WordPress core updates
? SSL certificate renewal date
? Domain renewal date
? Hosting plan renewal
? Content refresh schedule

The Handover Meeting

Checklists exist to catch the things you forget when you’re focused on the obvious. Work through them methodically.

Documentation alone isn’t enough. Schedule a training session:

Walk through the WordPress admin
Show how to do common tasks
Explain what not to touch without developer help
Answer questions
Record the session (Loom, Zoom recording) for future reference

Support Period

Website handover documentation ensures the receiving team can operate, maintain, and troubleshoot the site without constant help from the original developers. Thorough handover prevents emergencies and reduces the risk of losing critical institutional knowledge.

Build in a support period after handover:

30-day email support for questions
1-2 follow-up calls to check in
Clear boundaries: what’s included, what’s billable

After the support period, transition to a retainer or hourly rate for ongoing help if needed.

Final Checklist Before You’re Done

Complete these steps first to ensure smooth execution.

? All credentials transferred and tested
? Your own access removed (or reduced to role they want you to have)
? Documentation delivered and reviewed
? Training completed
? Source files transferred
? Final invoice sent
? Contact info exchanged for future questions

A clean handover protects both you and the client. They can run the site, and you’re not getting calls at 11pm about forgotten passwords.

The Handover Completion Checklist

All credentials are transferred securely
Documentation is complete and accessible
New owner can log in and make changes
Support contact exists for questions during transition

Sources

Website Handover Questions Answered

What credentials need to be transferred in a website handover?

WordPress admin login, hosting control panel, domain registrar, DNS management, SSL certificate provider, CDN dashboard, email service, analytics (Google Analytics, Search Console), social media accounts linked to the site, and any third-party SaaS tools (forms, CRM, payment processor). Missing even one can cause an emergency later.

How long should post-handover support last?

30 days minimum for standard projects, 60-90 days for complex sites with custom functionality. Define what’s included (bug fixes from the build vs. new feature requests) and response time expectations in writing before the handover. Most disputes arise from unclear support boundaries.

Should I transfer domain ownership during handover?

Yes, if the client should own the domain. Initiate the registrar transfer at least 2 weeks before handover completion—transfers can take 5-7 days and may require authorization from the losing registrar. Never hold a client’s domain hostage; it destroys trust and may violate ICANN transfer policies.

What training should I provide during handover?

Record a 15-30 minute screen share covering: how to log in, how to create and edit pages/posts, how to add media, where to find help documentation, and who to contact for issues. Recorded video is more valuable than written instructions because recipients can pause and replay. Store the recording in the shared documentation folder.

✓ Your Website Handover Is Complete When

All credentials (hosting, domain registrar, CMS admin, third-party services) are transferred to the new owner
Documentation covering site architecture, workflows, and maintenance tasks has been delivered
A recorded walkthrough video of key admin tasks is stored in the shared documentation folder
The new owner has successfully logged in and performed a test edit independently
Emergency contacts and support escalation paths are documented and acknowledged

Test it: Have the new site owner complete three tasks independently—publish a blog post, update a plugin, and restore a backup—without contacting you for help.