Skip to content




WordPress logo
Framer logo

From WordPress to Framer

We are the WordPress to Framer migration experts

Last verified:


The process

How we migrate from WordPress to Framer

  1. 01

    Access and gating audit

    First we check the existing WordPress and see whether the data is clean enough to move straight over to Framer, and plan around any auth walls or bot protection in the way.

  2. 02

    Rendering assessment and extraction

    Then we work out how WordPress renders its pages and pull the content out, even without CMS access.

  3. 03

    AI-assisted sanitization

    Everything extracted runs through our sanitization pipeline, which flags slop, normalizes structure, and leaves us clean content to work with.

  4. 04

    Content-model design with the client

    Before anything moves, we agree the Framer content model with you, shaped around how your editors actually work.

  5. 05

    Transform and soft-migrate

    We transform the content to the agreed schema and run a full dry run, so mappings and edge cases prove out before production.

  6. 06

    Execute the real migration

    Once the dry run is clean, everything moves into Framer in one controlled cutover.

  7. 07

    Redirect mapping and throttled sitemap submission

    Every old URL gets mapped to its new home with the right redirect, so rankings and link equity survive the move.

  8. 08

    Agentic-browser QA

    Finally, automated browsers sweep the new site for data issues, design regressions, and missing SEO signals.

  9. Ready when you are. We'll bring the moving boxes.Start my migration


What the move involves

WordPress to Framer

A content-only move from WordPress to Framer takes at least six weeks. Framer is a visual builder, so the design moves too, and every page template is rebuilt by hand on the Framer canvas. Cost follows how messy the content is more than how much of it there is: how many post types and ACF field groups you have, how many block types and shortcodes sit in post bodies, and how much content plugins hold outside the posts table.

WordPress keeps a post as one blob of HTML in wp_posts, with everything else spread through wp_postmeta. Framer keeps content in CMS collections with typed fields, and lays out everything else directly on its canvas. So most of the work happens before anything moves. We go through the post types, field groups and block types, decide which ones become Framer collections and which were only ever layout, and agree the collections with your editors first.

Then we script the transform and run a full dry run into a copy of the Framer project. Post bodies go into Framer's formatted text fields, which hold HTML, so standard paragraphs, headings, lists, links and images carry across. Custom blocks and shortcodes don't, and anything the script can't map gets flagged rather than dropped. Categories, tags and authors load first as their own collections, so every post can reference them, and images come out of the uploads folder and into Framer.

The pages themselves are a rebuild: your WordPress theme becomes Framer components, stacks and effects. We build the redirect map from the WordPress permalink structure before cutover, including the category, tag, author and attachment URLs WordPress generates on its own, keep the WordPress site live until the Framer one is verified, and run automated browser QA across the new site.

Scope my migration


Where WordPress content lands in Framer

Content mapping

In WordPressIn FramerWhat to know
Posts and custom post typesFramer CMS collectionsOne collection per post type, within the collection limit of your Framer plan.
Gutenberg blocks and classic editor HTMLFormatted text fieldsParagraphs, headings, lists, links and images carry across. Custom blocks and shortcodes don't.
ACF fieldsFields on the collectionSimple fields map one to one. Repeaters and flexible content get flattened, split into a referenced collection, or rebuilt as page layout.
Categories, tags and custom taxonomiesTheir own collections, linked with reference fields
Media libraryFramer image fieldsAlt text comes across with each image.
AuthorsAn authors collection
PagesFramer pages rebuilt on the canvas
Yoast or Rank Math titles and descriptionsSEO settings on each CMS pageImported as fields and bound to the page title and description, so search snippets don't reset at launch.
MenusA navigation component


What doesn't move cleanly

Watch for these

Shortcodes and page builder markup

Elementor, Divi and WPBakery store layout as nested shortcodes or their own markup inside the post body, and Framer's formatted text has no use for any of it. We rebuild those pages on the Framer canvas, or strip the layout and keep the copy.

ACF repeaters and flexible content

Framer collections hold fields and references, not nested groups of fields. We flatten short repeaters into fixed fields, split longer ones into their own collection, and rebuild flexible content layouts as Framer pages and components.

Content that lives in plugins

Forms, sliders, tables, comments and anything WooCommerce manages sit outside the posts table, so a posts export misses them. We list every plugin that holds content during the audit and decide for each one whether Framer has an equivalent, a third-party service takes over, or it gets archived.

Auto-generated archive URLs

