Transferring a Webflow site to another account can seem daunting, but it’s essential for various reasons—selling a website, changing project ownership, or simply shifting to a new account.

Understanding how to transfer a Webflow site to another account is crucial for these scenarios. In this article, I’ll guide you through the steps to ensure a smooth transition.

You’ll learn how to prepare for the transfer, address potential hurdles, and avoid common mistakes. From verifying DNS settings to managing third-party integrations, I’ll cover every aspect.

By the end, you’ll be equipped to handle the transfer process confidently and efficiently. Whether you’re managing multiple projects or just one, this guide will help you navigate the complexities of transferring Webflow sites with ease.

How to Transfer a Webflow Site to Another Account: Quick Workflow

  1. Access Project Settings:
    • Log into your Webflow account and navigate to your project dashboard.
    • Select the project you wish to transfer and go to its Project Settings.
  2. Initiate Transfer:
    • In the project settings, look for the Transfer Project option, usually indicated by an icon of a person with an arrow.
    • Click on this icon, and you will have two options: transfer to a user or a team.
  3. Enter Recipient’s Email:
    • If transferring to a user, enter the email address associated with your client’s Webflow account. If transferring to a team, select the appropriate team from your list.
  4. Complete Transfer:
    • After entering the email, a transfer request will be sent to your client. They must accept this request within 7 days for it to be completed.
    • Once accepted, the project will appear in their dashboard.

Planning and Preparation for the Transfer

Aligning Expectations with All Stakeholders

Establishing communication between the current and new owners
Clear and open channels of communication are crucial here. Both parties need to be in sync, so start by establishing a direct line of contact. Email, Slack, or even a quick call can do wonders. Misunderstandings can easily derail the entire process, and nobody wants that.

Setting transfer timelines and responsibilities
Set a concrete timeline. Outline who does what and when. Assign responsibilities like confirming backup creation, updating domain settings, and checking account plan compatibility. Document everything—having a shared spreadsheet works wonders.

Reviewing the Site Status Before Transfer

Checking for active custom domains and DNS settings
Before moving anything, scrutinize the custom domains and DNS settings. Make sure they’re correctly configured. Discrepancies here can lead to downtime or broken links. Verify MX records if you’re handling email services through the domain.

Identifying and preserving third-party integrations (e.g., Adobe Fonts)
List out all third-party integrations in use, such as Adobe Fonts or any other APIs. Ensure these connections are documented and preserved during the transition. Losing an API connection can render parts of the site non-functional.

Ensuring backups are created to prevent data loss
A manual backup of the site is indispensable. Use Webflow’s export options to create a comprehensive backup. This safeguards against any data loss or corruption during the migration. Make sure this backup is also accessible to the new owner.

Reviewing Webflow’s Transfer Policies and Limitations

Understanding account plan restrictions
Webflow’s transfer policies can trip you up if you don’t understand the account plan restrictions. Certain features might be tied to specific plans. Confirm the current plan and match it with the recipient’s plan to avoid compatibility issues.

Confirming eligibility for transferring to teams or individual users
Know who you’re transferring to—a team or an individual user? Webflow differentiates between business and individual accounts. Make sure the recipient meets all criteria for the transfer, including any required permissions or account setup. Check Webflow’s guidelines to verify eligibility.

Step-by-Step Guide to Transferring a Webflow Site

YouTube player

Step 1: Accessing Webflow Account and Project Settings

Logging in and navigating to the Dashboard
Log in to your Webflow account. Once logged in, the Dashboard is your main control center. From here, you manage all your projects, settings, and account details. Navigate to the project you intend to transfer.

Selecting the project to be transferred
In the Dashboard, find the project you want to move. Click on it. This takes you into the project settings where all the magic happens.

Step 2: Initiating the Transfer Process

Clicking on the transfer icon within project settings
Inside the project settings, look for the transfer icon. It’s usually an arrow or some kind of shift symbol. Click on it to start the transfer process. This is where you decide how the transfer will go down.

Selecting the transfer type (User vs. Team)
A crucial decision: Will you transfer to a User or a Team? Teams have collaborative tools, while individuals don’t get those perks. Click User if it’s going to another personal account. Click Team if it’s a collaborative project.

Step 3: Providing Necessary Transfer Details

Entering the recipient’s email address
Now, input the recipient’s email address. Double-check this to avoid headaches later. One typo and the transfer goes nowhere.

Confirming the type of recipient (User or Team)
Clarify the recipient. This step may seem redundant, but it’s to ensure there’s no mix-up. Confirm whether the email belongs to a single user or a team.

Notifying the recipient of the transfer request
Shoot a quick message to the recipient. Let them know about the incoming transfer so they’re not blindsided. This keeps everyone on the same page and speeds up the acceptance process.

Step 4: Recipient’s Acceptance and Finalization

Reviewing and accepting the transfer within 7 days
The recipient has a 7-day window to accept the transfer. They get an email with a link. Clicking it brings them to a confirmation page. They must accept the terms to complete the process.

