How to Migrate from WordPress to Webflow: A Practical Guide

Back to insights

To migrate from WordPress to Webflow, rebuild the pages and functionality you need, prepare repeated content for CSV import into CMS Collections, map changed URLs, and test the published staging site before connecting your domain. WordPress themes and plugins do not transfer automatically.

This guide focuses on a business or marketing website. Stores, memberships, and custom applications need their own feasibility review before the same approach is applied.

1. Check whether the move fits

Webflow may make sense when your priority is a considered marketing website with repeatable content and a visual editing workflow. Write down the problem you want to solve: inconsistent layouts, difficult routine updates, or a site structure that no longer matches the business.

WordPress may remain the better fit when essential workflows depend on its existing plugins, custom code, or a team already comfortable managing it. Compare the cost of improving the current site with replacing it. A platform change alone cannot resolve unclear content or ownership. Webflow's migration overview is a starting point, not a substitute for this assessment.

2. Audit what the website actually does

Create an inventory with one row for each important URL. Record its purpose, content owner, traffic importance, and whether it should be kept, revised, combined, or retired. Include landing pages that are missing from the main navigation.

List images, downloads, videos, forms, plugins, tracking, and external integrations separately. For each plugin, describe the job it performs rather than simply its name. A form might route inquiries to several recipients; an embed might support bookings. Ask who relies on those workflows and how you will prove that their replacements work.

3. Keep backups and a record of current performance

Take a restorable backup of the WordPress database and files, including uploads. WordPress's backup guidance explains why both parts matter. Confirm access and the restore procedure with whoever manages hosting; a downloaded content export is not your entire rollback plan.

Record search traffic, important landing pages, existing redirects, page titles, descriptions, and indexing status using the tools already available to your team. Save dated reports and note campaigns or seasonal changes. Those records help you investigate later differences without assuming every change was caused by the migration.

4. Map pages and Webflow CMS Collections

Agree on the future navigation before building. Separate one-off pages, such as Contact, from repeated content, such as articles. Define which content deserves a Collection and what each item needs: a title, slug, summary, body, image, or relationship to another item.

Keep the model understandable to the people maintaining it. Decide whether categories need their own Collection, then document naming rules and required fields. Preserve a mapping between old content and the new structure. Check the intended Webflow plan's current CMS limits against your actual inventory before committing to that structure.

5. Prepare XML content as CSV

WordPress's built-in Tools → Export produces an XML file in its WXR format. That export can contain posts, pages, taxonomies, and other content data. It is not a transferable theme or a complete site backup. See the WordPress export documentation.

Webflow CMS imports CSV rather than that WordPress XML file. Convert the relevant content into a reviewed spreadsheet or use a suitable export/conversion workflow. Renaming the file extension does not convert its contents.

Use columns for the target fields and rows for items. Keep a separate source-URL column in your working spreadsheet for traceability. Review quotes, commas, HTML, and character encoding; retain the original export so corrections can be checked against the source.

6. Rebuild layouts and replace functionality

Content transfer does not recreate a WordPress theme, page-builder layout, or plugin behavior in Webflow. Rebuild the agreed pages and responsive layouts, then evaluate each functional requirement individually. Plugin-generated shortcodes need particular attention: copying them into a new page does not make the underlying feature work.

For forms, agree on validation, recipient routing, consent wording, and the handling of submissions. For bookings, search, or other integrations, confirm a workable replacement before retiring the old setup. Some requirements may need a separate service or a different platform decision. Keep the functionality checklist next to the design review.

7. Import a small sample, then check the result

Use the Webflow CMS import guide to map CSV columns to fields and preview items. Start with representative content: a long article, an image-heavy page, and an item with category references. Take a Webflow backup before changing an existing content set.

Import referenced items first and use their matching slugs, including any custom slugs. Image fields need direct image URLs; file fields need manual uploads. CSV-imported images do not receive responsive image variants, so optimize the source images or upload them directly. Check rich text carefully: unsupported HTML, classes, and attributes may be removed.

