Website Handover Checklist Before Final Payment

Tarun KumarWebsite Development 5 min read 15 Nov 2026
Website handover checklist before final payment to a web developer

Quick answer: Before the final invoice, get the domain, hosting, website admin and Google tools (Search Console owner, GA4 Administrator) in your own name, test each login yourself, and make final payment due on delivery of these items.

Your developer says the site is ready and asks you to clear the last invoice. Before you pay, get four things in your own name and test each one yourself: the domain in an account registered to your email, the hosting (where the files, database and backups live), admin access to the site and its code, and the Google tools (Search Console and Analytics). Then run a short live check of forms, mobile, HTTPS and SEO basics, and tie the final payment to delivery of these items in writing — WebsNP's advice is that the last payment falls due on delivery of the handover items.

Website handover checklist: the four things that must be in your name

These four come first. If any one is still in the developer's name, you do not fully own the site.

  1. Domain. In a registrar account on your email, logged into and checked by you personally.
  2. Hosting. Log in yourself during the handover meeting; hosting is where the site's files, database and backups live.
  3. Website admin. The login you receive should be a full administrator account, not a restricted editor account.
  4. Google tools. In GA4, ask for the Administrator role, which gives full control including managing users. In Search Console, ask to be an owner — owners can add and remove users and use all tools. When the developer removes themselves, ask them to delete their old verification token too, because a removed owner whose token remains on the site can re-verify.
Item Whose name/email How you test it
Domain Your email Log in to the registrar account yourself
Hosting Your email Log in and locate the files, database and backups
Website admin Your email Log in and confirm you can change settings and users
Search Console Your Google account Confirm you are listed as an owner
GA4 Your Google account Confirm you hold the Administrator role

Website handover checklist before final payment: domain, hosting, website admin, Google tools, then the final invoice AI-generated illustration.

Files, code and the repository

Ask for a full copy of the website files plus a database export, along with the logo and design source files in their original formats. Store these somewhere you control.

If there is a code repository, check whose account it sits under. A repo under the developer's personal account is not proof the code is yours, even with you added as a collaborator — transfer ownership before the final payment, not after. On GitHub, a transfer keeps the issues, pull requests and wiki, and old links redirect; the person transferring needs admin access on the repository. Repo ownership is also one of the points worth comparing when hiring — see freelancer vs agency for an MVP.

Also ask where each environment — live, staging, test — is deployed, and where the API keys and environment variables are stored.

Paid themes, plugins and licences

Many sites run on premium themes and plugins bought on the agency's bulk licence, and those licences can lapse if you part ways. Ask which paid components the site uses and what happens to each one after handover.

This is really a contract question. The clauses that decide whether you own the site or effectively rent it are the IP assignment, the treatment of proprietary components, who holds the domain and hosting accounts, and a real exit.

The live check before you sign off

Do these checks yourself, on your own phone and laptop, before you confirm the site is complete:

  • Submit every form with real data and confirm the email arrives.
  • Test on real devices, not just a shrunk browser window.
  • Check that each page has a unique title and meta description.
  • Confirm sitemap.xml and robots.txt exist.
  • Open a wrong URL to see a custom "page not found" page, and click through menus and footers for broken links.
  • Confirm the site forces HTTPS.
  • Confirm automated backups are set up.

Documentation and training

Insist on a recorded training session or video showing how to update pages, products and images — a live demo is easy to forget, so get it recorded. Ask also for a short written record of why the key decisions were made: why that theme, those plugins, that structure. The next person to work on the site will need it.

Tie the final payment to the handover

The cleanest way to handle a website handover before final payment is to make the payment conditional on the list: final payment due on delivery of the handover items. Write the list into the contract or into the last invoice's milestone, so both sides work from the same tick-list. Include the repository transfer in that milestone — it should happen before the final payment, not after.

Treat the website ownership transfer as a condition of payment, not a favour to ask for afterwards. For the exact wording, ask your lawyer or CA. If you have not hired yet, these terms are easiest to set at the start — the guide on how to choose a website developer near you covers what to agree before work begins.

If something is missing

Chase items in the order they are hardest to replace: domain first, then hosting, then the Google tools.

If the domain is still in the developer's account, ask for a transfer to an account on your email — nothing else matters much without it. If hosting is missing, ask for the account in your name, or at minimum full access plus a complete copy of the files and database.

For the Google tools, ask for the exact roles from the first section: owner in Search Console, with the developer's old verification token removed, and Administrator in GA4. If the repository is still theirs, ask for a GitHub transfer to an account you own; the person sending it needs admin access on the repository.

I'm Tarun, founder of Gigzman. Gigzman builds websites for small businesses: https://gigzman.com/services/website-development?utm_source=gigzman-blog&utm_medium=blog&utm_campaign=website-handover-checklist

Questions people ask

Who should own the domain?

You — in a registrar account registered to your email, with you able to log in yourself rather than relying on the developer for renewals or changes.

Is a collaborator invite on GitHub enough?

No. A collaborator invite on a repo under the developer's personal account is not proof the code is yours. Ask for the repository to be transferred to an account you own.

What if the developer uses their own hosting?

Then your files, database and backups sit in an account you do not control. Ask for the site to be moved to hosting in your name; if that is not possible, get full login access plus a complete copy of the files and a database export.

Do I need the database if I never open it?

Yes. Files alone are only half the site — without the database export you do not have a complete copy, and moving or rebuilding later becomes guesswork. Store it with your backups even if you never look inside.

Want this done on your site?

Tell us what you are working with and we will come back with a plan.

Start a Project
Get Started

Ready to Build Something That Moves Your Business Forward?

Share your ideas and we’ll come back with a clear plan, a timeline and a price.

30-Minute Discovery

A focused conversation to understand your goals, challenges and opportunities.

Direct Team Conversation

Speak directly with our strategists and developers, no middle layers.

No-Commitment First Call

Get clear insights and practical recommendations with zero obligation.

Start a project

Five fields. We reply with a plan, a timeline and a price.

Prefer the long form? Open the contact page. By sending this you agree to our Privacy Policy.