Migration insights / September 30, 2026

Webflow Migration Guide: Content, CMS, Redirects and Launch

Moving to Webflow is more than recreating the homepage. A reliable migration connects the content model, responsive design, URL plan and launch testing into one project. Use this guide to scope each part before you start.

Agency team planning a website migration

Is Webflow the right migration destination?

For a service website with reusable pages and a manageable CMS, Webflow may be a good fit. Before committing, list every form, integration, editor workflow and URL that must survive. If the site depends on complex memberships or commerce, confirm a workable replacement first. Compare scope and starting options on our Webflow migration service page.

What should you ask a migration partner?

Ask who exports content, maps old URLs, tests redirects and forms, and owns the launch checklist. Webflow explains CMS CSV imports; Google’s site move guidance covers redirect and sitemap checks. Neither guarantees retained rankings. If you are moving from WordPress, review the WordPress-specific route before requesting a quote.

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.

Designer reviewing reusable website components and content fields
Designer reviewing reusable website components and content fields

WordPress to Webflow: prove the content transfer first

WordPress normally exports content as XML, while Webflow imports CMS content through CSV. Convert and clean a sample before committing to the full move. Map the original post URL, title, body, image, author, categories and any required custom fields to the proposed Collection fields. Webflow’s WordPress migration instructions explain this workflow and recommend checking the destination plan’s Collection item limits.

Use an illustrative test post such as /2024/06/kitchen-renovation/ and record its proposed destination, for example /blog/kitchen-renovation. Check the formatted body, image access, author and category relationships on the published test page. If the old path cannot be retained, add its exact replacement to the redirect map. These are planning examples, not client URLs or proof of retained traffic.

Content transfer does not bring across a WordPress theme, plugin logic or an editorial approval workflow. List must-have behavior and test replacements before signing off. If essential publishing, membership or transaction workflows cannot be reproduced within budget, improve the current WordPress site instead. Review the WordPress to Webflow migration scope and cost factors for the delivery decisions to resolve before a quote.

Illustrative planning example

An inspectable WordPress migration sample

Use this fictional six-URL example to review the deliverables with your migration partner. The paths and counts are invented for planning; they contain no client data or measured project results. Actual scope follows your site's inventory and required workflows.

1. Account for every old URL

This example retains one URL, moves three, merges one and removes one. The client approves content changes and retirement decisions before the redirect file is prepared.

Six source URLs, four destinations and one approved removal
Old pathDecisionDestinationExpected responseResponsible owner
/services/remodelingRetain/services/remodeling200Choquer checks the page and links.
/2024/06/kitchen-renovation/Move/blog/kitchen-renovation301 to 200Choquer maps and tests the post.
/2024/08/bathroom-remodel/Move/blog/bathroom-remodel301 to 200Choquer maps and tests the post.
/2023/10/kitchen-budget/Merge/blog/kitchen-renovation301 to 200Client approves the combined content; Choquer maps it.
/downloads/planning-checklist.pdfMove/documents/planning-checklist.pdf301 to 200Client supplies the current file; Choquer tests it.
/spring-offer-2021/RemoveNo relevant replacement404Client approves retirement; Choquer checks the response.

The removed offer has no useful equivalent, so a 404 is intentional. Changed paths go directly to the agreed destination. After the move, internal links point to the final paths.

2. Map and reconcile a small CMS import
Fields to verify in a two-post pilot
WordPress sourceWebflow destinationAcceptance check
Post title and approved pathPosts: Name and SlugBoth posts have the approved title and unique slug.
Formatted post bodyPosts: Rich textHeadings, lists, links and merged content are checked on the published preview.
Featured image and image descriptionPosts: Image and alt-text fieldBoth images load, and the template uses the approved alt text.
Author and categoriesAuthors and Categories, linked from PostsCreate one author and two categories first; confirm the post references.
SEO title and descriptionPosts: text fields used by template SEO settingsInspect the rendered title and description on both post pages.

In this sample, three source posts become two approved Posts records because the kitchen-budget content is merged into the kitchen-renovation post. The pilot also has one Author and two Categories: five expected CMS items across three Collections. Reconcile each Collection separately and investigate missing, duplicate or rejected rows before the full import.

Open both published preview posts and check the entire body, image, author, category links and metadata. A matching item count alone cannot verify the content. Keep the source export and a record of the approved merge.

Webflow's WordPress migration guidance covers XML-to-CSV preparation and recommends checking Collection item capacity.

3. Agree the launch checks and recovery owner
  • URL checks: test all six old paths. Four must permanently redirect to a working destination, one stays 200 and the retired offer returns 404. Resolve loops, chains and unexpected destinations before launch.
  • Page checks: inspect the retained service page and both post pages for approved content, a self-referencing production canonical, crawl access and direct internal links. Open the PDF and check that it is the approved file.
  • Enquiry checks: agree a safe test of the service-page form, validation, delivery and recovery on desktop and mobile. Confirm tracking without counting staff tests as leads.
  • Content freeze: the client approves the final content snapshot. Choquer reconciles the agreed export, CMS counts and redirect sheet against it.
  • Go or hold: name the launch decision-maker, DNS administrator and recovery owner in the proposal. A missing record, broken required form or wrong destination keeps launch on hold until resolved.
  • After launch: the named owner checks the live domain against the same sheet and records exceptions. Agree the monitoring window, editor handover and recovery steps before changing DNS.

Back up existing redirect rules before adding new mappings. Webflow's redirect CSV guidance states that an import replaces existing rules, so combine and review the full file before publishing. Google's site-move guidance explains mapping, redirects and monitoring; search visibility can fluctuate during recrawling.

Set the boundaries in the proposal

Choquer prepares the agreed inventory, field map, redirect sheet and test record. Your team supplies access and approved content, confirms essential workflows and signs off on merge or removal decisions. The proposal names the launch and post-launch owners.

Plugin rebuilds, memberships, commerce, custom integrations, content cleanup and third-party subscriptions need explicit scope and costs. The pilot determines whether Webflow can support the required workflow within budget; improving the existing WordPress site remains an option.

Review the WordPress migration service and starting packages, then bring your current URL and the workflows the proposal must cover.

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.

Before a bulk redirect import, export the existing rules and merge them with the new mapping: Webflow’s redirect CSV documentation says a new import replaces all existing redirect rules. Keep a backup, validate the combined file, publish and test representative old URLs to their final destinations. Do not assume a successful import has preserved earlier rules.

Responsive website checked on desktop tablet and phone before launch
Responsive website checked on desktop tablet and phone before launch

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.

A useful next step

Let’s look at your website together.

Book a complimentary website audit call with Bryce. We’ll review your current site, the migration risks and the next step that makes sense for your business.

Bryce Choquer, founder of Choquer AgencyBRYCE CHOQUER / FOUNDER