Website Handover Checklist for Small Business Owners

A website handover should leave the business able to operate its site without relying on one person. A folder of files is only part of that result. Verify account access, recovery options, working copies, renewal responsibilities, and a practical support route before calling the handover finished.

Inventory the website accounts

List the domain registrar, DNS service, hosting, website editor, email provider, forms, analytics, and any paid extensions. Record the business purpose and account owner for each. Include renewal dates and who receives billing notices. Do not place passwords or recovery codes in this inventory document.

Verify business access independently

Have an authorized business representative sign in with their own account while the outgoing provider remains available. Check that the role permits the necessary administration. Verify recovery email and multifactor setup. A screenshot of another person being logged in does not establish that the business can recover access.

Separate domain and hosting changes

Document where the domain is registered and where its DNS records are managed. These may be different from the website host. Record the current arrangement before making changes. If a registrar transfer is needed, check its eligibility and instructions first; do not combine unrelated moves merely to finish a checklist.

Test a usable website backup

Request the site files, content, configuration, and other exports appropriate to the platform. Note what an export does not include. Restore a copy in a safe test environment if the platform supports it. Confirm the recovery procedure with the owner rather than treating a downloaded archive as proof of recoverability.

Check the business workflows

Walk through a content edit, image replacement, form inquiry, and any booking or purchase path that applies. Use test modes or harmless inquiries where available. Check who receives notifications and how they respond. Record the steps a colleague would need to repeat these tasks without the original provider present.

Close the website handover deliberately

Agree who handles updates, outages, renewals, and future changes, then store that contact route with the inventory. Remove obsolete access only after the business confirms its own access and recovery work. Keep a dated acceptance record listing unresolved items and their owners, rather than calling an incomplete handover finished.

A practical working record

Use a simple acceptance table with one row per system: owner, access verified, renewal owner, recovery route, and open issue. Mark an unknown value as unresolved rather than guessing. For example, a business may control its website editor but still depend on a former contractor for domain renewal. That is a distinct handover item even if the public site looks fine. Ask for source design files and content permissions where relevant, and document any assets or subscriptions that do not transfer. The checklist is an operating aid; it does not change the terms of your existing contracts.

Source and next steps

ICANN explains domain transfer procedures and circumstances that can restrict a transfer. Check the current registrar instructions before planning that part of a handover. The broader operating checklist above is our suggested process. Read the primary guidance.

Use our website speed guide when checking page performance. For a repeatable review routine, see our small business publishing schedule.

A useful handover record is short enough to use during an outage. Keep account locations, responsible people, backup instructions, and unresolved items together, with secrets stored separately. Could your business update and recover its website without the original builder? Verify that ability while help is still available.