WordPress serves date archives, tag pages, author pages, attachment pages and feeds without anyone creating them. Framer's redirect settings accept wildcards, so whole groups like /tag/* can redirect in one rule, but each group still needs a deliberate destination or it becomes a 404 that search engines still have indexed.



Challenges with WordPress

Key pain points

Talking trash about WordPress is therapy at this point. We've had to build it for years, and it's consistently awful. I guarantee that if you have used it for long enough, you've experienced a site-breaking PHP error or been locked out of your admin panel due to a faulty plugin. We know the world of horrors, and we regret adding to that share of the web. Yes, it really does power over 40% of all sites, roughly 41.5% at the last count.

Help me migrate


WordPress security vulnerabilities

Potential security vulnerabilities

Core, plugins and themes all need regular patching, and some fixes aren't yours to make. In October 2026, PHP2Shell left WordPress sites exposed until they or their host updated PHP, and WordPress.org said no WordPress update was planned.

Heavy reliance on plugins

Heavy reliance on plugins

If you want any new feature, install a new plugin. Before you know it, your site is held together by 27 plugins and a prayer that none of those plugins are removed from the market.

Compatibility issues

Compatibility issues

Themes, plugins, and core updates sometimes play nicely together, leading to surprise breakages and debugging sessions you didn’t plan for.

WordPress maintainance challenges

Maintenance takes time

WordPress doesn’t run itself. You have to run backups, security patches, plugin conflicts, and random errors. Someone has to tuck it in at night.

WordPress performance needs tuning

Performance needs tuning

WordPress sites need caching, CDN, and database optimization to stay fast, especially if you plan to scale.

Requires careful management - Contentful

Customization has limits

You think you can do a lot with themes and plugins, but when it comes to custom experiences, it means custom dev work (or going headless entirely).



Benefits of Framer

Key advantages

If you live in Figma all day, Framer is the right choice for you. You can import your layouts, tweak a few interactions, hit publish, and suddenly you’ve "built a website" without ever opening VS Code. The no-code editor is fast, the animations look like you actually care about UI, and the built-in hosting + global CDN means you never have to touch a server or pretend you know what an SSL certificate is.

Multiple people can jump in, rewrite copy, adjust layouts, and preview the site instantly in real time with zero handoff pain, and "can you push this to staging?" nonsense. The SEO defaults are strong, images automatically behave, and performance is fast without you having to obsess over Lighthouse scores.

Can't knock the service, but we're here when you're looking to build something more scalable.

Start my migration


Drag and drop Framer

Ability to control layout with drag and drop

You can drag, drop, and publish without the need for any developer or having experience in website development. With Framer, you can easily turn your mockup into a working page.

Quick and cheap to build something

Quick and cheap to build something

If you need a site yesterday (and on a budget), go ahead with Framer. You can go from a Figma-level idea to a live marketing page in a few hours without writing any code or having developers wait on stand-ups.

Some optimization comes by default

Some optimization comes by default

Framer quietly handles things like image compression, semantic markup, and basic SEO hygiene. You ship quickly, and the site doesn't fall apart in Lighthouse analyses.

Huge library of themes

Huge library of themes

You can pick a template, tweak a few components, and you’re basically done. Its theme library is stacked, and most of it looks "portfolio ready" right out of the box.

Real-time team collaboration

Real-time team collaboration

Multiple people can jump in, edit, comment, and tweak designs live like Figma. It speeds up feedback loops and kills the endless back-and-forth.

Intuitive, designer-friendly UI

Intuitive, designer-friendly UI

If you know your way around Figma, you’ll be able to use Framer without any difficulty. Framer’s interface is simple, and keeps designers moving without begging a developer for help.





Common questions

WordPress to Framer migration FAQs

Answers to the most common questions about WordPress to Framer migration

