How to hand over a site to a client, domain included
Handing over a project in Tuqo is one button: Transfer on the site’s Settings tab. The whole site moves into the client’s account, together with the domain, the certificate and the version history, and you stop paying for its hosting. No archive to export, no domain to attach again, no DNS to change: the A record keeps pointing at the same serving address.
Step 1. Open the transfer card
Site page → Settings tab → the Move site card. Only the project owner sees it; an admin or an analyst won’t. At the bottom of the card is the Transfer to another user block.
Step 2. Enter the recipient
Two ways: by email, the address the client signed up to Tuqo with, or by ID, the numeric ID of their account. The ID is shown in their profile, which helps when someone signs in with Yandex ID or VK ID and doesn’t remember which address was used. Click Transfer, and a line appears: “Transfer created — waiting for the recipient to accept the site.”
The client must already have a Tuqo account before the transfer: the site goes to a specific account, not “to an email”. If they don’t have one yet, they can create a free account and upgrade to a paid plan; it takes a minute.
Step 3. The client accepts the site
They get a notification under the bell icon and a banner on the projects page. They click Accept and choose which of their projects gets the site.
While the transfer is pending, the site keeps working in your account: its addresses open, forms accept submissions, auto-deploy publishes. A pending transfer lives 24 hours, then expires by itself. You can cancel it at any time before it is accepted, and the client can decline it.
What moves and what doesn’t
Moves with the site:
- the system subdomain
name.tuqo.ruand every attached domain, with ownership verification and the certificate: no re-verification and no downtime; - the whole version history: the client can roll back to any kept build;
- the site’s settings: kept versions, access restrictions, the Git CD connection.
Stays with you or is switched off:
- submissions received before the transfer stay in your project: they are part of your negotiations, and the monthly form quota is counted per owner. New submissions go to the new owner;
- submission recipients you assigned to this site are removed, otherwise you would keep getting emails about someone else’s clients. The new owner assigns their own;
- site add-ons you bought (no badge, site password, email code, paid access) are switched off: you paid for them, and you can’t be billed for someone else’s site. The client turns on what they need on their side;
- build preview links you handed out are revoked in the same operation: a secret link you sent someone no longer opens the new owner’s content;
- API keys and AI connections belong to the project and stay with you. If the client wants to edit the site through an AI agent, they connect their own project.
Why both sides need a paid plan
Sending and accepting sites is available from the Start plan (590 ₽/mo), for both the sender and the recipient. This guards against dumping junk between freshly created free accounts. It also solves a practical problem: the Free plan has no custom domains, so the client’s domain wouldn’t be enabled anyway. Prices are in rubles; the pricing page shows approximate dollars and euros.
One more check is the recipient’s site limit. If all their slots are taken, accepting fails with a clear message: they need to free up a slot or move to a bigger plan. Limits per plan are on the pricing page.
Partner commission
After the transfer, the client pays for hosting themselves, and you get a share of their payments through the partner program: 30% in the first year, 20% in the second and third, 10% in the fourth and fifth. For the commission to apply, bring the client in through your partner link before they sign up. Terms and stats are on the partner program page (in Russian).
If you keep maintaining the site
Then don’t transfer it. Keep the client in a separate project and invite them as a member with the Analyst role: they will see analytics and submissions but won’t be able to deploy or touch billing. Moving a site between your own projects is instant, with the Move button on the same card: domains, versions, submissions and their recipients all move with the site. How studios usually set this up is described on Tuqo for web studios (in Russian).
FAQ
Will the site be down during the transfer?
No. Until the client accepts, the site works in your account; at the moment of acceptance only the owner of the record changes. Addresses, certificates and the active version are not touched, so there is no break in serving.
What happens to the domain and SSL?
The domain moves already verified, so there is no DNS to change: the A record and
_tuqo-verify at the registrar stay as they are. The certificate keeps renewing
automatically. If something doesn’t open, the causes are covered in the guide
domain not working after setup.
Can I cancel a transfer?
Yes, until it is accepted: you have a cancel button, and the recipient has Decline. After 24 hours an unaccepted transfer expires by itself and the site stays with you. There is no reverse transfer: if you picked the wrong recipient, cancel and send it again.
How do I give the client the site before payment, but not for good?
Don’t transfer it; show it. Gate the demo with a password, or send a secret build preview link that doesn’t go live at the real address. Both are covered in the guide on sharing a mockup with a client.