Website Handover Checklist: Accounts, Files and Access
A website handover is complete when your business can sign in, renew essential services, retrieve the agreed files and prove that the site can be maintained. A folder of passwords or a screenshot is not enough. Use this checklist before changing providers, and keep access checks separate from the rights and licenses documented in your contract.
Buyer guides. By Chleb AI Editorial (AI-assisted). Published 2026-11-09. 4 min read.
Start with a website handover inventory
List the domain registrar, DNS provider, hosting platform, source repository or site builder, business email, form destination, booking calendar and analytics accounts. One provider may operate several of these, but they are separate assets with separate recovery and renewal arrangements.
For each asset, record the account holder, the person who pays, the owner access level, the export format and the agreed handover date. Mark an unanswered field unresolved. Do not put passwords, recovery codes or API keys into the shared checklist.
- Name the business owner responsible for the handover.
- Inventory every account that keeps the site and its forms working.
- Record access, billing and export evidence for each asset.
- Agree who fixes each missing item and by what date.
Prove domain access before making changes
Use ICANN Lookup to identify the registrar and inspect available registration data. A missing public name does not establish that ownership is wrong. Sign in to the actual registrar account and verify the registration details, recovery contact, renewal date and payment arrangement with the provider.
Have the owner perform the sign-in independently. Check that the account has the permission needed to manage the domain, rather than merely receiving notices. If access depends on an employee who is leaving, agree and test the replacement access before removing the existing user.
Ask the registrar about transfer eligibility and the order of changes before changing registration details or requesting a registrar transfer. ICANN distinguishes those actions; a change of registrant can trigger a 60-day transfer lock, subject to the policy and available opt-out. Do not assume that changing an email address and moving registrars can happen in any order. Do not change DNS during an access audit.
Inspect the actual source and export
For a code repository, have the business owner sign in and confirm their role. Download or clone the repository into a separate test directory and locate the build instructions and dependency lockfile. Ask the developer to build that copy and show the resulting preview without relying on files from their laptop.
For a hosted site builder, document what its export includes and excludes. A static page export may not include the editor, database, forms, search or booking behavior. Ask the provider to demonstrate the supported migration or restore process on a test copy before describing the export as a complete replacement.
Source access does not decide copyright ownership. Record the custom deliverables, third-party licenses, ongoing subscription dependencies and rights after cancellation in the agreement. Ask a qualified adviser about unclear rights; do not infer them from who holds the login.
Use a handover acceptance record
Copy these rows into your own checklist. Fill each with observed evidence, an owner and a date. The entries below are checks to perform, not results from a Chleb customer.
| Asset | Evidence to save | Do not mark complete until |
|---|---|---|
| Domain | Owner sign-in, renewal date, recovery contact | Owner can access the correct registrar account |
| Hosting or builder | Admin role, recurring payer, export limits | Owner verifies the required permissions |
| Source and content | Repository or export, license list, build instructions | A separate test copy builds or restores |
| Forms and booking | Test destination and expected outcome | A fictional submission reaches the approved test destination |
| Analytics | Owner access and property identity | Owner opens the property for the correct site |
Source: Chleb editorial checklist informed by ICANN and GitHub access guidance, checked 2026-11-09.
Test the parts that visitors depend on
Agree on an isolated test environment or a clearly identified test submission with the owner. Use fictional details and inspect the exact destination record. A thank-you screen proves that the browser showed a response; it does not prove that the office received the inquiry.
Check the main contact form, booking link, click-to-call links, important redirects and mobile navigation. Record the page, expected result, actual result, time and person checking it. Do not use a real customer or trigger an unwanted message to prove that the system works.
If a handover involves a new host, compare the agreed page and asset list on the preview before changing the domain. Keep the current site available until the owner accepts the test evidence and the cutover plan.
Close the handover with named responsibilities
Keep a final record of what was delivered, what remains unresolved, who pays each recurring bill and who handles future changes. Store secrets in the approved password manager; put only references to those entries in the checklist.
Remove obsolete access only after replacement access is verified and the responsible owner approves it. Retain the agreed backups and instructions so the next provider does not have to reconstruct the site from screenshots.
Chleb discusses website scope and setup with the business owner. Bring the account inventory and unresolved questions to that conversation. A proposal should state its deliverables and handover arrangements; this checklist is not a statement that every platform exports the same way.
Related reading
Sources
How this article was made
Written with AI assistance. Every factual claim links to its source above. Illustrations are AI-generated, not photographs; cover cards are set in type; charts and diagrams are built from the public data they cite. This is general information, not legal, financial or tax advice. Found an error? Tell us at chleb@chleb.ai or through the contact page and we will correct it and note the correction on this page.
More stories
Questions readers ask
Does repository access mean I own the website?
No. Access is an operational permission. Rights in custom work, licensed assets and third-party software are separate questions to document in the agreement.
Should I transfer the domain first?
Check the registrar, access and transfer sequence first. Ask the registrar about eligibility and any lock before changing registrant details or starting a transfer.
What is the minimum proof of a useful export?
Retrieve it independently and have the agreed test copy build or restore. Document any features that still depend on the original hosted platform.
Can a screenshot prove administrator access?
It can document a screen at one moment. The owner should also sign in independently and verify the permissions and recovery route they need.
