Webflow Migration Guide: To or From WordPress, or Astro

Three routes, one decision

Most Webflow migrations follow one of three routes. The right one depends less on the platform and more on who edits your site every week.

This guide covers why teams move, what Webflow lets you take with you, the steps for a Webflow to WordPress migration, a WordPress to Webflow migration and a move to Astro, and the SEO checks that protect your rankings. At the end is a fit check to help you choose. If you already know your route, our Webflow migration services can take it from there.

Why teams leave Webflow, and why some come back

The usual reasons for leaving

• Cost as the site grows. Webflow’s site plans start at $15 a month (Basic, no CMS) and $25 a month (Premium, which adds the CMS), billed yearly. Extra editors cost $15 a month per limited seat and $39 per full seat, billed yearly. Code export needs a paid workspace plan, and publishing workflows, foundational governance and bundled localization sit in the Team plan at $2,500 a month on an annual contract. A static Astro site can often host for free: Cloudflare Pages’ free plan allows 500 builds a month and up to 20,000 files per site.
• Updating friction. Every change runs through the Designer or the Editor, and every extra person who needs to make changes adds a seat.
• AI editing. Webflow now ships an official MCP server that lets AI assistants create pages, edit styles and manage CMS content through Webflow’s APIs. Teams that use AI coding assistants all day still often prefer a plain codebase, where the AI can read and change every file, run the build and open a pull request.
• Ownership. Your site lives on Webflow’s platform. Code export exists, with major limits (next section).
• Retired features. Webflow sunset User Accounts on January 29, 2026 and points membership sites to partners such as Outseta and Memberstack. If you relied on native memberships, you are already migrating something.

Why some teams come back

The move away from Webflow runs both ways. A common failure pattern with code-first rebuilds: prompt-based edits slowly produce inconsistent page sections and off-brand changes, because nobody has a visual source of truth for the design. Marketing teams that edit pages visually every day often find Webflow easier to live with.

The lesson: a code-first site needs component rules, a review step and a sensible editing path for marketers. Without those, the flexibility that attracted you turns into drift. We cover this in the fit check below.

Route 1: Webflow to Astro or Next.js

What Webflow lets you take with you

Webflow’s code export requires a paid workspace plan (Core, Growth, Freelancer or Agency on the pricing page). It gives you HTML for every static page, CSS, JavaScript and your uploaded images. According to Webflow’s help center, it does not include:

• CMS content: collection lists show their empty state and collection pages show no content bound to collection fields
• Ecommerce content and user account data
• Code components
• Working forms (including file upload and reCAPTCHA) or site search
• Password protection: protected pages become public
• Localized pages, elements and content

CMS collections and ecommerce products can be exported separately as CSV files. Each export covers the locale you are viewing, so a localized site needs one export per locale, and rich text fields come out as HTML. So a real migration runs on two streams: the design (from the code export or rebuilt) and the content (from the CSVs).

Steps

1. Benchmark first. Crawl the site and export Search Console data before anything else (see our website migration SEO checklist).
2. Export CMS collections to CSV and convert each row into a Markdown file (Astro) or CMS entry (Next.js with Sanity, Payload or similar). An AI coding assistant can write this conversion script quickly.
3. Download all images, including CMS images hosted on Webflow’s CDN, and update paths. Don’t leave images linked to Webflow’s servers.
4. Rebuild the design as components. Use the code export or rendered HTML as a reference and have the AI build clean, reusable components. Webflow’s class-heavy markup is rarely worth keeping as-is.
5. Rebuild localization if you used it, with proper hreflang, since the code export leaves localized pages out.
6. Replace forms and search with a form service or serverless function and a static search index such as Pagefind.
7. Keep Webflow’s URL structure. Webflow collection URLs follow a /collection-slug/item-slug pattern. Keep them identical unless you have a clear reason to change.
8. Set up governance: a component library, design rules, a preview-and-review workflow and an editing path for marketers.

Astro or Next.js?

Astro for content and marketing sites; Next.js if you need logins, dashboards or live data. Most Webflow sites are marketing sites, so Astro is usually the fit.

For a sense of what a well-run move to Astro can do: our Prawomat case study moved a WordPress site to static Astro pages. Its 2,646 URLs became about 1,370, each judged on clicks and backlinks, and in the 19 days after the switch Google clicks rose 2.9x and appearances in Google AI answers 6.4x. The source was WordPress, but the playbook (URL map, content triage, static build) is the same one we use for Webflow.

Route 2: Webflow to WordPress migration

This route suits teams that need WordPress’s plugin ecosystem, WooCommerce or a large pool of freelancers. If you are still weighing the platform itself, read is WordPress still worth it first.

1. Export CMS collections to CSV and import them into WordPress with a CSV importer (WP All Import is a common choice), mapping fields to posts, custom post types and custom fields.
2. Rebuild static pages in the block editor or a lightweight theme. Avoid heavy page builders if speed matters to you.
3. Move images into the WordPress media library and update references.
4. Set permalinks to match Webflow URLs. WordPress’s default structure differs, so configure permalinks and custom post type slugs to keep /collection/item paths where possible.
5. Install an SEO plugin (Yoast or Rank Math) and fill in the SEO titles and meta descriptions from your Webflow export.
6. Rebuild forms with a form plugin and connect them to your CRM.
7. Harden and maintain: keep plugins to a minimum, set up automatic updates and backups, and add a security plugin or managed host. Patchstack counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025, and 91% of them were in plugins (Patchstack).

