Convert WordPress to Webflow: What Actually Needs to Be Migrated?

To convert WordPress to Webflow, you need to move more than pages and blog posts. Content can be exported and imported in parts, but the design system, templates, plugin functionality, forms, integrations, tracking, and SEO setup each need a separate decision.

The useful question is not simply, "Can this move?" It is: should this item be imported, rebuilt, replaced, or retired?

This framework helps you define the real migration scope before the build estimate, content import, and launch date are fixed.

The short answer: what gets imported, rebuilt, replaced, or retired

There is no single transfer that turns a complete WordPress website into an equivalent, editable Webflow site. WordPress can export content, and compatible structured data can be prepared for Webflow CMS Collections. The rest of the website must be assessed separately.

One blog system may require all four actions. Article records are imported, the article template is rebuilt, a plugin-powered related-content feature is replaced, and unused tag archives are retired. The parts are connected, but they do not move in the same way.

The goal is not to recreate every historical WordPress decision. It is to preserve what creates value, rebuild what the new site needs, replace necessary workflows, and leave unnecessary complexity behind.

Start with a migration inventory, not a page list

A URL list shows what visitors can open. It does not show everything the marketing, sales, SEO, and operations teams depend on. A useful migration inventory covers both the visible website and the systems behind it.

Inventory what users see

Start with static pages, blog posts, custom post types, media, navigation, search, archives, and templates. Record the current URL, business purpose, value, and intended destination. A high-value landing page may keep its URL, while overlapping articles may be consolidated and an expired campaign page retired.

Inventory what the business depends on

Then capture the behavior that is less visible:

• Forms, validation, notifications, and lead routing
• CRM and marketing automation connections
• Analytics events and advertising pixels
• Cookie consent dependencies
• Search, filters, calculators, scheduling, or chat
• Custom scripts and embeds
• Editor roles, approvals, and publishing workflows

A plugin name is only a clue. Record its purpose, dependencies, owner, and expected result. A simple contact form may support consent, CRM assignment, automation, attribution, and sales notifications.

Give every item an action, owner, and acceptance test

An acceptance test is a plain statement of what must be true for the item to count as migrated. Add priority and open questions so uncertainty is visible before development starts.

Without these decisions, "migrate the website" means something different to every stakeholder. A clear WordPress to Webflow Migration scope makes proposals easier to compare.

What can be imported: content, CMS data, and selected media

WordPress can export content, but an export is only source material. Before preparing an import, decide what the Webflow CMS should contain and how editors will use it.

Pages, posts, and custom content types

Static page copy can move, but the page layout belongs to the rebuild. Blog posts and other repeated content may fit Webflow CMS Collections. WordPress custom post types may also become Collections, but only after the destination model is defined.

Resources, webinars, customer stories, and product updates may be separate post types. Combining them could simplify import while weakening filtering, relationships, and templates. Design the destination CMS around the new templates and editor workflow, not the export columns.

Fields, taxonomies, authors, dates, and relationships

Article bodies are only one part of a CMS record. A field map should define the source, destination, transformation, owner, and validation rule.

A valid CSV import can still create a poor CMS. Categories, tags, authors, custom fields, and related records often need cleanup or transformation rather than a direct column match.

This matters more at scale. In the MonitorQA migration, the known scope included more than 120 blog posts alongside CMS architecture, redirects, technical SEO, analytics, and tracking. At that size, the hard part is not copying article text. It is making the mapping repeatable and proving that each record works in its destination.

Images, files, alt text, and other media

Inventory each asset's source URL, record relationship, alt text, caption, file type, and current use. Avoid moving duplicates, unused uploads, outdated files, and generated variants simply because they exist.

What must be rebuilt: design, templates, navigation, and behavior

WordPress themes and page-builder layouts can guide the Webflow build, but they do not become a maintainable Webflow system by importing content.

Static pages, CMS templates, and reusable components

Static layouts must be recreated, repeated content needs CMS templates, and global elements should become reusable components where appropriate.

Can marketing create an approved page or CMS record without cloning and repairing a one-off layout? If not, the old maintenance problem has probably been rebuilt.

A desktop screenshot does not define how navigation, forms, images, and long content should behave across breakpoints.

If visual and structural changes happen during the migration, treat the project as a redesign with migration risk. Page purpose, URL decisions, and template acceptance should be approved separately because changing them together makes problems harder to isolate. See [Internal link: How to Redesign a Website Without Losing SEO] for the wider redesign controls.

Navigation, search, filters, and interactive behavior

Rebuild menus from the approved information architecture. Assess search, filtering, tabs, calculators, and other interactions by user need. The destination may use native Webflow features, an external service, or custom code. The correct choice depends on behavior, operating cost, ownership, and testability, not whether a similarly named WordPress plugin exists.

What must be replaced or reconnected: plugins, forms, integrations, and tracking

WordPress may use plugins for SEO, forms, redirects, search, schema, consent, security, and integrations. Those plugins do not move into Webflow, but the business requirements behind them may remain.

