The WordPress XML export will not import into Webflow CMS, which is where most of these moves stall. The reliable path is to convert your posts into a clean CSV that maps directly to a Webflow Collection: one column per field, the body as clean HTML, and the slugs preserved. Then redirect every old URL, since rankings follow the address and the content. The reformat is straightforward; the SEO discipline around it is what protects your traffic. WPBuildAI crawls the site, strips the theme code and shortcodes, and produces a Webflow-ready CSV plus the 301 map, so the import works on the first try.

Export from a settled version rather than mid-cycle: WordPress 7.0 arrived on 20 May 2026, with 7.0.1 fixing 31 bugs on 9 July and 7.0.2 following on 17 July, and an export taken between those points can carry quirks you will spend longer cleaning than re-exporting.

Why the XML file does not work

WordPress XML is a backup format meant for moving between WordPress installs, not an import schema Webflow understands. Its structure, custom fields, and embedded shortcodes do not line up with Webflow’s CSV importer, so the upload fails or produces broken posts. What Webflow wants is a CSV whose columns match your Collection fields exactly, with the post body reduced to clean HTML. The format mismatch is the whole reason a direct import is impossible, and recognising that early saves you from fighting the importer.

The 2024 Web Almanac shows how much shortcode and theme markup a typical WordPress post carries, and all of it has to be cleaned out before the content maps cleanly into a new CMS. A shortcode that rendered a gallery or a button in WordPress is meaningless in Webflow, so it has to be converted to real HTML or rebuilt as a Webflow element, not carried across as a bracketed tag.

Map your Collection fields first

Before exporting anything, define the Webflow Collection you are importing into, because the CSV has to match it. A typical blog Collection has fields for the title, slug, post body, summary or excerpt, published date, author, featured image, and categories, plus any meta fields you use for SEO. Decide which WordPress field maps to which Collection field, and the export becomes a matter of filling those columns. Skipping this step is why imports come back misaligned, with the body in the wrong field or categories missing.

Getting the mapping right once means the rest of the conversion is mechanical. Each post becomes a row, each field a column, and Webflow ingests the CSV directly. The mapping is the thinking; the export is the execution.

Build the CSV around clean HTML

The post body is the field that causes the most trouble, because it has to be clean HTML that Webflow’s rich text accepts. That means the headings, paragraphs, lists, links, and images, without the theme wrappers, shortcodes, and inline styles WordPress added. Convert shortcodes to their rendered output or rebuild them as Webflow elements, and strip the markup that does not belong. A body field full of leftover shortcodes or nested div soup imports as a mess, so the cleaning step is not optional.

Keep the slugs in their own column and matched to the originals wherever you can. Preserving the slug is what keeps a post’s URL close to its old one, which makes the redirect simpler and the ranking transfer cleaner.

Preserve what makes the posts rank

A reformat is also a chance to lose rankings if you are careless. Backlinko’s analysis of 11.8 million search results found content depth, clear structure, and authority signals correlate with ranking, so the content you carry over should keep its headings, internal links, and meta fields intact rather than being flattened. The titles and meta descriptions belong in the CSV too, mapped to Webflow’s SEO fields, so the new pages are not thinner than the old ones in the eyes of search engines.

Map every URL before launch

The single step that protects your traffic is the redirect map. Google’s site move guidance treats a complete old-to-new URL mapping as the core of a safe move, and a WordPress-to-Webflow change is exactly that kind of move. Map each old post URL to its new Webflow URL with a 301, and confirm each resolves in a single hop. Ahrefs found in its search traffic study that a small share of pages carries most organic traffic, so verify the redirects on your best-performing posts first, where a miss would hurt most.

Images and internal links travel with the posts and are easy to neglect. Export the images and re-host them on Webflow or a stable location, then update the references so nothing points back at the old WordPress media library, which will eventually 404. Rewrite internal links to the new Webflow URLs rather than relying on redirects to catch them. The discipline is the same as in migrating images without broken links, and it is what keeps the imported posts from dead-ending on a missing image or a broken link.

Automating the conversion at scale

For a handful of posts you can format the CSV by hand, but for hundreds it pays to automate. A crawl gives you every post, the field mapping is defined once, and the conversion runs mechanically from there, leaving only the exceptions for review: custom fields, unusual post types, or posts with heavy shortcode use. Automating the bulk and reviewing the exceptions is far faster and more reliable than hand-formatting hundreds of rows, where a single misaligned column can break the import. This is the operational version of the structure work in mapping a site before migrating.

A worked example: a 300-post blog into Webflow

Picture a 300-post WordPress blog moving to Webflow. The owner tries the XML export, Webflow rejects it, and the move stalls. The working path is to crawl all 300 posts, map the WordPress fields to a Webflow blog Collection, and convert each post’s body to clean HTML with shortcodes resolved. The result is a 300-row CSV that Webflow imports directly, with slugs preserved and meta fields in place. Alongside it, the old URLs map to their new Webflow URLs as 301s. The posts land complete, the URLs barely change, and the redirects carry the rankings across. The XML never works; the clean CSV always does.

