WordPress to Framer migration with your URLs and rankings intact

We move WordPress sites to Framer for teams that want designers and marketers publishing without plugin updates. Posts, pages and custom post types become Framer collections and designed pages, each plugin's job gets a replacement, and every URL either stays put or gets a permanent redirect, tested against the complete list of old URLs before launch.

Get a proposalMessage us on WhatsApp
Dardo / Editorial illustration
On this page

Why teams move from WordPress to Framer

Upkeep is the usual trigger. A WordPress site is core, a theme and a stack of plugins, and someone has to keep all three current. The plugin layer carries most of the risk: Patchstack's 2026 report found 11,334 new vulnerabilities across WordPress in 2025, up 42% on 2024, and plugins accounted for 91% of them. Framer includes hosting, SSL, CDN delivery and publishing, so there is no server or plugin stack for your team to patch.

  • Designers and marketers change the live layout on Framer's canvas, without a page builder or a developer in between.
  • Field speed: HTTP Archive's September 2026 data has 81.7% of US Framer sites passing Core Web Vitals on mobile; for WordPress the share is 62.0%.
  • Page-builder lock-in: layouts made in Elementor or a similar builder are stored in that builder's format, so changing builders or leaving WordPress means rebuilding them either way.
  • SEO basics without plugins: titles and descriptions per page and per CMS page, an automatic sitemap.xml and robots.txt, and redirects in Site Settings.
  • Fewer moving parts: forms, hosting and the CDN come with the Framer plan instead of separate plugin licences and a hosting account.

Our website platform speed report shows how those field-data averages vary by country, and a carefully built WordPress site can pass as well, so measure your own pages before treating speed as the reason to move.

WordPress and Framer compared for this move

WordPress offers more depth and asks for more maintenance; Framer asks for less configuration and sets firmer limits. Framer's figures here come from its pricing and help pages as of October 2026.

WordPress and Framer compared for this move
AreaWordPressFramer
HostingAny PHP host you choose, or managed WordPress hostingFramer's own servers and CDN; no HTML export for self-hosting
Editingwp-admin, the block editor or a page builder, with built-in roles and no per-user feeDesign canvas; editor seats at USD 20 and content editor seats at USD 10 a month, with a cap of 10 people on Basic or Pro
Content limitsNo plan limit on posts, pages or custom post typesBasic: 30 pages, 2 collections, 1,000 items. Pro: 150 pages, 10 collections, 2,500 items, up to 700, 40 and 40,000 with add-ons
SEO controlsPlugins such as Yoast SEO or Rank Math, which also generate schemaBuilt in per page and CMS page; JSON-LD added by hand; hreflang set automatically and not editable
RedirectsA redirect plugin or rules at the hostPro only, paths on the same domain, wildcards; bulk CSV import through the Redirect Sync plugin
OwnershipOpen source; an XML export carries posts, pages and their fields and termsCMS content exports through plugins as CSV or JSON; layouts stay in Framer
Store and loginsWooCommerce, membership and booking pluginsNo native store or bookings; Framer points to integrations and custom components
Running costHosting, premium plugin licences and someone to apply core, theme and plugin updatesA Pro plan for each site, USD 30 a month on yearly billing, then seats, locales and add-ons on top

What comes across from WordPress, and what doesn't

WordPress lets content leave cleanly. Tools, Export produces a WXR file, an XML document holding posts, pages and custom post types with their custom fields, categories, tags and custom taxonomies, plus comments and users. The REST API returns the same posts, up to 100 per request, with the rendered HTML of each, which helps when a theme or plugin changes what the visitor sees.

Framer's CMS takes CSV files: drop one in and Framer's agent reads the columns and creates the collection schema. As of October 2026 Framer's documentation describes no dedicated WordPress importer, so turning WordPress data into clean CSV files, one per collection, is part of our work.

  • Comes across: post and page text, excerpts, dates, slugs, authors, categories, tags and custom taxonomies, as collection items and references.
  • Comes across: SEO titles and descriptions from Yoast SEO or Rank Math, read for every URL from the live pages and checked again after import.
  • Comes across with work: ACF fields. Simple ones map to Framer field types; ACF PRO repeaters and flexible content have no matching type and become their own collection or a designed section.
  • Comes across with work: everything in /wp-content/uploads/. The XML export doesn't contain the files themselves, so we copy the originals and upload them to Framer.
  • Rebuilt: the theme and every page-builder layout, as Framer pages and components.
  • Replaced or dropped: plugins that worked on the front end, such as forms, sliders, pop-ups, caching and social sharing.
  • Stays out of Framer: WooCommerce, memberships, courses and anything else that needs user accounts, a database or payment logic.
  • Needs a decision: comments, and attachment pages, which stay on for sites that existed before WordPress 6.4 and can add one URL per uploaded file.

