How to migrate from Webflow to Payload CMS
Plan a Webflow-to-Payload move with collection, asset and URL maps. Preserve references and locales, rebuild presentation and check the new answer source.
- Published
- Last updated
You can migrate from Webflow to Payload CMS by exporting Collection records, converting their fields and importing them into destination collections. Your team must rebuild the site’s presentation and publishing connections. Preserve the original assets before removing Webflow, because exported media links can still depend on the source site.
Choose the scope of the replacement
Treat the move as a content migration plus a separate delivery project. A Collection export supplies records for mapping. It doesn’t rebuild page layouts, responsive behaviour, forms or checkout in Payload.
Payload fits a team that wants developers to define its content model and delivery. Editors then work within those configured fields and publishing controls. Keep Webflow when your editors need its existing visual workflow and the site already meets your needs. A different content store alone doesn’t justify taking on frontend maintenance.
Before starting, assign a content owner and a developer who can change Payload’s schema and the frontend. Confirm access to every source Collection and locale. Inventory forms, commerce connections and other services separately, including who owns their credentials and billing. Agree on an editing freeze or a final export window so changes made during the transfer aren’t lost.
Export collections and preserve source assets
In Webflow’s CMS panel, open a Collection and choose Export for the entire Collection, including archived items. For a subset, use Select to choose the intended records before exporting. Record which scope you used. Webflow’s Collection export instructions explain both routes.
Repeat the export in every required locale view. Each CSV contains only that view’s items. Webflow’s localisation model also allows items specific to a secondary locale, so equal counts across locales aren’t a valid acceptance rule.
Keep the untouched CSVs alongside a field inventory. Use the following transfer matrix to record the work for each Collection.
| Source item | Exported material | Retain in Payload | Manual action |
|---|---|---|---|
| Plain fields and slug | Text or other field values | Approved values and original URL mapping | Define compatible field types and validate values |
| Rich text | HTML | Text, headings and intended links | Convert into the selected editor format and inspect rendering |
| Reference | Plain text or URL value | Intended target record | Resolve to a destination document ID |
| Multi-reference | Comma-separated text | Every intended target | Parse values and resolve destination IDs |
| Image or file | Source-hosted URL | File plus relevant descriptive fields | Download, upload and replace the source URL |
| Locale variant | Records from the selected view | Variant content and its source identity | Map locale codes and corresponding records |
Download required files, including images embedded in rich text, before removing the original site. Keep a manifest from each source URL to its saved file and eventual destination. Webflow’s CSV export guidance warns that deleting the original project breaks its hosted asset links. A CSV containing image addresses is not an independent media backup.
Map collections into Payload
Define the destination collections before importing. Give each record a stable source identifier separate from its new Payload ID. Retain the source Collection and locale in your mapping when they are needed to distinguish records. Don’t use an editable title as the only matching value.
Choose a supported import method for the mapped data. Payload’s Import Export plugin supports collection imports and a preview. Its CSV structure has its own field and relationship conventions, so transform the Webflow export before using it. Configure the plugin’s job runner when using queued imports, or they can remain pending.
For conversion that needs ordered operations, a developer can write an importer using Payload’s Local API. Run the first import in a disposable development environment. Give the importer a repeatable matching rule so correcting a failed relationship doesn’t create a second copy of every guide.
- Create the schema and choose which fields are localised. Map each Webflow locale to a configured destination locale.
- Upload preserved media and record the new IDs and URLs in the asset manifest.
- Import independent records, such as guide categories. Save a source-to-destination ID map for each collection.
- Import guide records and convert their rich text. Resolve reference values through the ID maps, then fill dependent or circular relationships in a second pass.
- Compare the import results with the source manifest before enabling public delivery.
Payload’s relationship field documentation defines the expected values. A single relationship uses a destination ID, while a relationship with multiple targets uses the configured array shape. A familiar category name displayed in the editor doesn’t prove that its underlying target is correct.
For Lexical rich text, use the documented HTML conversion procedure. Images need separate handling. Upload them first and connect the resulting media records during conversion. Inspect lists, embedded images and internal links in the rendered page instead of treating accepted HTML as proof of equivalent content.
Configure Payload localisation at field level. Decide where fallback is allowed and inspect actual translated values with fallback disabled during migration checks. Otherwise a default-language result can conceal a missing translation.
Rebuild previews, editor access and publication delivery explicitly. Decide who can edit, approve and publish. Connect the frontend to the published content and confirm that draft edits stay private. Recreate forms and commerce behaviour through their separately assigned implementation work.
Verify content and the customer-answer handoff
Use an expected-record manifest for each Collection and locale. Compare accepted imports with that manifest, accounting separately for intentionally excluded or archived records. Check reference targets and media files, then inspect representative rendered guides on desktop and mobile.
Consider a fictional export with 12 guides and four categories. One guide references two categories and has a second-language variant. Expect 12 base guides, four category records and the explicitly mapped variant. That guide must resolve to both intended destination categories, and its variant must retain its translated text. A matching total cannot detect a relationship attached to the wrong category.
Keep unchanged URLs where possible. For changed paths, test each old public URL against the approved redirect map. Confirm that it reaches the intended guide and that the guide’s links use the destination paths. Check locale routes and image requests independently.
Then follow one approved policy change through the whole customer-answer route. In a fictional returns guide, replace an old 14-day period with an approved 30-day period. Publish the Payload record and confirm that the public guide shows 30 days. Refresh the document or retrieval connection used by the retailer’s shopping-answer service, then ask the relevant returns question.
The answer must use the new period and the correct guide. Remove the retired Webflow source from that connection so it can’t continue supplying the obsolete policy. Repeat with a locale-specific question if translated guidance is supplied to the service. Correct content in Payload is only one part of a successful publication handoff.
Cut over without losing recovery material
Give separate owners to domain routing, editor accounts and integration credentials. Record the previous routing and source settings before changing them. Switch public delivery only after the content checks and rebuilt customer interactions pass. Keep the original Webflow site available during the agreed recovery window, with editing controlled to avoid two competing sources.
Retain the original exports, copied media and ID maps. Also keep the final source edits made after the first export. Confirm which team member can restore each system and what happens to new destination edits if delivery returns to Webflow.
Webflow’s backup and restore instructions describe restore points and settings affected by restoration. Have a Site manager confirm the available restore point before the switch. A Webflow restore does not reverse changes to the new frontend or external connections.
In Payload, versions can restore earlier document states when enabled. Keep database and uploaded-file backups through your hosting arrangements as well. Document versions don’t replace the full recovery material needed for a failed initial import.
If records or references differ, pause the affected publication and isolate the failing source row. Give your implementation owner the source ID, destination ID and expected target. Use Webflow support for source export problems and Payload’s official community help for destination questions. Share a redacted example with the relevant schema and import error. Keep the source site and recovery copies until the discrepancy is resolved and the public guide and shopping answer agree.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.