CMS Collection Export Eligibility on Webflow Basic Plan

The goal is to assess whether a low‑traffic Webflow site can be fully replaced by a static export hosted elsewhere while retaining CMS collection data, form handling, and plan‑specific features.

Key constraints include the current plan’s code‑export eligibility, limitations on exporting CMS collections, the inability of static HTML to process native forms, and the need for repeated exports when content changes frequently. Uncertainty surrounds whether exported output preserves collection routing, search indexing, and canonical URLs.

Can a Basic‑plan Webflow site with CMS collections be fully exported to static HTML without losing collection data? Does static export preserve native form submission functionality, or must forms be rerouted to a third‑party endpoint?