Migration
WordPress to Webflow
Posts come across as CSV, pages and the design are rebuilt, and posts move under a folder. A 301 for each changed address protects the search traffic.
Trusted by teams from pre-seed to the S&P 100
What moves, and what gets rebuilt
Each part of the site, what it becomes, and whether it comes across, needs converting or is rebuilt.
WordPressPosts with categories, tags and authors, in the XML file from Tools, Export
Blog postsNeeds convertingWebflowA Blog posts Collection filled from CSV, with Categories and Authors as reference fields
WordPressPages laid out by the theme, the block editor or a page-builder plugin
Pages and designRebuiltWebflowStatic pages and a post template built again in the Webflow Designer
WordPressThe Media Library, with images placed in posts by URL
Images and filesNeeds convertingWebflowImages pulled in by URL during the CSV import; PDFs and other files uploaded by hand
WordPressPermalinks set in Settings, Permalinks, often /post-name/ at the root of the site
URLs and redirectsNeeds convertingWebflowPages keep their paths, posts sit under a Collection folder, and a 301 covers each change
WordPressTitles, descriptions and the sitemap, usually held by an SEO plugin
Search settingsNeeds convertingWebflowSEO fields on each page and template, the sitemap switch and a canonical URL setting
WordPressForms from a form plugin, and the entries it stored in the database
FormsRebuiltWebflowWebflow form blocks with email notifications; old entries exported before the switch
WordPressPlugins for caching, security, backups, redirects, analytics and the rest
PluginsRebuiltWebflowHosting jobs Webflow does itself; the others as settings, Marketplace apps or code
WordPressYour domain, registered wherever it is now and pointed at the WordPress host
DomainComes acrossWebflowThe same domain, connected to the Webflow site on launch day
Moving from WordPress to Webflow, step by step
What the export holds, how posts map to Collections, where the plugins’ jobs go, the redirects, the checks, and who should stay put.
Why teams move from WordPress to Webflow
The usual reason is that the people running the site are marketers and designers, and WordPress keeps needing a developer. Plugin and theme updates are switched on one at a time, a flaw in a plugin is its own developer’s to fix, and backups and the security certificate belong to whoever runs the hosting. On Webflow the hosting, the certificate and the patching are Webflow’s job, and a content editor can change copy and CMS items while the design stays locked.
The second reason is design. A WordPress site looks the way its theme allows, and changing that takes a developer or a page-builder plugin. In Webflow the design is built in the same tool the team edits in, so a new landing page can be laid out without a ticket.
Some reasons are not enough on their own. Moving will not lift your rankings, and for a while it puts every address at risk. A slow WordPress site can often be made quick with a better host and fewer plugins, for much less than a rebuild. If the trouble is the writing or the structure, a new platform carries it across.
Know before you start that there is no automated path. Webflow’s help centre says that moving from any platform to Webflow is a rebuild. The content can come across in bulk. Everything else is made again.
What WordPress lets out, and what Webflow takes in
WordPress has one export, under Tools, Export. Choose All content and it writes a single XML file, in a format WordPress calls WXR, holding posts, pages, comments, custom fields, categories, tags, custom taxonomies, navigation menus and custom post types. You can instead export only posts, filtered to one category, one author, a date range or a status, or only pages. WordPress.com’s guide says the file leaves out the theme, its customisations and the plugins.
Webflow’s CMS takes CSV, one Collection at a time, up to 4 MB a file, and the Site plan sets how many items you can import. Webflow’s own WordPress guide tells you to run the XML through an XML to CSV converter. That conversion is where most of the content work happens. A 300-post blog with full HTML bodies can run past 4 MB, so split it by year and import the files in turn.
What Webflow does with each column depends on the field you map it to. A rich text field accepts HTML, though Webflow may strip elements and attributes it does not support. An image field needs a direct URL ending in an image file, and images imported that way get no responsive variants, so use images that are already sized. Several images go in one multi-image field, separated by semicolons. A file field takes nothing from a CSV: PDFs and downloads are uploaded by hand after the import. Name the CSV columns after the Webflow fields and they map themselves.
Webflow offers to back up the site before each import. Say yes, or save a backup first if the site is large.
How WordPress content maps to Webflow Collections
In Webflow each kind of content is a Collection, with one template page and one set of fields. Map it type by type:
- Posts become a Blog posts Collection. The title goes to the Name field, the slug to Slug, the body to a rich text field, the excerpt to plain text, the publish date to a date field and the featured image to an image field, as a URL.
- Categories become a Categories Collection, linked from each post by a reference field, or a multi-reference field if posts carry more than one.
- Tags become a Tags Collection and a multi-reference field. Every tag is an item and counts towards the plan’s cap, so a site with hundreds of tags used once each should cut them down first.
- Authors become an Authors Collection. The WordPress user accounts stay behind, and anyone who will edit the new site needs a Webflow seat.
- Pages become static pages, built in the Designer. Child pages go in folders, which only static pages can use.
- Custom post types, such as case studies or team members, each become a Collection, and their custom fields become its fields.
Import Authors, Categories and Tags first, then Posts, so the references have something to match. Webflow turns the text in a reference column into a slug and looks for an item with that slug. A category whose slug was edited by hand in WordPress needs that slug in the CSV, or the field comes in empty. A Collection can have up to 10 reference fields, which is plenty for a blog.
Comments have nowhere obvious to go. Webflow’s comments are design feedback for your own team, and we did not find a way for visitors to comment on posts in Webflow’s documentation. Keep the useful ones in the post body, add a comments service through custom code, or let them go.
Post bodies need a pass before import. They hold the HTML WordPress stored, which can include shortcodes: WordPress-specific codes in square brackets that only the plugin that made them can display. Search the export for an opening square bracket and decide what each shortcode becomes in Webflow.
Where each plugin’s job goes
None of the plugins comes with you. Open the Plugins screen, list every active one and write down the job it does. Most jobs land in one of these places:
- SEO plugin: titles and descriptions become fields on each page and Collection template, the sitemap is a switch, the canonical is a site setting, and structured data goes in each page’s schema field on a paid plan.
- Redirect plugin: export its list and merge it into your redirect map, so rules made years ago are kept. Webflow’s redirects are under Site settings, Publishing.
- Form plugin: Webflow’s form block, with file upload, reCAPTCHA and email notifications. Entries are kept under Site settings, Forms, and download as CSV, or a form can send to another service.
- Caching, security, backup and SSL plugins: nothing to replace. Webflow hosts and patches the site, provides the certificate and saves a restore point every 50 auto-saves. It has no scheduled backups.
- Analytics, tag manager and chat scripts: the site-wide head or footer code fields, which need a paid plan.
- Search plugin: Webflow’s site search, which adds a results page at /search.
- Multilingual plugin: Webflow Localize, a paid add-on.
- WooCommerce: Webflow Ecommerce, which has plans of its own. If the store is the business, look at Shopify.
- Anything that connects to another tool: an app from the Webflow Marketplace, a connector such as Zapier or Make, or custom code.
The order of work
We run the move in this order, and it holds if you are doing it yourself:
- Inventory. Take every URL from the WordPress sitemap at /wp-sitemap.xml, or the SEO plugin’s, and add the pages that bring in visits or links from analytics and Search Console.
- Redirect map. Write the new address beside each old one in a spreadsheet before anything is built. It decides the Collection URLs.
- Content model. Create the Collections and fields from the mapping above, then import a test CSV of ten posts and check every field.
- Rebuild. Design and build the static pages and the Collection templates in the Designer, on the staging address.
- Content. Import the full export, the referenced Collections first, then upload the files, paste in the page copy and fix the shortcodes.
- Checks. Set titles, descriptions and the canonical URL, then check forms, internal links and indexability on staging.
- Launch. Import the redirects, connect the domain, publish, test the redirect map against the live site and submit the new sitemap in Search Console.
- Watch. Read Search Console’s not found report and the traffic to the old top pages for weeks after launch, and add redirects for anything the map missed.
Keeping URLs, redirects and search
Pages can usually keep their addresses: a page at /about or /services/consulting becomes a static page at the same path. Category and tag archives at /category/name and /tag/name can keep theirs if you set the Categories Collection URL to category and the Tags one to tag. Webflow Ecommerce reserves category, so a site with a store needs another name.
Posts are the hard part. Every Collection item lives under its Collection’s URL, so a post can sit at /blog/post-name and cannot sit at /post-name. If WordPress used the Post name permalink, each post needs a redirect of its own, 300 rows for 300 posts. Webflow recommends 1,000 redirects at most, and wildcard rules where possible. With Day and name permalinks and unchanged slugs, one rule with capture groups can carry them all: (.*) in the old path for each part of the address, %1, %2 and so on in the new. Plain permalinks such as /?p=123 need a rule each, with the ? and = escaped by a % sign.
Webflow lowercases capitals in page slugs, removes punctuation such as full stops and turns other alphabets into Latin letters, so an old slug with capitals or accents changes on import and needs its own row. Redirects need a paid Site plan or Workspace. They run oldest first, so add specific rules before wildcards. Importing a CSV of redirects replaces all of them, so keep one master file. Webflow will not redirect an address a live page or item still answers: unpublish it or change its slug first.
Turn on the sitemap in Site settings. Set the global canonical URL, because Webflow adds no canonical tags until you do. Carry the SEO plugin’s titles and descriptions across as CSV columns and bind them on the post template.
We inventory valuable URLs, plan redirects and check canonicals, indexability, content and internal links. We also monitor after launch. These steps manage migration risk; they cannot guarantee that rankings will stay unchanged. A dip in the first weeks while Google recrawls is normal.
When this site’s addresses changed, we mapped each old address by hand to the page that replaced it, used permanent redirects and wrote no wildcard rule. Pages with no replacement return a 404 instead of sending people to the homepage.
Checks before you switch the domain
Go through these on the staging site, and the redirect checks again on the live one:
- The number of posts in Webflow matches the number in the WordPress export.
- Every post has its featured image, and opening five posts shows their body images loading from Webflow’s servers, with none still pointing at the WordPress host.
- A search of the published posts for an opening square bracket finds no leftover shortcodes.
- PDFs and downloads linked from posts are uploaded and the links point to the new files.
- Each Collection template and each static page has its own title and description.
- The global canonical URL is set to the live domain, written exactly as the site is served, with https:// and with or without www.
- The sitemap is on and lists the posts under their new folder.
- Every row of the redirect map has been requested and lands on the right page in one hop.
- Each form has its own name, sends notifications to a named person, and a test entry has arrived.
- Analytics and tag scripts are in the site-wide head code and recording visits.
- No robots.txt rule or noindex setting is blocking the site.
- Old form entries, comments worth keeping and a full WordPress backup of files and database are saved somewhere you control.
When to stay on WordPress
For some sites the move costs more than it saves. Stay on WordPress if:
- Several people write every day and an editor approves. WordPress lets a Contributor write without publishing, keeps a revision on every save and can schedule any post. Webflow schedules only items never published before, and not on its lowest plans.
- Many people edit. Each of them needs a Webflow seat.
- The site sells through WooCommerce, or depends on a plugin that runs memberships, courses, bookings or a directory. You would be replacing that system as well as the site.
- The content is large or heavily cross-linked. Collections allow 10 reference fields, show 100 items to a list, and the plan caps the total.
- The site runs in several languages. Webflow’s localisation is a paid add-on, it does not cover Ecommerce, and each locale path needs its own redirects.
- Readers comment, and the comments matter to them.
- The real complaint is speed or upkeep, and a better host, fewer plugins and someone who owns the updates would fix it.
- The site has to share logins or parts with your product. That is a job for custom code.
What decides the time and the cost
The pages take most of the time, because each one is built again. The number of distinct layouts matters more than the number of pages: a dozen landing pages that share three layouts are quicker than six that are all different. The blog is one template however many posts it holds.
The content work grows with how untidy the export is. Shortcodes, page-builder markup inside posts, hundreds of tags and files linked from posts each add to it. Redirects follow the permalink structure: Day and name with unchanged slugs needs a few rules, Post name needs a row per post. Integrations add time too, such as a CRM behind the forms or a newsletter tool.
Our websites start from $15,000, and most take four to eight weeks. A migration is priced as a website project, on the page system, content work, integrations, publishing requirements and migration complexity, and we agree the scope and the price before we start. We build websites in Webflow; Morse Micro’s is one.
If you do the move yourself, the costs are the Webflow Site plan and seats, on Webflow’s pricing page, and the hours of whoever converts and checks the content.
Vendor details were checked against WordPress’s and Webflow’s own documentation on 15 November 2026. Both change their plans and features, so read theirs before you start.
Moving from WordPress?
Short answers, from the guide above.
No. Webflow says there is no automated way to convert a site from another platform, so moving to Webflow is a rebuild. The content can come across in bulk: export it from WordPress as XML under Tools, Export, convert that to CSV, and import it into a Webflow Collection. The pages, the design and the forms are built again in Webflow.
You can keep most of what protects them, and nobody can promise every position holds. We inventory valuable URLs, plan redirects and check canonicals, indexability, content and internal links, then monitor after launch. On Webflow that means a 301 for every changed address, the sitemap switched on and the canonical URL set. Some movement in the weeks after launch is normal.
Most of our website builds take four to eight weeks, and a migration is scoped as a website project. The number of different page layouts decides more than the number of posts, because every page is rebuilt and the blog is one template. Messy post bodies, many forms and integrations, and a permalink structure that needs a redirect per post all add time.
Pages, yes: a static page in Webflow can sit at the same path, with child pages in a folder. Posts usually change, because every Webflow Collection item lives under its Collection’s address, such as /blog/post-name. If WordPress put posts at the root, each one needs a 301 redirect. Date-based permalinks can often be covered by one wildcard rule.
They stay behind, because Webflow does not run them. Caching, security and backup plugins have no replacement to find, since Webflow hosts and patches the site. SEO and redirect plugins become settings in Webflow. Forms are rebuilt with Webflow’s form block. Analytics and chat scripts go in the custom code fields, and other jobs move to Marketplace apps or connectors.
Where to go next
- Webflow vs WordPressWebflow if a marketing team wants a fast, tidy site without plugins. WordPress if an editorial team already lives in it, or needs its ecosystem.
- WordPress to custom codeContent stays in WordPress behind the new site or leaves as XML or JSON. Design and plugins are rebuilt in code, and a redirect map protects search.
- Webflow to custom codePages are written again as components, CMS content leaves as CSV or through Webflow’s API, and a permanent redirect for each changed URL protects search.
Planning this move?
Tell us where it is now and where it is going. We’ll say what we’d keep, what we’d rebuild and how long it takes.
Most teams start with a call, then a sprint or an audit.
The people you’d work with, from the first call to launch