WordPress Website Handover Checklist

Your WordPress website is live. Before you close the project, can your team update a service, receive an enquiry and find the person responsible when something stops working? A website handover checklist helps you answer those questions while the developer is still available.

This guide is for business owners in India receiving a new website or moving to a different support provider. Use it alongside your agreed project scope. The aim is a usable handover: clear access, understandable running costs and evidence that the essential business tasks work.

WordPress website handover checklist: the essentials

Confirm the business can access the accounts it is meant to control.
List the services that renew, their billing frequency and who pays.
Check that a recoverable backup includes the required website data.
Complete everyday editing and enquiry tests with your own staff.
Record unfinished work, support responsibilities and next steps.

Keep account access details in an appropriate secure system. Your handover worksheet should identify the account and responsible person, not expose passwords or recovery codes.

Domain, hosting and WordPress access: check them separately

Being able to log into WordPress does not demonstrate that you can renew the domain or manage hosting. Ask the developer to identify the provider for each service and show the authorised business contact how to sign in.

For domain and hosting accounts, check which email address receives renewal messages. Confirm that the business can access that mailbox. A reminder delivered to an inactive address does little to prevent an avoidable expiry.

For staff who only edit content, choose access that suits the task. WordPress provides different roles and capabilities; not everyone who uploads a blog post needs administrator permissions. Keep individual accounts so responsibility is easier to understand.

Website renewal costs: make the second year visible

A first-year package can combine several services into one amount. Ask for a separate renewal list before accepting the handover. Include the domain, hosting, email, paid theme or page builder, extensions and any maintenance arrangement.

For each entry, record the renewal date, billing currency, whether taxes are additional and whether the amount is an introductory price. Ask what happens if an agency-owned licence is no longer available. The answer may involve buying a replacement licence or changing a feature, so it should be known before the support relationship ends.

Here is an illustrative comparison: Proposal A includes one year of hosting but excludes future content edits. Proposal B includes a limited monthly editing allowance but bills hosting separately. Neither is automatically better. Your worksheet should make the differences visible so you can budget for the work you actually need.

WordPress backup handover: ask for recovery evidence

Ask where backups are stored, how often they run and who can restore them. WordPress’s backup documentation explains the importance of both database and file backups. A content export alone should not be treated as a complete recovery package.

Request a restoration demonstration in a separate, controlled environment. Record when the backup was taken and what was successfully recovered. A backup status labelled “successful” is less useful than knowing the incoming team can actually use it.

For a live store, ask how orders received after the backup would be protected during recovery. Do not restore an old copy over production merely to test whether it works.

Website acceptance testing your team can perform

Use a short working session with the employee who will maintain the site. Let that person carry out the tasks rather than only watching a developer demonstrate them.

Edit a service: change an agreed test paragraph, preview the result and restore the original wording.
Publish content: prepare a draft article with a heading, link and image; confirm who reviews it before publication.
Send an enquiry: submit a clearly labelled test message and verify where it appears, including any notification email.
Check a phone journey: use the menu, read a service page and follow the contact action on an actual phone.
Find a report: confirm the authorised business user can access the agreed analytics and search reports.
Report a problem: locate the support contact and explain how urgent issues are distinguished from routine edits.

For an online store, add the relevant checks from our WooCommerce checkout testing checklist. Store operations require more than checking a contact form.

Copyable website handover worksheet

Copy the following fields into your project notes. Complete one record for each account, service or business-critical feature.

Item: the account, service or feature being handed over.
Purpose: what the business uses it for.
Business contact: the person responsible for decisions.
Access checked: who signed in or performed the task, and when.
Renewal: billing frequency, next date and confirmed amount or quote reference.
Acceptance evidence: the completed check or location of the test record.
Open issue: what remains, who will resolve it and the agreed date.

For example, an enquiry-form record might say: “The office coordinator submitted TEST-01 from a phone; the message appeared in the agreed inbox; the reply-to address worked; no open issue.” This is an illustrative record, not a result from a Vylino client project.

Changing WordPress developers without losing the handover trail

Agree the transition sequence with both providers. First establish the incoming team’s authorised access and responsibilities. Then verify the essential workflows before retiring access that is no longer needed.

Ask for a list of custom features and where their instructions are kept. A booking rule, an enquiry integration or a custom product field may not be obvious from the homepage. The new team needs to know which behaviour is intentional before changing it.

Keep the existing URL list and record any proposed changes separately. Switching support providers does not, by itself, require a redesign or a change to public URLs. If a migration is required, use a separate migration scope and acceptance plan.

Post-launch support: agree what happens after sign-off

Separate correction of an agreed defect from a new feature request. Record the support window, contact channel, working hours and any response commitment in the proposal. Do not assume that “support included” means unlimited edits or round-the-clock availability.

A practical sign-off has three groups: accepted items, outstanding items with owners, and work outside the current scope. That makes it easier to close the build while keeping genuine unfinished work visible.

WordPress handover FAQs

Is an administrator password enough for website handover?

No. The business also needs the agreed account access, renewal information, operating instructions and a recovery arrangement. An administrator login is one part of that package.

Should I ask for a recorded training session?

A short task-based recording can be useful. Ask for the actions your team will repeat, such as updating service text or checking enquiries. Keep credentials and private customer information out of the recording.

What if some items are not ready?

List them explicitly with an owner and an agreed next step. A missing decorative image is different from a form that loses enquiries; prioritise according to the business impact.

Need help reviewing your WordPress handover?

Vylino can discuss a scoped review of the website, access checklist and outstanding work for businesses across India. Share your website URL and a description of what has been delivered. Send account invitations through the relevant service when access is needed; do not send passwords in an enquiry.

Discuss your website handover on WhatsApp or email contact@vylino.com. Explore our WordPress development services for a new project.