★★★★★ 4.6 CE

Framer Migration & Switching Guide 2026

Framer migration is rebuild-and-redirect, not import: there's no content importer, but the redirect system is strong. There's no full export, so the move is one-way.

Website BuildersVerified today

Full review Pricing Official site ↗

Framer Migration verdict

Verified today·5 sources checked

Migrating to Framer is rebuild-and-redirect, not import.

There is no documented content importer from WordPress, another builder or a CSV, so pages, CMS content and design are rebuilt on Framer. What Framer gives you is a genuinely strong redirect system, with folder wildcards, capture groups and drag-to-reorder priority, so old URLs keep working, though redirects only cover sub-paths of your current domain.

How to plan the move

Migrate to Framer when you are rebuilding the design anyway and your main continuity need is preserving URLs and SEO. Rebuild the pages, then map every old URL to its new path, using folder wildcards and capture groups to fold whole sections in one rule, before you switch DNS. Connect the domain with the two A records and the www CNAME, clear conflicting records, and allow up to 48 hours. Keep a master copy of your content outside Framer, because there is no full export if you ever leave.

Honest limits

There is no documented content importer, so pages, CMS content and design are a manual rebuild on Framer, and WordPress or CSV import is not documented.
Redirects are strong, with wildcards and capture groups, but limited to sub-paths of your current domain, so a full domain move needs your old host. Lock-in is high, since the current Framer builder has no documented full-site code or HTML export.
Even custom code does not reduce lock-in: Code Components and Code Overrides are React that runs inside Framer, not a portable codebase.

Content import: None documented
Redirects: Wildcards + capture groups
Redirect scope: Sub-paths only
Domain cutover: A+CNAME, up to 48h
Site code export: None (high lock-in)

View sources

This page covers migrating into Framer and switching safely. SEO output and pricing live on their own pages.

What moves into Framer, and can you leave?

Migration & portability receipt

Pick what you are bringing to Framer, and see exactly what transfers.

Migration read3 transfer, 3 need hand work

URL redirects (301s): imports natively, Site Settings, Redirects; one-to-one rules.
Folder / wildcard redirects: imports natively, /blog/* with capture groups :1, :2.
Custom domain: imports natively, connect a domain you own; two A records + www CNAME.
Full external site (pages/content): manual rebuild, no importer; rebuild on Framer.
WordPress / CSV bulk import: does not transfer, not documented.
Cross-domain redirect: does not transfer, sub-paths only; set domain-level redirect at your old host.

Cutover steps, in order

1Rebuild pages and CMS on Framer, no content importer.
2Map old URLs to redirects, use folder wildcards + capture groups.
3Connect custom domain, two A records + www CNAME.
4Clear conflicting records, wait for DNS, up to 48h to propagate.
5Verify redirects and submit sitemap, Search Console.

Every row is a documented import/export capability from Framer and the source platforms, not an effort estimate.

Framer migration configuration

In Site Settings, Redirects, add one rule per row: old path on the left, new path on the right. Use * to match any segment and :1, :2 to reuse the matched segments, so a single rule can fold an entire old folder onto its new home. Drag rules to set which matches first.

Redirect map (wildcards + capture groups)text

# Old path            ->  New path        (Site Settings -> Redirects)
/about-us.html        ->  /about
/contact.php          ->  /contact

# Fold an entire old folder with a wildcard + capture group:
/blog/*               ->  /news/:1        # /blog/hello-world -> /news/hello-world
/2024/*/*             ->  /articles/:2    # reuse the 2nd matched segment

# Note: redirects cover sub-paths of your current domain only.
# A full domain-to-domain move is set at your old host, not here.

Point an apex domain at Framer with two A records and a www CNAME, and remove any other A or AAAA records so nothing competes. Propagation can take up to 48 hours, so schedule the cutover after the redirect map is live.

DNS cutover (apex + www)text

; Apex / naked domain (example.com): two A records to Framer
@      A      31.43.160.6
@      A      31.43.161.6
www    CNAME  sites.framer.app

; Remove any other A / AAAA records on the domain so they do not conflict.
; Allow up to 48 hours for DNS to propagate worldwide.

After the redirect rules are live and DNS has propagated, confirm an old URL returns a 301 to its new path, then confirm the auto sitemap responds and connect Search Console so the new URLs are recrawled.

Verify redirects and indexingbash

# Confirm an old URL now 301-redirects to its new Framer path:
curl -sI https://your-domain.com/blog/hello-world | grep -i 'HTTP/\|location'
# expect: HTTP/2 301  and  location: https://your-domain.com/news/hello-world

# Confirm the auto-generated sitemap is live, then connect Search Console:
curl -I https://your-domain.com/sitemap.xml

What moves when you migrate to Framer

