Part of your site
Posts, pages and custom post types
In the export file?
Yes
WordPress to Webflow Migration
We move WordPress websites to Webflow by turning your content types, categories and relationships into Webflow Collections, then rebuilding the design there. WordPress holds a lot of behaviour in plugins, and plugins do not travel with the content. We assess both, then plan and build the Webflow site.
This route suits teams who want tighter visual control of the front end.

01Choose
Select one part, several parts or the whole project to see what each involves.
Where this startsOur WordPress site has custom content types and plugins behind it. We want it in Webflow and need to know what carries over.
02Map
Collections are Webflow's database-style lists. A Collection holds items that share the same fields, and a reference field (a field that points to an item in another Collection) links them. Build the map in this order.
03Export
WordPress's built-in export creates an XML file. The table shows what to expect from it.
Part of your site
In the export file?
Yes
Part of your site
In the export file?
Yes
Part of your site
In the export file?
Yes, with the "All content" option
Part of your site
In the export file?
No, only their details and addresses
Part of your site
In the export file?
No
The file is not a full backup, so we also look at the live site and the database. Image files are collected separately and uploaded to Webflow. Plugin data needs its own check.
04Test
Rich content is where a clean import goes wrong. We open long articles with embedded video, tables, shortcodes (short tags that plugins turn into features) and pasted formatting, then compare them with the original. Page-builder layouts are tested as pages, not only as text.
Functions that never lived in the content need their own tests. These include forms, search, memberships, bookings, redirects and tracking tags. Each plugin is listed and then replaced by a Webflow feature, an outside tool or a custom build, or it is dropped. The export file holds comments, so we decide with you where they should live.
05Launch
Your WordPress addresses may not match the Webflow structure, so we prepare a redirect map (a list sending each old address to its new one) before launch. We test it on the new site and keep WordPress running until your team approves.
After launch, we monitor search performance and fix problems the checks missed. We make no promise that rankings or traffic stay the same. Before the domain changes, we agree who keeps the old site's backups. See Website Migration Services for the wider process.
No. WordPress says the file is not meant as a complete backup. It leaves out your theme, plugins, settings and the image files themselves.
Usually, yes, but we decide one by one. A post type with its own fields and list page often maps to a Collection. A small set of fixed pages may be better as ordinary pages.
No. Plugins are WordPress software and do not move. We list what each plugin does and choose a replacement or a custom build.
It depends on what stays. If every function has a new home, you can retire the old site once the checks are signed off. Otherwise, part of it may stay running.

Share your WordPress address, your custom post types and the plugins you rely on. We will assess what maps cleanly and what needs a rebuild. Our WordPress Website Design service covers staying on WordPress.