How to Transfer a Webflow Site to Another Account (Step by Step)

To transfer a Webflow site to another account, both people need a Webflow Workspace. Move the project by opening the project menu and choosing Transfer to Workspace. To send it to someone else, share a Workspace first, then transfer the project into it. The design, pages, and CMS move with the project. The site plan, billing, and custom domain do not, so the new owner sets those up again.

You may need to hand a Webflow site to a client or a new team. Webflow makes this possible without rebuilding the site. The whole project can move to another account in a few steps. This Webflow transfer site guide shows you how to transfer a Webflow site the right way, and what to check after.

We hand off Webflow sites to clients every month at theCSS Agency. These are the exact steps and checks our team uses.

Why Transfer a Webflow Site?

There are a few common reasons to move a project. Each one calls for a clean transfer.

• Agency to client handoff: you built the site and now give the client full control.
• Selling a site: you sell a finished project to a new owner.
• Team or account change: you move a project to a new Workspace or company account.

In each case, a proper transfer keeps the design, content, and settings intact.

How Webflow Projects and Workspaces Work

First, a quick note on how Webflow is set up. Every Webflow project lives inside a Workspace. A Workspace is the account that holds your projects and members.

To move a project, it has to go from one Workspace to another. So a webflow account transfer is really a move between two Workspaces. Both sides need a Webflow account to make it work.

What You Need Before You Transfer

Get these ready before you start. They make the transfer smooth.

• Both people have a Webflow account and a Workspace.
• You have admin or owner access to the project.
• You know which Workspace will receive the project.
• You have saved a backup or a read-only link, just in case.

A quick check here saves time and avoids errors later.

What Transfers and What Does Not

This is the part people miss most. Not everything moves with the project.

What moves with the project:

• All pages and their design
• CMS collections and content
• Interactions and animations
• Custom code and SEO settings
• Forms and their structure

What does not move:

• The paid site plan and billing
• The custom domain connection
• Payment details

So after a webflow site transfer, the new owner adds their own site plan and connects the domain again. Plan for this step so the live site stays online.

Method 1: Transfer a Project to Another Workspace You Own

This is the simplest case. You move a project between two Workspaces you already own.

1. Open your Webflow Dashboard.
2. Find the project you want to move.
3. Open the project menu, shown as a three-dot icon.
4. Choose Transfer to Workspace.
5. Pick the destination Workspace from the list.
6. Confirm the transfer.

The project now sits in the new Workspace. This is the fastest way to move a Webflow project to another Workspace.

Method 2: Transfer a Webflow Site to a Client or Another Person

To send a project to someone else, you must share a Workspace first. Webflow only lets you transfer into a Workspace you belong to. There are two clean ways to do this.

Option A: They Invite You to Their Workspace

1. The recipient creates their own Workspace.
2. They invite you as a member of that Workspace.
3. You accept the invite.
4. You open the project menu and choose Transfer to Workspace.
5. You select their Workspace as the destination.
6. The recipient removes you as a member once the transfer is done.

This option gives the new owner full control at the end. It is the common path for a transfer webflow site to client handoff.

Option B: You Invite Them to Your Workspace

1. You invite the recipient to your Workspace.
2. They accept and gain access to the project.
3. They create their own Workspace to receive the project.
4. One of you transfers the project into their Workspace.
5. You both remove any access that is no longer needed.

Both options reach the same result. Pick the one that fits who owns which Workspace.

Method 3: Copy a Site With a Read-Only Link

Sometimes you only need to copy the design, not move the live site. A read-only link lets someone clone the project into their own account.

1. Open the project and turn on the read-only share link.
2. Send the link to the other person.
3. They open the link and clone the project into their Workspace.

Keep one thing in mind. A clone copies the design and structure, but not the CMS content or hosting. So this is a copy, not a full transfer webflow project move. Use it for templates and starting points, not for live handoffs.

After the Transfer: What to Check

The move is done, but a few steps remain. Run through these to keep the site healthy.

1. Add a site plan. The new owner picks a hosting plan for the project.
2. Connect the custom domain. Set the domain again in the new Workspace.
3. Republish the site. Publish so the live site reflects the new setup.
4. Check forms and integrations. Confirm forms, analytics, and tools still work.
5. Review team access. Remove any old members who no longer need access.

A quick pass here prevents downtime and broken links.

Webflow Site Transfer Checklist

Use this checklist to keep the transfer webflow project to another account clean.

• Both people have a Webflow Workspace.
• You saved a backup or read-only link first.
• You shared a Workspace before the transfer.
• You used Transfer to Workspace to move the project.
• The new owner added a site plan.
• The custom domain is connected again.
• The site is republished and live.
• Old access is removed for security.

Common Problems and Fixes

A few issues come up during transfers. Here are quick fixes.

• Transfer to Workspace is greyed out. You are not a member of the target Workspace. Share the Workspace first.
• The live site went down. The site plan did not move. The new owner must add a plan and republish.
• The custom domain stopped working. Reconnect the domain in the new Workspace.
• You cannot see the project after transfer. Ask the new owner to add you back if you still need access.

Conclusion

A webflow transfer ownership move is simple once you know the steps. Share a Workspace, then use Transfer to Workspace to move the project. The design, pages, and CMS travel with it. The site plan, billing, and domain do not, so set those up again after.

Plan the handoff, run the checklist, and confirm the live site works. Done well, the new owner gets a clean, working Webflow site with full control.

Need help with a smooth Webflow handoff or migration? theCSS Agency handles Webflow builds, transfers, and migrations for SaaS and B2B teams. Book a call to plan your handoff.

FAQs

1. How do I transfer a Webflow site to another account?

Share a Workspace between both people, then open the project menu and choose Transfer to Workspace. Select the destination Workspace to move the project.

2. Does the site plan transfer with a Webflow project?

No. The site plan, billing, and payment do not move with the project. The new owner must add their own site plan and republish the site.

3. What moves when I transfer a Webflow project?

The pages, design, CMS content, interactions, custom code, and forms all move. The site plan, billing, and custom domain do not.

4. Can I transfer a Webflow site to a client?

Yes. The client creates a Workspace and invites you as a member. You then transfer the project into their Workspace and remove your access after.

5. Do both people need a Webflow account to transfer a site?

Yes. A transfer moves a project between two Workspaces, so both people need a Webflow account and a Workspace.

6. What is the difference between transferring and cloning a Webflow site?

A transfer moves the full project, including CMS content. A clone from a read-only link copies only the design and structure, not the content or hosting.

7. What should I check after transferring a Webflow site?

Add a site plan, connect the custom domain, republish the site, and confirm forms and integrations still work. Then remove any old member access.