What tends to go wrong

A few mistakes recur. Trying to import the XML directly wastes time on a format Webflow cannot read. Leaving shortcodes in the body imports broken content. Letting Webflow generate new slugs instead of preserving the originals multiplies the redirects and the risk. Forgetting the meta fields makes the new pages look thin. And skipping the redirect map drops the rankings entirely, the failure examined in does WordPress to Webflow hurt SEO. Each is avoidable with the mapping-and-cleaning discipline, and each is a common reason a Webflow move underperforms.

Webflow import limits to plan for

Webflow’s CSV importer has practical limits worth knowing before you start. Collections have field-count and item-count ceilings, CSV uploads have a size limit, and very large blogs may need to be imported in batches rather than one file. Rich text fields accept clean HTML but not arbitrary markup, so anything exotic in your post bodies has to be simplified to what Webflow supports. Knowing these constraints up front shapes how you prepare the CSV: split a large export into batches, keep the HTML to supported elements, and confirm your Collection has the fields you mapped. Hitting a limit mid-import is frustrating; planning around it is routine.

Test the import before it goes live

Import into a staging Collection or a copy first, not straight into the live site. Bring in a small batch, check that each field landed in the right place, the body renders cleanly, the slugs match, and the images resolve, then fix the mapping before running the full import. Catching a misaligned column on ten posts is trivial; catching it after importing three hundred is a cleanup job. A test import is the cheapest insurance against a malformed CSV, and it turns the full run into a confident repeat of something you already saw work.

Custom fields and unusual post types

Standard posts map cleanly, but custom fields, custom post types, and ACF-driven content need a decision. Each custom field becomes a Webflow Collection field, and each custom post type usually becomes its own Collection, so the mapping has to account for them rather than forcing everything into a single blog Collection. Content that lived in page-builder layouts has to be rebuilt as Webflow elements, since it will not survive as a CSV value. These are the exceptions that turn a quick export into a project, and identifying them during the field-mapping step keeps them from surprising you mid-import.

How long the conversion takes

For a straightforward blog, the conversion is quick once the field mapping is set: the crawl and the CSV generation run mechanically, and the import is a few minutes per batch. The time goes into the mapping, the body cleaning, and the exceptions, plus the redirect map and verification. A small blog is an afternoon; a large blog with custom fields and heavy shortcode use takes longer, not because the CSV is hard but because each non-standard piece needs a decision. The redirect map and the staging test are where careful time pays off, since they are what protect the rankings and catch the errors.

When Webflow is the right destination

Webflow suits teams that want design control and a visual editor and are comfortable with its Collection model and pricing. It is a strong fit for marketing and content sites where the design matters and the content volume is manageable. It is a weaker fit for very large content libraries that strain its CMS limits, or for sites that need functionality Webflow does not offer without workarounds. The move is worth it when Webflow genuinely fits how you build and edit; if the main goal is just speed and lower maintenance, it is worth comparing against a static or AI-built rebuild before committing.

Posts are one piece of the move

Moving the posts is the visible part, but a full site move also covers pages, navigation, and any non-blog content, each with its own redirects. The blog Collection is usually the largest and most SEO-sensitive piece, which is why it gets the most attention, and the approach extends to the rest of the site, covered in moving blog posts without losing rankings. Treating the whole move as one redirect-mapped migration, with the posts as the largest Collection, keeps every part of the site intact rather than just the blog. The blog CSV gets the most engineering attention, but the homepage, landing pages, and contact paths all need their redirects too, and skipping them leaves gaps that show up as 404s even when the posts imported perfectly.

Keeping content in sync after the move

If you keep publishing on WordPress during a phased move, the export becomes a moving target, so decide on a cutover. The cleanest approach is to freeze new WordPress publishing once the conversion starts, do the import, set up the redirects, and then publish only in Webflow afterward. If a longer overlap is unavoidable, re-export and import the posts added since the first conversion, just before cutover, so nothing published during the project launches without a redirect. Treating the conversion as a dated snapshot with a clear cutover, rather than an open-ended sync, prevents the awkward gap where a post exists on one platform and not the other.

Key points to remember

Webflow cannot read WordPress XML, so convert posts to a clean CSV that matches your Collection fields, with the body as clean HTML, shortcodes resolved, slugs and meta preserved. Map the fields once and the conversion is mechanical, even at scale. Re-host images, rewrite internal links, and 301 every old URL, verifying the high-value posts first. WPBuildAI crawls the site and produces the Webflow-ready CSV and the redirect map together, so the move imports cleanly and keeps its rankings; send your site URL for a fixed quote.

Not affiliated with WordPress, Webflow, or Lovable.