1. Audit the current website
Start with a crawl of every public URL and an inventory of pages, posts, images, downloads, forms, integrations and tracking. Identify the pages that bring search traffic or enquiries. Record current titles, descriptions, canonical URLs and internal links so nothing important is lost in the redesign.
The source platform changes the export process. A WordPress to Webflow migration may involve posts, categories, custom fields and plugin features. A Wix to Webflow or Squarespace to Webflow project may require more manual review of page blocks and widgets.
2. Design the Webflow CMS before the pages
List the content types editors will maintain: articles, authors, services, projects, team members, locations and testimonials. Define their fields and relationships. Build a small sample collection and page before importing everything. If editors cannot perform common updates easily, revise the model now rather than after launch.
Webflow’s CMS import guidance describes the CSV import workflow. It is useful for structured content, but imports still need checks for images, rich text, references and formatting.
3. Rebuild responsive components
Create a small design system: type scales, spacing, buttons, cards, navigation and forms. Reuse components across pages so changes stay consistent. Check tablet and mobile states, not only the desktop mockup. Accessibility basics such as heading order, focus states, labels and readable contrast belong in the build.
If you already have approved designs, Figma to Webflow development is a production build rather than a platform migration. For an existing coded site, an HTML to Webflow project also needs a new editing model; copying markup alone does not create useful CMS templates.
4. Map URLs and preserve search signals
Keep existing paths where possible. For changed paths, map each old URL to the closest relevant new URL and create a permanent redirect. Preserve useful content, titles, descriptions and image context. Update internal links so they point directly to new destinations.
Google’s site move guide recommends testing redirects, updating links and submitting a new sitemap. Webflow’s 301 redirect documentation explains its redirect controls. Build a redirect sheet before launch, then test it against a fresh crawl.
5. Test conversion paths and publish
Test every lead form, booking link, download, email notification and analytics event. Check the actual published domain on desktop and mobile, including CMS templates and less visited pages. Confirm the staging domain is not indexed and the production site can be crawled.
Publish at a quieter time for the business, but keep the team available to fix issues. Review redirected URLs, form delivery, checkout or integrations immediately. Submit the sitemap and monitor Search Console over the following weeks. Some ranking movement is normal while search engines process changed URLs.
Common Webflow migration mistakes
The most expensive mistake is moving pages before deciding how editors will maintain them. If every article is built as a static page, publishing becomes slow and inconsistent. Build and test the CMS model with a small sample before importing the whole library.
The second is redirecting all old URLs to the homepage. That frustrates visitors and gives search engines a weak replacement signal. Map each valuable page to a relevant new page, and allow genuinely removed content to return an appropriate 404 or 410 when there is no good substitute.
The third is treating the homepage as the whole QA plan. CMS templates, pagination, category pages, forms, downloadable files and less visited service pages should all be sampled. A post-launch crawl catches mistakes that a visual review often misses.
6. Choose a scope that fits the site
A faithful rebuild, a rebuild with motion and a full redesign require different budgets. Count distinct page templates, CMS items, integrations and forms rather than relying on visible page count alone. A ten-page site with a complex blog can be more involved than a thirty-page brochure site.
Our Webflow migration service outlines starting packages for standard marketing pages. We confirm a fixed scope after the audit because commerce, memberships and custom logic change the work substantially. If you are still choosing a platform, read the website migration path guide first.
Explore a specific route
Have an existing site and a destination in mind? Start a project → and we’ll review the migration scope.
