Dardo
Start a project
ENESPT
ENESPT

WordPress to Webflow migration that keeps your URLs and rankings

We move WordPress sites to Webflow. Posts, pages, custom post types and ACF fields become Webflow collections, plugins are replaced or retired, and the theme is rebuilt as Webflow components. Every WordPress URL either keeps its path or gets a 301, and titles, canonicals and redirects are checked on staging before launch.

By Nicolas Ceron13 min read
Get a proposalMessage us on WhatsApp
Dardo / Editorial illustration
On this page

Why teams move from WordPress to Webflow

The usual reason is upkeep. A WordPress site is a theme plus a stack of plugins, and someone has to update, test and secure each one. Patchstack's count for 2025 was 11,334 new vulnerabilities across WordPress, and 91% sat in plugins. Webflow runs the hosting, SSL and the platform itself, so there is nothing to patch. The move pays when a marketing team, not a developer, will run the site after launch.

  • A plugin list nobody wants to own, where each update risks a broken layout
  • Marketers waiting on a developer to change a page or publish a landing page
  • A page builder that has grown hard to edit and slow to load

Speed data favors Webflow too. HTTP Archive figures for September 2026 show 80.2% of US Webflow sites passing every Core Web Vital on mobile, compared with 62.0% of US WordPress sites. Each figure averages a whole platform and says nothing certain about one site, so look at your own Search Console data before making speed the reason.

WordPress and Webflow compared for this move

Both platforms can run a fast marketing site that ranks. What changes is who maintains it, how content is structured and what each extra person costs. Webflow figures are its 2026 plans as listed in October 2026, billed yearly. Our Webflow vs WordPress comparison prices a full bilingual site on each over three years.

WordPress and Webflow compared for this move
AreaWordPressWebflow
Hosting and updatesAny host; you or the host apply core, theme and plugin updatesWebflow hosts the site on its CDN; no plugins to patch
EditingBlock editor or a page builder, with roles such as Contributor, Author and EditorVisual editing on the page; Limited seats edit content and build pages from components
Content modelPosts, pages, custom post types and custom fields, with no item limit in the softwareCollections with typed fields and references; Premium holds 20,000 items in 40 Collections
SEO controlsAdded through SEO and redirect plugins you configure and updateTitles, descriptions, canonical, sitemap and a schema field built in
RedirectsA plugin or server rules301s on paid site plans, imported by CSV; Webflow recommends 1,000 rules at most
Code and lock-inOpen source; content leaves as an XML export and the site moves to any hostRuns only on Webflow; code export needs a paid Workspace and leaves out CMS content
Running costHosting and premium plugins; no fee per userPremium at USD 25 a month, plus USD 15 for each Limited seat

What comes across from WordPress, and what doesn't

Content comes across; the machinery around it doesn't. Webflow offers no automatic conversion from another platform, and its own WordPress guide routes content through WordPress's XML file, converted to CSV and imported Collection by Collection. The XML carries posts and pages, custom post types and fields, comments, users, and categories, tags and other taxonomies; media files stay on the old server, referenced only by link. Our guide to moving from WordPress to Webflow walks through each export route.

  • Posts, pages and custom post types: exported to CSV, one file per Webflow Collection
  • SEO titles and meta descriptions kept by your SEO plugin: exported as custom fields, so each post keeps its own
  • Shortcodes: arrive as literal text, so the export is searched for them and each is replaced before import
  • Page-builder layouts from Elementor, Divi and the like: rebuilt in Webflow, because the layout lives in the builder's own data
  • Forms: rebuilt in Webflow; paid site plans take unlimited submissions, and upload fields work on Premium or Ecommerce Plus and higher, 10 MB per file at most
  • Members, courses and gated content: Webflow ended User Accounts on 29 January 2026, and its suggested replacements are Outseta and Memberstack
  • WooCommerce: Webflow Ecommerce stops at 15,000 items on its USD 212 Advanced plan, so large catalogs and subscriptions are better served by staying or by Shopify
  • WPML or Polylang translations: mapped to Webflow Localize, at USD 9 to 29 a locale a month

How WordPress content maps to Webflow collections

Webflow's CMS import sets the rules the content model has to follow. A CSV file tops out at 4 MB. Reference fields link by item name or slug, so categories and authors must exist before the posts that use them. Rich text arrives as HTML, and Webflow may remove embed markup it doesn't support. Images are pulled from their URLs with no responsive variants, so they're resized beforehand, and file fields can't be filled by any import.

