Edited by Clinton Feyisitan. Review scope: official documentation read on 14 October 2026 and local worksheet checks with synthetic examples. No native account migration, paid execution or timed completion test was performed.
Resolve the export uncertainty first
Framer’s official documentation conflicts as read on 14 October 2026. Its data-portability page says site output is downloadable and CMS data can be exported through plugins. Its HTML-export page says HTML export for self-hosting is unavailable. Confirm the deliverable in your account before relying on an export tool. This guide does not assume an automatic transfer of a Framer design into Webflow.
Make a scope sheet for static pages, CMS collections, assets, forms, locales, analytics, integrations and custom code. Identify the person who controls the domain and DNS. Keep the original site running while you rebuild on a staging address. Check the website reference configurations for a dated starting cost, then quote the actual CMS volume, access and extras.
Capture content and recreate the structure
Inventory every public URL, title, description, canonical and image alternative text. Obtain a CMS export using an available method you have checked, record the tool and scope, and inspect the resulting CSV before treating it as complete. Retain original media files and their usage rights. A screenshot is useful for visual comparison but does not preserve editable content, forms or interactions.
Recreate Webflow templates and responsive layouts explicitly. Start with one representative page and collection item. Include the longest title, a missing optional image, a rich-text item and a reference to another collection in the pilot. Check keyboard navigation and focus as well as desktop appearance.
Map CMS fields before import
| Source content | Destination | Validation |
|---|---|---|
| Title and slug | Name and slug fields | Keep the public path or record its redirect. |
| Rich text | Rich-text field | Check links, headings and embedded content. |
| Image and alt text | Image plus explicit text field | Check imported image and rendered alternative text. |
| Category / author relationship | Reference field | Match the destination item’s actual slug. |
| SEO title / description | Mapped fields and template bindings | Inspect rendered page source. |
In Webflow, open the CMS panel, select the Collection and choose Import. Upload the CSV, confirm its header row and review the field mapping and item preview. Create a pre-import backup. Reference values must match destination slugs; images need working source URLs. Existing matching item IDs can update records, so distinguish new items from updates. Read the official import instructions and keep the failure report when any rows are rejected.
Preserve existing redirects
Webflow’s redirect CSV import replaces the existing redirect list. Export that list first, merge the intended old-path → new-path mappings, and review duplicates and loops. In Site settings → Publishing → 301 redirects, import the reviewed two-column CSV. Publish to apply the changes. See Webflow’s redirect procedure.
The downloadable worksheet below is a planning file, not a provider-ready redirect import. Keep its validation columns out of the final two-column upload. Map each retired page to a relevant destination; redirecting unrelated pages to the homepage conceals content loss.
Validate and cut over
- Compare source and destination page and item counts. Explain every intentional omission.
- Test desktop and narrow-screen layouts, keyboard focus, media, internal links and a synthetic form submission to an authorised test destination.
- Check canonical tags, titles, descriptions, sitemap and indexing settings on the intended production configuration.
- Record old DNS values, current redirects, backup identifiers and a cutover owner. After switching the domain, check HTTPS, representative pages, redirects and form delivery again.
If routing or forms fail, restore the previous DNS target and pause edits on the new site while resolving the problem. DNS rollback is not instant; retain both hosts and access during the transition. Reconcile content or enquiries created during the overlap before retrying. No completion time is promised because this workflow has not been timed in a native migration.
Keep a migration record
Download the CSV planning worksheet
Synthetic examples are marked and all execution statuses start as “not run”. Replace them with your own inventory. This worksheet is for planning and verification, not an import file for either provider. Keep customer data in your own approved storage.
Sources checked
Need help scoping the work? Ask about a separate migration proposal. The £149 newsletter decision memo does not include this migration.