
Lungfish Architects
How an award-winning architecture firm achieved 80% faster website performance and significant cost savings through strategic digital optimization and hosting solutions.
From WordPress to Framer
Last verified:
The process
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.
Then we work out how WordPress renders its pages and pull the content out, even without CMS access.
Everything extracted runs through our sanitization pipeline, which flags slop, normalizes structure, and leaves us clean content to work with.
Before anything moves, we agree the Framer content model with you, shaped around how your editors actually work.
We transform the content to the agreed schema and run a full dry run, so mappings and edge cases prove out before production.
Once the dry run is clean, everything moves into Framer in one controlled cutover.
Every old URL gets mapped to its new home with the right redirect, so rankings and link equity survive the move.
Finally, automated browsers sweep the new site for data issues, design regressions, and missing SEO signals.
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.
Content mapping
| In WordPress | In Framer | What to know |
|---|---|---|
| Posts and custom post types | Framer CMS collections | One collection per post type, within the collection limit of your Framer plan. |
| Gutenberg blocks and classic editor HTML | Formatted text fields | Paragraphs, headings, lists, links and images carry across. Custom blocks and shortcodes don't. |
| ACF fields | Fields on the collection | Simple 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 taxonomies | Their own collections, linked with reference fields | |
| Media library | Framer image fields | Alt text comes across with each image. |
| Authors | An authors collection | |
| Pages | Framer pages rebuilt on the canvas | |
| Yoast or Rank Math titles and descriptions | SEO settings on each CMS page | Imported as fields and bound to the page title and description, so search snippets don't reset at launch. |
| Menus | A navigation component |
Watch for these
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.
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.
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.
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.
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.

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
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
Themes, plugins, and core updates sometimes play nicely together, leading to surprise breakages and debugging sessions you didn’t plan for.

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.

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

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).
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.

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
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
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
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
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
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.
We plan the content model, move the content and set up the redirects, so nothing gets lost on the way.
CMS migration agencyTell 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.
Functional, beautiful, websites that you actually want to edit