WordPress to Webflow Migration Guide for Businesses

WordPress sites often contain three overlapping systems: public content, structured database records, and behavior supplied by themes and plugins. Tools > Export addresses part of the content layer. WordPress documents that its export file uses WXR, an XML format, and can contain posts, pages, comments, custom fields, categories, and tags. That file is useful, but it is not a clone of the live site. It does not recreate the theme, plugin code, server configuration, accounts, scheduled tasks, or every vendor's private data inside Webflow.

Audit WordPress as a system, not a page list

Start with a crawl, but reconcile it with WordPress exports and administrator review. Draft, private, scheduled, orphaned, and noindexed records may not appear in a public crawl. Conversely, the database may hold obsolete records that should not reach the replacement. Record the disposition of every public URL and every required nonpublic record. The website redesign and migration library keeps the supporting audits and launch guides together, while the broader website migration planning guide explains how that inventory becomes a launch and rollback plan.

Translate content types instead of copying tables

Webflow's WordPress migration guidance describes exporting WordPress content as XML and converting selected data to CSV before importing it. Conversion is preparation, not strategy. First decide whether a WordPress “Team” custom post type becomes a Webflow People Collection, whether practice areas deserve references, how multiple authors are represented, and whether old tags have any visitor value. Only then define the CSV columns and transformations.

Handle media, authors, comments, and history separately

• Media: build an inventory with source URL, attachment relationship, filename, caption, alt text, rights, dimensions, and destination. Download required originals while the source remains available; do not rely on hotlinking the retired WordPress host.
• Authors: decide whether an author is a public content entity, a byline string, or an administrator. A public author profile does not require giving that person publishing access, and a Webflow editor does not automatically need a public profile.
• Comments: decide whether comments remain public, become a static archive, move to a supported comment service, or are removed. Preserve moderation, consent, and retention obligations; comments in a WordPress export do not create a Webflow comment system.
• Revisions: retain source history when the business or regulator needs it. A new Webflow Collection item will not reproduce the WordPress revision timeline.
• Submissions and users: export through the responsible form, membership, commerce, or CRM system. Treat personal information with approved access, retention, and deletion rules.
• Dates and slugs: distinguish original publication, latest update, import date, and future modification behavior. Test time zones and preserve useful URLs unless a documented reason requires change.

For images, verify that imports create assets the new site can serve independently. Check missing originals, duplicate sizes created by WordPress, WebP or other formats, orientation, captions, and alt text. Do not copy every thumbnail variation merely because it exists in uploads. Keep the best authorized source, create appropriate responsive outputs, and verify image URLs after the old host is unavailable.

Replace plugin outcomes one by one

A plugin inventory often changes the platform decision. If the site is mostly publishing and lead generation, Webflow may remove a layer of WordPress maintenance while supporting a controlled design system. If the business relies on mature membership, learning, multilingual, commerce, or application plugins, replacing them may cost more and reduce capability. A website design engagement should document those replacements before production, and the Webflow versus WordPress guide helps compare the ongoing operating models before the team commits to migration.

Rebuild search controls and redirects

• Export current URL, status, title, description, canonical, robots directive, primary heading, structured-data types, internal links, sitemap membership, and redirect rules.
• Preserve public paths such as post and category URLs when they remain useful and Webflow can represent them cleanly.
• Map changed URLs one to one where an equivalent destination exists. Google recommends permanent server-side redirects for permanent moves; avoid chains and blanket home-page redirects.
• Update internal links, canonicals, structured data, Open Graph fields, feeds, navigation, breadcrumbs, and XML sitemap so they name final URLs directly.
• Recreate valid schema based on visible page content rather than copying plugin output blindly. Validate representative templates and any rich-result markup against current Google guidance.
• Test pagination, archives, tag or category decisions, author pages, attachments, feeds, and search results. These WordPress URL families are easy to overlook.
• Keep WordPress live or otherwise able to serve old URLs until the Webflow domain, SSL, redirects, pages, media, and critical functions are confirmed.

Make the new editorial workflow part of acceptance

Give real editors a staging exercise: create a draft, assign a person and category, add an image and alt text, preview a long title, edit SEO fields, schedule or publish through the approved process, correct an error, and restore an earlier state if supported. Confirm who may change slugs, templates, redirects, custom code, billing, domains, and integrations. A polished migration that makes everyday publishing unsafe has not solved the operating problem.