Replace the business purpose, not the plugin name

This avoids assuming a native feature replaces the full workflow or rebuilding legacy behavior without a current need.

Rebuild forms as complete lead workflows

A form is more than visible fields. Account for validation, consent, spam protection, submission storage, notifications, CRM or email destination, automation, analytics, and confirmation behavior.

A browser success message does not prove the migration worked. A form can show "thank you" while CRM routing or measurement fails. Test one submission through every downstream system and record the result.

Reconnect analytics, advertising, consent, and custom scripts

Do not treat copied code snippets as verified measurement. For each important event, document the event name, trigger, parameters, consent condition, and destination. Then test the real user journey.

Can the team distinguish a view from a submission? Do events fire once? Does the thank-you flow preserve attribution?

Scheduling tools, calculators, chat, embeds, APIs, and custom scripts need the same treatment: purpose, destination, owner, and acceptance test. Hidden workflows are cheaper to discover in the inventory than during launch QA.

What must be preserved or remapped for SEO

SEO preservation is not a final redirect task. Search signals belong in the migration inventory from the beginning.

URLs, redirects, and internal links

Export the current URL set and decide what happens to every important address.

Avoid broad redirects that send unrelated pages to the homepage. Update internal links to point directly to new destinations instead of relying on redirect chains.

The broader guide to WordPress to Webflow Migration: How to Move Without Losing SEO covers the end-to-end process. Here, the key point is that every URL needs an explicit decision.

Metadata, canonicals, indexation, and schema

Inventory titles, descriptions, Open Graph fields, canonicals, noindex decisions, robots controls, sitemap behavior, and structured data. Recreate the intended behavior and validate the rendered output. Blindly copying old settings can preserve mistakes.

Prove production behavior after launch

Staging QA is necessary, but production is the final environment. A redirect spreadsheet is not evidence until the live old URL has been tested.

Use template checks for shared behavior, automated coverage checks for large URL sets, and item-level review for exceptions. The Flotek migration involved more than 400 articles alongside redirects and technical SEO. Sampling can find a template issue, but it cannot prove that every individual decision was implemented.

Use a Website Migration SEO Checklist for Webflow Projects for deeper launch controls, with an owner, expected result, status, and remediation path for every critical check.

What should be retired instead of migrated

Migration is also an opportunity to remove content and functionality that no longer creates value. Retirement reduces build work, but it still requires stakeholder, URL, data, and compliance decisions.

Content to consolidate, redirect, or remove

Candidates include duplicate articles, expired campaigns, thin archives, unused taxonomies, and outdated offers.

Low traffic alone is not a reason to delete a page. Consider backlinks, conversions, sales use, support value, contractual needs, and replacement purpose. Document every retired URL and required redirect.

Functionality to simplify or stop supporting

The same principle applies to plugins, forms, scripts, and integrations. If nobody owns a workflow, no current process relies on it, and it creates no measurable value, recreating it may only carry technical debt into Webflow.

Before retirement, confirm the purpose, users, revenue or compliance role, replacement need, and affected data or URLs.

Build the scope before choosing DIY, freelancer, or agency execution

Page count is a weak proxy for migration complexity. The execution model should reflect the number of content models, critical integrations, conversion paths, URL changes, and approval teams involved.

A small migration may be manageable internally

An internal team may be able to handle a site with few pages and CMS items, limited organic search exposure, simple forms, few integrations, no complex custom behavior, and clear ownership for implementation and QA.

The team still needs URL decisions, tested forms, and launch checks, but the dependencies may be manageable without a large cross-functional process.

Complex migrations need cross-functional ownership

Specialist support becomes more valuable when the site has:

• A large content library or several custom content types
• Valuable organic traffic and many indexed URLs
• Major URL or information-architecture changes
• CRM, automation, consent, and attribution dependencies
• Localization, ecommerce, memberships, or custom applications
• A redesign happening alongside migration
• A fixed launch date with little room for remediation

These projects require cross-functional decisions. External support does not replace internal owners; it should give them a shared framework and verifiable handoff.

What a complete migration scope should contain

Before comparing estimates, look for:

• An inventory and action for every important item
• A destination CMS model and field map
• A URL and redirect map
• Decisions for forms, plugins, scripts, and integrations
• A tracking and consent plan
• Named owners and acceptance tests
• Launch and post-launch validation

Compare proposals on these outputs, not only page count and development hours. Scope also determines delivery time, so use a realistic How Long Does a WordPress to Webflow Migration Take? only after the dependencies are known.

Conclusion

A WordPress to Webflow migration becomes easier to control once every important item has a destination, an action, an owner, and a test. That work should happen before the build estimate and launch date become commitments.

If your inventory includes a large content library, valuable organic traffic, or several critical integrations, a readiness review can identify omitted scope, classify the import, rebuild, replace, and retire decisions, and surface SEO, CMS, integration, and tracking risks early.