By Mehdi HassanHow do you move a WordPress site to Framer?
You move a WordPress site to Framer by rebuilding its pages in Framer and importing its posts into a Framer CMS collection, then redirecting any URLs that change. There's no one-click converter: our research found every move between platforms is a manual rebuild, and Framer is no exception.
That's less daunting than it sounds. Most marketing sites have a handful of unique page layouts and one or two content types, such as posts and case studies. The layouts are designed once in Framer, and the content arrives through an import. This guide focuses on the import choice, because that's where rich WordPress content tends to break. If you're still choosing a destination, read our guide on where to go when you migrate from WordPress.
Is Framer the right fit for your WordPress content?
Framer fits WordPress sites that are mostly designed pages with a modest blog, edited by designers or marketers who value speed and motion. It fits less well when content is large, deeply related or managed with complex editorial workflows.
Our research notes that Framer's CMS has item and collection caps (sources disagree on the exact numbers), no multi-reference fields and a limited API. If your WordPress site relies on posts linked to several categories, authors and related resources, compare it with WordPress to Webflow, whose CMS handles references more fully. If the site carries product logic, look at WordPress to Next.js.
Which WordPress to Framer plugin should you use?
Use a WordPress sync plugin from the Framer Marketplace when you have more than a few dozen posts or regular formatting like headings, lists, links and images. Use CSV import when the blog is small and the content is plain.
Plugins such as WP Sync, WordPress Sync and PostPort connect to your WordPress site, usually through its REST API, and create or update items in a Framer CMS collection. They differ in which fields they map, whether they bring categories, authors and featured images across, and whether they can re-sync later. Features change often, so check each plugin's current listing and test it on a copy of your collection first.
Route | Best for | Where it breaks |
|---|---|---|
Sync plugin (WP Sync, WordPress Sync, PostPort) | Blogs with formatted posts, featured images and taxonomies | Shortcodes, page-builder markup, custom blocks and embeds |
CSV import | Small blogs with plain text and few images | Inline images, complex HTML and references between items |
Custom script via API | Large or unusual content models | Needs a developer; Framer's API is more limited than some CMSs |
Manual rebuild | A few key pages and landing pages | Slow for anything more than a handful of items |
Whichever route you choose, import into a test collection first, open ten varied posts and compare them with the live WordPress versions side by side. Our guide to importing content into Framer CMS walks through CSV, plugins and the API in more detail.
Where does rich WordPress HTML break?
Rich WordPress HTML breaks wherever the content depends on WordPress to render it: shortcodes, page-builder markup, Gutenberg blocks with custom styling, galleries, embeds and plugin-generated elements. Framer's formatted text field handles standard content like headings, paragraphs, lists, links, quotes and images, but not WordPress-specific output.
- Shortcodes like [gallery] or a form shortcode arrive as literal text, or vanish.
- Page-builder content from Elementor, Divi or similar tools is wrapped in nested markup that doesn't map to formatted text.
- Custom blocks such as columns, callouts, tables and buttons lose their layout and styling.
- Embeds for video, social posts and forms often need re-adding with Framer's own embed components.
- Inline images may point to your old wp-content uploads folder and break once WordPress is switched off.
How to find problem content before you import
Search your WordPress database or XML export for common markers: square-bracket shortcodes, page-builder class names, iframe tags and links to wp-content/uploads. Each match is a post that needs attention.
Sort the list by traffic. Posts that rank or convert get cleaned by hand after import. Posts with no traffic and no backlinks may be better retired or merged, which shrinks the import and the redirect sheet at once.
For images, decide whether the plugin re-hosts them in Framer or keeps linking to WordPress. If it links to WordPress, you'll need to re-host them before you shut the old server down.
How do you rebuild WordPress pages in Framer?
Rebuild WordPress pages in Framer by designing each unique layout as a page or a reusable component, then filling it with current, edited copy. Don't recreate a theme pixel by pixel; it's the moment to fix structure, speed and messaging.
List unique templates
Home, product or service pages, pricing, about, contact, blog index, post template and any landing pages. Most sites have fewer than they think.
Audit the copy
Decide what to keep, rewrite or remove on each page before you design it. Moving weak copy to a new platform keeps it weak.
Build components
Make shared sections, such as navigation, footer, call-to-action and testimonials, into components so edits happen once.
Design the CMS templates
Build the post template and listing page, binding fields for title, body, author, category, image and SEO fields.
Add motion with restraint
Framer makes animation easy. Use it for a few meaningful moments and keep pages fast; see Core Web Vitals for Framer, Webflow and Next.js.
Replace plugins
Forms, popups, cookie consent and analytics each need a Framer-native or embedded replacement. Our list of WordPress plugins to replace maps them.
How do you keep SEO when moving WordPress to Framer?
Keep SEO by matching URLs where possible, redirecting the rest permanently, and carrying titles, descriptions, canonicals and structured data over from your WordPress SEO plugin. Framer gives you SEO fields per page and per CMS template, and redirect settings for the site.
- Match the post path. If WordPress posts sit at /blog/post-name, set the Framer collection page path to /blog/ and keep slugs identical.
- Redirect root and date URLs. Posts at the domain root or under date paths need redirects to their new collection URLs.
- Export SEO plugin data. Titles and descriptions live in plugin fields, not post content; add them as CMS fields and bind them to the template's SEO settings.
- Recreate schema. Add Article or FAQ structured data through custom code on templates where it matters.
- Update internal links in post bodies to the new URLs.
If your WordPress site is translated, Framer's localization works differently from WPML or Polylang; read moving translated WordPress sites before you plan URLs.
How much does a WordPress to Framer migration cost?
A WordPress to Framer migration costs whatever the rebuild and import take, and that depends on unique templates, post count, content cleanup and integrations. Our research found agencies quoting $1.5k to $25k for migrations depending on size, and quotes vary widely.
Our WordPress to Framer migration cost and timeline breaks this down week by week. If you're comparing Framer with a code build for later, Framer to Next.js migration cost shows what moving on again would involve. And if you might want full control and plugins back one day, Framer to WordPress migration explains that path honestly.
