Website handover checklist: what the owner needs to control

By IGEARS TECHNOLOGY LIMITED · Reviewed 2026-09-13

Scenario: you can edit pages but cannot change supplier

In this illustrative scenario, a business has an Editor account and copies of the original design.Read more

A new supplier still cannot move DNS, access the database or renew a key plugin. The acceptance test should be whether an authorised replacement team can operate and recover the whole service, not merely whether a password was emailed.

Accounts and recovery routes

Use organisation-controlled accounts with delegated access for suppliers. Verify recovery email addresses and MFA recovery methods without sharing personal passwords.

Supporting detail

Domain registrar, registrant details, renewal billing and transfer procedure.
DNS, CDN, TLS certificates, hosting and cloud account roles.
WordPress administrator access, database access and file access appropriate to the hosting service.
Email delivery, analytics, Search Console, payment gateways and integration accounts.

Files, data and source code

Obtain a full database backup and website files, including uploaded media, themes, plugins and configuration. Confirm how secrets will be transferred securely and rotated. Request custom source code and build instructions where your agreement provides them; check licences for fonts, images and third-party assets. A screenshot, static HTML copy or WordPress WXR export alone is not a complete recovery package.

Licences and third-party services

List the legal account holder, renewal dates, installed edition and dependencies.Read more

Agree whether the subscription transfers, the owner buys a replacement, or the feature is rebuilt. Never assume an agency-wide licence can simply be transferred. Document consent records, form destinations, translation services and scheduled integrations so those connections do not silently stop.

Prove the handover on staging

Restore the package to a separate protected environment with the new team.Read more

Test sign-in, page editing, menus, search, forms, mobile layouts, translated links and any checkout or membership flows. Compare a sample of records and attachments. Document scheduled tasks and confirm monitoring, backup frequency, retention and a successful restore.

Close the engagement in an agreed order

Agree deliverables, legitimate fees, the cutover window and acceptance criteria before removing the old provider.Read more

Preserve the original service until the replacement passes its checks. Then rotate secrets, revoke obsolete delegated access and record responsibility for renewals and support. If ownership terms are disputed, obtain advice on the actual agreement; technical access alone does not settle contractual rights.

Ask IGEARS to verify the handover

IGEARS can review the inventory, witness a restore and identify missing access or documentation. The deliverable should be a clear gap list and an agreed remediation scope, with the customer able to choose a future maintenance provider.

Sources and verification

Policies and features can change. Verify the current terms and your installed edition before implementation.