How WordPress content maps to Webflow collections
In WordPressIn WebflowHow it moves
PostsA posts Collection, at /blog/post-slugCSV with title, slug, body HTML, excerpt, image, dates and SEO fields
PagesStatic pages built from componentsRebuilt in the Designer, copy moved page by page
Custom post types such as case studies or locationsOne Collection eachTheir own CSV, after the Collections they reference
Categories, tags and authorsCollections linked by reference or multi-referenceImported first and matched by slug
ACF text, select, true or false, date and numberPlain text, option (up to 100 choices), switch, date and numberMapped column by column; values like $100 are cleaned to plain numbers
ACF image and galleryImage and multi-image fieldsImage URLs; gallery URLs separated by semicolons
ACF relationship and post objectReference or multi-referenceMatched by name or slug
ACF repeater and flexible contentNo direct equivalentA separate Collection with references, or rich text, decided field by field
ACF file fields and PDFs in /wp-content/uploads/Webflow assetsUploaded by hand; linked file URLs redirected to the page that now hosts them

How we move a WordPress site to Webflow

We start with an inventory of everything the WordPress site answers, not only the pages in the menu: posts, archives under /category/, /tag/ and /author/, feeds, plain /?p= links, attachment pages and files in /wp-content/uploads/. Landing pages from Search Console and analytics over at least a full year are added, along with the pages other sites link to. Each URL gets a decision: keep, redirect, merge or retire.

The content model follows from that list: one Collection per post type, Collections for categories, tags and authors, and a decision for every ACF field, repeaters above all. We export a CSV per Collection, rebuild the theme as Webflow components and Collection templates on a staging copy kept out of search engines, and import in reference order. The live WordPress site keeps serving visitors until the switch.

Redirects are where WordPress moves go wrong. Webflow always places CMS items under a Collection folder, so posts at the root or under date permalinks need one rule each. A redirect CSV import replaces every existing rule, older rules are tried first, and a path that still has a published page can't be redirected. So we write the full 1:1 map once, import it as one file and check its size against Webflow's recommended 1,000 rules. Our free redirect map generator does the first pass from your WordPress sitemap and the Webflow staging sitemap.

Ahead of launch, staging is crawled with every old URL, trailing slash included, since WordPress permalinks end in one and Webflow paths don't. The switch happens in a scheduled window: DNS pointed at Webflow, redirects live, sitemap submitted and forms tested with real submissions. At 30 and 60 days, indexing and clicks are checked against pre-launch numbers, and the accounts, DNS records and redirect list are handed over. The full scope is on our website migration service page; design and build on their own sit under Webflow development.

Checks before and after a WordPress to Webflow launch

Rankings rarely fall because of the new platform. They fall when URLs that earned traffic stop answering, or when a post loses the title it ranked with. These checks run on staging and again on the live domain, and our migration SEO checklist has the full list.

  • Every old URL in the inventory returns 200, a single 301 to a page that returns 200, or a deliberate 404 or 410
  • No chains, no loops and no batches of old posts sent to the home page
  • Each post keeps its own SEO title and description, through fields used in the Collection template's pattern
  • The global canonical URL is set in Webflow's SEO settings, without a trailing slash
  • Structured data is rebuilt in each template's schema field, which can't use reference, multi-reference or multi-image fields
  • Every form delivers a real test submission to the right inbox or CRM
  • Analytics, conversion events and the consent banner work on the live domain
  • Webflow's generated sitemap is submitted in Search Console; a Change of Address is filed only if the domain changes
  • Indexing and clicks are reviewed at 30 and 60 days, and redirects stay in place for at least a year

A migration ends at the 60-day review. If the data then points to content or technical work beyond the move, that's a separate SEO engagement rather than part of the migration scope.

When to stay on WordPress

Some WordPress sites are better left where they are, or moved somewhere other than Webflow. These are the cases where the move costs more than it returns:

  • More than 20,000 posts, pages and other CMS items, which is Premium's ceiling
  • Over 1,000 posts at root URLs, which would need more redirect rules than Webflow recommends
  • A WooCommerce store with subscriptions, or a catalog near Webflow's 15,000-item limit
  • Members, courses or bookings run by plugins, unless you budget for a tool such as Outseta or Memberstack
  • A large writing team: each Limited seat is USD 15 a month billed yearly, while WordPress charges nothing per user
  • A site that works and a team that's happy editing it, where fixing speed and design in place costs less

If the real problem is speed or plugin upkeep and your editors like WordPress, WordPress to Astro keeps WordPress as the editor behind a fast coded front end. If the site is mostly designed pages with a small blog, compare a WordPress to Framer move.

What Webflow costs to run after the move

