In short
- Keep the URLs, content, backlinks, metadata, proof and journeys that already bring traffic, trust or leads.
- Redesign positioning, navigation, templates, CMS structure and conversion paths if they reflect an older version of the business.
- WordPress exports content as XML, and Webflow’s CMS import works with CSV, so plan field mapping and cleanup before you import.
- Build and test a full old-to-new URL map with permanent redirects before launch.
- For most established sites, a hybrid works best: keep what works, rebuild what holds you back.
When you move from WordPress to Webflow, keep what already creates value: important URLs, useful content, backlinks, metadata, proof, internal links and conversion journeys that work. Redesign the parts that describe an older version of your company or make the site hard to use and run: positioning, navigation, weak templates, plugin-based features, the CMS structure and broken paths to conversion.
The platform is only one decision. You still have to choose whether to rebuild the current site as it is, redesign it completely or mix both. For most established sites, the best answer is a mix: carry over the content and search visibility you’ve earned, and rebuild what’s holding you back.
Three ways to move from WordPress to Webflow
A like-for-like move makes sense when the site does its job and the platform is the problem. A full redesign makes sense when the business and the website no longer match. The hybrid covers the common middle case: parts of the site are valuable, and other parts block the next stage of growth.
What should you keep?
URLs that already bring value
Keep the same path when it still describes the page and fits the new structure. Prioritize URLs with organic traffic, rankings, backlinks, external mentions, conversions or regular returning visitors.
When a URL has to change, redirect it to the closest matching new page. Google recommends preparing a map of old to new URLs and using permanent server-side redirects for a permanent move (Google Search Central). Both 301 and 308 redirects count as permanent (Google: redirects).
Don’t send every retired page to the homepage. A redirect should take people to what they were looking for. If there’s no relevant replacement, removing the page is more honest than a misleading redirect.
Content that still serves the reader
Keep content that’s accurate, distinctive and matches what people search for or need before buying. A redesign can change how it looks without throwing away useful explanations, FAQs, case study evidence, definitions and depth.
Check the data before you cut anything. A page that looks dated may still bring qualified traffic or backlinks. A polished page may bring nothing. Base migration decisions on performance, not looks.
Metadata, structured data and internal links
Export page titles, descriptions, canonical tags, social metadata and structured data. Don’t copy them blindly: remove duplicates, fix outdated messaging and match each field to the final page.
Keep important internal links, but point them at their final URLs. After launch, your navigation shouldn’t depend on redirects when you already know the correct address.
Proof and customer language
Carry over testimonials, case study results, the words your customers use, answers to common objections and the messages your sales team knows work. A redesign should make proof easier to see. It shouldn’t disappear because it lived in an old component.
Everything the site does
List everything the WordPress site does, not only what it shows. Forms, CRM connections, consent, analytics, translations, site search, gated content, memberships, calculators, redirects and plugin features all need a place in the new setup.
What should you redesign?
Positioning that describes an older company
If your audience, category, offer or buying context has changed, keeping the old message only means rebuilding an inaccurate website more neatly.
Use the move to align your core pages with the business you are today. Keep customer language and proof that still work, and rewrite the hierarchy and value proposition where needed.
Navigation that mirrors your org chart
Old navigation often follows how the company is organized inside, or how pages piled up over the years. Redesign it when visitors can’t find what they need to evaluate your offer.
Navigation changes still need URL mapping. A cleaner structure shouldn’t produce unexplained 404s or drop pages that bring search traffic.
Plugin features and markup
WordPress themes, page builders, plugins and shortcodes don’t turn into a working Webflow site. The standard WordPress export contains your content data, but not the theme, plugins, customizations or the media files themselves (WordPress documentation).
Rebuild the features you need on purpose. Drop the ones nobody uses. Replace plugin markup with clean content and Webflow components instead of importing old code into the new CMS.
A CMS model shaped by old limits
Don’t recreate every WordPress post type and custom field by default. Start with what marketing actually needs to publish: articles, case studies, resources, team members, events or other repeatable content.
Define your Webflow collections, fields, references, slugs, filters and who edits what before importing anything. A cleaner model means fewer manual fixes and more consistent publishing later.
Problems that repeat across templates
Redesign templates when mobile, accessibility, speed or consistency problems repeat across the site. Fixing the same issue page by page is a sign that the template or design system is the real problem.
What actually transfers from WordPress to Webflow?
WordPress’s built-in export creates a WXR (XML) file. It can include posts, pages, custom post types, comments, fields, categories, tags, taxonomies and users. It doesn’t recreate the theme, plugins or custom front-end behavior.
Webflow’s built-in CMS import works with CSV files, so the XML has to be converted first, by hand or with a migration tool. Then you create the collections in Webflow, import the file and map each column to a field. Check collection item limits and supported field types for your Webflow plan before you start.
A realistic content migration looks like this:
- Export and back up your WordPress content and media.
- List custom post types, fields, taxonomies, shortcodes and plugin dependencies.
- Design the Webflow CMS structure.
- Convert and clean the data.
- Import a small sample first.
- Check rich text, slugs, dates, authors, categories, images, metadata and references.
- Fix the conversion rules, then import the full set.
The import is one data step. The migration is the whole project around it.
SEO checklist for a WordPress to Webflow move
Before you rebuild
- Crawl the current site and save every indexable URL.
- Export baselines from Search Console, analytics, backlinks, conversions and the sitemap.
- Flag pages with traffic, rankings, backlinks, conversions or strategic value.
- Record titles, descriptions, canonicals, schema, hreflang and internal links.
- Decide for every URL: keep, move, merge, redirect or retire.
Before launch
- Finish the old-to-new URL map.
- Set up direct permanent redirects, without chains.
- Test every old URL against its new destination.
- Check forms, analytics, consent, integrations and conversion events.
- Check titles, descriptions, canonical tags, robots settings, structured data and social metadata.
- Crawl the staging site for broken internal links and missing assets.
- Confirm the production sitemap lists the final canonical URLs.
After launch
- Crawl the live domain and test the old URL list again.
- Submit the new sitemap in Google Search Console.
- Watch indexing, 404s, redirects, rankings, traffic, conversions and lead quality.
- Keep the redirect map, and the old hosting if you can, long enough to track down gaps.
- Fix problems quickly instead of waiting for traffic to recover on its own.
No migration can promise that rankings won’t move at all. The goal is to prevent avoidable losses, make every change deliberate and keep enough baseline data to see what happened.
A practical migration process
1. Audit the current site
Crawl pages and URLs, and also list templates, CMS records, media, plugins, forms, scripts, integrations, tracking and publishing workflows. Ask which parts get used, which create value and which exist only because WordPress needed them.
2. Decide what happens to every important page
Give each URL one outcome: keep at the same path, rebuild at the same path, move and redirect, merge into a stronger page, or retire. Add the owner, destination, content status, metadata status and QA result to your migration sheet.
3. Design the destination before moving data
Set the navigation, page templates, Webflow collections, fields, components and conversion journeys before the bulk import. Otherwise the old WordPress structure quietly becomes the structure of the new site.
4. Build and migrate in batches
Start with representative pages and CMS items. Test the hardest content early: long rich-text articles, multi-reference items, images, embeds and plugin-based content. Scale up once the conversion rules work.
5. Test everything together
A page that looks right isn’t enough. Check URLs, redirects, metadata, structured data, internal links, forms, integrations, analytics, accessibility, speed and responsive behavior.
6. Launch and keep improving
A good migration leaves your team with a site it can run and improve, and that’s the real upgrade over a cleaner copy of the old build. Connect the new site to a prioritized backlog: launch the new core, measure real behavior and improve from what you learn. That’s the Living Website method we use after every launch.
When should you hire a specialist?
The more a mistake would cost, the more a specialist is worth. Consider one if your site has a lot of organic traffic, a large CMS, custom post types, several languages, complex forms or integrations, many backlinks, regulated content, or a redesign happening alongside the platform move. Before you set a budget, see how long a website project usually takes.
The hard part isn’t rebuilding pages in Webflow. It’s deciding what the business can safely change, keeping what already works and checking that the new site serves visitors and search engines correctly.
Still deciding whether the site needs structural work? Read website redesign vs. optimization. If you’ve decided to move, our WordPress to Webflow migration covers the URL audit and redirect map, the redesign, the CMS and content move, a supervised launch and fixes in the first week after.
Frequently Asked Questions
Can you migrate WordPress to Webflow without redesigning?
Yes. A like-for-like rebuild makes sense when your positioning, navigation, content, design and conversion journeys already work, and WordPress itself is the problem. It’s a poor fit when the structure or message is part of the problem, because the move would copy those weaknesses.
Will moving from WordPress to Webflow hurt SEO?
Some ranking movement in the first weeks is normal while Google recrawls the site. Lasting losses usually come from missing pages, wrong redirects, changed content, broken internal links, incorrect canonicals, blocked crawling or missing metadata. Map every important old URL to its new page, use permanent redirects, test the live site and watch Search Console after launch.
Can Webflow import WordPress content directly?
Not from the standard WordPress export. WordPress exports XML, and Webflow’s CMS import uses CSV. The data has to be converted, cleaned, mapped to Webflow collection fields and tested. Themes, plugins, front-end customizations and the media files themselves need separate handling.
What should you keep during a website redesign?
Keep what has evidence behind it: valuable URLs, accurate content, backlinks, proof, customer language, internal links, metadata, structured data and conversion journeys that work. Redesign what’s outdated, structurally weak or hard to run.
How long does a WordPress to Webflow migration take?
For most small and mid-sized sites we work with, 6–10 weeks from kickoff to launch. Page count, the number of content types, extra languages, new copy, redirect complexity and feedback speed move the date. See the week-by-week migration timeline on our service page.