webshunya icon logo

Chosen

Website Handover Checklist: What Your Developer Should Give You

Know which accounts, files, renewal details and recovery instructions to collect before your developer signs off.

Milan Gohil

·

9 min read

Two understated cut-paper hands pass a single orange key above an open ivory folder holding a miniature website card and neatly arranged small tools.
Two understated cut-paper hands pass a single orange key above an open ivory folder holding a miniature website card and neatly arranged small tools.

OVERVIEW

Here is a short version of what I write

A complete website handover gives your business control of essential accounts and a clear record of how the site works. A login alone may not cover renewals, recovery or a future change of provider.

  • Confirm domain, hosting and administrator access.

  • Record files, licences, recurring costs and renewal owners.

  • Document backups, recovery and ongoing support responsibilities.

  • Try essential tasks together during the handover meeting.

When a website project is nearly finished, there’s usually a final round of small changes. Replace a photograph. Correct a phone number. Check the contact form once more. It’s easy for the handover to become another item to get through. The developer sends a login, you save the email, and everyone moves on. That may be enough for updating a paragraph next week. It may leave you short when you need to renew the domain, bring in someone new or recover the site after a problem.

A good handover gives your business a clear way to do those things. You can still leave the technical work to a specialist. You should know where the accounts are, what you’re paying for and how another person could pick up the work.

1. Start with the domain account

Before working through a long checklist, find the account where your website address is registered. Can someone in your business open it and check the next renewal date? If you don’t know where to look, search your emails and invoices for the domain name. You’re looking for the registrar, the company managing its registration. That may be different from the company hosting your website. Once you’ve found it, check:

  • Whose details are attached to the domain and its account.

  • Who can sign in and manage it.

  • When it renews and how payment is handled.

  • Where renewal reminders go.

  • Who can recover access if the usual contact is unavailable.

An agency may manage renewals for you. That can work well, provided your business understands the arrangement and what happens if you change providers. Don’t mark this complete just because you have an invoice. Find the account and confirm the details with the person managing it.

2. A working login can still leave you stuck

Imagine hiring a new developer to make a few improvements. You send over your website login, only to discover that it allows page editing but cannot add users or manage the software. The login works. It simply doesn’t cover the job you need done. WordPress, for example, gives Editors and Administrators different permissions. An Editor can manage content; an Administrator has broader control within the site.

During the handover, sign in with your own account and establish:

  • What you can change yourself.

  • Who can invite a new developer or marketing specialist.

  • Which separate account handles hosting and billing.

  • How the business would regain access if someone left.

Pay particular attention to recovery. A company email address on the account won’t solve everything if sign-in approvals still go to a former employee’s phone. Keep passwords and recovery codes in a secure password manager. Give people their own accounts where possible, with the access needed for their work. You don’t need everyone to be an administrator; you need to know who can manage access on the business’s behalf.

3. Ask what “the website files” actually contain

If you receive a folder called “Final Website,” ask someone to walk you through it. Does it contain the images and copy? The editable design files? The code needed to run the site? Instructions for the next developer? What you should receive depends on the agreement and how the website was built. A custom website and a subscription-based website builder won’t necessarily have the same handover.

There are three useful questions here:

  1. What have we received? Identify the files, content and other deliverables included in the project.

  2. What can we use or change? Clarify any licence restrictions on software, photographs, fonts or other material.

  3. What would another provider need? Have the person taking over check whether anything essential is missing.

Be careful with the word “export.” For example, WordPress.com’s standard content export includes links to media, rather than the actual media files. There is a separate option for exporting the media library. So, if someone says all your content has been exported, ask whether the images and documents have also been saved. Keep the original service available until the required material has been checked. For a custom build, the incoming developer should review the code, instructions and services it depends on. As the owner, your job is to make sure that review happens before everyone considers the handover finished.

4. Find out what your monthly fee is keeping running

A maintenance payment may cover more than updates and support. It might also pay for your hosting, booking software, backups or the service that delivers enquiry emails. Before changing that arrangement, ask:

“If we stop this service, which parts of the website would we need to pay for or replace ourselves?”

