Fill in these first
- Business and website: [e.g. a dental clinic chain with a booking website]
- Who built and runs it: [agency or freelancer, and the contract end date]
- What is known about ownership today: [e.g. the domain is registered in the agency's account, unsure about hosting]
- Services in use: [domain registrar, hosting, email, analytics, ad accounts, payment gateway, plugins or paid themes]
- Contract terms on ownership of code and content: [paste the relevant clause, or none]
- Handover deadline: [date]
Task
Make sure the business owns and controls every part of its website before the relationship ends.
Output format
- A note at the top: "This is not legal advice. If ownership of the domain, code or content is disputed, consult a qualified lawyer."
- | Item | Current owner of the account | Action needed | Who does it | Done |, covering domain, DNS, hosting, source code and repository, database backup, email, analytics, search and ad accounts, payment gateway, paid licences, fonts and images, and documentation.
- Access rules: the business holds the main owner login for every account; the agency keeps only user access until the end date, then it is removed.
- Handover request letter to the agency, under 250 words, polite and specific, with a deadline.
- Sign-off form listing each item received, for both sides to sign.
- Checks after handover, such as renewing the domain from the business's own account.
Rules
- Never ask for passwords to be sent in plain email or chat; request transfers or new invitations instead.
- Licences bought in the agency's name may not transfer; flag them for repurchase.
- Keep a full backup in the business's own storage before any account is closed.






