A platform move feels like a design task and behaves like an engineering one. Pages are easy to rebuild. The things that go wrong are the ones nobody drew: a redirect that was never written, a form that stopped sending, a canonical tag that points at the old domain.
This guide shows you a Webflow to Framer migration plan for a SaaS site. You will get an eight step sequence, an inventory sheet, a redirect and metadata checklist and the mistakes that cost teams rankings. A disclosure first: we build sites in Framer, so we are not neutral on the platform. This guide covers the move itself, not whether you should make it.
Key takeaways
A migration can keep your rankings if URLs and content stay stable. Change the platform first, then everything else.
Start with an inventory. Mark every URL keep, redirect, merge or remove before you build.
CMS content moves by CSV. Pages, styles, forms and integrations are rebuilt.
Redirect only what changes, straight to the closest page, with no chains.
Keep the old site running until the new one is verified, and watch search for weeks.
Should you migrate from Webflow to Framer at all?
Migrate when the platform is the bottleneck, and not before. A move costs time and carries risk, so it needs a reason that survives the cost.
Common reasons SaaS teams give are faster design iteration, easier edits for marketing and a closer match to how the design team works. Common reasons to stay are a deep investment in Webflow’s CMS logic, ecommerce, complex localization or a large team already fluent in it. For a fuller comparison, read Framer vs Webflow for B2B SaaS.
If you are also changing the message or the design, do those as separate releases. When rankings move after one change, you know why.
What is the Keep, Redirect, Merge, Remove Sheet?
It is a spreadsheet with one row per URL and one decision per row. Framer’s migration guide recommends giving each URL a keep, redirect, merge or remove decision, and we use the same four labels.
Decision | When to use it | What happens to the URL |
|---|---|---|
Keep | The page stays as it is | Same path on the new site |
Redirect | The URL must change | Permanent redirect to the closest page |
Merge | Two pages cover one topic | One page stays, the other redirects to it |
Remove | The page has no value | Removed, with a redirect if it has links or traffic |
Fill it from your sitemap, analytics, Search Console and a crawl, so it includes pages that are not in the navigation. Add columns for traffic, links, title and the Framer URL. This sheet becomes your redirect list and your launch test.
What are the eight steps of a Webflow to Framer migration?
Do them in order. Each step has an output, and the next step depends on it.
Inventory. List every page, CMS collection, asset, integration and style. Fill the sheet and note existing Webflow redirects.
Set up Framer. Create the page structure, text and color styles, components and the three breakpoints. Create the CMS collections, starting with those that other collections refer to.
Migrate CMS content. Export each Webflow collection as a CSV and import it into the matching Framer collection one at a time. Map the columns, then check slugs, dates, rich text, images and references.
Rebuild key pages. Start with one representative page, replace repeated sections with components and check each breakpoint before moving on.
Recreate forms and integrations. Rebuild forms with the same validation, success states and consent text. Reconnect analytics, CRM, chat and embeds.
Set up redirects. Redirect only the URLs that changed, and test each one.
Test before DNS. Check routes, links, forms, metadata, the 404 page, the sitemap and robots.txt on desktop, tablet and phone.
Switch DNS. Connect the domain, add the records and keep Webflow available until the production site is verified.
Framer’s guide is explicit about the split: CMS content can be imported, while pages, styles, components, forms, custom code and interactions are rebuilt. Webflow’s CMS, forms, search and localization behavior are not recreated automatically.
Pro tip: Rebuild one page and one CMS template completely, then review them with the whole team before you build the rest. Problems with components and breakpoints are cheap to fix on page one and expensive on page forty.
How do you migrate the CMS and blog?
Move collections one at a time, referenced collections first, and check a sample of items by hand. A blog is the largest source of search traffic for many SaaS sites, so it deserves the most care.
Export each collection from Webflow as a CSV.
Create the matching collection in Framer with the same field types.
Import the CSV and map each column to a field.
Check slugs first. A changed slug is a changed URL.
Check rich text for broken formatting, images for missing alt text and references between items.
Open the list page and a handful of detail pages on all three breakpoints.
Rich text often needs hand cleanup, especially tables, embeds and custom code blocks. Budget time for it.
How do you protect SEO during the move?
Keep URLs and slugs the same wherever you can, redirect anything that changes and verify metadata on every template. Framer’s SEO guidance says a platform move does not have to reduce search visibility if URLs and content stay stable.
Area | What to do |
|---|---|
URLs | Keep paths and CMS slugs unchanged where possible |
Redirects | Use permanent redirects (301 or 308), straight to the final page |
Redirect tools | Framer supports exact, wildcard and capture group redirects and bulk import from a CSV |
Metadata | Set each page’s title, description, social preview and canonical |
Structured data | Recreate JSON LD with custom code, match it to visible content, validate it |
Sitemap | Framer generates one; check it and submit it in Search Console |
Search Console | Save a baseline before the move and keep a verification method that survives the cutover |
Google’s site move guidance adds three rules: map old URLs to relevant new ones instead of the homepage, avoid redirect chains and keep redirects in place. In Google’s words: “Keep the redirects for as long as possible, generally at least 1 year.” Use the domain Change of Address tool only if the domain or subdomain changes.
Pro tip: Save a Search Console export of queries and pages before you begin. After launch, compare the same pages week by week, so a drop on one page is visible, not lost in the total.
What can go wrong with forms and integrations?
Forms and tracking are the quiet failures, because nothing looks broken. Test them as carefully as pages.
A form that submits but sends nowhere, or sends to the old inbox
Consent banners that no longer block scripts until accepted
Analytics events and conversion goals that stop firing
A booking tool embed that breaks on phones
UTM parameters lost in a redirect or form handoff
Hidden fields for the CRM that were not rebuilt
Submit every form from a real phone and check the CRM, the inbox and the analytics. Do it again after the DNS switch, because test and production settings often differ.
How do you launch and monitor?
Switch DNS at a quiet time, keep the old site available and watch the first weeks closely.
Connect the domain and wait for DNS and SSL to be active.
Repeat the key checks on the production domain.
Inspect your most important URLs in Search Console and submit the sitemap.
Watch crawl errors, indexing, rankings, traffic and conversions daily for the first week, then weekly.
Keep redirects for at least a year.
Keep Webflow available until you are confident, then plan the shutdown with a date.
Avoid Friday launches. A problem found on Monday has already cost a weekend of leads.
What can go wrong in a Webflow to Framer migration?
Most of the risk sits in URLs, redirects and content that does not copy cleanly, such as rich text, embeds and forms. Six to check:
No inventory. Pages nobody remembered lose their traffic.
Changing URLs for tidiness. Each change needs a redirect and risks lost links.
Redirecting everything to the homepage. Google advises mapping to relevant pages.
Forgetting rich text and embeds. Content looks fine in the list and broken in the detail page.
Not testing forms. Leads vanish without an error.
Switching off the old site early. You lose the fallback.
Also read: SaaS Homepage Redesign Checklist.
To see how we design and build SaaS pages, browse all of our case studies.
Is your migration plan ready?
Send us your sitemap and we will return a filled inventory sheet. Book a migration review · See our work
Webflow to Framer migration FAQs
Inventory every page and asset, set up the Framer structure and styles, import CMS content by CSV, rebuild pages, forms and integrations, set redirects, test before switching DNS and keep Webflow live until the new site is verified. CMS content can be imported, but pages and forms are rebuilt.
It does not have to. Framer’s SEO guidance says a platform move can keep visibility if URLs and content stay stable. Keep slugs, redirect only what changes with permanent redirects, verify metadata and structured data and watch Search Console closely after launch.
Yes, by CSV. Export each collection from Webflow, create a matching collection in Framer and import, mapping the columns to fields. Then check slugs, dates, rich text, images and references. Webflow’s CMS logic, forms and search are not recreated automatically.
It depends on the number of pages, the size of the CMS, the number of integrations and how much you also change. A small marketing site is faster than a large site with a big blog and localization. Most of the time goes to the inventory, rich text cleanup and testing.
Yes. Kraftbase is a product messaging and UI/UX design studio for AI and B2B SaaS companies, and we build in Framer. We start with the inventory sheet and a redirect plan, and we will say plainly if staying on Webflow suits you better.
As long as possible, and generally at least a year according to Google’s site move guidance. Keep them longer if the old URLs still have meaningful links or traffic. Update your own internal links so they point straight to the new URLs.
Avoid it. Changing URLs adds risk, because every changed URL needs a redirect and may lose some link value. Keep paths and slugs the same, and improve the structure in a separate release once the migration is stable.
About the author
Dhaval Agrawal is the founder and CEO of Kraftbase, a product messaging and UI/UX design studio in Vadodara, India, that helps AI and B2B SaaS teams in the US, UAE and India explain and design what they’ve built.
Sources
How to move a site (site move with URL changes), Google Search Central, read Nov 3, 2026
Webflow to Framer SEO migration guide, Framer, read Nov 3, 2026
Webflow to Framer step by step guide, Framer, read Nov 3, 2026
Keep, Redirect, Merge, Remove Sheet: follows Framer’s own labels, adapted by Kraftbase
Migration review
Is your migration plan ready?
Send us your sitemap and we will return a filled inventory sheet.
A platform move feels like a design task and behaves like an engineering one. Pages are easy to rebuild. The things that go wrong are the ones nobody drew: a redirect that was never written, a form that stopped sending, a canonical tag that points at the old domain.
This guide shows you a Webflow to Framer migration plan for a SaaS site. You will get an eight step sequence, an inventory sheet, a redirect and metadata checklist and the mistakes that cost teams rankings. A disclosure first: we build sites in Framer, so we are not neutral on the platform. This guide covers the move itself, not whether you should make it.
Key takeaways
A migration can keep your rankings if URLs and content stay stable. Change the platform first, then everything else.
Start with an inventory. Mark every URL keep, redirect, merge or remove before you build.
CMS content moves by CSV. Pages, styles, forms and integrations are rebuilt.
Redirect only what changes, straight to the closest page, with no chains.
Keep the old site running until the new one is verified, and watch search for weeks.
Should you migrate from Webflow to Framer at all?
Migrate when the platform is the bottleneck, and not before. A move costs time and carries risk, so it needs a reason that survives the cost.
Common reasons SaaS teams give are faster design iteration, easier edits for marketing and a closer match to how the design team works. Common reasons to stay are a deep investment in Webflow’s CMS logic, ecommerce, complex localization or a large team already fluent in it. For a fuller comparison, read Framer vs Webflow for B2B SaaS.
If you are also changing the message or the design, do those as separate releases. When rankings move after one change, you know why.
What is the Keep, Redirect, Merge, Remove Sheet?
It is a spreadsheet with one row per URL and one decision per row. Framer’s migration guide recommends giving each URL a keep, redirect, merge or remove decision, and we use the same four labels.
Decision | When to use it | What happens to the URL |
|---|---|---|
Keep | The page stays as it is | Same path on the new site |
Redirect | The URL must change | Permanent redirect to the closest page |
Merge | Two pages cover one topic | One page stays, the other redirects to it |
Remove | The page has no value | Removed, with a redirect if it has links or traffic |
Fill it from your sitemap, analytics, Search Console and a crawl, so it includes pages that are not in the navigation. Add columns for traffic, links, title and the Framer URL. This sheet becomes your redirect list and your launch test.
What are the eight steps of a Webflow to Framer migration?
Do them in order. Each step has an output, and the next step depends on it.
Inventory. List every page, CMS collection, asset, integration and style. Fill the sheet and note existing Webflow redirects.
Set up Framer. Create the page structure, text and color styles, components and the three breakpoints. Create the CMS collections, starting with those that other collections refer to.
Migrate CMS content. Export each Webflow collection as a CSV and import it into the matching Framer collection one at a time. Map the columns, then check slugs, dates, rich text, images and references.
Rebuild key pages. Start with one representative page, replace repeated sections with components and check each breakpoint before moving on.
Recreate forms and integrations. Rebuild forms with the same validation, success states and consent text. Reconnect analytics, CRM, chat and embeds.
Set up redirects. Redirect only the URLs that changed, and test each one.
Test before DNS. Check routes, links, forms, metadata, the 404 page, the sitemap and robots.txt on desktop, tablet and phone.
Switch DNS. Connect the domain, add the records and keep Webflow available until the production site is verified.
Framer’s guide is explicit about the split: CMS content can be imported, while pages, styles, components, forms, custom code and interactions are rebuilt. Webflow’s CMS, forms, search and localization behavior are not recreated automatically.
Pro tip: Rebuild one page and one CMS template completely, then review them with the whole team before you build the rest. Problems with components and breakpoints are cheap to fix on page one and expensive on page forty.
How do you migrate the CMS and blog?
Move collections one at a time, referenced collections first, and check a sample of items by hand. A blog is the largest source of search traffic for many SaaS sites, so it deserves the most care.
Export each collection from Webflow as a CSV.
Create the matching collection in Framer with the same field types.
Import the CSV and map each column to a field.
Check slugs first. A changed slug is a changed URL.
Check rich text for broken formatting, images for missing alt text and references between items.
Open the list page and a handful of detail pages on all three breakpoints.
Rich text often needs hand cleanup, especially tables, embeds and custom code blocks. Budget time for it.
How do you protect SEO during the move?
Keep URLs and slugs the same wherever you can, redirect anything that changes and verify metadata on every template. Framer’s SEO guidance says a platform move does not have to reduce search visibility if URLs and content stay stable.
Area | What to do |
|---|---|
URLs | Keep paths and CMS slugs unchanged where possible |
Redirects | Use permanent redirects (301 or 308), straight to the final page |
Redirect tools | Framer supports exact, wildcard and capture group redirects and bulk import from a CSV |
Metadata | Set each page’s title, description, social preview and canonical |
Structured data | Recreate JSON LD with custom code, match it to visible content, validate it |
Sitemap | Framer generates one; check it and submit it in Search Console |
Search Console | Save a baseline before the move and keep a verification method that survives the cutover |
Google’s site move guidance adds three rules: map old URLs to relevant new ones instead of the homepage, avoid redirect chains and keep redirects in place. In Google’s words: “Keep the redirects for as long as possible, generally at least 1 year.” Use the domain Change of Address tool only if the domain or subdomain changes.
Pro tip: Save a Search Console export of queries and pages before you begin. After launch, compare the same pages week by week, so a drop on one page is visible, not lost in the total.
What can go wrong with forms and integrations?
Forms and tracking are the quiet failures, because nothing looks broken. Test them as carefully as pages.
A form that submits but sends nowhere, or sends to the old inbox
Consent banners that no longer block scripts until accepted
Analytics events and conversion goals that stop firing
A booking tool embed that breaks on phones
UTM parameters lost in a redirect or form handoff
Hidden fields for the CRM that were not rebuilt
Submit every form from a real phone and check the CRM, the inbox and the analytics. Do it again after the DNS switch, because test and production settings often differ.
How do you launch and monitor?
Switch DNS at a quiet time, keep the old site available and watch the first weeks closely.
Connect the domain and wait for DNS and SSL to be active.
Repeat the key checks on the production domain.
Inspect your most important URLs in Search Console and submit the sitemap.
Watch crawl errors, indexing, rankings, traffic and conversions daily for the first week, then weekly.
Keep redirects for at least a year.
Keep Webflow available until you are confident, then plan the shutdown with a date.
Avoid Friday launches. A problem found on Monday has already cost a weekend of leads.
What can go wrong in a Webflow to Framer migration?
Most of the risk sits in URLs, redirects and content that does not copy cleanly, such as rich text, embeds and forms. Six to check:
No inventory. Pages nobody remembered lose their traffic.
Changing URLs for tidiness. Each change needs a redirect and risks lost links.
Redirecting everything to the homepage. Google advises mapping to relevant pages.
Forgetting rich text and embeds. Content looks fine in the list and broken in the detail page.
Not testing forms. Leads vanish without an error.
Switching off the old site early. You lose the fallback.
Also read: SaaS Homepage Redesign Checklist.
To see how we design and build SaaS pages, browse all of our case studies.
Is your migration plan ready?
Send us your sitemap and we will return a filled inventory sheet. Book a migration review · See our work
Webflow to Framer migration FAQs
Inventory every page and asset, set up the Framer structure and styles, import CMS content by CSV, rebuild pages, forms and integrations, set redirects, test before switching DNS and keep Webflow live until the new site is verified. CMS content can be imported, but pages and forms are rebuilt.
It does not have to. Framer’s SEO guidance says a platform move can keep visibility if URLs and content stay stable. Keep slugs, redirect only what changes with permanent redirects, verify metadata and structured data and watch Search Console closely after launch.
Yes, by CSV. Export each collection from Webflow, create a matching collection in Framer and import, mapping the columns to fields. Then check slugs, dates, rich text, images and references. Webflow’s CMS logic, forms and search are not recreated automatically.
It depends on the number of pages, the size of the CMS, the number of integrations and how much you also change. A small marketing site is faster than a large site with a big blog and localization. Most of the time goes to the inventory, rich text cleanup and testing.
Yes. Kraftbase is a product messaging and UI/UX design studio for AI and B2B SaaS companies, and we build in Framer. We start with the inventory sheet and a redirect plan, and we will say plainly if staying on Webflow suits you better.
As long as possible, and generally at least a year according to Google’s site move guidance. Keep them longer if the old URLs still have meaningful links or traffic. Update your own internal links so they point straight to the new URLs.
Avoid it. Changing URLs adds risk, because every changed URL needs a redirect and may lose some link value. Keep paths and slugs the same, and improve the structure in a separate release once the migration is stable.
About the author
Dhaval Agrawal is the founder and CEO of Kraftbase, a product messaging and UI/UX design studio in Vadodara, India, that helps AI and B2B SaaS teams in the US, UAE and India explain and design what they’ve built.
Sources
How to move a site (site move with URL changes), Google Search Central, read Nov 3, 2026
Webflow to Framer SEO migration guide, Framer, read Nov 3, 2026
Webflow to Framer step by step guide, Framer, read Nov 3, 2026
Keep, Redirect, Merge, Remove Sheet: follows Framer’s own labels, adapted by Kraftbase
Migration review
Is your migration plan ready?
Send us your sitemap and we will return a filled inventory sheet.