That question is more useful than asking whether everything is “included.” Take a booking tool covered by the agency’s subscription. You’ll want to know whether:

  • Your business can take over the subscription.

  • You need to buy a separate licence.

  • Existing bookings and settings can move.

  • Someone needs to reconnect or replace the tool.

  • There is a date by which the work must be completed.

The same applies to less visible services. For example, your contact form might send messages through an agency-managed email service. Moving the website pages would not, by itself, resolve that dependency. Someone needs to arrange continued email delivery and test it before the old service ends. These are questions to settle while your provider is still available. They help you understand the work and cost involved in leaving, even if you have no plans to leave now.

5. Put the important details in one handover record

You shouldn’t have to search several inboxes to work out who looks after the website. Keep one record that points to the accounts, files and people involved. Use the checklist below during the handover meeting. For each item, add its location, the person responsible and anything still outstanding. Keep the passwords themselves elsewhere.

Item

What your business needs to know

What to check before closing it

Domain

Registrar, account access, recovery and renewal arrangements.

The correct account and renewal details have been checked.

Hosting or website platform

Provider, plan, billing, support contact and options for moving.

You know how another specialist would receive access or take over.

Website users

Who can edit content, manage users and carry out technical work.

Your own account has been tested and the necessary permissions confirmed.

Domain settings and email

Who manages DNS, the settings connecting your domain to website and email services.

The current setup is documented for whoever handles future changes.

Files and backups

Where the agreed files are stored, what backups include and who can restore them.

The recipient has checked the files; recovery arrangements and limitations are recorded.

Paid tools

What each tool does, who pays and what happens when the agency relationship ends.

Each essential service has a plan to continue, transfer or be replaced.

Search and visitor reports

Which reporting accounts belong to the website and who manages access.

The business can open the correct reports and arrange access for a new specialist.

Forms, bookings and orders

Which services support them and where the information goes.

The relevant customer journeys have been tested through to your team.

Use simple status labels: checked, needs action or not applicable. Include the date checked. An unfinished item should be specific enough for someone to act on. For example:

Domain renewal reminders go to a former employee. The operations manager will arrange the contact update by the agreed date and confirm the new details in the account.

That gives the next person something concrete to follow up.

6. Use the handover meeting to try things yourself

A demonstration can make everything look straightforward while leaving the person receiving the site unsure what to do. Let that person take the controls for a few ordinary tasks:

  • Sign in with their own account.

  • Edit and preview a draft page.

  • Find the renewal information.

  • Open the website’s search and visitor reports.

  • Send an agreed test enquiry and find it in the receiving inbox or system.

For a store or booking site, have the team test the relevant purchase or booking process too. Include the customer confirmation and the record your staff need to fulfil the request. Leave technical recovery tests to the person responsible for the website. Ask them to explain where backups are held, what they cover and whether a restore has been tested. Where appropriate, demonstrate restoration in a separate test environment.

If you take orders or bookings, ask what happens to transactions received after the backup was taken. That is a business question you should understand before relying on the recovery plan. Finally, confirm who handles problems after handover. Project support, ongoing maintenance and additional development may have different scopes or charges. Write down the contact and the date responsibility changes.

7. If something is missing, decide what it could interrupt

You may finish the review with several open items. Deal first with anything that could stop the site, email, enquiries or orders: a renewal due soon, an essential account nobody can access or a service about to be cancelled. Then address the gaps that would make recovery or a change of provider difficult. After that, finish the supporting documentation and file organisation. For every open item, record:

  • What needs doing.

  • Who will do it.

  • The agreed completion date.

  • How you will check that it is finished.

Keep existing services active until replacements have been verified. Once the new arrangements work, review the outgoing provider’s access and remove what is no longer needed. You can be happy with your agency and still ask for a thorough handover. It makes everyday changes easier for both sides. Six months later, when someone needs to renew a service or bring in a specialist, the answer should be in the record you already have.

Frequently asked questions

Does paying for the website mean I own every part of it?

