A note for clients

Please check messages claiming to be from me

Someone is using a different email address to impersonate me and contact clients about supposed website updates and payments. Those messages are not from me.

Genuine emails from me only come from hello@derrick.dk. If you receive a request from another address, please do not act on it or make a payment. Contact me directly through this website to check first.

Contact me to verify

Webflow: How to Transfer Your Project to a Client

00
Derrick KityoWritten by Derrick Kityo

Understanding Webflow Project Transfer When a designer or developer creates a website using Webflow, they may need to transfer the project to their client's account. This process a…

a white rounded package with a charcoal browser panel emerging from it and a smooth blue transfer arrow, with blue “Client handover” text and supporting icons on lime green.

Understanding Webflow Project Transfer

When a designer or developer creates a website using Webflow, they may need to transfer the project to their client's account. This process allows the client to take control of the website and make changes as needed.

To transfer a Webflow project, the developer must have a Pro plan. Once the project is ready for transfer, the developer can click to transfer it to the client's account by selecting the email address associated with it.

It is important to note that the client must have Webflow editor access to maintain the website on their own account. If the client is afraid of "breaking things" or "messing up a design," the designer/developer can maintain the website on their own Webflow account as the website administrator.

Here are some important things to keep in mind when transferring a Webflow project to a client:

  • The client must have a Webflow account to receive the transferred project.
  • The client must have Webflow editor access to maintain the website on their own account.
  • The developer must have a Pro plan to transfer the project.
  • Once the project is transferred, the client will have full control over the website and can make changes as needed.

By understanding the process of transferring a Webflow project to a client, designers and developers can ensure a smooth transition of control over the website.

Pre-Transfer Preparations

Before transferring a Webflow project to a client, it is important to make sure that everything is set up correctly. This section will cover the key steps to take before initiating the transfer.

Checking Account Status

Firstly, it is essential to ensure that both the client's account and the project are in good standing. This means that the client's Webflow account must have an active subscription, and the project should not have any outstanding issues or errors.

Reviewing Project Settings

It is also important to review the project settings before initiating the transfer. This includes checking that all necessary integrations and custom code have been properly configured and that the project is set up to use the correct site plan and hosting subscription.

Confirming Domain Details

If the project is using a custom domain, it is important to confirm that the domain is registered and managed by the client. This includes checking that the domain is correctly configured to point to the Webflow hosting servers and that any necessary DNS records have been set up correctly.

Verifying Hosting Subscriptions

Before transferring the project, it is essential to ensure that the client has an active hosting subscription. This can be either a Starter Site Plan or a CMS Site Plan, depending on the project's requirements.

Ensuring Client-Specific Configurations

Finally, it is important to ensure that any client-specific configurations, such as permissions, security settings, and privacy settings, have been properly set up. This includes making sure that the client has the necessary permissions to access and edit the project, and that any necessary security and privacy settings have been configured correctly.

In summary, before transferring a Webflow project to a client, it is essential to ensure that the client's account and project are in good standing, that all necessary settings and configurations have been properly set up, and that the client has an active hosting subscription. By taking these steps, you can help ensure a smooth and successful transfer process.

Executing the Transfer

Transferring a Webflow project to a client account is a straightforward process that requires a few steps. In this section, we'll go over the steps involved in executing the transfer, including initiating the transfer, sharing project settings, transferring assets, and moving custom fonts.

Initiating Project Transfer

The first step in transferring a Webflow project to a client account is to initiate the transfer. To do this, the designer must log in to their Webflow account and navigate to the project they wish to transfer. They can then click on the project settings and select the "Transfer Project" option.

The designer will then be prompted to enter the email address associated with the client's Webflow account. Once the email address is entered, the designer can click on the "Send Transfer Request" button to initiate the transfer.

Sharing Project Settings

After initiating the transfer, the designer must share the project settings with the client. This can be done by navigating to the project settings and selecting the "Share Project Settings" option. The designer can then choose which project settings to share with the client, including pages, styles, custom code, and more.

Transferring Assets

Once the project settings have been shared, the designer can transfer the assets associated with the project. This includes images, content, CMS content, blog posts, and more. To transfer assets, the designer must navigate to the project settings and select the "Transfer Assets" option. They can then choose which assets to transfer and click on the "Transfer Assets" button.

Moving Custom Fonts

