You cannot directly transfer CMS hosting from one Webflow project to another. Webflow hosting is tied to the specific project, and each hosted project requires its own individual hosting plan.
1. Webflow Hosting is Project-Specific
- Webflow hosting is applied per project, not per account or domain. That means each project that is published to a custom domain must have its own hosting plan.
- You cannot "move" hosting from one project to another. If you clone or rebuild a project, the new project will require its own paid hosting plan.
2. Options for Migrating CMS Content
- If you're moving to a new Webflow project but want to retain the same content:
- Export CMS content from the original project using the
Export CSV option in the CMS Collections. - Import the CSV into the new project’s CMS Collections, matching the fields appropriately.
- Note that Collection Page URLs and Slugs may need to be manually restored or updated in the new project.
3. Considerations for the Live Site
- If you want to keep the same live domain, you'll need to:
- Purchase hosting for the new project, then
- Point your domain settings to the new project via updated DNS records.
- This will allow you to switch to the new site without downtime, but only after hosting is paid for on that new project.
4. No Duplicate Hosting Charges
- To avoid duplicate hosting costs during setup:
- Use Webflow’s free staging domains (yourproject.webflow.io) to develop the new project.
- Only add paid hosting when you're ready to go live and switch the domain.
Summary
You cannot transfer CMS hosting between Webflow projects. Hosting is tied to each individual project. To migrate, you'll need to purchase hosting on the new project and manually move CMS content and domain settings.