Website Handover Checklist: Everything You Must Receive Before Final Payment

The day you make final payment is the day your negotiating power drops to roughly zero. Not because designers turn villainous at that moment, but because chasing a busy vendor for a forgotten password is slow, and chasing a vanished one is hopeless. So treat handover as a real event with a real checklist. This website handover checklist covers everything you must receive, and the balance payment is the natural moment to receive it: money moves, keys move, everyone shakes hands.

Access Credentials: The Big Four

• Domain registrar login. The account holding your domain, registered to your email, tested by you personally. Not "we'll manage it for you". If you read only one item on this page, this is the one; a lost domain is the most expensive thing on this entire list.
• Hosting control panel login. cPanel or equivalent. This is where your files, database and backups live. Log in yourself during handover, don't just file the password away untested.
• Website admin login. The WordPress or CMS dashboard where you edit content, as an administrator account, not an "editor" account with clipped permissions.
• Business email accounts. If info@yourdomain.com was set up, you need its password and the webmail address, plus instructions for adding it to phones.

Store these somewhere better than a single WhatsApp chat: a password manager, or at minimum a document two trusted people can find.

Files and Technical Property

You paid for the work, so the work product is yours. That means a full copy of the website files and the database export, even if you never open them; they're your insurance and your freedom to migrate. It means your logo and design source files in original formats. And it means a note of any paid licenses: premium themes and plugins are often bought under an agency's bulk license, which can lapse if you part ways. Ask the direct question: "Which paid components does my site use, and what happens to them if we stop working together?" A clear answer now prevents a broken site in eighteen months.

Knowledge: The Part Everyone Forgets

Credentials without knowledge are car keys without driving lessons. A proper handover includes being shown how to change text, swap photos, add a product or post, and check your enquiry form submissions. Insist on a recorded session or video, because you will forget the live demo within a week; everyone does. At WebsNP every project ships with a recorded training video plus free support, 15 days on Starter up to 6 months on Enterprise, precisely because handover without training just converts into support calls anyway. Whoever your designer is, ask what happens after launch and get the support window in writing.

Verifications Before You Transfer the Balance

Fifteen minutes of checking, ideally done together with the designer:

• Submit the contact form yourself; confirm the enquiry lands in your email, not the developer's leftover test address. This misconfiguration is comically common and silently eats real customer enquiries.
• Load the site on your own phone over mobile data, and check the padlock (SSL) shows on https.
• Google your business name; confirm the site appears and links to the new site, and your Google Business Profile points to it.
• Confirm backups exist and where they go. "The host does daily backups" should be verifiable in your own cPanel.

Make the List Part of the Deal

The elegant move is to agree all of this before the project starts: one line in the agreement saying final payment is due on delivery of the handover items above. No awkwardness at the end, no chasing, no leverage games in either direction. Honest designers love this arrangement, because it defines "done" precisely and gets them paid faster. The ones who resist a written handover list are telling you, politely and in advance, exactly what kind of handover to expect.