How to migrate Webflow to WordPress

Start with a page and content inventory

List your ordinary pages, CMS collections, collection item URLs and anything visitors can submit or buy. Keep a copy of your source site and note the pages that bring enquiries or sales. Check your homepage, article lists and individual articles, since each may behave differently.

For each collection, write down the fields you actually edit. A Projects collection might need a title, thumbnail, client, gallery and body. This gives you a concrete checklist for the WordPress editing screen instead of judging the migration by its homepage alone.

• Record published page and item counts so you can spot omissions.
• Capture desktop and phone screenshots of representative pages.
• List forms, search, filtering, checkout, private areas and third-party embeds separately.

Choose the published URL or an export

AnythingTo reads the published site and follows the links it can discover. Use an address you own or have permission to migrate. A public webflow.io address can be used; an editor URL cannot. Do not expose confidential content just to make a conversion possible.

Webflow’s code export does not include CMS content and functionality. Keep collection exports as a separate backup when planning a migration. Check private or unlinked pages separately, and compare the converted pages with your original list.

Reference: Webflow: what code export includes

Check how your team will edit the site

Your team will update text, images, links and page sections in WordPress. It is a different editing experience from the Webflow Designer, so try the changes you make most often. Larger layout changes may still need design help.

Before adding more content, try the WordPress editor. Check that related content, such as projects or articles, is grouped as expected. Edit an existing item and add a new one, then confirm that both appear in the right places.

Test interactions and services separately

Supported interactions are rebuilt for WordPress. Check the features your visitors use rather than assuming every effect will transfer. Open dropdowns, use the mobile menu, switch tabs and try sliders. Compare both the default and interactive states.

Complex scroll sequences may need developer work. Ecommerce checkout, memberships and external automations need a separate implementation plan. A converted form looking correct is only the first check: submit it and verify that the intended recipient actually receives the message.

Launch only after the migration checklist passes

Preview key pages at more than one width, inspect important content and check your URL map. Verify metadata and media on a representative article as well as the homepage. If a URL changes, test its destination before changing DNS.

Keep access to the original site until you have checked the live result and have a rollback plan. After launch, look for missing pages, broken links and unexpected changes to search traffic. A migration is a good time to improve the editing workflow, but combining it with a complete redesign makes differences harder to diagnose.