Canceling a Webflow plan doesn't just turn off the editor — it can quietly take content, form submissions and integrations with it. The full checklist of what to pull out first.
Key takeaways
- CMS Collection exports, form submission history and custom code embeds are all invisible once a Webflow plan lapses — pull them out first.
- Redirects, DNS records and cookie-consent configuration don't come with any export and need to be written down manually.
- Missing an item rarely breaks the new site immediately — it breaks quietly, weeks later, as a 404 or a form that stops arriving anywhere.
Canceling a Webflow plan doesn't just turn off the editor — it can quietly take content, form submissions, and integrations with it if you haven't pulled everything out first. Before you cancel anything, work through this list.
Content and CMS Collections
- Export every CMS Collection (Webflow's own CSV export, under each Collection's settings) — not just the pages that reference them.
- Screenshot or copy the raw text of any page you can't export cleanly, especially ones with heavy custom interactions.
- Note every image's actual file, not just how it displays — Webflow's own asset URLs stop working once the site is off Webflow hosting.
Forms and form submissions
- Export existing form submission data — Webflow keeps a limited history, and it's gone once the plan lapses.
- Note where each form actually sends its data today (email, Zapier, a CRM integration) so the replacement form can be wired the same way.
SEO and redirects
- Export your current URL list and page-level SEO titles/descriptions — these need to survive the move exactly, or you lose rankings.
- Write down every 301 redirect currently configured in Webflow's settings; they don't come with an export.
- Save your sitemap.xml and robots.txt as they currently exist.
Domain and DNS
- Record your current DNS records before touching anything — you'll need to repoint them, not guess them from scratch.
- Confirm who has access to the domain registrar itself, separate from Webflow's own hosting.
Custom code and integrations
- Copy every custom code embed (head/body/page-level) — these are invisible in an export and easy to forget entirely.
- List every third-party integration connected to the site: analytics, chat widgets, cookie consent, ad pixels.
Legal and consent
- Save your privacy policy, cookie policy and any consent-banner configuration — these need to exist on day one of the new site, not get added later.
Missing even one of these doesn't always break the new site immediately — it breaks quietly, weeks later, when a redirect 404s or a form stops arriving anywhere. Working through this list before you cancel is the difference between a clean migration and untangling it after the fact.
If this list feels like a lot, we handle all of it as part of every migration package — from a $490 static export to a full CMS Collections rebuild.