How to Transfer a Webflow Site to a Client, Step by Step

TL;DR: Transferring a Webflow site to a client moves the site, its paid Site plan and its connected custom domains into the client's Workspace with no downtime, and Webflow allows it only from a Freelancer or Agency Workspace to a non-Enterprise one. The transfer is initiated from Site settings with the Transfer icon and the client's email address, and nothing moves until the client accepts. A short list of account-specific settings resets on the way across, and those are what actually break handovers.

• Only Freelancer and Agency Workspace plans can transfer a site that has an active paid Site plan.
• The destination Workspace must not be an Enterprise Workspace.
• Webflow states the transfer carries the paid Site plan and custom domain with no downtime and no loss of unused Site plan time.
• Form notification settings, reCAPTCHA keys, Adobe Fonts keys, billing details and comments do not transfer.
• Shared Libraries are uninstalled on transfer, with components, variables and assets in use copied into the site.
• Made in Webflow listings and Creator Credits contributors must be cleared before the transfer unlocks.

What does transferring a Webflow site to a client actually move?

A Webflow site transfer moves the whole build into another Workspace, not a copy of it. Webflow's site transfer documentation lists what travels: styles including classes and global styles, static and CMS-driven pages, assets, backup versions, Collections and Collection items, Ecommerce products and order history, user accounts, custom code, custom fonts, form submissions, 301 redirects and other site settings. The paid Site plan and any connected custom domains go with it.

The thing worth telling a client in plain words is that a transfer is not an export. Their site keeps its version history, its redirects and its CMS structure intact, and the URL never changes. On the handovers I run, that sentence removes most of the anxiety, because clients usually expect a migration and a broken week.

Which Workspace plans can transfer a Webflow site with a paid Site plan?

Webflow restricts paid-plan transfers to two Workspace plans. Webflow's documentation states that only Freelancer and Agency Workspace plans can transfer sites with active Site plans, and that the destination Workspace must not be an Enterprise Workspace. If the source Workspace is Starter, Core, Growth or Enterprise, or the target Workspace is Enterprise, Webflow requires you to downgrade the site to the free Starter Site plan before transferring, which it warns will result in site downtime if the site has been published.

What I see agencies get wrong here is discovering the plan restriction on handover day. A Core Workspace looks perfectly adequate for building client sites right up to the moment a client asks for ownership, and then the only path is a downgrade that takes their live site off its custom domain. If you deliver client work, the Workspace plan is a delivery decision, not a billing one.

How do you transfer a Webflow site to a client, step by step?

The transfer itself is short. The preparation around it is where the time goes, so treat the numbered steps below as the last ten minutes of a handover rather than the handover itself.

1. Confirm your Workspace is on a Freelancer or Agency plan and the client's Workspace is not Enterprise.
2. Ask the client to create a Webflow account and Workspace if they do not have one, since the transfer needs a destination.
3. Remove the site from Made in Webflow if it is showcased there, because Webflow keeps the transfer feature locked until you do.
4. Remove all site contributors from Creator Credits, and note who to re-add afterwards.
5. If the site uses Webflow Localize, duplicate the site first and transfer the duplicate, which is Webflow's documented route for localized content.
6. Open Site settings and click the Transfer icon.
7. Enter the client's email address and click Transfer.
8. Wait for the client to accept from the email invitation or the banner in their Dashboard. The site shows as locked in your dashboard until they do.
9. Have the client add their card, then re-authenticate any third-party apps connected to the site.
10. Ask the client to add you back as a Workspace guest if you are continuing to work on the site.

If you initiated a transfer by mistake, Webflow lets you cancel it from the more options dots under the site thumbnail before the recipient accepts.

What resets when a Webflow site changes hands?

Webflow deliberately drops account-specific and client-specific configuration during a transfer for security and privacy reasons, and that short list is responsible for most post-handover support tickets. Form notification settings, reCAPTCHA keys, Adobe Fonts integrations, billing information and comments do not travel. The reCAPTCHA case is the sneaky one: Webflow resets the keys but leaves reCAPTCHA enabled, so forms can look fine and fail quietly.

The rule I apply on client projects is to send the form notification recipients and the reCAPTCHA setup as written instructions before the transfer, not after, and to test one live form submission on the client's side within an hour of them accepting. Everything else can wait a day. A silently broken contact form cannot.

Transfer the site, or use client payments instead?

A transfer and Webflow client payments solve two different problems, and choosing wrongly is the most expensive mistake in this whole process. Client payments keeps the site inside your Freelancer or Agency Workspace while the client's card covers the Site plan and add-on charges, which is set up by choosing Charge to client on a site already on a Site plan. A transfer hands the asset over entirely. The question that decides it is not who pays; it is who should be able to publish the site in twelve months.

What I do the week before a Webflow handover

The transfer button is the least interesting part of a handover, and the week before it is where a client either ends up self-sufficient or ends up emailing you every Tuesday. The sequence below is what I run on client projects, and it is deliberately boring.

• Confirm the client's Workspace exists and is not Enterprise, in writing.
• Send the form notification recipients and reCAPTCHA setup as instructions, since neither transfers.
• List every third-party app connected to the site so the client knows what to reauthorise.
• Export or note anything living in comments, because comments do not survive the transfer.
• Record which contributors to re-add to Creator Credits after the transfer completes.
• Walk the client through publishing once, on a real change, before ownership moves.
• Agree the guest invitation if you are staying involved, rather than assuming access continues.

Most of that overlaps with the documentation set I cover in what a Webflow handoff package should include, and with the wider process in my guide to the Webflow client handoff.

If you are an agency handing sites to clients regularly and the handover keeps eating a week of someone's time, tell me how your delivery works and I will tell you what I would change and what it would cost. I run this process on white label builds most months.