Understanding locked status in the sender’s Dashboard during transfer
While the transfer is pending, the project is in a locked status on your Dashboard. You can’t make changes. This is to ensure the integrity of the site during the transition. The project will unlock once the recipient completes their end of the transfer.

Managing Subscriptions, Billing, and Ownership

Transitioning Billing and Subscription Plans

Ensuring the new owner updates billing information
First, billing. The new owner needs to update their billing information immediately. Webflow runs on subscriptions, and you don’t want any disruption. It’s straightforward—head to the Account Settings, find the Billing section, and input the new payment details.

Handling existing site plans during the transition
While the billing info is changing, remember the existing site plans. If the site has a Site Plan or Workspace plan, ensure these get carried over smoothly. Any lapse can affect your domain, SEO rankings, and the user experience. Double-check everything—ping-pong between your account and theirs if you must.

Managing Domain and Hosting Configurations

Updating DNS settings to reflect the new account
Next up, DNS settings. When you transfer ownership, the custom domains might still be pointing to your account. Update the DNS settings to reflect the new account. Go into the domain registrar’s dashboard, adjust the A and CNAME records, and confirm everything lines up with Webflow’s guidelines.

Avoiding downtime by scheduling changes during low-traffic periods
Downtime is the enemy. Schedule these changes during low-traffic periods. Late nights or early mornings are less impactful. This step is crucial for user retention and maintaining a steady SEO ranking. Analyze your traffic data and pick the best window to minimize disruption.

Ensuring Smooth Handover of Site Responsibilities

Providing Access to Collaborators and Teams

Transferring ownership to team members if needed
First things first—if you need to bring team members on board, transfer ownership efficiently. Head to the Webflow Dashboard, locate the project, and look for the Collaborators tab. From here, add team members and assign roles. Ensure everyone has the proper permissions to avoid bottlenecks.

Coordinating responsibilities for ongoing site management
Now, coordinate. Define who handles what. Is someone overseeing SEO? Who’s managing third-party integrations? Write this down. Use tools like Asana or Trello to keep responsibilities clear and manageable. Communication is key—slack channels or regular meetings keep everyone aligned.

Post-Transfer Review

Checking for content accuracy and integration functionality
Post-transfer, you must review everything with a fine-tooth comb. Start with content accuracy. Scrutinize each page, check links, and verify that all third-party integrations, like Adobe Fonts or API connections, are intact. Test functionalities—broken elements hurt user experience and credibility.

Monitoring SEO rankings and performance metrics
Keep an eye on your SEO rankings and performance metrics after the transfer. Use tools like Google Analytics and SEMrush to monitor organic traffic, bounce rates, and other key performance indicators. Immediate dips might suggest issues needing attention—fix these fast to maintain SEO health.

Avoiding Common Pitfalls in Webflow Transfers

Compatibility Issues between Accounts

Verifying the recipient account’s plan compatibility with the site
First off, compatibility. You can’t just hand over any site to any account. Recipients need the right account plans. Webflow has restrictions tied to feature sets, so make sure the receiving account matches the plan requirements. If it doesn’t, some functionalities might be locked out or, worse, completely disabled.

Mitigating risks of feature limitations after transfer
How do you mitigate these risks? Simple, check everything. Go through each feature your site uses and confirm they’re supported by the recipient’s account. Should gaps be found, upgrade plans as needed before the transfer begins.

Challenges with Domain and DNS Configurations

Resolving domain pointing issues during the transfer
Now, let’s talk domains and DNS. When you transfer a site, existing DNS settings might not automatically update. That’s trouble waiting to happen. Fix this by dealing with domain pointing issues upfront. Verify A records and CNAME records to ensure they align with the new account.

Preventing downtime with proper planning
Downtime is your enemy here. Plan these changes meticulously. Execute DNS updates during off-peak hours to minimize visitor disruption. Keep an eye on traffic metrics and choose the optimal time for potential downtime.

Handling Third-Party Integrations

Transferring ownership of external services (e.g., fonts, APIs)
Third-party integrations complicate things. Fonts, APIs, and other external services tied to the site won’t automatically transfer ownership. Log in to each third-party platform and manually transfer or update ownership details. This keeps design elements and functionalities consistent post-transfer.

Addressing any potential integration failures
Integration failures can be sneaky. They might not show up immediately but can break down over time. After transferring ownership, test each integration rigorously. Look for errors or interruptions. Fixing these on the fly can save a lot of troubleshooting later.

Best Practices for a Seamless Webflow Site Transfer

Scheduling Transfers Strategically

Choosing off-peak hours to minimize impact on visitors
Transfer timing is everything. You don’t want to disrupt site traffic, so pick off-peak hours. Late nights, early mornings—whatever aligns with the site’s audience. Analyze your analytics to identify these windows. The main goal is to create the least amount of friction for visitors.

