How to Migrate from Webflow to Custom Code
The short answer: export each Webflow CMS collection as CSV, rebuild the templates as components in Astro or Next.js, import the content into a headless CMS or Markdown by script, keep every slug, copy every 301 redirect, and compare the new site with the old one URL by URL before switching DNS. For a B2B marketing site this usually takes 2 to 4 weeks.
When to leave Webflow
Webflow is a mature visual builder with a solid CMS. Teams usually move to code when:
- Plan costs grow with the site. Localisation, extra CMS items and editor seats add up on large sites.
- The CMS model gets in the way. Item limits, reference limits and collections that can’t express the content the team needs.
- The site needs logic. Personalisation, data from your own systems, calculators or gated content that need a server.
- Performance and SEO need more control. Custom JSON-LD per page, hreflang, response headers and llms.txt.
If your team edits layouts visually every week and the site is small, Webflow may still be the better fit.
Step 1: Inventory
Crawl the site and save, for each URL: status code, title, meta description, canonical, H1, Open Graph tags and structured data. List every CMS collection with its fields and item count, every form, every embed and custom code block, and every redirect in the hosting settings. Export 12 months of Search Console data.
Step 2: Export content and assets
- Export each CMS collection as CSV from the collection settings.
- Download images and files referenced in the content and self-host them; links to Webflow’s asset CDN can stop working once the site is unpublished.
- Use the code export (on paid workspace plans) only as a reference for markup and styles. It does not include CMS content.
Step 3: Choose the stack and content model
- Astro for content-heavy marketing sites that should load fast and ship little JavaScript.
- Next.js when the site shares components or data with a React product app.
Map Webflow collections to content types in the new CMS. Turn multi-reference fields into references, and fix collections that duplicate each other.
Step 4: Rebuild templates
Rebuild each template as components. Move Webflow’s classes and variables into design tokens (CSS variables for color, type and spacing). Interactions built in Webflow’s timeline usually become CSS transitions plus small scripts.
Step 5: Localisation
If the Webflow site uses localisation, decide the URL pattern in the new setup (for example /de/ folders), keep the same paths, and output hreflang tags for every language pair, including x-default.
Step 6: Redirects and parity
Copy every 301 from Webflow into the new host’s redirect file and add new ones for any changed URL. Crawl the staging site (set to noindex) and compare it with the baseline: status, title, meta, canonical, H1, schema and hreflang. Test forms, CRM connections and analytics.
Step 7: Launch and monitor
Switch DNS, submit the sitemap and check Search Console daily for two weeks for new 404s and indexing errors.
How Allsite can help
Allsite is a design and development studio for marketing websites. We move Webflow sites to custom code (or to Framer, when a visual editor fits the team better) at a fixed price, typically in 2 to 4 weeks. See the full website migration process, website migration or request a project.