How long does a WordPress to Framer migration take?
A content-only WordPress to Framer migration takes at least six weeks, including the collection mapping, a full dry run and the cutover. Because the WordPress theme is rebuilt by hand on the Framer canvas, sites with many page templates or page builder layouts take longer.
Can WordPress posts be imported into the Framer CMS?
Yes. WordPress posts move into Framer CMS collections, and post bodies go into Framer's formatted text fields, which store HTML, so paragraphs, headings, lists, links and images carry across. Shortcodes and custom Gutenberg blocks don't, so we flag each one for rebuilding rather than letting it import as broken markup.
What happens to WordPress plugins when moving to Framer?
WordPress plugins don't run on Framer, so each one that holds content or adds a feature needs a decision before the move. Forms can be rebuilt with Framer's own forms, while comments, WooCommerce stores and other plugin data need a third-party service or an archive. We list every plugin during the audit.
Will we lose search rankings moving from WordPress to Framer?
Not if the redirects are complete. Before cutover we map every WordPress URL to its new Framer path, including the category, tag, author, attachment and date archive pages WordPress creates automatically, using Framer's wildcard redirects for whole groups of URLs. We carry Yoast or Rank Math titles and descriptions across as well.
When is Framer the wrong choice after WordPress?
Framer's CMS feeds only the Framer site, so it is the wrong choice if the same content needs to reach an app or other channels, or if your WordPress content model leans heavily on ACF repeaters and nested relationships. In those cases a headless CMS such as Sanity, with a separate frontend, fits the content better than Framer does.
How much does WordPress cost per month?
WordPress.org itself is free, but hosting, themes, premium plugins, and maintenance add up quickly. Managed hosting like SiteGround looks cheap at intro pricing, around $3-8/month, then renews closer to $18-45/month. Add a premium theme ($50-200 one-time), a few paid plugins ($100-500/year), and a security solution. Realistically, you're looking at $30-100/month for a properly maintained small business site. WordPress.com's managed plans run $9/month (Personal, or $4/month billed annually) to $70/month (Commerce, or $45/month billed annually) on annual billing. Since September 2025, plugin installs work on every paid plan from Personal up, not just Business as they used to. WordPress.com Enterprise starts at $25,000/year.
Was WordPress affected by PHP2Shell?
Yes, WordPress sites were exposed if the PHP underneath them wasn't patched, although WordPress itself isn't the bug. PHP2Shell is two critical PHP flaws, CVE-2026-109618 and CVE-2026-109619, both rated CVSS v4 9.2. They allow unauthenticated remote code execution on PHP that serves web requests, including mod_php, PHP-FPM, php-cgi, FrankenPHP and LiteSpeed, in code going back to PHP 5.4. PHP fixed them on October 21, 2026 in 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP 7.4 to 8.1 get source backports only, and 5.4 to 7.3 get no fix. WordPress.org says no WordPress update is planned, so the fix is your host updating PHP. Headless WordPress still runs PHP and needs the same patch. We last checked this on October 23, 2026.
What are the best WordPress alternatives?
It depends on what you're building. For marketing sites, Webflow or Framer will get you further with less pain. For content-heavy projects that need a headless CMS, Sanity is our go-to recommendation. It gives developers full control over the frontend while editors get a clean, modern interface. If you're a developer looking for alternatives specifically, Next.js paired with Sanity or even a static site generator will outperform WordPress on speed, security, and developer experience.
How do I migrate from WordPress to a headless CMS?
We start by exporting your WordPress content using WP's REST API or a database export, then restructure it for the target CMS. Posts, pages, categories, tags, media, and custom fields all get mapped to the new schema. The frontend gets rebuilt in a modern framework like Next.js. The whole process takes at least six weeks, and longer depending on how many custom post types and plugins you have. We've done this migration enough times to have solid tooling for it.
What are the best WordPress alternatives for developers?
If you're a developer tired of PHP and plugin conflicts, look at headless CMS options paired with a frontend framework. Sanity with Next.js is our top pick. You get TypeScript, version control for your content schema, and a frontend you actually enjoy working with. Strapi is another option if you want self-hosted and open-source. For simple sites, Astro with markdown content is surprisingly powerful and deploys anywhere.
Is it worth migrating away from WordPress?
For most teams we work with, yes. The maintenance burden alone costs more than people realize. Between plugin updates, security patches, performance tuning, and the occasional site-breaking PHP error, WordPress demands constant attention. Modern alternatives give you better performance, stronger security by default, and a developer experience that doesn't feel like 2010. The migration itself is an investment, but the reduced ongoing costs and improved site speed usually pay for it within 6-12 months.
Does Framer support headless or API content delivery?
Not really. Framer renders and hosts your site on its own infrastructure, and the CMS is built to feed that frontend, not to serve content over an API to another app. There is a read API for pulling collection data out, which is enough for an export or a migration, but you can't point a separate Next.js or mobile app at Framer as a content backend the way you would with Sanity or Contentful. If you need one content source feeding a website, an app, and a few other surfaces, Framer is the wrong shape. A headless CMS is built for exactly that.


We plan the content model, move the content and set up the redirects, so nothing gets lost on the way.

CMS migration agency


Related migrations





Get in touch

Tell us what you're building. We reply within one working day. Jono or someone on the team picks up every message personally.

You can also book a call.

By sending this you agree to our privacy policy. We only use your details to reply.