0% Loading page…

XimiTech

What should a business own after its website is built?

Website ownership checklist for businesses: domain, source code, data, admin accounts, analytics tools, documents and rights to third-party assets.

A well-managed handover lets a business continue operating or change partners without losing control. Here are the accounts, data and documents to review.

Handover questions often arise just before acceptance, when source code and accounts already exist. To avoid dependence on one person or provider, agree on an ownership list within the project scope. Handover means more than sending an administrator link: it enables continued control and operation of the asset.

Website ownership checklist to document

ItemWhat the business needs to receive or confirm
Domain and DNSRegistered owner, recovery email, registrar, renewal date and DNS access.
Hosting or serverProvider, owner account, backup and recovery methods, and renewal information.
Source codeThe source repository or handover package, running and deployment instructions, and contractual usage rights.
Website administrationPrimary and backup admin accounts, with instructions for granting or revoking role-based access.
DataData export methods, important data structures, backup locations and authorised access.
MeasurementOwnership of GA4, Search Console, advertising tools and related integration accounts.
Third-party assetsList fonts, plugins, libraries, images, paid services and license conditions.
DocumentationAcceptance scope, administration guidance, deployment information, warranty and support contacts.

Distinguish ownership from access

Receiving an account does not necessarily mean the business owns it. A domain registered to a supplier’s personal email, for example, can make recovery or switching providers dependent on that person. Use a business-controlled email for primary accounts, enable appropriate authentication and give each person only the access they need.

Source code, design, content and licensed third-party software may have different usage conditions. Do not assume every component transfers alike; read the terms and specify in the contract what the business owns and what it is licensed to use.

A concise but complete acceptance and handover process

  1. List accounts and the person responsible for each item.
  2. Test the business account login, recovery email and two-factor authentication where supported.
  3. Test exporting data or downloading a sample backup to ensure the team knows how to retrieve its assets.
  4. Request instructions for content updates and everyday tasks.
  5. Record unresolved issues, warranty periods and support request procedures in writing.

Test a handover scenario before signing acceptance

A simple test is to imagine the person responsible leaves today and your current provider stops supporting you tomorrow. Can their replacement recover domain access? Do they know where form data is stored? Are there instructions for deploying a new version or restoring a backup? If not, record the missing information in the handover document and assign a recipient.

  • Store account details in the business's password manager, rather than scattered messages.
  • Record account owners separately from those granted operating access.
  • Test a data or backup download to confirm its format and storage location.
  • Check support links, warranty duration and the limits of covered work.
  • Confirm assets with recurring fees, renewal dates and who is responsible for payment.

When changing providers, do not revoke all old access before checking the live system and arranging replacements. List dependent services, create new access for the receiving team, test operations and then remove unnecessary permissions. This maintains service continuity and reduces access loss caused by rushed actions.

If you are preparing a new project, include this checklist when agreeing scope, alongside the terms in what a website design contract should include. A suitable website design provider will explain clearly how the business retains control after handover.

Frequently asked questions

Should the business own its domain?

Yes. Register the domain using business-controlled information and email, with someone responsible for renewals and recovery details.

Does every website include full source code handover?

Source code scope and usage rights depend on the contract, technology model and third-party licences. Both parties should document them before starting.

Should you receive an administration guide?

Yes. Documentation helps business staff update content and perform everyday tasks without depending on the website builder.