Coordinating with stakeholders for smooth operations
Stakeholder coordination is critical. Whether it’s the current owner, the recipient, or a third-party service provider, everyone should be on the same page. Use tools like Slack or Trello to maintain clear, real-time communication. Make sure everyone knows the timeline and their respective roles.

Preparing Backup Plans for Unexpected Issues

Creating additional backups for added security
Backups are your safety net. Before initiating the transfer, create additional backups. Use Webflow’s built-in tools or external methods to ensure you have multiple recovery points. You never know when something might go wrong, so better to be safe than sorry.

Having contingency plans for DNS or domain issues
DNS and domain issues can crop up when least expected. Create contingency plans for any potential hitches here. Have alternative settings ready to be deployed at a moment’s notice. This minimizes downtime and prevents service interruptions for users.

Maintaining Clear Communication throughout the Process

Ensuring all stakeholders are aware of timelines and expectations
Communication is your best friend. Make sure everyone involved knows the timelines and what’s expected of them. Send reminders and updates as you hit major milestones. Clear communication prevents last-minute surprises and aligns everyone toward the common goal.

Following up with the new owner after transfer completion
Once the transfer is complete, follow up with the new owner. Check in to ensure they’re up to speed with everything. Answer any questions they might have, and offer guidance if they run into issues. This step is crucial in ensuring a smooth transition and maintaining long-term site health.

FAQ on How To Transfer A Webflow Site To Another Account

How do I initiate a site transfer in Webflow?

You start by logging into your Webflow account. Head over to your Dashboard and select the project you want to transfer. In the project settings, find and click on the transfer icon. Choose between transferring to a user or a team.

What happens to my custom domains during the transfer?

If you have a custom domain, you’ll need to update the DNS settings to match the new account. Current DNS settings won’t automatically update. Verify A records and CNAME records to ensure they align with Webflow’s guidelines.

Are there any restrictions on which accounts can receive a transferred site?

Yes, the recipient’s account must match certain criteria. Specifically, their account plan must be compatible with the site’s features. Confirm that their account plan supports all functionalities of the site before initiating the transfer.

What about third-party integrations like Adobe Fonts?

Third-party integrations need manual updates. You’ll have to log into each third-party platform and transfer or update ownership details. This ensures that design elements and functionalities remain consistent after the transfer.

How can I avoid downtime during the transfer?

Execute DNS updates during off-peak hours to minimize disruptions. Analyze your site traffic and pick a time window that affects the least number of visitors. Proper planning here is crucial to maintaining a seamless user experience.

Can I retain my Webflow site plan when transferring?

Yes, you can retain your site plan, but ensure that billing details are updated promptly. The new owner should handle the billing information and site plans to avoid any service disruption during the transition.

How do I handle billing and subscription transfers?

The new owner must update billing information immediately after the transfer. Go to Account Settings, navigate to the Billing section, and input the new payment details to keep the subscription active and avoid interruptions.

Do I need to prepare backups before transferring?

Absolutely. Create additional backups using Webflow’s export options or external methods. Having multiple recovery points can save you from potential data loss. This step adds an extra layer of security throughout the transfer process.

What should I do if the recipient doesn’t accept the transfer in 7 days?

The recipient has a 7-day window to accept the transfer. If they don’t, the site remains locked in your Dashboard. Communicate promptly with the recipient to ensure the transfer is accepted within the given period.

What are the common mistakes when transferring a Webflow site?

Common pitfalls include overlooking third-party integrations, failing to update DNS settings, and not confirming account plan compatibility.

Mitigate these risks by thorough planning and double-checking all settings and guidelines before initiating the transfer.

Conclusion

Transferring ownership of your Webflow site is essential for various scenarios like shifting to a new account or selling a site. Knowing how to transfer a Webflow site to another account involves precise steps and attention to detail.

Update DNS settings, handle third-party integrations, and ensure that billing information is up-to-date. These actions ensure a seamless transition. Confirm account plan compatibility and ensure backups are created as a safety net.

Avoid common pitfalls by meticulously planning the transfer during off-peak hours and maintaining clear communication with all stakeholders. This keeps downtime minimal and user experience intact. Lastly, double-check everything post-transfer, ensuring that all functionalities and integrations work as expected. Follow these steps, and you’ll efficiently manage the transfer process, maintaining site integrity and performance.

If you liked this article about how to transfer a Webflow site to another account, you should check out this article about how to delete a site in Webflow.

There are also similar articles discussing how to use Webflow templateshow to create a blog in Webflowhow to create a form in Webflow, and how to set up 301 redirects in Webflow.

And let’s not forget about articles on how to remove “made in Webflow”how to add Google Analytics to WebflowFigma to Webflow, and Webflow Shopify integration.

Author

Bogdan Sandu is the principal designer and editor of this website. He specializes in web and graphic design, focusing on creating user-friendly websites, innovative UI kits, and unique fonts.Many of his resources are available on various design marketplaces. Over the years, he's worked with a range of clients and contributed to design publications like Designmodo, WebDesignerDepot, and Speckyboy among others.