Review formatting, alt text, downloads, and internal links, including assets still served by the old host. Compare expected and imported item counts. Missing required references can leave items as drafts, so review errors and publication status before expanding the import.

8. Preserve useful URLs and map changes

Retain existing paths where the new structure permits it. For changed paths, map each old URL to the closest relevant replacement with a permanent 301 redirect. Avoid sending every retired page to the homepage; visitors still need an answer to the intent behind their original link.

Webflow's redirect import documentation specifies a CSV with old and new path columns. Importing replaces existing redirects, so export and merge any rules you need to retain first. Publish for the rules to take effect, then test important mappings for loops, chains, and correct destinations.

9. Review metadata, canonicals, and indexing

Check titles and descriptions on static pages and Collection templates. Ensure canonical URLs point to the intended production versions, with no conflicting tags or staging addresses. Review the sitemap, robots rules, and page-level indexing choices together rather than treating one setting as proof that everything is correct.

Keep staging out of search results using the appropriate Webflow staging-indexing controls. At launch, remove temporary restrictions only from pages approved for indexing. Use Webflow's canonical, sitemap, and indexing guidance to check the current controls.

10. Test before switching the domain

Review the published staging site, not just the editing canvas. Test mobile, tablet, and desktop layouts, keyboard navigation, visible focus, headings, menus, and images. Follow the main journeys from arrival to contact or purchase, where relevant.

Check form validation and actual delivery with authorized test submissions; a success message alone is not evidence of receipt. Verify links, downloads, integrations, and analytics behavior. Ask a content owner to make a routine update. Record unresolved issues and agree on which ones block the launch.

11. Switch the domain without disrupting email

Follow Webflow's current domain connection instructions and manual DNS guide. Use the records shown for your specific site in Publishing settings; do not copy an old tutorial's IP addresses. Verify domain ownership and the chosen default domain before publishing.

Save the existing DNS configuration and change only the records needed for website routing and verification. Preserve email-related MX, SPF, DKIM, and DMARC records, including any mail-related CNAME records. Cloudflare's email DNS guidance explains their roles. Have the DNS or email administrator review uncertain changes. After switching, check HTTPS, the main domain variants, and email operation while DNS changes propagate.

12. Monitor and retain a rollback plan

Check important live URLs, redirects, forms, and media immediately after release, then continue reviewing search and inquiry data against your baseline. Investigate missing pages and unexpected changes rather than declaring success from a screenshot. Google's site-move guidance provides further search-monitoring context.

Keep the old hosting, backups, and DNS record history available until the agreed review is complete. Define who can approve a rollback and what would trigger it. Account for content edits or new submissions received after the switch so reverting does not silently discard them. Redirects help continuity but cannot guarantee unchanged rankings or traffic.

Launch checklist

Content inventory reconciled; media and downloads checked.
Important URLs preserved or mapped to tested redirects.
Layouts, keyboard access, and key journeys reviewed.
Forms and integrations checked with authorized delivery evidence.
Metadata, canonicals, sitemap, and indexing reviewed.
Site-specific DNS instructions followed; email records preserved.
Monitoring owner, backups, and rollback decision agreed.

Practical FAQs

Can I move everything with a single import?

No. A CMS import transfers prepared content data. Layouts, plugin behavior, and connected workflows need separate rebuilding and testing.

Should I rewrite every page during the move?

Prioritize necessary changes. Keeping an inventory and separating migration fixes from broader editorial work makes review and troubleshooting easier.

Will redirects prevent all traffic loss?

No. They connect changed URLs with replacements, but search visibility can fluctuate. Monitor the live site and address problems promptly.

When can the old site be removed?

After the responsible team confirms the new site, needed assets, backups, and rollback arrangements are sound. Agree that decision rather than relying on a fixed waiting period.

Sources

Reviewed October 10, 2026. Platform controls can change; follow the current documentation when carrying out a migration.

Considering a different website setup? We can discuss your pages, content, and development needs before agreeing on a scope.

If you are still deciding between platforms, read our Webflow and WordPress comparison. For the work involved in building a website, see our website development service.

Talk through your website