How to Migrate a Webflow Site to WordPress Step by Step

Before you start: what to gather

Collect a full list of your Webflow pages, CMS collections and their field types, and every custom code snippet embedded in the site (found under Project Settings → Custom Code in Webflow), since these embeds often power things like chat widgets or analytics that need to be added back manually later.

Also export your current XML sitemap so you have a definitive record of every URL that Google currently indexes, which becomes essential for the redirect step later.

Step 1: set up the new WordPress environment

Install WordPress on a staging subdomain or a temporary URL so you can build and test without affecting the live Webflow site. Set your permalinks structure under Settings → Permalinks to match the pattern you plan to use post-migration.

1. Install WordPress on staging
2. Set Settings → Permalinks to your target URL structure
3. Install core plugins you know you will need (SEO, forms, redirects)
4. Confirm PHP memory limits with your host meet WordPress recommended minimums

Step 2: rebuild the theme from your live Webflow page

Open your live Webflow site in a browser and use a capture tool like Themify to read the rendered page and generate a WordPress theme package locally, no source code is uploaded anywhere. This produces a theme zip containing style.css, index.php, header.php, footer.php, functions.php and a bundled assets folder.

Install it in your staging environment via Appearance → Themes → Add New → Upload Theme, then confirm the screenshot.png thumbnail and layout render correctly across breakpoints before moving on.

Step 3: migrate CMS content

Export each Webflow CMS collection to CSV from the collection's settings panel. In WordPress, create a matching custom post type (using Pods or Advanced Custom Fields) for each collection type, then import the CSVs with WP All Import, mapping each Webflow field to its WordPress equivalent.

1. Export each CMS collection as CSV from Webflow
2. Create matching custom post types and custom fields in WordPress
3. Import CSVs using WP All Import with careful field mapping
4. Manually clean up any rich-text formatting issues after import
5. Reconnect dynamic collection lists on template pages

Step 4: rebuild forms and custom code

Recreate Webflow forms with WPForms or Gravity Forms, and re-add any analytics or chat widget scripts from your custom code inventory into the WordPress theme's header or footer via a plugin like Insert Headers and Footers rather than editing functions.php directly.

Step 5: map redirects and go live

Compare your saved list of Webflow URLs against the new WordPress permalinks and create a 301 redirect for every URL that changed, using the Redirection plugin. Test a representative sample manually in a browser before touching DNS.

Once redirects and content are verified on staging, point your domain's DNS at the new WordPress host, then immediately resubmit your XML sitemap in Google Search Console and watch the Coverage report over the following weeks for crawl errors.

• Map every old Webflow URL to its WordPress equivalent
• Test redirects before DNS cutover
• Resubmit sitemap to Search Console after launch
• Keep the Webflow site unpublished, not deleted, as a fallback reference

What to expect timeline-wise

For a marketing site with a few CMS collections, the theme-rebuild step using a capture tool typically takes minutes, while content migration and redirect mapping realistically take several days to a week depending on how much content exists. Themify's plans start at $9/mo for 10 conversions with a free trial conversion, which is enough to validate design fidelity before committing to the rest of the migration timeline.