This is a migration guide, not a "which is better" comparison — if you're still deciding, Framer vs WordPress covers that. This is for people who've already decided: they're moving an existing Framer site to WordPress and want to know what actually carries over.
The short version: nothing transfers automatically
Framer has no WordPress export, and WordPress has no Framer import. There is no plugin, no migration tool, no XML file that moves a Framer site into WordPress the way you'd move one WordPress install to another. Every part of the move is manual, and the amount of manual work depends entirely on which path you take.
Path 1: Rebuild the design in a WordPress page builder
The most common route — use a builder like Elementor, Bricks, or the native WordPress block editor and rebuild the layout from scratch, using the live Framer site as a visual reference. What you keep: nothing automatically, but you can copy text content, re-download images from the live site, and match colors/fonts by eye or by inspecting the page. What you lose: exact pixel positioning, Framer's specific animation curves, and any custom interaction — WordPress page builders have their own animation systems that don't map one-to-one onto Framer's.
This is real design and development work, not a technical migration — budget for it accordingly.
Path 2: Convert to HTML first, then wrap it as a WordPress theme
A less common but sometimes faster route for design-heavy sites: convert the Framer site to a clean, optimized static HTML bundle first, then hand that HTML/CSS to a developer to slice into a custom WordPress theme (or serve it through a static-HTML plugin). This preserves the exact visual design and Framer's own layout — the thing rebuilding in a page builder can't guarantee — at the cost of losing WordPress's page-builder editing experience; changes to a hand-coded theme go through code, not a visual editor.
This only makes sense if pixel-exact fidelity to the original design matters more than being able to visually drag-and-drop edit the result afterward. If you want both fidelity and continued visual editing, that's a different tradeoff than WordPress — see the note at the end.
What to actually check before you start
- Content. Copy your text and re-download your images from the live Framer site before you touch anything else — this is the one step every path shares, and the easiest thing to lose track of mid-migration.
- CMS Collections. Framer's CMS Collections (a blog, a portfolio grid) map conceptually to WordPress's Custom Post Types, but the field structures don't transfer — you'll be re-entering the schema by hand, then re-entering or scripting the import of each item's content.
- SEO. Whatever you do, keep your URL structure identical if at all possible (same paths, same slugs) so you don't need a redirect map, and set up 301 redirects for anything that does change. Framer's per-page SEO settings (title, meta description, OG tags) need to be manually re-entered in WordPress's SEO plugin (Yoast, Rank Math) for every page.
- Forms. Framer's native forms won't work in WordPress — you'll need a WordPress form plugin (Contact Form 7, WPForms) reconfigured from scratch, including re-wiring wherever your form submissions used to go (email, a webhook, a CRM).
If pixel-exact fidelity AND continued editing both matter to you
Worth knowing before you commit to the WordPress rebuild: converting a Framer site to a real Next.js project keeps the exact design (including animations) and gets you actual source code you own, hosted anywhere, for free — without the manual rebuild step Path 1 requires or the code-only editing tradeoff of Path 2. It's a different platform than WordPress, so it's not a fit if you specifically need WordPress's plugin ecosystem — but if what you actually want is "get off Framer's monthly plan without losing the design," it's worth comparing before you start the WordPress rebuild.