If the project uses custom fonts, the designer must also transfer them to the client account. To do this, the designer must navigate to the project settings and select the "Transfer Fonts" option. They can then choose which custom fonts to transfer and enter the Adobe Fonts API key associated with the project. Once the API key is entered, the designer can click on the "Transfer Fonts" button to move the custom fonts to the client account.

In summary, transferring a Webflow project to a client account involves initiating the transfer, sharing project settings, transferring assets, and moving custom fonts. By following these steps, designers can easily transfer their projects to their clients and ensure a seamless transition.

Want to apply this to your own website or app?

Tell me what you are working on and where it is getting stuck. I will help you turn the useful ideas into shipped work.

Post-Transfer Steps

After transferring a website project to a client in Webflow, there are a few important steps that need to be taken to ensure that the site is fully functional and live on the client's hosting account. Below are some recommended post-transfer steps to take:

Updating Hosting Settings

The first step after transferring a site to a client is to update the hosting settings. This involves modifying the DNS settings to point to the client's hosting account. The client should have access to the hosting account details, including the hosting subscriptions, to make the necessary changes. It is important to ensure that there is no downtime during this process.

Modifying Domain Details

If the site is using a custom domain, the client will need to modify the domain details to point to the new hosting account. This can be done by updating the DNS records or by transferring the domain to a new registrar. It is important to ensure that the domain is properly configured to avoid any issues with the site's accessibility.

Adjusting Form Submissions and Redirects

After the site has been transferred, the client should review the form submissions and redirects to ensure that they are properly configured. This includes updating the form notification information and reCAPTCHA keys, if necessary. The client should also review the redirects to ensure that they are pointing to the correct pages on the site.

Overall, transferring a Webflow site to a client requires careful attention to detail and a thorough understanding of the site's hosting settings, domain details, and form submissions. By following the recommended post-transfer steps outlined above, clients can ensure that their site is fully functional and live on their hosting account.

Troubleshooting Transfer Issues

When transferring a Webflow project to a client, there can be some issues that arise. Here are some common problems and solutions to help troubleshoot any transfer issues.

Resolving Billing Concerns

One of the most common issues that arise when transferring a project is billing concerns. If the client's account does not have a paid plan, they will not be able to receive the transfer. If the developer's account has a paid plan, the client will need to upgrade their account before the transfer can be completed.

To resolve billing concerns, the developer should ensure that the client has a paid plan or upgrade their account if necessary. If the client is having trouble upgrading their account, they can contact Webflow support for assistance.

Handling Transfer Errors

Another issue that can arise during the transfer process is transfer errors. If the project is not transferring to the client's account, it may be due to an error in the transfer process. In this case, the developer should try transferring the project again, making sure to follow all the necessary steps.

If the transfer still fails, the developer can contact Webflow support for assistance. They may be able to identify the issue and help resolve it.

Addressing SEO Considerations

When transferring a project to a client, it's important to consider SEO. If the project has an established SEO presence, transferring it to a new domain can cause a drop in rankings. To avoid this, the developer should ensure that the client's domain is properly set up and all necessary redirects are in place.

The developer should also make sure that the client's Google Analytics and Search Console accounts are properly set up and connected to the new domain. This will help ensure that the client's SEO efforts are not negatively impacted by the transfer.

In summary, when transferring a Webflow project to a client, it's important to consider billing concerns, handle transfer errors, and address SEO considerations. By following these steps, developers can ensure a smooth transfer process and help their clients maintain their online presence.

Frequently asked questions

What should I confirm before transferring a Webflow project to a client?

Confirm the receiving account, required plan, domain and billing ownership, and who needs editing or development access. Follow Webflow’s current transfer requirements for the actual project configuration rather than assuming every site transfers in the same way.

Does a project transfer move every connected service?

Do not assume it does. Inventory forms, analytics, payment services and other integrations separately, then confirm their accounts and credentials remain appropriately owned and working after the transfer.

What should I test after handing a Webflow site to a client?

Test the public site, publishing permissions and one routine content update with the new owner. Send a controlled form submission and check its destination. Provide an account and subscription inventory alongside the operating guide.

I build websites and apps

I work across product marketing and engineering, turning ideas into useful digital products and improving how they perform after launch.

Webflow developerWebflow LondonWebflow product workshop

On this page