Migration field guide
WordPress to Framer: content, URLs and cutover
Rebuild a small representative page first. Preserve URLs and assets before moving the domain.
Edited by Clinton Feyisitan · Documentation checked
Review scope: Official documentation and field mapping reviewed. The steps below are a proposed validation procedure, not a completed native migration or a measured completion-time claim.
What the documented route supports
WordPress.com exports content as XML. That export includes posts, pages and comments, but not the theme, design customizations or plugins. XML is not automatically a Framer-ready CSV. Framer’s migration guidance uses collection-by-collection content import and a rebuild of page structure. Treat layout, forms, redirects and application features as separate work.
Map before importing
| Source | Destination | Check |
|---|---|---|
| Title / slug | CMS text / slug | Preserve stable URLs or explicitly redirect them. |
| Rich text / dates | Mapped content fields | Check headings, lists, time zones and original publication dates. |
| Images / downloads | Accessible destination assets | Open files after removing reliance on the old host. |
| Forms / plugins / interactions | Separate rebuild | Test actual submission and error behaviour in an authorized test environment. |
A controlled migration
- Inventory pages, collections, slugs, locales, images, downloads, forms and integrations. Export the content and separately save assets you are allowed to reuse.
- Create matching Framer collection fields. Convert the selected XML content into a reviewed CSV or use a verified import workflow; preserve the untouched XML backup. Pilot a small set before importing everything.
- Rebuild list and detail pages with the imported content. Recreate forms and integrations; a content export does not recreate application behaviour.
- Create an old-to-new URL map and redirects. Test on the temporary domain before changing DNS, then recheck the public site after cutover.
Acceptance checks
Record the result and evidence for each check. Stop the cutover if a required check fails.
- Compare expected page counts and inspect a long, short and empty CMS record.
- Check redirects, canonicals, robots, sitemap and important inbound links.
- Test mobile navigation, keyboard access, forms and downloads.
Budget for overlapping plans, required features, seats, storage or usage, and the time to reconcile exceptions. Check the current provider quote; this guide does not reuse historical subscription prices.
Keep a way back
Keep the source site, assets and DNS record of the known-good setup. If the new site fails critical checks, restore the previous domain route and reconcile form submissions collected during the cutover. Do not cancel the old host before asset dependencies are removed.
Official sources
Source availability and account UI can change. Native account execution remains untested in this guide.
Earlier editorial risk estimate
This historical rating has not been recalculated by this documentation review.