How to transfer form ownership to a client (without handing over your whole backend)

Every client project ends the same way: invoice sent, site live, and one small loose thread - the contact form is still pointed at your account. It works fine, which is exactly the problem. Six months later the client emails asking why their leads aren't coming through, and you're the one who has to remember you own a form you haven't thought about since launch.

Most form backends never solve this, because they were never built to hand a form off - they were built to collect submissions for whoever created the account. Handoff, if it happens at all, is something you improvise.

How freelancers actually close this out today

Ask around and the same four workarounds come up, none of them clean:

• Leave it on your account forever. The simplest option and the one most people default to. It also means every client site you've ever shipped is a live dependency on your account staying active, your card staying charged, and you staying reachable when something breaks.
• Export a CSV and email it over. A one-time data dump, not a working form. The client still has no way to receive new submissions unless they set up their own backend and you go edit the site's HTML to point at it - which usually means another invoice for a job that was supposed to be finished.
• Share your login. Fast, and a bad idea. Now the client has access to every other form on your account, and you have no clean way to revoke just their piece of it later.
• Make the client sign up and rebuild the form. Technically correct, practically annoying. It means a second integration pass, and every submission collected during testing and soft-launch is gone unless someone remembers to export and reimport it first.

Each of these treats ownership transfer as an afterthought bolted onto a system that assumes one permanent owner per form. None of them are actually a transfer - they're workarounds for a step the product never designed for.

What an actual transfer looks like

On Formhook's Studio plan, handoff is a first-class action instead of a workaround. The shape of it:

1. Provision the form under the client's email. When you create the form, you add the client's email address up front. You still own and configure the form - it's just marked for eventual transfer.
2. Build and test normally. Submissions land in your own dashboard while you wire the form into the site and test it. Nothing about your workflow changes here.
3. Send the transfer invite at handoff. One button in the form's settings emails the client a claim link. The form keeps accepting submissions the entire time - there's no dead window where the contact form silently stops working while you wait on the client to click a link.

The client gets seven days to accept. When they do, the form and every submission collected since day one - including everything from testing - move to an account they control. Read the full walkthrough on the client handoff page.

What moves, and what honestly doesn't

The part worth being precise about, because it's the part that makes this different from a CSV export: the form's API key doesn't change at claim. Nothing about the client's live site needs to be touched - no redeploy, no editing the form's action attribute, no second invoice for a five-minute fix. The handoff is invisible to visitors.

What genuinely transfers: the form itself, its full submission history, and the day-to-day dashboard - notifications, export, spam settings. What doesn't, and shouldn't be oversold:

• You keep a metadata-only view in a Clients console - form name, status, a rolling 30-day submission count - and nothing else. You can't read submission content or attachments after the claim. That's a deliberate boundary, not a missing feature.
• Submissions on a transferred form still count against your Studio submission cap, not the client's. That's not a catch - it's what lets the client run the form on a Free account indefinitely while it keeps behaving like a paid one.
• File attachments stay billed to your storage quota after the claim, and a connected Google Sheets sync doesn't carry over automatically - it's tied to whoever owns the form, so the client reconnects their own Google account if they want the sync to continue.
• You still technically know the form's API key unless you rotate it. The client owns the form; that's a separate question from whether you've forgotten the key exists.

Why this is worth caring about beyond convenience

There's a compliance angle here too, not just a workflow one. Once a client claims their form, they become the sole controller of their own submission data under GDPR - not you, and not some third account neither of you can see into. Combined with EU-only data storage, that's a handoff you can describe to a client's lawyer in one sentence instead of a data-processing conversation you'd rather avoid.

Ownership transfer isn't a feature you bolt onto a form backend after the fact - it has to be part of how the product thinks about who owns a form in the first place. If you build sites for clients regularly, that's worth checking for the next form you ship, on Formhook or wherever else you're comparing.