WordPress to Framer: migration check
Yes, if the site is content and marketing pages; plugins are where the work hides.
What maps where
TodayIn FramerFit
- Posts and pagesCMS collectionsNative
- Theme templatesFramer pages and componentsNative
- Form pluginsFramer FormsNative
- SEO pluginsBuilt-in SEO settingsNative
- Multilingual pluginsLocalization (Pro plan)Native
- ShortcodesCode componentsCode component
- WooCommerceStripe links or Shopify embedExternal
- CommentsDrop or use an external serviceExternal
Where it gets tricky
- The WXR export is the theme-independent truth: it surfaces shortcodes that only render because a plugin exists and ACF fields the theme never printed. Read it before scoping.
- Redirects often live in a plugin's database table (Redirection, Yoast), not in server config. Export that table first or years of accumulated 301s die with the install.
- Framer CMS paths are flat (/blog/slug). Every dated or category-based permalink needs its own 301, so build the redirect map as a file before launch.
Questions that come up
Will I lose my SEO moving off WordPress?
No, if the migration respects your URLs. Post paths stay identical in Framer, anything restructured gets a 301 redirect, and the metadata your SEO plugin managed moves into Framer's built-in settings.
What happens to my WooCommerce store?
It stays where it works. The marketing site and blog move to Framer on the main domain; the store keeps running on a subdomain or path. I do not rebuild working checkouts for the sake of one tool.
What about all my plugins?
Most plugins exist because WordPress needs them. Forms, SEO, caching, and security come built into Framer; the few doing real product work get an external service or a code component, and I list those before we start.
From the design gallery
See all
