Business ownership
Website handover checklist: keep your business in control
A website may look finished while the business still depends on one person’s email address or laptop. A useful handover makes ownership, access and responsibilities clear enough that another authorised person can keep the service running.
Begin with domain and account recovery
Record the registrar, renewal date, billing contact and recovery process for the domain. Confirm who can change DNS and who receives important notices. Business-controlled accounts should remain recoverable if an employee or supplier leaves.
Use named access and appropriate roles where available. Share secrets through a protected password manager or vault, with a clear owner, rather than ordinary email or an unrestricted document.
List what the website actually needs
Include hosting, database, email, scheduled jobs, file storage, CDN, certificates and third-party integrations. A project can stop working even when its web server remains healthy if an overlooked service expires.
For each item, record its purpose, business owner, provider account reference, renewal responsibility and recovery route. Keep sensitive credential values out of this inventory.
Make the code and content usable
Obtain the agreed source code, deployment instructions, content exports and original assets. Check licences for themes, plugins, fonts and stock imagery, including whose account owns each purchase and whether it can be transferred.
Ask a second authorised person to follow the setup notes in an isolated environment. Missing build instructions and dependencies are much easier to fix while the outgoing supplier is still available. Contractual ownership should be confirmed against the actual agreement.
Transfer measurement and renewal responsibility
Check Search Console and analytics access through their current ownership and permission settings. Removing someone from a contact list is not necessarily the same as removing a verified ownership method. Follow the provider’s handover guidance.
Record upcoming payments, support arrangements and incident contacts. Confirm who monitors renewal failures and backup alerts. An automatic payment method still needs an accountable business owner.
Complete the handover with a small exercise
Verify a controlled deployment, a backup restore and an important user journey. Review old supplier access and revoke what is no longer required after the agreed transition. Keep an audit of the changes and a way to escalate unresolved items.
Mesh Creation can help turn scattered accounts into a clear website inventory and handover plan, then address the missing access or operating documentation in a controlled order.
Ask for a handover register, not a password message
Use one row per service: domain registrar, DNS, hosting, mail, source repository, analytics, Search Console and paid plugins. Record the legal/account owner, recovery contact, renewal date, billing responsibility and how a replacement operator receives access. Share credentials through an appropriate secure vault, not in the register itself.
In Google Search Console (opens in a new tab / नए टैब में), ownership and user permissions are different. Removing a user does not necessarily remove an ownership verification token. Review the verification methods as part of offboarding rather than assuming one deleted login removes every route back in.
A handover acceptance test for the owner
Ask the receiving team to deploy a small approved change, restore a test backup and show where renewal notices arrive. Check that the domain’s registrant/account arrangement, DNS and source repository are accessible to the intended owner.
Record outstanding licences, inaccessible accounts and dependencies explicitly. Agree who resolves each gap and by when. Finish with the list of access that can now be revoked and the operator responsible for doing it; keep a recovery route until the handover checks pass.
Reader conversation
Share your experience
What has worked for you, or what would you like to know about this topic?
1. Verify your email
Choose Send code to receive a verification email. Your email address stays private.
2. Write your comment
Verify your email before submitting a comment.
Reader comments