The short answer
WordPress plugins don't move to Webflow. Each one is replaced by a built-in Webflow feature, an integration or, in a few cases, custom code, and many simply aren't needed. Posts move into Webflow CMS collections by CSV import. Forms are rebuilt with Webflow forms. Any URL that changes gets a 301 redirect, so search traffic and links follow you.
Full migration checklists already exist, including Webflow's own. This guide answers the three questions WordPress teams ask most: what happens to our plugins, our forms, and our URLs?
What happens to your plugins
Webflow has no plugin system like WordPress. That sounds like a loss until you list what your plugins actually do. Most cover hosting, speed, security or SEO, and Webflow handles those itself. The rest map to Webflow features or integrations.
| WordPress plugin type | Examples | In Webflow |
|---|---|---|
| SEO | Yoast, Rank Math | Built-in SEO settings for every page and CMS template, plus an auto-generated sitemap |
| Forms | Contact Form 7, Gravity Forms, WPForms | Webflow forms, connected to your CRM or email tool when needed |
| Custom fields and post types | ACF, Custom Post Type UI | CMS collections with their own fields and templates |
| Caching and speed | WP Rocket, W3 Total Cache | Not needed: Webflow hosting includes a CDN |
| Security and backups | Wordfence, UpdraftPlus | Not needed: Webflow handles security patches and backups |
| Page builders | Elementor, Divi | Replaced by the Webflow Designer; pages are rebuilt |
| Redirects | Redirection | Webflow's 301 redirect settings, with CSV import |
| Multilingual | WPML, Polylang | Webflow Localization (a paid add-on) |
| Store | WooCommerce | Webflow Ecommerce, or keep a separate store such as Shopify |
Before you plan the move, list every active plugin and write one line on what it does for the business. Anything with no clear job can usually go. Anything doing something unusual, like memberships or complex calculators, needs a plan of its own.
What happens to your posts and pages
Blog posts and other repeating content move into Webflow CMS collections. Webflow's help center describes the route: export your WordPress content, then import it into a collection with a CSV file. Each CSV upload can be up to 4MB, and how many items you can store depends on your Webflow site plan.
- Plan the collections first. Decide the fields for each collection: title, slug, body, image, author, category, date.
- Move images too. Images linked in a CSV still point at your old site until they are brought into Webflow.
- Rebuild regular pages by hand. Pages built with a theme or page builder are redesigned or rebuilt in the Designer, not imported.
See how we set up collections on our Webflow CMS development page.
What happens to your forms
Forms are rebuilt as Webflow forms. Submissions are stored in Webflow and can be emailed to your team, and they can also be sent to tools like HubSpot, Mailchimp or Slack through an integration.
- List every form on the old site and where its submissions go today.
- Rebuild each one, then test that a submission lands in the same place as before.
- Check spam protection and any tracking events, such as an analytics goal on submit.
Our forms and integrations page covers the setup in more detail.
What happens to your URLs
This is where rankings are kept or lost. Every old URL that gets traffic or has links pointing to it needs to end up somewhere: either the same address on the new site, or a 301 redirect to its new home.
- Expect blog URLs to change. Webflow CMS pages sit under a collection path, such as /blog/post-name. If your WordPress posts lived at the root or under dates, they will need redirects.
- Map every URL. Crawl the old site, list every URL, and pair each with its new address.
- Import redirects in bulk. Webflow lets you import 301 redirects from a CSV in its publishing settings. Webflow notes that a CSV import replaces the existing redirects rather than adding to them, so import the full list in one go.
- Carry over page SEO. Copy titles, descriptions and social images for each page, and keep the same headings where the content stays the same.
On launch day
- Keep the old site live until the new one is approved.
- Publish the Webflow site with all redirects in place, then point the domain.
- Test the top pages, every form and a sample of old URLs.
- Submit the new sitemap in Google Search Console and watch for errors over the next few weeks.
Questions people ask
Will I lose my Google rankings?
A short dip can happen with any move. Keeping URLs where possible, redirecting the rest and carrying over page SEO is what protects rankings.
Can I import my WordPress posts automatically?
Yes, through a CSV export and Webflow's CMS import. Plan the collection fields first, and bring images over separately.
Do I need a new design to move to Webflow?
No. You can rebuild the current design as it is, or switch to a new design from Figma during the move.
Ready to leave WordPress?
ManyBuilds moves your pages, posts and forms to Webflow, redirects every old URL and keeps your current site live until you approve the new one.
Sources
- Webflow help center: Migrate from WordPress to Webflow CMS.
- Webflow help center: Importing content into the CMS: CSV import and the 4MB file limit.
- Webflow help center: Import/export 301 redirects.
- Webflow: 301 redirect management update: CSV imports overwrite existing redirects.
- BRIX Templates: Does Webflow require ongoing maintenance?: what Webflow hosting handles.