Route 3: WordPress to Webflow migration

This route suits marketing teams who want a visual editor and no plugin maintenance, and who are comfortable paying platform fees.

1. Audit your plugins first. List what each plugin does and how Webflow will replace it: native features, embeds or third-party tools. Memberships now always need a third-party tool, since Webflow retired User Accounts, and complex ecommerce may not have a clean equivalent.
2. Export posts from WordPress to CSV (via a plugin or the REST API) and import them into Webflow CMS collections. Check your plan’s CMS item limit before you start: the Premium site plan allows 20,000 CMS items and 40 collections.
3. Rebuild the design in Webflow using components, so editors can update pages without breaking layouts.
4. Match URLs. Webflow places CMS items under a collection path (for example /blog/post-slug). If WordPress posts lived at the root (/post-slug), you will need a 301 redirect for every post. Webflow’s paid site plans include 301 redirects in site settings.
5. Carry over SEO fields into Webflow’s SEO settings and CMS fields for titles and descriptions.
6. Rebuild structured data. Webflow’s paid plans include schema markup support, but check that it covers everything your WordPress SEO plugin used to output, and add custom code embeds for the rest.
7. Handle images: re-upload to Webflow, add alt text and use Webflow’s responsive image output.

The common SEO trap on this route is step 4. Moving from root-level WordPress URLs to Webflow’s collection paths changes every post URL, and a sloppy redirect map quickly produces redirect chains.

Webflow migration checklist

These checks apply to all three routes. The full version is in our website migration SEO checklist.

• Crawl the old site and export Search Console data before starting.
• Build a one-to-one URL map, paying special attention to CMS collection paths.
• Carry over every SEO title, meta description and Open Graph image. Webflow stores these per page and per CMS field.
• Download all images from the old platform’s CDN, including those in CMS rich text.
• Rebuild localized pages with hreflang, since Webflow’s code export leaves them out.
• Rebuild forms and test submissions end to end.
• Rebuild structured data; custom code embeds are easy to miss.
• Check canonical tags, especially on the webflow.io staging domain, which must not be indexed or used as a canonical.
• Submit a fresh XML sitemap on launch day.
• Keep the old site live on a private URL until redirects are verified.
• Monitor rankings, 404s and indexing for 90 days after launch.

Fit check: which route suits your team?

Answer honestly. The right route is the one your team will still be comfortable editing in two years.

Ask these before you commit

• Who will publish content every week, and what tool will they use?
• Who owns the GitHub repository, CMS, hosting, domain and backups after launch?
• What stops AI or human edits from drifting off-brand?
• Which Webflow features do you use that need a replacement: forms, search, localization, memberships, ecommerce?

When to bring in a Webflow migration agency

If nobody on your team owns redirects, URL mapping and post-launch monitoring, that is the moment to bring in a Webflow migration agency. SEO Savages runs website migrations that grow organic traffic in Google and AI search, including Webflow to Astro or Next.js, Webflow to WordPress and WordPress to Webflow. We start with a free pre-migration risk check and a fit recommendation, and we set up the editing workflow so the site stays on-brand after launch.

FAQ

Can I export my Webflow site?

Partly. Paid workspace plans can export HTML, CSS, JavaScript and images. CMS content, ecommerce content, user accounts, code components, working forms, site search and localized content stay behind. CMS collections and ecommerce products can be exported separately as CSV.

Will I lose SEO moving from WordPress to Webflow?

You keep your rankings if you redirect every changed URL. The biggest risk is that WordPress posts at root URLs move under a Webflow collection path, which changes every post URL.

Is Webflow to WordPress a step backwards?

It makes sense when you need plugins, WooCommerce or a larger freelancer pool. The trade-off is more maintenance and security work.

Is Astro better than Webflow?

For performance, running cost and code ownership, usually yes. For visual editing by non-technical teams, Webflow is easier. Choose based on who edits the site.

How much does a Webflow migration cost?

Webflow migration cost depends on page count, CMS size, localization and integrations. MigrateLab, a specialist agency, publishes fixed-price ranges for moving off Webflow to modern frameworks: $3,000-$8,000 for small sites (5-15 static pages, no CMS), $8,000-$20,000 for 20-60 pages with a blog and one or two CMS collections, and $20,000-$50,000 for 60-150 pages with multiple collections and rich interactions. Enterprise sites with ecommerce, memberships or localization start around $50,000.

Sources

• Webflow Help Center: How do I export my Webflow site code?
• Webflow Help Center: Import/export Collection content
• Webflow pricing (checked 29 September 2026)
• Webflow Help Center: User Accounts sunset
• Webflow Developer Documentation: Webflow MCP server
• Cloudflare Pages: Limits
• Patchstack: State of WordPress Security in 2026
• MigrateLab: Webflow migration cost breakdown 2026