Migration element	On Framer	Detail	Source
301 redirects (one-to-one)	Native	Route each old URL to a new one in Site Settings, Redirects	—
Folder wildcards + capture groups	Native	/blog/* matches any segment; reuse it with :1, :2 in the destination	—
Redirect priority	Drag to order	Reorder rules by dragging and dropping to set which matches first	—
Cross-domain redirect	Not supported	Sub-paths of your current domain only; a full domain move needs your old host	—
Full external site (pages/content)	Manual rebuild	No content importer; rebuild the design and CMS on Framer	—
Custom domain	Native	Connect a domain you own with two A records and a www CNAME	—

Source-to-Framer mapping

Old-site element	Lands on Framer as	Caveat	Source
A single old URL	A 301 redirect rule	Enter old path and new path in Site Settings, Redirects	—
A whole old folder	One wildcard rule (/blog/* to /news/:1)	Sub-paths of your current domain only	—
Pages and layout	Manual rebuild on a Framer design	No content importer; this is the heavy part	—
CMS / blog content	Re-entered into the Framer CMS	No WordPress or CSV import documented	—
Structured data	JSON-LD via Custom Code or a CMS field	Re-authored per template; can bind to CMS variables	—
Custom code	Code Components / Code Overrides (React)	Runs inside Framer, not a portable codebase out	—
Your domain	Connected (two A records + www CNAME)	Up to 48 hours to propagate	—

Framer migration timeline and rollout

Phase	What happens	Effort	Source
1. Rebuild site	Pages and CMS rebuilt on Framer	High, no content importer	—
2. Redirect map	Old to new, with wildcards + capture groups	Medium, folder rules fold many URLs at once	—
3. Connect domain	Two A records + www CNAME	Low, fixed record values	—
4. DNS propagation	Clear conflicting records, then wait	Low effort, up to 48h to propagate	—
5. Verify	Confirm 301s and sitemap, connect Search Console	Medium, check each redirected path	—

What to verify before you commit to Framer

Getting out is the hard part: the current Framer web builder has no documented full-site code or HTML export, so the design is effectively proprietary to Framer, treat the move as one-way and keep your content master elsewhere
Even the code you write lives inside Framer: Code Components and Code Overrides are React that runs in the Framer canvas, not a standalone codebase you can lift out, so custom work does not reduce the lock-in
There is no content importer, so pages, CMS entries and design are a manual rebuild on Framer; budget that time rather than expecting a WordPress or CSV import
Redirects only cover sub-paths of your current domain, so if you are also changing domains, set the domain-level redirect at your old host and reserve Framer's rules for the path-to-path mapping

Framer Migration FAQ

Can I import my existing website into Framer?

Not as content. Framer does not document an importer from WordPress, another builder or a CSV, so the pages, CMS entries and design are rebuilt on Framer. What Framer provides for a migration is its redirect system, which it calls essential when moving a site, so your old URLs keep resolving to the new pages. Plan a rebuild first, then a redirect map, then the domain cutover.

How good are Framer's redirects for migration?

Better than most hosted builders. You set one-to-one 301s in Site Settings, Redirects. You also get folder wildcards, where /blog/* matches everything under /blog, and capture groups like :1 and :2, so a single rule can fold an entire old URL tree onto new paths. You drag rules to set priority. The one limit is scope: redirects cover sub-paths within your current domain only, so a full domain-to-domain move is set at your old host.

Can I export my site or its code out of Framer later?

Largely no, and this is the biggest thing to weigh. The current Framer web builder has no documented full-site code or HTML export, so the design is effectively proprietary to Framer. Even the code you write, Code Components and Code Overrides, is React that runs inside the Framer canvas rather than a standalone codebase you can lift out. Treat a move to Framer as one-way, and keep a master copy of your content elsewhere.

How do I migrate to Framer without losing SEO?

Map every old URL to its new Framer path and load the redirects before you switch DNS. Use folder wildcards and capture groups to cover whole sections in one rule, and drag rules to set priority where they overlap. Then connect the domain with the two A records, 31.43.160.6 and 31.43.161.6, and the www CNAME to sites.framer.app. Remove any conflicting A or AAAA records, and allow up to 48 hours to propagate before confirming the redirects resolve.

How do I connect my domain to Framer?

From Site Settings, Domains, choose Connect a domain you own and enter it. For an apex domain, set two A records to 31.43.160.6 and 31.43.161.6 and a CNAME from www to sites.framer.app, and make sure no other A or AAAA records remain. The connection can take up to 48 hours to propagate worldwide, though it is usually faster. Yearly plans include a free domain that renews at the standard rate.

How long does a Framer migration take?

It depends on the rebuild, not the platform steps. Rebuilding the pages and CMS content on Framer is the heavy part, since there is no content importer. The redirect map is quick if you use wildcards and capture groups to fold whole folders. The domain cutover is two A records plus a CNAME, with up to 48 hours of DNS propagation. The fast parts are redirects and DNS, while the time goes into rebuilding the design.

Sources & verification

Verified by ComparEdgeMethod: Vendor docs, official pages, and selected independent sources

Source	What was checked	Last checked
Framer Official	Official product page	July 10, 2026
Framer Articles How To Connect A Custom Domain	Articles How To Connect A Custom Domain	July 10, 2026
Framer Articles How To Setup Redirects To Maintain Se	Articles How To Setup Redirects To Maintain Seo Ranking	July 10, 2026
Framer Articles Structured Data Through Json Ld	Articles Structured Data Through Json Ld	July 10, 2026
Framer Developers	Developers	July 10, 2026

Every fact on this Framer page is tied to a named source and a verification date. Freshness-sensitive figures trace to the sources above; verify against the vendor before relying on them.