Enterprise Webflow Migration Checklist: From Sign-Off to 90 Days After Launch

Key takeaways

• Plan the migration in six phases: sign-off, baseline, content model and build, SEO and redirects, launch QA, and post-launch monitoring.
• Record a baseline of traffic, rankings, leads and AI answers before anything moves, or you can't prove the migration worked.
• Map every URL to its new home and redirect it with a 301. Google recommends keeping redirects in place for at least a year.
• Test forms, CRM routing, tracking and permissions on staging, and hide the staging site from search engines.
• The checklist doesn't end at launch. Watch the site weekly for the first month and monthly until day 90.

This checklist is for marketing, web and engineering teams moving an enterprise or established B2B site to Webflow. Copy it into your project tool and assign an owner to every line.

If you would rather have a team run it with you, see how Beqi handles Webflow migrations.

What should an enterprise website migration checklist cover?

Six phases, each with a clear owner and a clear point where it counts as done.

Phase 1: Who needs to sign off before the migration starts?

Everyone who can stop the project later: marketing, engineering, security, procurement and whoever owns the current site.

• Name one owner on each side: one lead at your company, one at the partner.
• Agree the scope in writing: which pages, content types, languages and integrations move, and what is retired.
• Start the security review early: share how access, data flows and integrations will work. Webflow's Enterprise plan comes with SOC 2 Type II and a security profile your team can request.
• Set a content freeze date: the point after which changes go into the new site only.
• Agree the launch window: a quiet day and time, with people available to fix issues.

Our guide to what an enterprise Webflow partner needs to handle covers the security and procurement side in more detail.

Phase 2: What do you need to record before you move anything?

A full picture of what exists today and how it performs, so you know what has to survive the move.

• Crawl the current site: every URL with its title, meta description, H1, canonical and status code.
• Export the sitemap: and compare it with the crawl to find orphaned pages.
• Save the search baseline: top pages, queries, clicks and impressions from Google Search Console for the last 12 months.
• Save the conversion baseline: form fills, demo requests and sign-ups per page from your analytics and CRM.
• List pages with backlinks: these are the redirects you can least afford to get wrong.
• Record your AI answers: ask ChatGPT, Perplexity, Gemini, and Claude the questions buyers ask about your company and note what they say.
• Inventory integrations: every form, CRM connection, tag, script and third-party tool, with its owner.

Phase 3: How should the content model and build be planned?

Around how your team will publish after launch, not around how the old site was built.

• Design the CMS first: one collection per content type, with every field the content needs. Webflow can't create collections during an import, so the structure must exist before content comes in.
• Build a component library: reusable sections, so new pages are assembled, not rebuilt.
• Plan the URL structure: CMS items in Webflow always sit under a collection path such as /blog/, so decide those paths before import.
• Set up roles and permissions: who can edit, review and publish, matched to your teams. Webflow's legacy Editor was retired in August 2026, so editors now work through seats and roles.
• Import content in batches: import reference collections such as authors and categories first, since references match on slugs, then review the drafts.
• Build on staging: use the webflow.io staging domain, or branch staging on the Enterprise plan, and keep the old site live until launch.

Our take: Most migration checklists end at launch day. That's the wrong finish line. A migration is the handoff into a site your team has to keep shipping on, so the content model, the components and the permissions matter more than the launch itself. If nobody owns what happens in the first 90 days, the checklist was only half done.

Phase 4: What belongs on the website migration SEO checklist?

Everything search engines and AI tools already know about your site: URLs, redirects, metadata, structured data and crawl access.

• Map every URL: one row per old URL with its new destination, in a single sheet.
• Redirect to the closest match: never send old pages to the homepage in bulk.
• Import redirects as a CSV: Webflow accepts a two-column file under Site settings > Publishing > 301 redirects. An import overwrites existing redirects, so export first.
• Use wildcards for whole folders: and add specific rules before the wildcards that would catch them, because Webflow runs redirects in the order they were added.
• Carry over metadata: titles, descriptions and Open Graph fields for every page, bound to CMS fields in templates.
• Keep structured data accurate: markup must match what is visible on the page.
• Update internal links: point body links and navigation to the new URLs, not through redirects.
• Check crawl access: robots.txt and any firewall rules should allow search engines and AI search crawlers like OAI-SearchBot.
• Hide staging from search: turn off indexing for the staging domain in Site settings, and make sure it is on for production.

For a step-by-step version for one platform, read our guide to migrating from WordPress to Webflow without breaking SEO.

Phase 5: What should you test before launch day?

Every path that produces a lead or a data point, plus the controls your security team approved.

• Forms: every form submits, reaches the right CRM fields, and carries source and campaign data.
• Tracking: analytics, tag manager and conversion events fire on staging.
• Integrations: each one tested end to end with real data, including what happens when it fails.
• Permissions and login: roles work as agreed, and SSO is configured if you use it.
• Performance and accessibility: key templates pass Core Web Vitals and an accessibility check on mobile and desktop.
• A full staging crawl: no broken links, missing titles or pages blocked from indexing.
• A launch plan: DNS steps, who does what, and how to roll back if something critical fails.

From our projects: Axiom Space needed a CMS that could publish missions, astronaut profiles and live launch video without manual work. Beqi moved the site to Webflow in six weeks, and the content team now publishes a new mission in one day. Read the case study.

Phase 6: What should you check after launch?

That every old URL lands on a live page, and that traffic and leads hold against the baseline.

1. Day one: crawl the old URL list. Every URL should return one 301 to a live page.
2. Day one: submit the new sitemap in Google Search Console and Bing Webmaster Tools, and inspect your top pages. Webflow's sitemap now also includes a last-modified date per page.
3. Week one to four: compare clicks, impressions and leads for your protected pages against the baseline every week, and fix any 404s Search Console reports.
4. Month two and three: check monthly, ask the same AI questions you recorded in phase 2, and compare the answers.
5. For at least a year: keep every redirect in place. Google recommends at least one year so the move is seen several times.

What should your team do next?

1. Copy this checklist: into your project tool, one task per line.
2. Assign owners: a name next to every phase, on your side and the partner's.
3. Start with phase 2: the baseline takes the longest and is the easiest to skip.
4. Book the post-launch reviews now: put the week-one, month-one and day-90 checks in the calendar before launch.

If you want a team that has run this checklist on enterprise sites, talk to us about a Webflow migration.

Frequently asked questions

How long should you keep 301 redirects after a migration?

At least a year. Google recommends keeping redirects in place for at least one year so its crawlers see them several times. Pages with backlinks are worth redirecting permanently.

Will our rankings drop after a website migration?

Some movement in the first weeks is normal while search engines recrawl the site. A drop that lasts usually points to a missing redirect, lost metadata or a page blocked from indexing, which the post-launch checks in phase 6 are designed to catch.

When should the content freeze start?

Once the content is imported and reviewed on staging, usually one to two weeks before launch. After that, new content goes into the new site only, so nothing is lost between the two.

Does Webflow have a staging environment for testing a migration?

Yes. Every Webflow site has a webflow.io staging domain, which you should hide from search engines in Site settings. On the Enterprise plan, branch staging lets you publish a branch to its own staging environment for review.

Who should own the migration checklist?

One named lead on your side, usually the marketing or web lead, and one at the partner. Each phase still needs its own owner, since SEO, engineering and security each sign off on different steps.

Can an enterprise site be migrated to Webflow in phases?

Yes, section by section, as long as each stage has its own URL map, redirects and launch checks. A phased move takes more planning, so it makes sense when a single cutover is too risky for the business.