How do I transfer a Webflow site to a client or another workspace?

Send the transfer from Site settings

A transfer moves the site from your Workspace to someone else's. The recipient needs their own Webflow account and a Workspace before you start. Open Site settings, click the Transfer icon, enter their email, and click Transfer. The site shows as locked in your Dashboard. They get an email and a banner in their Dashboard. Nothing moves until they accept.

When they accept, Webflow removes the site from your Workspace and adds it to theirs. If the transfer includes an active Site plan, the plan and any connected custom domains go with the site. You can cancel before they accept: open the more options menu on the site thumbnail and choose Cancel site transfer.

If you still need the original in your Workspace, duplicate the site and transfer the duplicate. A site that has localized content and settings must be handled that way. Duplicate first, then transfer the duplicate.

Giving a content editor access is a different task. An invite lets someone edit inside your Workspace. A transfer hands them the site itself.

See whether the Site plan can move

Freelancer and Agency Workspaces can transfer a site that has an active Site plan. The destination Workspace cannot be an Enterprise Workspace. That transfer is meant for a handoff to a client. Webflow describes it as moving the paid Site plan, custom domain, and related settings with no downtime and no loss of unused Site plan time. On an Agency or Freelancer plan, unused time on the paid subscription can be credited back to you when the site had an active plan at transfer.

If your Workspace is Starter, Core, Growth, or Enterprise, or if the destination is Enterprise, you cannot move an active paid Site plan as-is. Downgrade the site to the Starter Site plan first. Remove add-ons, choose Downgrade to Starter, confirm, then send the transfer. A published site goes offline for that downgrade, so agree on a time with the client. After the site arrives in a non-Enterprise Workspace, the new owner adds a paid Site plan, connects the custom domains, and publishes. An Enterprise destination has to arrange the Enterprise plan with their Webflow account team before domains and publishing.

Example: a Freelancer Workspace sends a brochure site on a Site plan to a client's Growth Workspace. The client accepts, the same domain stays connected, and the live site does not have to be rebuilt. A Core Workspace sending that same paid site has to downgrade first, and the client publishes again after they upgrade.

An Ecommerce store can be transferred, with extra limits. Order history moves, and payment providers can stay connected, so disconnect them first if the client should use their own accounts. The Ecommerce site plan does not transfer. The new owner adds an Ecommerce Site plan and turns checkout back on. Cancel active User Accounts subscriptions before you transfer a store that uses them. If the new owner changes payment accounts, they cannot refund older orders.

Write down what does not come along

The Designer work moves. That includes classes and global styles, static and CMS pages, assets, backup versions, Collections and items, custom code, custom fonts, form submissions, 301 redirects, and other site settings. Ecommerce products, categories, and order history move when the site is a store. User accounts move too.

Some account-specific settings are reset:

• Form notification settings
• reCAPTCHA keys, while reCAPTCHA stays enabled
• An Adobe Fonts API key, if one was connected
• Billing details and other email-specific account information
• Comments

Shared Libraries are uninstalled. Components, variables, and assets from a Library that the site is already using are copied onto the site. Connected apps must be authorized again by the new owner. If the site is on Made in Webflow, remove that showcase, and remove site contributors from Creator Credits, or the transfer stays locked. You can add contributors back after the move.

Example: the contact form is still on the page and old submissions are still stored, but the notification address is blank. The client's inbox receives nothing until they enter their email in the form settings and publish.

Check the handoff before they accept

Use a short list so the live site is not the place you discover a reset setting.

• Confirm the email belongs to the person who should own the site, and that they already have a Workspace.
• Record the custom domains connected today, and who controls DNS.
• Copy the form notification addresses and any reCAPTCHA notes, because those settings reset.
• If you will still edit after the move, plan a guest seat. A client can add you as a Workspace guest when you have an Agency or Freelancer plan.
• If the site should stay in your Workspace and the client should only pay the Site plan, use client payments instead of Transfer. An owner or admin on a Freelancer or Agency Workspace can charge the client. That client must not already be a member of your Workspace.

After they accept, open the live domain. If you had to downgrade, wait until they have a paid plan, the domain is connected, and a publish has finished. Send a test form submission. Open one CMS item and one redirected URL. Ask them to reauthorize any app the site still needs. The design can look finished while notifications and apps are still disconnected.