How to stop a developer handover from going wrong
Know which five accounts must sit in your own name, what belongs on a handover list, and how to test a handover before the final payment.
The site you paid for and cannot move
The developer stops replying. Or the relationship ends politely and then you discover the domain is registered in their name. The hosting sits inside their reseller account. The premium theme licence belongs to their agency. The analytics property was created on a personal address. You own a website in every sense except the ones that let you move it.
This is rarely malice. Small studios set things up on their own accounts because it is faster and nobody asks otherwise. The cost arrives years later when you want to change supplier and find that leaving requires permission from the person you are leaving.
What a build quote excludes and what ownership costs
Exclusions first. A build quote usually excludes handover documentation. It often excludes design source files. It almost always excludes third-party licences which are frequently non-transferable and have to be bought again in your own name. It excludes ongoing maintenance unless a retainer is stated. Assume none of these are included until you read the words that include them.
Getting ownership right is cheap in money and real in effort. You will pay annual fees you may currently be paying through someone else. A registrar fee. A hosting plan. Perhaps a theme or plugin licence repurchased in your company name. Service fees in India carry GST at 18%. The larger cost is a few hours of administrative work and the willingness to hold an awkward conversation before the final invoice rather than after it.
Who needs full handover and who should not ask for it
Do not demand code repository access and self-hosting if you have nobody technical and no intention of hiring one. Credentials you cannot use are not safety. They create the illusion of control while the site drifts without updates. A business with no technical capacity is usually better served buying a managed arrangement where someone is accountable for the site staying up and where the contract says what happens if you leave.
Also accept the limits of your platform before you sign. On several hosted website platforms the code is genuinely not portable. You can export your content and nothing else. That may be an entirely sensible trade for a small business and it is only a problem when discovered in year three.
Everyone however should own the registrar the DNS the hosting account the content management login and the analytics property in their own company name. There is no business small enough for that to be optional.
The handover list and when to use it
Open the five accounts yourself in a company email address that outlives any individual employee. Not a personal address and not the developer's. Then invite the developer in as an administrator. Reversing this later is possible and it is far more work than doing it at the start.
Agree a written handover list before the project begins and tie the final payment to it. The list should name credentials for every system, licence keys with proof of purchase, design source files in an editable format, the font licences and what they permit, a written inventory of plugins with renewal dates, a plain-language note on where the site is hosted and how to deploy a change, and a database and file backup you have downloaded yourself.
Then test it. Take the backup and restore it somewhere else. Log in to every account from your own machine with the developer absent. A handover that has never been exercised is a claim and not a fact.
The test that tells you the handover was real
The metric that matters is whether a second developer given only your documents and credentials could deploy a small change without contacting the first one. Ask someone to try. A paid hour of an independent developer reading your handover pack is the cheapest insurance available on a website.
The flattering signal is holding a password. People assume a login means ownership. A content management login does not let you move hosting. Hosting access does not let you transfer a domain. Each layer has its own key and a handover is only as good as the weakest one.
The mistake that removes all your leverage
The common mistake is clearing the final invoice before the handover list is complete and tested. The moment the payment lands your position changes entirely. Requests that were contractual obligations become favours. Most handovers that go wrong were not refused. They were simply never finished because nothing depended on finishing them.
This is expensive in a specific way. The replacement cost is not the handover work. It is rebuilding a site that already exists and already ranks because nobody can get inside the one you have. Hold back a meaningful final portion until a restore has been tested.
Who owns the code is a contract question
Ownership of the code and the design is determined by what your agreement says rather than by who paid. Commissioning work does not automatically transfer copyright in every situation and an assignment in writing is the normal mechanism for making the position clear. Open-source components carry their own licence terms which continue to apply whatever your contract says. A qualified professional should confirm how this applies to your specific agreement before you rely on it.
This guide explains how something works. It is not legal, tax or financial advice, and rules change. Confirm anything regulatory with a qualified professional before you act on it.