Webflow → WordPress
Move structured Webflow CMS content and supported static-page data into WordPress with explicit collection mapping, relationship resolution, validation, and URL rules. Designer layouts and application behavior remain separate scope.
Self-service migration path
This pair is not currently listed as a fully supported self-service direction. webflow: Beta. wordpress: Available. Review system status and directions. Available migration objects and capabilities depend on the selected source and target systems.
Create an account, connect a staging destination, and let the app analyze the supported scope for this direction.
No credit card required to analyze the migration and run a free sample.
Scope
The app confirms available entities after connection. Final coverage depends on source access, downloadable assets, and the destination model you prepare.
Before you connect
Use a staging destination and the least-privilege access supported by each platform. Do not send credentials through a public form.
Provide the public site URL, Site ID, and an API token with CMS read access. Optional explicit Collection IDs prevent ambiguous auto-detection.
Static-page extraction requires working Pages API access; localized projects also require the relevant locale and CMS locale identifiers. Permissions are verified during discovery.
Provide the staging site URL and an Application Password. A compatible Migranetix Bridge may be required for broader destination entity coverage.
How it works
You control each stage in the app. Optional expert assistance is available for custom data or destination requirements.
Start in the app and select the real source and target.
Authorize read access to Webflow and connect a prepared staging WordPress destination.
Review detected records, available entities, media, URLs, and anything that needs a decision.
Choose where supported Webflow data belongs in the prepared WordPress model.
Move a small set of real records to staging and inspect the result before purchasing the full migration.
Review counts, records, media, links, warnings, and exceptions, then purchase and start the full migration when ready.
Technical detail
Open only the detail you need for planning, mapping, or validation.
This page is synchronized with the Webflow source and WordPress destination capability snapshots. Webflow and WordPress are both enabled in both directions; this page documents the Webflow-to-WordPress path only.
The current adapter reads configured author, category, and blog/article Collections plus supported static pages. It normalizes content records rather than exporting the Webflow Designer project.
Authenticated REST and versioned Bridge adapters load records into a prepared WordPress model. Custom post types, fields, SEO plugins, and multilingual behavior still require destination-specific rules.
Standard means the current adapters expose a direct structured path. Review means field shape, permissions, locale behavior, or the destination architecture must be approved. Custom means the feature is outside the configured content entities.
| Webflow source | WordPress target | Status and boundary |
|---|---|---|
| Configured blog or article Collection items | Posts or a prepared custom post type | Standard: title, slug, body, excerpt, dates, status, and supported relationships are normalized. |
| Authors Collection or author field | WordPress authors | Review: native references or stable synthetic identities can be resolved; authentication and passwords are not included. |
| Categories or tags Collection | Categories, tags, or another taxonomy | Standard with mapping: terms load before content and source references resolve to destination IDs. |
| Image and file fields | WordPress media | Standard with validation: supported asset URLs are downloaded, checked, uploaded, and rewritten. |
| Static site pages | WordPress pages | Review: page metadata and available static content are read through the Pages API; collection template pages and utility pages are excluded. |
| Page hierarchy | WordPress parent pages | Review: parent IDs are extracted, but destination hierarchy must be explicitly mapped and validated. |
| Staged, draft, archived, and live state | WordPress publication status | Review: platform states are translated to the approved WordPress workflow. |
| Primary and localized CMS variants | WordPress multilingual model | Review/custom: locale IDs can be read, but the destination language plugin and relationships must be defined. |
| SEO fields and published paths | WordPress slug, SEO fields, and redirect plan | Review: standard page metadata and recognized CMS field slugs are mapped; target storage depends on the SEO implementation. |
| Arbitrary Collections and custom references | Custom post types, fields, and relationships | Custom: the current adapter is oriented to configured article, author, and category Collections rather than every site schema. |
| Forms, memberships, ecommerce, and business records | Plugins or custom applications | Custom: these are not configured source entities in the current adapter. |
| Designer layout, classes, components, and interactions | Theme, blocks, templates, and front-end code | Rebuild: presentation and behavior do not transfer as content records. |
The mapping workbook records Collection IDs, field slugs, destination fields, relationship dependencies, locale handling, and fallbacks before the first staging load.
| Webflow value | Migration rule | WordPress result |
|---|---|---|
| Collection item ID | Preserve as source identity in the migration dataset and ID map | Stable post lookup for reruns and delta updates |
| Name, slug, rich text, excerpt | Normalize recognized fields and approved custom rich-text sections | Post title, slug, content, and excerpt |
| Author reference | Load or synthesize the author identity, then resolve its destination ID | WordPress author assignment without password migration |
| Category and tag references | Load terms before content and resolve single or multi-reference values | WordPress taxonomy relationships |
| Image or file field | Download, validate, upload, and record source-to-target asset IDs | Media attachment, featured image, or rewritten inline reference |
| Published path and SEO fields | Build the approved URL and metadata map | Destination slug, SEO metadata, canonical review, and redirect requirement |
| Content type and Collection | Route each approved source type into the prepared destination model | Post, page, or project-specific custom post type |
Webflow sites mix structured CMS records with Designer-managed pages. Treating them as one uniform export causes missing relationships or low-quality page reconstruction.
Record Collection IDs, field slugs, field types, required values, references, item counts, and publishing states before mapping starts.
Load authors and taxonomy terms before articles, then resolve every source relationship through the migration ID map.
Extract supported page metadata and static content nodes while excluding collection templates, 401/404 utility pages, and Designer layout assumptions.
Map business-critical fields into WordPress core, taxonomies, post meta, ACF, or a custom model instead of flattening everything into body HTML.
Webflow Collection paths and static-page paths rarely match the final WordPress permalink structure without an explicit URL contract.
Crawl the live Webflow site and pair every indexable Collection item and static page with its approved WordPress destination.
Transfer supported titles, descriptions, slugs, and source paths, then verify the destination SEO plugin and canonical behavior.
Rewrite internal links and media references, test redirect coverage, and prevent chains or collisions across changed Collection paths.
Verify sitemap output, crawlability, analytics, high-value landing pages, redirect logs, and indexation during stabilization.
Acceptance is based on reconciled records and relationships, not simply on a successful API response.
Compare Collection, page, extracted, loaded, skipped, failed, draft, and published totals by content type and locale.
Inspect representative rich text, custom fields, authors, taxonomies, locale variants, dates, hierarchy, and source-to-target IDs.
Validate downloads, uploads, featured images, inline references, HTML rendering, internal links, and responsive destination templates.
Test metadata, canonicals, sitemap entries, old-to-new redirects, and document every corrected, accepted, deferred, or custom exception.
Before purchase
The free sample migration creates a limited set of records in staging. Check fields, relationships, media, URLs, rendering, and reported exceptions before paying for the full run.
Pricing
Package fit depends on supported record volume and complexity. Analyze the source first, then review the fixed package or dynamic estimate shown for the migration.
Compare migration packagesPlan the move
Review Webflow CMS extraction, static-page boundaries, references, localization, and URL handling.
Open guide →Review WordPress destination modeling, custom content, users, media, and SEO handling.
Open guide →Understand the broader content migration scope and delivery boundaries.
Open guide →See how mapping, dry runs, validation, and cutover decisions are controlled.
Open guide →Clear answers
Not through one generic rule. The current adapter is optimized for configured article, author, and category Collections. Other schemas require field and relationship review before they are approved.
Supported page metadata and available static content can be extracted through the Pages API. Collection templates, full Designer structure, styles, classes, and interactions are not reproduced as portable page data.
No. Components, classes, animations, responsive design, forms, and front-end behavior require a separate WordPress implementation.
Locale identifiers and CMS variants can be read when access and configuration allow it. WordPress language storage, translations, relationships, and URL rules must be designed for the destination plugin.
Authors can be mapped as content identities. Webflow memberships, user authentication, permissions, and passwords are not part of the standard content scope.
Rankings cannot be guaranteed. Reduce migration risk with URL mapping, metadata review, redirects, internal-link updates, sitemap checks, analytics, and post-launch monitoring.
Yes. Load representative records into staging, validate mappings and relationships, correct systematic issues, and reuse the approved rules for final or delta migration.
Next step
Create an account, connect the systems, and analyze the supported scope before purchasing the full migration.
