The website is finished and paid for. Two years later, though, you find you can't change even the phone number without the original vendor, because the domain and the passwords stayed with them. This can be prevented at handover.
How vendor lock-in happens
It's rarely bad intent. The vendor registers the domain in their own name because it's faster, and buys paid plugins on their own account. They keep the passwords because they manage the website anyway. While the cooperation runs, nobody minds. The problem comes when you part ways, the vendor stops answering or closes the business.
The new vendor then starts by working out who actually owns what. Sometimes that costs more than a new website.
What to ask for at handover
- The domain registered to you. The holder should be your company or organization, not the vendor or their managing director. The management, meaning renewals and DNS, can stay with the vendor.
- Access to everything the website runs on: hosting, website admin, database, FTP, DNS, email mailboxes. Handed over in writing, not just read out over the phone.
- Source code in an archive from which the website can be built again. Without passwords and without internal notes, those belong with the access details.
- A license that explicitly allows anyone to edit the website, another vendor included.
- Documentation: how the website is deployed, where backups run and how they are restored.
- A manual for the people who will edit the website, written for them, not for programmers.
- Licenses for paid plugins and services in your name. Where that's not possible, at least a list of what is paid for and when the licenses expire. Why this matters is shown in the article about Elementor Pro.
On a website for a school, the domain was registered to our managing director. Before the handover we transferred it to the school, and in the license we wrote that another vendor may also edit the website and that the school receives the source code.
Why the license matters
Under the Czech Copyright Act (autorský zákon), a website is a work, and you need to know who may do what with it. For a computer program created to order, Section 58(7) of the Act provides that the economic rights (majetková práva) are exercised by the client who ordered it, unless the parties agree otherwise. If the vendor keeps the rights in the agreement so they can reuse the code, that's fine. What matters is that the agreement leaves you the right to edit the website, also through a third party, and the right to the source code. A license without the code is just paper.
One more thing belongs in the operation and support contract: what happens when you leave. Who hands over the data, backups and access, and by when, if you end the cooperation.
How to check the handover
- Check in the public WHOIS or with the registrar who holds the domain.
- Log in to the hosting and the website admin yourself. Not through the vendor, but with your own credentials.
- Unpack the source code archive and check that there are no passwords in it.
- Give the manual to the person who will edit the website and have them change one piece of text by following it.
- Store the access details in a password manager that more than one person can access.
If any step doesn't work, you know what is missing while the vendor can still be reached.
When you take over a website from someone else
The process is the same, just in reverse. Start with the domain, because without it nothing else makes sense. Then hosting and access. On a WordPress website the source code usually sits on the hosting. On a custom website you may not be able to get it without the original vendor. That's why you should ask for it before you part ways.
When to call in an expert
When you're taking over a website and don't know everything that belongs to it, or when you want to check that you got everything you should have at handover. We go through the domains, hosting, licenses and code and write down what you have, what is missing and whom to ask for it.