How WordPress content maps to Framer

WordPress stores almost everything as a post of some type. Framer splits the site into designed pages and CMS collections, and the plan caps how many collections you get, so each post type needs a decision before anything is imported.

How WordPress content maps to Framer
In WordPressIn FramerHow it moves
Pages from the block editor or a page builderDesigned pages on the canvasRebuilt from the live site, then text placed from the export
PostsA Posts collection with a CMS detail pageWXR or REST export converted to CSV and imported; slugs kept
Custom post types such as case studies, team or locationsOne collection eachSame route; Basic holds 2 collections, Pro 10, up to 40 with add-ons
Categories, tags and custom taxonomiesTheir own collections, referenced from postsImported before the posts that point at them
AuthorsAn Authors collectionNames, bios and photos only; WordPress logins stay behind
ACF and other custom fieldsTyped fields: text, rich text, date, image, file, link, toggle, color, referenceMapped field by field; repeaters split into a collection
Featured images and /wp-content/uploads/Image and file fields hosted by FramerOriginals copied and uploaded; old file URLs with backlinks go in the redirect map
Shortcodes and embeds in post bodiesFormatted text, or an Embed componentCleaned in the conversion script; leftovers listed for manual fixes
Yoast SEO or Rank Math fieldsPage and CMS page metadataRecorded per URL and compared after import
Form plugins such as Contact Form 7, Gravity Forms or WPFormsFramer forms, or HubSpot, Typeform or FormsparkRebuilt; submissions sent to email, Google Sheets or a webhook
A redirect plugin's rulesFramer redirects, on ProExported, merged into the new map, imported as CSV with from and to columns
WPML or Polylang languagesFramer locales, USD 20 a month each, up to 20Translated page paths and CMS slugs set per locale

How we move a WordPress site to Framer

The work runs as part of our website migration service, and nothing moves until the inventory is complete. A WordPress inventory starts from the site's XML sitemap, adds Search Console landing pages for at least a full year and the pages other sites link to, then the URLs WordPress creates by itself: category, tag and author archives, /feed/, ?p= shortlinks, attachment pages and uploaded files.

The inventory becomes a 1:1 redirect map and a Framer content model sized to the plan. Most of these moves need Pro, because Basic has no redirects and its limits can't grow. Our free redirect map generator matches the WordPress and Framer sitemaps for a first pass. Date-based permalinks such as /year/month/post-name/ often collapse into a few wildcard rules, and the rest go into Framer as a CSV.

Pages are designed in Framer and collections filled on a staging copy blocked from indexing, while WordPress keeps answering visitors. The design and build are our Framer development work. We crawl staging with the complete old-URL list and fix every mismatch before DNS moves.

Launch happens in an agreed window: DNS pointed at Framer, redirects published, sitemap submitted, each form tested with a real submission. A large site can move in stages, as long as paths stay the same: Framer's Advanced Hosting add-on, USD 200 a month billed yearly on Pro as of October 2026, serves finished pages and passes every other path to the old site. Search reviews at 30 and 60 days compare against the WordPress baseline, then we hand over the accounts, DNS settings and the redirect list.

Launch checks for a WordPress to Framer move

We run every check on staging and repeat it on the live domain on launch day. Our website migration SEO checklist covers the reasoning and the 90 days after, and our Framer SEO guide covers the settings on the Framer side.

  • The whole old-URL list, archives, feeds, ?p= links and uploads included, answers with its page, a single redirect to a live page, or an intentional 404 or 410.
  • No group of WordPress URLs is sent to the new home page; each goes to its closest equivalent.
  • Paths with and without a trailing slash both resolve, since WordPress permalinks usually end in one.
  • Titles, descriptions and headings match the plugin output recorded before the move.
  • Canonicals point at the new URLs, every locale has its hreflang, and schema the SEO plugin used to generate is back as JSON-LD.
  • Images keep descriptive alt text, and upload URLs with backlinks redirect to their new home.
  • Forms deliver to the right inbox, sheet or CRM; analytics, ad pixels and the consent banner work on the live domain.
  • Search Console: staging noindex gone, new sitemap submitted, Change of Address filed only if the domain changes.
  • Day 30 and day 60: indexed pages, clicks and impressions by page against the WordPress baseline.

When to stay on WordPress

