Website Provider Handover Checklist: Secure Access and Assets Before You Leave

What should a small business secure before leaving a website developer, platform or hosting provider?

Create a business-owned handover register before giving notice or cancelling anything. List the domain, DNS, hosting, CMS, content, media, email-related settings, analytics and other connected services; record who owns each account, who has administrator access, where renewal and recovery messages go, whether a usable export exists, the next action and the person responsible. Resolve critical access gaps before choosing the cutover date, and do not place passwords or recovery codes in the register itself.

Set the handover boundary

Hypersite lists changing a CMS, moving to a new host and changing domain names as common website migration types. State which relationship is ending, then list the services and assets that could be affected by that change. Treat the domain, DNS, hosting account and website platform as separate dependencies unless the business has verified that they are controlled together.

Sources: Website Migration: Complete Guide to Migrating Your Site Without Losing SEO Rankings | hypersite.

  • Name the relationship ending.
  • List services that may be affected.
  • Avoid assuming all services sit with one supplier.

Build the business-control register

Create one row for each dependency and record its supplier, account owner, administrator, renewal contact, recovery route, export status, next action and responsible person. Use plain dependency labels that a non-technical owner can check, such as domain and DNS, hosting, CMS and content, forms and integrations, or analytics and connected services.

Use the guidance on how to manage recurring website tasks to assign a continuing internal owner or technical provider to each responsibility found in the register.

  • Use one row per dependency.
  • Record control and recovery information.
  • Assign a responsible person and next action.

Check accounts without recording secrets

Test whether the business can sign in through an authorised route and whether recovery messages reach a business-controlled contact. Record the location and responsible custodian of secure credentials, but do not put passwords, secret keys or recovery codes in the register.

Apply practical AI website governance rules when defining access, approval and accountability around website work.

  • Test sign-in and recovery routes.
  • Keep secrets out of the worksheet.
  • Record gaps and a safe next action.

Identify assets that may not transfer cleanly

Ecomzier says platform changes can require design and URL changes because of technical limitations. Review themes, templates, licences, custom code, integrations and exportable content, then mark each item for transfer, rebuilding, replacement or retirement. Do not promise customers an unchanged feature until its behaviour on the destination has been checked.

Sources: A Guide to Website Migration.

Use the process to validate a vibe-coded website when a component must be rebuilt rather than transferred unchanged.

  • Review themes, templates and custom components.
  • Check licences and integrations.
  • Mark transfer, rebuild or retirement decisions.

Resolve critical gaps before giving notice

Pause the exit when the business cannot access or transfer an essential account, lacks a usable export for a critical asset, or has no recovery route for a dependency needed to operate the site. Recover business control, obtain current exports, document unresolved dependencies and confirm transition assistance before choosing the departure date. Before cancelling a service or making another irreversible change, confirm the provider’s current transfer, recovery and cancellation prerequisites in its own documentation.

  • Recover essential control first.
  • Obtain current exports next.
  • Document unresolved dependencies before selecting a date.

Business-control and handover register

Create one row for each actual website dependency. Record its supplier, account owner and administrator, renewal and recovery contacts, export status, next action and responsible person. The register is not a place for passwords, secret keys or recovery codes.

DependencySupplierAccount owner and administratorRenewal contact and recovery routeExport status, next action and responsible person
Domain and DNSRecord supplierRecord account owner and administratorRecord renewal contact and recovery routeRecord export status, next action and responsible person
HostingRecord supplierRecord account owner and administratorRecord renewal contact and recovery routeRecord backup or export status, next action and responsible person
CMS and contentRecord supplierRecord account owner and administratorRecord renewal contact and recovery routeRecord content export status, next action and responsible person
Forms and integrationsRecord supplierRecord account owner and administratorRecord renewal contact and recovery routeRecord configuration export status, next action and responsible person
Analytics or connected serviceRecord supplierRecord account owner and administratorRecord renewal contact and recovery routeRecord export status, next action and responsible person

Keep sensitive credentials in an appropriate secure system. Before cancellation or another irreversible change, check the provider’s current transfer, recovery and cancellation prerequisites in its own documentation.

When this is not the right approach: This checklist does not replace legal, contractual or specialist security advice when ownership is disputed, an account is inaccessible or a critical service is compromised. Use it to identify the gap and obtain appropriate help.

What follow-up questions matter most?

What belongs in a website handover register?
Include services that could prevent the business from operating, receiving enquiries or recovering the website. Typical categories include the domain and DNS, hosting, CMS, content, media, forms, analytics and connected services, but the register should reflect the actual site.
Should the register contain passwords or recovery codes?
No. Record where secure recovery information is governed and who can use it, but keep passwords, secret keys and recovery codes in an appropriate secure system rather than a handover worksheet.
Which gaps should delay leaving a provider?
Delay notice when the business cannot access or transfer an essential account, lacks a usable export for a critical asset, or has no documented route to recover a dependency needed for the website to work.

What steps does this workflow follow?

Build a business-control handover register

  1. Set the boundary: State which provider relationship is ending and which services, accounts and assets may be affected.
  2. Create one row per dependency: Record the supplier, ownership, administration, renewal, recovery, export and action details for each dependency.
  3. Verify access safely: Test business-controlled sign-in and recovery routes without placing secrets in the register.
  4. Review transfer gaps: Mark components that may require replacement or rebuilding rather than a simple transfer.
  5. Resolve before notice: Recover control, obtain exports and document unresolved dependencies before choosing a departure date.