A Webflow to Framer migration should start with a record of what the existing website does. Preserve useful URLs and content, rebuild the required behaviour, test the new site and release it against explicit acceptance checks. This reduces avoidable risk; it cannot guarantee unchanged rankings or traffic.
The easiest mistake is to judge the migration by how closely the new homepage resembles the old one. A visually accurate rebuild can still lose a case study relationship, break a form destination or leave a valuable old URL without a useful replacement.
Is moving to Framer the right decision?
Write down the operational problem first. Perhaps the marketing team cannot make routine changes, campaign pages take too long to launch or the current implementation has become difficult to maintain. Then test whether a different platform would actually solve it.
A move deserves further evaluation when the public marketing site can be separated cleanly from the product application. Pause before committing if the site depends on complex transactions, permissions, unusual content relationships or custom behaviour that nobody has documented.
Do a short feasibility build for the hardest requirement, not the easiest page. If an important workflow cannot be reproduced satisfactorily, resolve that before rebuilding the rest of the site. Switching tools should follow a workable delivery plan.
What transfers, and what needs to be rebuilt?
Framer’s migration guide describes exporting Webflow collections, mapping their fields and rebuilding the site in Framer. A Webflow code export does not recreate its hosted CMS, forms, search or other hosted behaviour in the destination platform.
Treat content, presentation and integrations as separate workstreams. Text and assets may be reusable. Layouts and responsive behaviour need implementation. Forms, analytics and third-party tools need their own configuration and verification.
That distinction belongs in the proposal. “Migrate 50 pages” is not enough detail when some pages are simple articles and others contain forms, filters, translated routes or custom tools.
Build one migration register
Use one row for every meaningful source URL. Include public pages, campaign pages, CMS items and important downloadable files. Combine a crawl with sitemap data, analytics, Search Console and a review of existing redirect rules so the inventory does not depend on one source.
For each row, record:
Old URL and proposed destination.
Decision: keep, change, merge or retire.
Page type and associated CMS collection.
Search or business importance.
Important assets, forms and integrations.
Owner and verification result.
Mark the pages that generate qualified enquiries or receive useful external links. Review them individually. A page with little recent traffic may still be an important sales resource, so traffic alone is not a deletion rule.
Decide URL handling before design approval
Keep a useful existing path when there is no reason to change it. If a URL changes, map it to the closest relevant replacement. If content is genuinely retired without an equivalent, decide how the site should communicate that rather than automatically sending every visitor to the homepage.
Google’s site-move guidance recommends a URL mapping, direct redirects to final destinations and retaining redirects for at least a year in general. It also advises against redirecting many unrelated URLs to one irrelevant destination.
An example migration register might contain these decisions:
/solutions/approvals stays at the same path because the offer is unchanged.
/old-approval-guide redirects to /guides/approval-workflows because the replacement covers the same task.
An expired campaign with no equivalent receives an intentional retirement decision.
A downloadable specification remains available at a documented location, with its referring links checked.
These are illustrative paths. The right destination depends on the actual content.
Test the CMS model with awkward items
Before importing everything, select a long article, an item with several relationships and an item with unusual media. Confirm that formatted text, dates, slugs, references and assets survive the process.
Create referenced records before assigning dependent relationships. Count the source and destination items, but do not stop at matching totals. Two collections can contain the same number of records while some references point to the wrong item.
Ask an intended editor to update a record during testing. They should be able to change its title, replace an image and understand the publishing workflow. A successful migration includes a maintainable editing experience.
Set four launch gates
Content and routing
Every priority URL resolves as planned. Titles, headings, canonical destinations and important body content have been checked. No essential page remains excluded accidentally. Existing internal links lead directly to their intended destinations.
Enquiry handling
Submit a clearly labelled test through every primary enquiry route. Confirm the visitor sees the right success state and the receiving team gets the record. Test booking embeds, file uploads and validation where used. A visible form is not proof that delivery works.
Experience
Review representative templates on mobile and desktop, including long titles and missing optional images. Test keyboard navigation, focus visibility and error recovery. Compare performance under consistent conditions.
Release ownership
Name the person responsible for DNS, the person checking the live site and the person authorised to pause or reverse the release. Keep the previous working configuration available. Define the failure that would trigger a rollback before the launch window begins.
Redirect rules need testing after deployment
Framer supports path redirects through Site Settings and offers wildcard patterns. Its redirect documentation also distinguishes path redirects from redirecting an entire old domain, which needs handling at the old domain’s hosting provider.
A rule entered into an editor is not yet a verified redirect. Test the old production URL after release, inspect the response and follow it to the final page. Check specific exceptions as well as broad patterns. Avoid a catch-all rule swallowing destinations that need individual handling.
Monitor the first month without guessing at the cause
Immediately after release, check core pages, old URLs, forms and tracking. During the following weeks, review indexing, unexpected errors, search landing pages and qualified enquiries.
Compare like with like: the same query groups, equivalent pages and a similar business period. Record campaign changes and seasonal effects. A total-traffic chart cannot tell you whether a decline came from organic search, a stopped advertising campaign or a tracking change.
Investigate sharp changes in important pages promptly. Keep a dated release log so you can connect an issue to a specific change rather than reversing unrelated work.
Common migration questions
Plan the move around the website you actually have
SXDSTUDIO’s Switch to Framer service starts with website and platform review, then scopes the rebuild, content transfer and launch checks. Share your current website so the plan can account for its URLs, content and working integrations.