Webflow bills per site and per person. These are Webflow's 2026 plans as listed in October 2026, in US dollars before tax. Any site with a blog needs Premium, because Basic has no CMS.

What Webflow costs to run after the move
LineBilled yearly, per monthBilled monthlyWhat it covers
BasicUSD 15USD 25300 static pages, no CMS
PremiumUSD 25USD 3920,000 CMS items, 40 Collections, 50 GB bandwidth
Limited seatUSD 15USD 19One person editing content
Full seatUSD 39USD 45Design and admin
Localize EssentialUSD 9 a localeUSD 12 a localeUp to 3 locales
Localize AdvancedUSD 29 a localeUSD 35 a localeUp to 10 locales, with translated URLs
Bandwidth to 100 GBUSD 20USD 30Premium add-on
Ecommerce, Standard to AdvancedUSD 29 to 212USD 42 to 235500 to 15,000 items

A blog run by an owner and two writers on Premium comes to USD 25 + 15 + 15 = USD 55 a month, or USD 660 a year, before languages and bandwidth. Since Webflow retired its legacy Editor, every new person who edits needs a paid seat. Our Webflow pricing calculator prices your own seats, locales and traffic, and Webflow pricing in 2026 explains renewals and add-ons.

We don't publish a migration price. Each WordPress move is quoted from the URL inventory, and the quote follows the number of URLs and templates, the post types and ACF fields to model, the plugins to replace, integrations, languages and any store data. For the prices other providers publish, see what a website migration costs.

Questions before you choose

Will we lose Google rankings moving from WordPress to Webflow?

Some movement is normal: Google says to expect temporary fluctuation while it recrawls a moved site. Lasting losses usually come from old URLs that stop answering or posts that lose their titles. A 1:1 redirect map tested on staging, carried-over SEO fields and reviews at 30 and 60 days prevent those. Nobody can guarantee rankings.

Can we keep our WordPress URLs in Webflow?

Many of them. Static pages can keep their paths, and posts under a base such as /blog/ keep the same path if the Webflow Collection uses that base, minus the trailing slash. Posts at the root or under date permalinks can't, because Webflow places CMS items inside a Collection folder, so each one gets a 301.

Does Webflow import WordPress sites automatically?

No. Webflow states it has no automated conversion from other platforms. Posts can come in through CSV, or through a Marketplace app such as WP to Webflow, made by Eclipse SRL and free according to its Marketplace listing, which brings over posts, images, categories and tags, though not pages or custom fields. The theme is rebuilt every time.

What happens to our custom post types and ACF fields?

Each custom post type becomes a Webflow Collection, and most ACF fields have a direct match: text, images, galleries, relationships, selects, dates and true or false switches. Repeaters and flexible content don't, so each becomes its own Collection or rich text. File fields are uploaded by hand, because Webflow's CSV import doesn't fill them.

Can our editors still publish after the move?

Yes, in Webflow's editing view, where writers change text, images and Collection items or build pages from approved components without touching the layout. Each person who edits needs a seat: a Limited seat costs USD 15 a month billed yearly, as of October 2026. Editor roles are checked before launch so the team can publish the next day.

What happens to the old WordPress site and hosting?

Hold on to the domain. WordPress and its hosting stay in place until three things are true: Webflow answers every old URL, you have a complete export and backup, and no redirect still relies on the old server. The handover dates each cancellation, so nothing renews or lapses unexpectedly.

How long does it take to move from WordPress to Webflow?

The build depends on how many URLs and templates there are, the custom fields to model, the plugins to replace and how fast approvals come back. Search runs on its own clock: Google notes that a small or medium site can need a few weeks before most of its pages move, which is why the reviews at 30 and 60 days are part of the work.

What does Dardo charge for a WordPress to Webflow migration?

Dardo quotes each move from the URL inventory: URLs and templates, post types and ACF fields, plugins to replace, integrations, languages and store data set the price. After launch, Webflow Premium is USD 25 a month on yearly billing, and each Limited seat adds USD 15, at October 2026 prices. Prices other providers publish are in our website migration cost article.

What happens to our images, PDFs and forms?

Media library images are re-hosted on Webflow, and old image URLs with links or image-search traffic are redirected. PDFs and other files are uploaded by hand, because Webflow's CSV import can't fill file fields. Forms are rebuilt in Webflow and tested with real submissions; export past entries from your form plugin first.

From the blog

Sources & further reading

Sources behind this page, with further detail from the original publishers.

Plan the WordPress move before you cancel hosting

Send your WordPress URL and a rough count of posts, post types and plugins. We reply with the questions that set the scope: which URLs change, how the custom fields map and which plugins need a replacement.