Free tools Windows power users keep installed
One-click scans. No signup required.
You can move a Webflow site to WordPress, but there is no complete one-click transfer. Webflow’s code export gives you static files and assets; it does not carry over the CMS database, ecommerce system, forms, search, memberships, localized content, or other hosted features. A successful move is therefore a rebuild, content migration, URL-mapping exercise, and controlled domain cutover.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Use the workflow below to inventory what exists, build and test the WordPress destination, preserve valuable URLs with accurate permanent redirects, and monitor search and user experience after launch.
As an Amazon Associate I earn from qualifying purchases.
Recommended Free Tools
What a Webflow-to-WordPress migration really involves
A Webflow export is an input to the project, not a backup of the live site. The exported archive can provide HTML, CSS, JavaScript, images, fonts, and other static assets. It does not recreate the systems that made the Webflow site dynamic or managed.
Plan the work as five related tracks:
- Discovery: record every page, URL, asset, data set, integration, and business rule.
- Destination build: configure WordPress, hosting, themes or templates, content types, and required plugins or custom code.
- Content and feature migration: move copy and media, then reproduce forms, search, ecommerce, localization, accounts, and integrations.
- URL and SEO migration: choose the new permalink structure, map old addresses to final destinations, and configure redirects.
- Testing and cutover: validate the staging site, switch traffic only when it is ready, and monitor both old and new URL sets.
Separating these tracks prevents a common failure: publishing the exported visual layer while assuming that the missing data and services will somehow appear in WordPress.
#1 Best Overall
Step 1: Inventory the live Webflow site before exporting anything
Make a spreadsheet or database that describes the current site, not just its visible pages. Give each item an owner and a migration decision: rebuild, move as data, replace, retire, or investigate.
Record pages and URLs
- Static pages, landing pages, legal pages, blog indexes, and individual posts.
- Every current path, including trailing-slash behavior, language folders, and query-string URLs that receive links or traffic.
- Important images, PDFs, downloads, and other files that may have search visits or external links.
- Title tags, meta descriptions, canonical tags, headings, open-graph data, schema markup, and any page-level noindex rules.
Record managed data and user-facing features
- CMS Collections and all items, including references, categories, authors, dates, and custom fields.
- Ecommerce products, variants, inventory, taxes, shipping rules, checkout, order notifications, and customer accounts.
- Forms, destinations, autoresponders, spam controls, and any submissions that must be retained outside Webflow.
- Site search, filters, gated or password-protected pages, memberships, and user-account behavior.
- Localized content, language selectors, alternate URLs, and translation workflows.
Record the technical dependencies
- Custom JavaScript, embeds, tracking pixels, analytics, advertising tags, and consent tooling.
- Webhooks, CRM connections, email delivery, payment services, inventory systems, and other integrations.
- Navigation, redirects, robots.txt rules, XML sitemap behavior, favicon files, and custom domains.
- Responsive breakpoints, interactions, animations, accessibility requirements, and browser-specific fixes.
Mark which items are essential for launch and which can follow later. A form that sends leads to a sales system or a checkout flow is a launch blocker; a decorative animation may not be.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Check Webflow export eligibility and export the right data sets
Webflow’s documentation says code export is available on paid Workspace plans; Site plans do not include code export. Plan availability and interface labels can change, so confirm the capability and your account’s current permissions before scheduling the move.
Code export does not include CMS, ecommerce, or user-account databases and functionality. Webflow documents separate CSV backups for CMS Collections, ecommerce Collections, and User Accounts. Export those data sets independently when they are part of your migration, then verify row counts, references, images, variants, and account fields against the live site.
Also preserve information that an export may not expose as a simple file: form submissions, order history, customer consent records, search analytics, redirect rules, and integration configuration. Keep an untouched copy of every export and note the date and account used. Do not decommission the Webflow project or old domain while you still need to retrieve data or serve redirects.
Step 2: Prepare WordPress before moving content
Create the WordPress installation and a nonpublic staging environment first. Use a separate database and credentials from production where practical, and restrict indexing while the site is being built.
Choose the permalink structure early
WordPress treats permalinks as permanent web addresses and supports a custom structure. Decide the final pattern before creating large numbers of pages or importing posts. If an old Webflow path is valuable and technically compatible, preserving it reduces redirect work. If the structure must change, document the reason and map every affected URL.
Changing a permalink after content is published creates avoidable redirect and internal-link work. Set the structure in Settings → Permalinks, save it, and confirm that representative pages resolve as intended on staging.
Understand what WordPress’s XML tools do
In WordPress, Tools → Export creates a WXR/XML content file. Tools → Import can consume a WordPress export for posts, comments, custom fields, pages, and categories. Those tools document WordPress-to-WordPress content transfer; they do not turn a Webflow code archive into a functioning WordPress installation.
Use WXR only when you actually have WordPress export data. For Webflow content, create a field map and use the method that fits the site: carefully structured CSV import, an independently verified migration utility, an API or script, or manual entry for a small number of pages. No universal importer is established by the available documentation, so test any tool against your real collections and relationships before committing to it.
Step 3: Rebuild the design and content model
Use the exported files as a visual and asset reference while rebuilding templates in WordPress. Recreate global header and footer elements, navigation, typography, spacing, responsive behavior, interactions, and accessibility semantics rather than pasting static HTML into every page.
Create WordPress content types that match the old model
For each Webflow Collection, define the equivalent WordPress post type, taxonomy, fields, and relationships. Decide how references, authors, dates, images, downloads, and rich-text content will be represented. Preserve stable identifiers in your migration sheet so that an old item can be matched to its new record.
Move content with a field-level map
A useful map lists the Webflow field, destination field, transformation, and validation rule. For example, a Webflow “Hero image” field may become a WordPress featured image; a multi-reference field may become a taxonomy or relationship; a rich-text field may require cleanup of embedded links and image paths.
- Copy text and headings without losing hierarchy.
- Download or relink images and documents, then check dimensions, filenames, alt text, and licensing.
- Preserve publication dates, authors, categories, tags, and canonical URLs where they matter.
- Convert Webflow-specific embeds, interactions, and classes into WordPress-compatible markup or components.
- Check internal links after import; links that point to Webflow collection paths often need systematic replacement.
Import in a small batch first. Compare source and destination records, then scale up after images, references, special characters, and duplicate slugs have passed validation.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallRecreate features that code export leaves behind
Each excluded Webflow capability needs a deliberate WordPress implementation and an owner responsible for testing it.
| Webflow capability | What the code export leaves out | WordPress migration decision | Minimum acceptance test |
|---|---|---|---|
| CMS Collections | Collection database, relationships, and management workflow | Build matching post types, taxonomies, fields, and templates; import the data separately | Known records, filters, pagination, and detail URLs match the inventory |
| Ecommerce | Products, checkout, orders, customer data, and commerce logic | Choose and configure a compatible commerce system, then plan data and payment migration | Test product, cart, payment, confirmation, refund, and notification paths in a safe environment |
| Forms | Submission processing and delivery | Rebuild forms, validation, spam protection, storage, and notifications | A test submission reaches the intended inbox or system and is recorded correctly |
| Site search | Search index and search behavior | Configure WordPress search or a suitable search service and tune included content types | Representative queries return useful, correctly linked results |
| Password protection and accounts | Protected content rules, users, and account database | Recreate access rules, users, password resets, and session behavior | Authorized and unauthorized users see the correct responses |
| Localization | Localized content and language configuration | Rebuild language paths, translations, selectors, and alternate URLs | Each language resolves, links internally, and exposes the correct metadata |
Do not assume that matching the old page’s appearance means the feature is working. A visually identical contact form that drops submissions is a migration failure.
Step 4: Build a complete old-to-new URL map
Start with a crawl or export of Webflow’s current URLs, then add URLs found in analytics, Search Console, server logs, backlinks, XML sitemaps, and navigation. Include valuable image and document URLs when they receive visits or links.
For every old address, record one final destination and a reason for the action. Use the most relevant equivalent page, not a blanket redirect to the home page. Google warns that sending many unrelated URLs to one homepage can confuse visitors and be treated as a soft 404.
| Old URL | Final WordPress URL | Action | Validation |
|---|---|---|---|
/old-path |
/matching-path |
301 redirect | One hop; destination returns 200 |
/old-collection/item |
/new-content/item |
301 redirect | Equivalent content and canonical URL |
/retired-page |
Not applicable | Return a genuine 404 or 410 when no useful replacement exists | Not redirected to an unrelated page |
Decide when to preserve a path
- Keep the old path when it has meaningful traffic, links, bookmarks, or a clear place in the new information architecture.
- Change it when the old structure is misleading, conflicts with WordPress routing, or cannot represent the new content model.
- Use separate rules for language or folder variations when their destinations differ.
- Ensure every redirect target is the final URL so visitors and crawlers do not pass through chains.
Implement permanent redirects at the layer that will still receive traffic
A redirect only works if the old domain or endpoint remains available to answer the request. Decide whether redirects will be handled by the web server, a reverse proxy, the old host, or WordPress, and keep that layer operating after DNS changes.
Use server-side permanent redirects where possible. Test status codes, destination URLs, protocols, hostnames, trailing slashes, query strings, and language folders. Google’s migration guidance recommends keeping redirects generally for at least one year. The practical retention period may be longer when old URLs continue to receive links or traffic.
Webflow’s redirect manager is specific to Webflow-hosted sites. Its rules are root-relative, localized paths may need separate entries, and changes take effect only after publishing. The documented manager requires a paid Site plan or paid Workspace plan. A CSV import replaces existing redirects unless you first export them and include the existing rules in the combined file. These details matter only if Webflow will own the old-domain redirect layer; verify ownership before cutover.
After the move, crawl the old URL list and check that each response is the intended permanent redirect, the destination is relevant, and no redirect chain or loop exists.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Step 5: Test the WordPress destination before launch
Test staging as if you were a visitor, an editor, a crawler, and an integration. Keep a defect list with severity and a retest result.
Page and content checks
- Open every important template and a representative sample of each content type.
- Check headings, images, captions, downloads, embeds, tables, pagination, archives, and 404 pages.
- Test desktop and mobile layouts at the breakpoints your audience uses.
- Follow navigation, breadcrumbs, calls to action, and internal links.
Functional checks
- Submit each form and verify validation, spam handling, storage, notifications, and downstream integrations.
- Test search, filters, account registration, login, password reset, and protected content where applicable.
- For ecommerce, use a safe test transaction and verify cart, payment, tax, shipping, confirmation, fulfillment notification, refund, and order records.
- Switch through every language and verify translated content, selectors, canonical tags, and alternate links.
- Confirm analytics, consent, advertising, CRM, email, and webhook events arrive once and with the expected values.
Crawl and SEO checks
- Remove development-only
noindexdirectives and robots.txt blocks before launch. - Check canonical URLs, title tags, descriptions, structured data, XML sitemap entries, and internal-link destinations.
- Verify that staging restrictions will not be copied to production.
- Run the old-to-new redirect list and record failures, loops, chains, and incorrect status codes.
Step 6: Cut over the domain in a controlled sequence
- Freeze or document last-minute Webflow edits so the source inventory remains accurate.
- Take a final content and data export, then reconcile it with the WordPress staging build.
- Put the WordPress site into its production environment and complete the final smoke test.
- Activate the old-domain redirects at the system that will serve them.
- Update DNS or the relevant domain routing only after the destination and redirects are ready.
- Open the site publicly and immediately test the home page, key landing pages, forms, search, representative content URLs, and several old URLs.
- Submit the new XML sitemap in Search Console and monitor the new property and the old URL set.
Verify both old and new properties in Search Console before the switch. Use the Change of Address tool only when the domain itself changes; moving from Webflow to WordPress on the same domain is a CMS change, not a domain move.
What to expect from Google after the move
Search visibility can fluctuate temporarily while Google recrawls, follows redirects, and processes the new URLs. Google says the duration varies with the number of URLs and server speed; for a small or medium-sized site, its guidance says most pages may move in a few weeks. That is an expectation, not a guarantee of unchanged rankings or a fixed recovery date.
Permanent redirects are important, but they cannot repair an inaccurate map, a broken destination, a blocked site, or a chain of redirects. Google Search Central states: 301 and other permanent redirects don’t cause a loss in PageRank.
The statement applies to correctly implemented permanent redirects and does not remove the need to preserve equivalent content and test every target.
Monitor after launch
- Review indexing and crawl errors in Search Console daily at first, then on a regular schedule.
- Compare impressions, clicks, landing pages, conversions, form submissions, and revenue with the pre-migration baseline.
- Watch server logs or analytics for repeated hits to unmapped old URLs and add only relevant, tested redirects.
- Check uptime, page speed, mobile usability, certificate coverage, and integration failures.
- Keep the redirect service and old-domain configuration available for at least the generally recommended one-year period.
Troubleshoot common migration failures
Pages look right but dynamic content is missing
The static export contains presentation files, not CMS records or runtime services. Recheck the collection inventory, import the data separately, and connect each content type to a WordPress template.
Forms submit but nobody receives the message
Test delivery from the production domain, inspect spam and mail logs, verify the destination address and integration credentials, and submit again with a known test record. A successful browser response alone does not prove delivery.
Many URLs redirect to the home page
Replace blanket rules with one-to-one mappings to equivalent pages. If no equivalent exists, allow the old URL to return an appropriate 404 or 410 instead of creating a misleading soft 404.
Redirects loop or take several hops
Inspect rules at every layer: CDN or proxy, old host, web server, and WordPress. Consolidate each path to one direct permanent redirect and normalize protocol, hostname, and trailing-slash rules.
The new site is not appearing in search
Check for leftover noindex tags, robots.txt disallows, authentication walls, incorrect canonicals, blocked assets, and an inaccessible sitemap. Confirm that the production hostname—not staging—is verified and submitted.
Localized pages disappear
Compare the language inventory with the destination URL map. Add distinct redirect rules and rebuild language selectors, translated metadata, and alternate URLs rather than assuming one default-language page can stand in for every locale.
Should you do the migration yourself?
An internal team can handle a small brochure site when it has few templates, no ecommerce or memberships, limited integrations, and someone who can test redirects and forms. Plan specialist help when the site has a large CMS, orders or customer accounts, multiple languages, complex integrations, or substantial organic traffic. The deciding factors are feature complexity, content volume, dependency risk, and your ability to run a complete staging and redirect test—not a promise that any particular tool will automate the work.
Quick Recap
Launch checklist
- Complete page, asset, CMS, ecommerce, account, form, search, localization, integration, analytics, and SEO inventories.
- Confirm export eligibility and create separate backups for collections, commerce data, and user accounts where applicable.
- Set the WordPress permalink structure before publishing.
- Build templates and content types, then validate a pilot import before scaling.
- Create an old-to-new map for pages, files, language paths, and high-value linked URLs.
- Configure direct permanent redirects and keep the old endpoint available.
- Test content, responsive layouts, forms, search, transactions, integrations, canonicals, internal links, robots rules, and sitemap output.
- Remove staging noindex and blocking rules, verify the production site, and submit the sitemap.
- Monitor indexing, crawl errors, traffic, conversions, and unmapped old URLs after cutover.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →
