Website access handover: what your contractor must give you
Website access handover is the moment a project stops being your contractor's work and becomes your asset. Until you hold the credentials, you use the site with the contractor's permission, and a studio can close or simply stop replying. Below: what to collect, how to verify it at acceptance and what to do if access is already lost.
Website access handover: the full list
Start with the domain. You need the registrar account, and your company must be listed as the owner (registrant). Check this in the registrar's dashboard or in the public domain record, where the zone shows one. If the owner is the contractor or one of its employees, the domain is not yours, legally or in practice.
Next come hosting or the server: the control panel, SSH or FTP access and, if the site lives in the cloud, the cloud account itself. Ask separately for the site admin panel (CMS) with a superuser role, access to the database and the regular backups.
For a custom build, add the source repository (GitHub, GitLab or similar), build and run instructions, and the list of environment variables. Without them the site keeps running, but nobody except the author can realistically develop it further.
The last layer is services: Google Analytics, Yandex.Metrica, Google Search Console, the Google business profile, domain email, SSL renewal, the CRM and the Telegram bot token if the bot receives enquiries. Keep a table: service, login address, account email, owner and whether two-factor protection is on.
Why it matters for the business
Without registrar access you cannot migrate the site, change contractors or renew the domain if the studio stops answering. When the domain is registered to the contractor, your address, the business cards that print it and the search positions built over the years depend on someone else's goodwill.
Without analytics and Search Console you cannot see the real picture or verify the contractor's reports. Without backups you cannot restore the site after a hack or a hosting failure. Without source code, every change turns into a migration or a rewrite.
This is not always about bad intent. Studios close, staff leave, and the site keeps bringing enquiries. Handover is insurance against ordinary life, not distrust.
How to accept access at delivery: a step-by-step check
A few days before acceptance, ask for a list of all accounts and compare it with the table above: domain, hosting, CMS, database, code, analytics. If something is missing, say so at once, not after the final payment.
At the meeting, log into every panel from your own device instead of watching the contractor's screen. Then change any password the contractor knew, switch on two-factor protection and store the backup codes somewhere safe.
Check permissions, not just login. Try adding a second user, changing domain settings, downloading a backup and opening the repository. If any action is blocked, your account is restricted: access exists on paper, control does not.
Record the result in the acceptance act: the list of handed-over credentials, the date and who received them. Tie the final payment to this check so the question does not slide into 'we will send it later'.
Common mistakes and where to keep credentials
The most common mistake is accounts created on the personal email of a developer or manager. You can log in, but notifications and password recovery go to someone else. Ask for the owner to be moved to a company email.
The second is receiving a password without the second factor: the code goes to the contractor's phone. The third is hosting and domain payments tied to the contractor's card, so the site goes offline at the worst moment if the card is blocked. The fourth is paid plugins and template licences registered to the studio.
Keep credentials in a password manager or a protected document that the owner can open, not only the marketer who may leave. Do not leave them in Telegram chats or in notes on someone else's phone.
Review the table every quarter and change passwords whenever someone involved with the site leaves.
What to do if access has already been lost
Start with the domain: registrars have a recovery procedure based on company documents. If the domain is registered to the contractor's legal entity, you will need an official request to it and possibly to the registrar. It is a long road and the timing depends on the registrar and how complete your documents are, but it exists.
Hosting and analytics can be recreated as a last resort: move the site to new hosting, install new counters and re-verify ownership in Search Console. You lose the statistics history but regain control.
The costliest loss is source code. Without it a new contractor will most likely propose rebuilding the site. So first ask the previous contractor for at least a code archive and a database export.
FAQ
Can the domain stay with the contractor if they promise to renew it? Better not. The domain is your address on the internet and the company should be the owner. The contractor can be the administrator or technical contact, but not the registrant.
Do I need source code if the site is on a website builder or a ready-made CMS? On a builder there is no code, but you need the builder account itself and access to the subscription. For a CMS you need the site files, the database and the list of installed plugins.
What if the contractor refuses to hand over access? Check the contract first: handover should be written into it. Then send a written request with the list and a reply deadline, and keep the correspondence in case you need a lawyer.
How do I agree on this before work starts? Put the handover scope into the contract or the technical brief. If you order a website from 4 Digital (turnkey website development starts at 1 399 000 UZS), the list can be agreed at the start and verified at acceptance using the scheme above.