Framer is built for marketing sites. Keep WordPress, or pick another destination, when any of these is true:

  • The store is the business. Framer's own comparison with Wix lists integrations and custom components for Framer, not native stores, bookings or payments.
  • A plugin does core work: memberships, courses, bookings, directories, or anything with logins and a database.
  • More than ten people need to edit. Basic and Pro stop at ten people with edit access, and an eleventh means Enterprise.
  • The archive is very large. Past 40,000 CMS items, 40 collections or 700 pages, Framer moves you to Enterprise, priced on request.
  • You want to own the code. Framer offers no HTML export; our WordPress to Astro migration keeps the site in your repository.
  • Your team wants a visual builder but Framer's limits are tight: compare our WordPress to Webflow migration.

When WordPress itself is fine and the trouble is speed, plugins or search visibility, fixing the current site costs less than moving it. Our SEO service works on the platform you already have.

What Framer costs to run

As of October 2026, billed yearly, Framer's Basic plan is USD 10 and Pro USD 30 a month per site, or USD 15 and USD 45 billed monthly. People are billed per workspace: USD 20 a month for an editor who designs and publishes, USD 10 for a content editor, and nothing for the owner or viewers. Each extra language costs USD 20 a month, and Pro add-ons sell more pages, collections, items and bandwidth. Our Framer pricing guide lists every limit.

Moving usually changes who pays for what more than the total. Framer charges per person and per language; WordPress charges for hosting, plugin licences and the time someone spends on updates. Our Framer vs WordPress comparison prices the same 18-page bilingual site on both over three years, with and without a paid WordPress care plan.

There is no price list for the migration itself: each one is quoted from the URL inventory. The drivers are the templates and URLs, the post types and custom fields, the plugins to replace, the forms and integrations, and the languages. For published market prices by platform and site size, read what website migrations cost in 2026.

Questions before you choose

Will a move to Framer cost us our Google rankings?

Expect some movement while Google recrawls and reindexes; its site-move guide says that on a small or medium site this can take a few weeks for most pages. Lasting drops come from URLs that stop answering or lose their titles and structured data. We keep slugs where Framer allows, redirect the rest one by one, and compare search data with the WordPress baseline at 30 and 60 days. No one can promise rankings.

Can we keep our WordPress URLs?

Most of them. Post and page slugs can stay the same, so paths change only where the new structure differs from WordPress's, such as date-based permalinks or /category/ archives. Those get permanent redirects, often a few wildcard rules rather than one per post.

Can Framer import our WordPress posts directly?

Not directly, as of October 2026. Framer's CMS imports CSV files, and its agent builds a collection from the columns. We export the posts from WordPress, clean shortcodes and builder markup, convert them to one CSV per collection, and import referenced collections such as authors and categories first. Then we check a sample of items against the live posts.

What happens to our WordPress plugins?

Each one gets a decision in the inventory. SEO plugins are replaced by Framer's built-in titles, descriptions and sitemap, plus JSON-LD we add by hand. Form plugins become Framer forms or an integration. Caching and security plugins have nothing left to do. Plugins that run the business, such as a store or memberships, are a reason to stay or to plan a separate system.

Can our writers still publish posts after the move?

Yes. Writers get content editor seats, USD 10 a month each billed yearly as of October 2026, to add and edit CMS items, translations and on-page text without touching layouts. Designers who change pages take editor seats at USD 20 a month.

What happens to our images and PDFs?

They are copied from the uploads folder, since the XML export doesn't hold the files, and uploaded to Framer's image and file fields with their alt text. Old /wp-content/uploads/ addresses with backlinks or image-search traffic get a row in the redirect map; the rest can return 404 once the WordPress host is gone.

Do we need Framer Pro for a migration?

Almost always. Basic has no redirects, and a site that replaces another needs them. Basic also caps you at 30 designed pages, 2 CMS collections and 1,000 items, with no add-ons. Pro costs USD 30 a month per site billed yearly as of October 2026 and adds redirects, staging, roles and 10 collections.

What happens to the old WordPress site and hosting?

It keeps running, reachable only to your team, until Framer answers every old URL and you hold a full export, the uploads folder and a database backup. Keep the domain at your own registrar. The handover lists when to cancel hosting and plugin licences so nothing renews or lapses by surprise.

How much does a WordPress to Framer migration cost?

There is no fixed price; the quote comes after we see the URL inventory. Templates, URLs, post types, custom fields, plugins to replace, forms and languages set the scope. Our website migration cost guide lists published market prices by platform and site size.

From the blog

Sources & further reading

Sources behind this page, with further detail from the original publishers.

Plan your WordPress to Framer move

Send your WordPress URL and the plugins the site relies on. We reply with what fits in Framer, which plan it needs and what the redirect map has to cover.