Check the agreement for what you receive and the rights attached to it. Ask the provider to identify custom work, third-party licences and any excluded deliverables. Having a login doesn’t establish permission to reuse every component elsewhere.

Should my agency keep administrator access?

It may need that access for agreed maintenance or development. Use separate accounts and review permissions when the work or working relationship changes. Your business should retain a clear way to manage access.

What if my website is on the agency’s hosting account?

Ask how your site can be handed over, what files or data you can receive, how much notice is required and whether there are transfer charges. You need a workable arrangement for your website; you don’t need the agency’s shared master account.

Can I move the website to any other platform?

Ask the incoming provider to check first. Some material may transfer, while the design or features need rebuilding. Establish those limits before agreeing the migration scope or cancelling the existing service.

Can I ask for a handover if the website has been live for years?

Yes. Start by gathering invoices, account invitations and renewal emails, then review the gaps with your provider. Agree any additional work needed to organise files, document the setup or transfer services.

ARTICLE WRITTEN BY

Milan Gohil

I like looking beyond the obvious problem to understand what is really holding a business back. I write about the patterns, questions and practical lessons I discover while working through real challenges

ARTICLE WRITTEN BY

Milan Gohil

I like looking beyond the obvious problem to understand what is really holding a business back. I write about the patterns, questions and practical lessons I discover while working through real challenges

Book your strategy call

Book your call now

On this page
AI Summary

Book your strategy call

Book your call now

All Blogs

All Blogs & Articles

Two small paper browser windows connected by a sturdy orange bridge; a continuous thin black route crosses intact from old to new, with a small magnifying glass beside the destination..

Found

How to Redesign or Migrate a Website Without Losing SEO

Two understated cut-paper hands pass a single orange key above an open ivory folder holding a miniature website card and neatly arranged small tools.

Chosen

Website Handover Checklist: What Your Developer Should Give You

A single central paper website card branches into three distinct service cards carrying only simple object icons: a gear, a pencil and a wrench.

Found

How Many Service Pages Does Your Website Actually Need?

A small paper analytics panel with an unlabeled black line that dips; a large orange-rimmed magnifying glass examines a disconnected paper link below the chart.

Found

Why Your Website Traffic Dropped After a Redesign and What to Check First

A tactile paper branching pathway with a tiny dark human figure at its entrance.

Seen

How to Test Your Sitemap and Navigation Before a Website Redesign

A miniature paper shopping trolley carrying three simple product boxes crosses a broad orange bridge between two spare storefront cards.

Found

Ecommerce Migration Without Losing Product URLs, Feeds or Customer Journeys

Two small paper browser windows connected by a sturdy orange bridge; a continuous thin black route crosses intact from old to new, with a small magnifying glass beside the destination..

Found

How to Redesign or Migrate a Website Without Losing SEO

A single central paper website card branches into three distinct service cards carrying only simple object icons: a gear, a pencil and a wrench.

Found

How Many Service Pages Does Your Website Actually Need?

A tactile paper branching pathway with a tiny dark human figure at its entrance.

Seen

How to Test Your Sitemap and Navigation Before a Website Redesign

Two understated cut-paper hands pass a single orange key above an open ivory folder holding a miniature website card and neatly arranged small tools.

Chosen

Website Handover Checklist: What Your Developer Should Give You

A small paper analytics panel with an unlabeled black line that dips; a large orange-rimmed magnifying glass examines a disconnected paper link below the chart.

Found

Why Your Website Traffic Dropped After a Redesign and What to Check First

A miniature paper shopping trolley carrying three simple product boxes crosses a broad orange bridge between two spare storefront cards.

Found

Ecommerce Migration Without Losing Product URLs, Feeds or Customer Journeys

Before you invest in another fix, make sure it is the right one.

Your website may not need more pages, more content or another redesign. It may need clarity on what is actually holding it back.

Before you invest in another fix, make sure it is the right one.

Your website may not need more pages, more content or another redesign. It may need clarity on what is actually holding it back.

Something isn’t working as well as it should?

Your website may not need more pages, more content or another redesign. It may need clarity on what is actually holding it back.

© 2026 Webshunya Studio®. All rights reserved.