All guides

Migration

A Webflow to Astro (or Next.js) Migration Checklist for SaaS Sites

Four phases for migrating a SaaS site from Webflow to a coded stack like Astro or Next.js, from the first MCP audit to the day you finally cancel your Webflow plan.

Overview

This is the checklist I actually run when moving a SaaS site off Webflow and into a coded stack. It splits into four phases: audit and plan, prepare the codebase, pick your stack and rebuild, and test and launch — in that order, because skipping the audit is how redirects and custom scripts quietly go missing.

Phase 1: Audit and plan

Before touching any code, every page, CMS collection, asset, and integration on the existing Webflow site needs a confirmed destination in the new stack. This is also where most of the easy-to-miss items live — redirects and custom code especially.

One shortcut worth knowing: you do not need to manually download every image and icon living on the Webflow site or in its CMS collections. An AI agent can pull those down for you.

  • Audit pages, components, CMS collections, assets, and languages — Webflow’s MCP tooling can speed this up
  • Decide what stays: keep, merge, or remove outdated pages instead of migrating everything by default
  • Export backups — site code, CMS collections as CSVs, and all assets
  • Export 301 redirects from Site settings → Publishing as CSV; MCP cannot reach these on most plans
  • Review custom code, both site-wide and page-level — you would be surprised what lives there
  • Audit third-party tools: cookies, analytics, tracking pixels, embeds, search, and CRM integrations

Phase 2: Prepare the codebase

Webflow exports carry more baggage than they look like they do — unused classes, duplicate styles, and CSS drift accumulate over the life of a project. Cleaning that up before rebuilding saves real time later, and it is a good use of an AI agent’s time to review and flag it.

Interactions and animations need the same pass. Some Webflow-specific functionality has to be rebuilt by hand in the new stack, and it is easy to lose a small one without a checklist in front of you.

  • Clean up the exported code — ask an AI agent to review for unused classes, duplicate styles, and CSS drift
  • Review every interaction and animation so nothing gets lost in the rebuild

Phase 3: Pick your stack and rebuild

Astro and Next.js are the two options worth comparing for most Webflow migrations. For a mostly static marketing or SaaS site, Astro is usually the simpler target — it ships close to zero JavaScript by default. Next.js earns its place once the site needs more app-like behavior, such as authenticated areas or heavy client-side interactivity. Decide the stack before converting page by page, not partway through.

The CMS decision follows the same logic: Astro content collections, Sanity, a git-based CMS, or no CMS at all, depending on who needs to edit content and how often. Whichever you pick, reference and multi-reference fields need the most attention during the content migration — slugs, rich text, and image URLs all need their relationships preserved rather than assumed to carry over.

One more decision belongs in this phase, and it is easy to skip: how agents are allowed to touch content after launch. If a client’s agent edits through the repo, every change lands as a commit. If it goes through the CMS over MCP instead, check that permissions are enforced per tool, and make sure you can hand out a read-only connection. That distinction matters most once it is no longer you running the agent.

  • Pick your stack — Astro for mostly static sites, Next.js for more app-like behavior — and convert pages into the chosen framework
  • Turn repeated elements into components: headers, footers, CTAs, cards, and recurring sections
  • Decide on a CMS — Astro content collections, Sanity, a git-based CMS, or none at all
  • Plan the CMS migration with care for reference/multi-reference fields, slugs, rich text, and image URLs
  • Rebuild forms with validation, spam protection, and CRM integrations, not just a working submit button
  • Reconnect every third-party tool found in the audit — analytics, cookies, tracking pixels, and the rest
  • Preserve SEO: meta tags, canonicals, structured data, sitemap, robots.txt, URLs, redirects, and multilingual settings
  • Pick hosting (Cloudflare, Vercel, Railway, etc.) and set up preview deployments, environment variables, and rollback workflows
  • Decide how agents touch content after launch — repo edits land as commits, CMS edits over MCP need per-tool permissions, and a read-only connection should be an option you can hand out

Phase 4: Test and launch

Nothing ships until the new site has been checked against the old one, not just against itself. And nothing gets canceled until the new site has proven itself live.

  • Compare against the original — an AI agent can check for visual differences, missing content, and broken functionality
  • Test everything before switching DNS: responsive layouts, animations, forms, redirects, CMS content, and integrations
  • Monitor after launch — watch for 404s, check analytics, and confirm everything behaves as expected
  • Do not cancel the Webflow plan until everything on the new site is verified

Questions teams ask before starting

Should I migrate a Webflow site to Astro or Next.js?

For a mostly static marketing or SaaS marketing site, Astro is usually the simpler target — it ships close to zero JavaScript by default and is built content-first. Next.js earns its place once the site needs more app-like behavior, such as authenticated areas or heavy client-side interactivity. Scope the decision against what the site actually needs to do, not just what it looks like today.

Can I keep my Webflow CMS content when migrating to Astro or Sanity?

Yes, but reference fields need the most attention. Multi-reference relationships, slugs, rich text, and image URLs all need to be mapped individually rather than assumed to carry over automatically — that mapping is most of the actual migration work.

Should an AI agent be allowed to edit the site directly after it launches?

It depends on how it connects. An agent editing through the repository turns every change into a commit you can review and roll back. An agent connecting through the CMS over MCP needs its permissions enforced per tool, and you should be able to hand out a read-only connection for anyone who should not be able to publish changes.

Apply this to a real project.

Send the current website, Figma file, or migration plan. I will review the context and suggest the clearest next step.

Start a project