migrating.toBrowse playbooks
← All playbooks
Publishing migration

Webflow → Astro

Rebuild a Webflow site in Astro while preserving design intent, CMS content, assets, URLs, SEO, forms, search, localization, and a recoverable production path.

Typical timeline15–30 business days60–110 hours active work
Statusneeds review
Source testedWebflow code export guidance updated 2025-10-31
Destination testedAstro migration guidance reviewed 2026-07-19
Last reviewed2026-07-19
Sources3
Before you migrate

Should you make this move?

Both platforms have a case. Compare what you gain with what you give up before scheduling the cutover.

Current platform

Webflow

Reasons to stay
  • Visual design, CMS, hosting, and interactions give designers strong production control
  • Editors get a purpose-built publishing workflow instead of raw files
Reasons to leave
  • Pricing, collection limits, and proprietary structure constrain portability
  • Themes, extensions, and content models add maintenance and portability constraints
New platform

Astro

What gets better
  • Content-focused sites ship very little client JavaScript by default
  • Managed deployments reduce infrastructure and release-management work
What gets worse
  • Repository-based publishing and custom integrations require engineering ownership
  • Runtime assumptions, platform services, and pricing models shape the architecture
Best of the move

Astro: Content-focused sites ship very little client JavaScript by default. This removes a major source-side concern: Pricing, collection limits, and proprietary structure constrain portability.

Worst of the move

What you lose: Visual design, CMS, hosting, and interactions give designers strong production control. What you inherit: Repository-based publishing and custom integrations require engineering ownership.

Connected catalog

2 destinations are documented from Webflow. Compare nearby routes before committing.

Also from Webflow
01At a glance

Know the shape of the move.

Transfer outcome10 features audited
Transfer outcome distributionClean transfer: 0, Partial transfer: 3, Manual rebuild: 2, Not transferred: 5.
Clean0
Partial3
Manual2
Lost5
Mapping route8 of 8 fields have a destination path

This timeline assumes

  • A content or marketing site with at most 1,000 routes, 20 CMS collections, and 5 GB of assets.
  • Ecommerce and user accounts require a separate approved replacement.
  • A paid Webflow Workspace can produce the code export.
  • Astro becomes the source of truth after cutover.
  • The destination is tested on a private preview before DNS changes.
02Loss matrix

What survives the move.

“Partial” and “manual” are not footnotes. They are work that must be scheduled and verified.

ItemOutcomeImpactWhat happensMitigation
Static HTML, CSS, JavaScript, and imagespartialhighWebflow exports these files, but they are generated output rather than maintainable Astro components.Use export as visual and behavior reference, then rebuild shared structure.
CMS collection datamanualcriticalCMS content is not included in exported code; collections export separately as CSV.Export every unfiltered collection and map it to typed Astro content.
Collection pages and listslostcriticalExported collection pages have no bound content and lists show empty states.Generate routes and lists from Astro collections.
Forms and submissionslostcriticalExported Webflow forms, uploads, and reCAPTCHA do not process submissions.Export history and implement a tested destination handler.
Site searchlosthighWebflow search does not work on exported sites.Build static or hosted search and test indexed coverage.
LocalizationpartialcriticalOnly primary-locale exported pages are included; localized content requires separate export and routing.Export localized CMS data and define locale routes, alternates, and fallback.
Password protection and user accountslostcriticalProtection and account functionality are not included in code export.Remove sensitive output and choose an explicit authentication replacement.
EcommercelostcriticalProducts can export as data, but checkout, orders, customers, and commerce behavior do not transfer.Run ecommerce as a separate migration with payment reconciliation.
Animations and interactionspartialmediumExported scripts may work, but dependencies and generated markup are brittle.Test every interaction and rebuild critical behavior in maintainable code.
SEO, redirects, and analyticsmanualcriticalMetadata, schema, redirects, domains, consent, and analytics need explicit destination configuration.Crawl both sites and require route, metadata, schema, and tracking parity.
03Field and feature mapping

Where each thing goes.

SourceDestinationMethodNotes
Static pageAstro page or routemanualExtract shared layouts and components.
CMS collectionAstro content collectiontransformDefine a schema before import.
CMS item slugroute slugautomaticPreserve public URLs.
Rich textMarkdown, MDX, or HTML bodytransformSanitize embeds and absolute URLs.
Reference/multi-referencecontent referencetransformResolve stable IDs before rendering.
Asset URLlocal or managed assettransformCopy originals and preserve alt text.
FormAstro endpoint or external formmanualRebuild validation, spam control, storage, and notices.
Redirect and page SEOhost redirects and Astro head datamanualVerify by crawl.
04Before you begin

Make the move recoverable.

Backup procedure

Create the source-of-truth backup

Preserve code, every collection, asset, route, setting, integration, and submission before rebuilding.

  1. Export the complete Webflow code ZIP.
  2. Export every CMS, Ecommerce, User Account, localization, and form dataset separately.
  3. Crawl production for URLs, metadata, schema, assets, forms, search, and status codes.
  4. Capture interactions, breakpoints, custom code, redirects, DNS, analytics, and integrations.
  5. Hash all archives.

Proof to capture: A manifest reconciles routes, collection rows, assets, forms, locales, integrations, and archive hashes.

Transformation · Astro content collections

Typed content model

Convert collection CSVs into validated Astro entries.

  1. Map every field and relation.
  2. Normalize dates, slugs, booleans, and assets.
  3. Fail builds on invalid content.

Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.

Transformation · Crawler and mapping table

Route and asset registry

Prevent SEO and media loss.

  1. Map each source URL to a destination or redirect.
  2. Copy and hash assets.
  3. Check links, canonicals, alternates, and status codes.

Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.

05Handle with care

The things most likely to hurt.

These are operating limits. Treat every “Stop if” condition as a blocked migration, not a suggestion.

Backup

The code export looks complete but omits CMS

criticallikely likelihood

Collection lists render empty in the export.

Consequence
Most public content disappears.
Mitigation
Export and reconcile collections separately.

Stop if: Any live CMS route lacks a content row and destination.

Build

Protected content becomes public

criticalpossible likelihood

Password-protected Webflow pages are present in static output.

Consequence
Sensitive information is exposed.
Mitigation
Classify routes and exclude them until authentication exists.

Stop if: Any restricted content is reachable anonymously.

Cutover

Forms appear functional but drop submissions

criticalpossible likelihood

The UI shows success without durable storage or notification.

Consequence
Leads and requests disappear.
Mitigation
Test the full submission record and alert path.

Stop if: Any production form lacks recoverable evidence.

06Precise timeline

Do the work in this order.

Estimate forUp to 1,000 routes and 20 CMS collections
Total elapsed15–30 business days
Active work60–110 hours
BufferAdd time for ecommerce, user accounts, localization, or complex interactions.
01
Days 1–4Inventory and backup4 days
02
Days 5–8Content and route model4 days
03
Days 9–18Rebuild6–10 days
04
Days 19–24Crawl and rehearse4–6 days
05
Days 25–30Freeze and switch2–6 days
  1. Days 1–4 · inventory

    Inventory and backup

    12–20 hours active4 days elapsedOwner review waiting
    • Export all data and code.
    • Crawl routes and runtime behavior.
    • Approve replacements.

    Depends on: Webflow admin and export plan

    Stop / go checkpoint

    Model?

    Go when: Every route, collection, runtime feature, and restricted area has a disposition.

    Stop when: Critical dynamic behavior is unknown.

  2. Days 5–8 · model

    Content and route model

    12–18 hours active4 days elapsedEditorial review waiting
    • Define Astro schemas, routes, components, assets, and redirects.
    • Transform a representative dataset.

    Depends on: Complete exports

    Stop / go checkpoint

    Build?

    Go when: Representative content and relations validate.

    Stop when: Any critical URL or field is unmapped.

  3. Days 9–18 · build

    Rebuild

    25–45 hours active6–10 days elapsedCode and visual review waiting
    • Build templates and components.
    • Import content and assets.
    • Replace forms, search, localization, and integrations.

    Depends on: Approved model

    Stop / go checkpoint

    Preview?

    Go when: Build, content, runtime, and access tests pass.

    Stop when: A critical feature lacks a tested replacement.

  4. Days 19–24 · rehearse

    Crawl and rehearse

    8–16 hours active4–6 days elapsedStakeholder review waiting
    • Compare crawls and screenshots.
    • Test forms, search, analytics, performance, and rollback.

    Depends on: Complete preview

    Stop / go checkpoint

    Cut over?

    Go when: Blocking parity and owner checks pass.

    Stop when: URLs, SEO, access, or submissions differ critically.

  5. Days 25–30 · cutover

    Freeze and switch

    3–11 hours active2–6 days elapsedDNS and observation waiting
    • Freeze Webflow edits.
    • Import final content delta.
    • Switch DNS and monitor.

    Depends on: Passed rehearsal

    Stop / go checkpoint

    Close rollback?

    Go when: Production crawl and runtime checks pass for seven days.

    Stop when: Critical traffic, forms, or content regress.

07The point of change

Cut over with a way back.

Go live

Cutover

Make the verified Astro build authoritative without losing final Webflow edits.

Recommended window: A low-traffic morning with DNS and content owners available.

  1. Freeze Webflow publishing.
  2. Export and apply the final CMS delta.
  3. Build and crawl the release.
  4. Switch DNS or routing.
  5. Test critical routes, forms, search, analytics, and access.
  6. Keep Webflow intact.

Proof to capture: Production crawl matches the approved route registry and every blocking runtime check passes.

Return to safety

Rollback

Restore Webflow while preserving changes made after cutover.

Deadline: Within seven days and before the Webflow plan or project changes.

  1. Freeze Astro content changes.
  2. Restore previous DNS or routing.
  3. Apply reviewed post-cutover content changes to Webflow.
  4. Re-enable Webflow forms and integrations.
  5. Test critical routes.

Proof to capture: Webflow again serves the canonical domain with current content and working runtime features.

Rollback immediately when
  • Missing critical routes or content
  • Protected content exposure
  • Form or search failure
  • SEO status/canonical regression
  • Unrecoverable runtime dependency
08Verification report

Prove the migration worked.

Every blocking check must pass. Capture the evidence before cleanup begins.

0%
Interactive report preview0 / 8 checks passed
PassIDCheckMethodExpected resultEvidence
V-01BlockingURL dispositionCrawl every source URL.One 200 destination or one-hop permanent redirect.Crawl diff.
V-02BlockingCollection reconciliationCompare rows and representative fields.All in-scope items map.Content manifest.
V-03BlockingBinary coverageCompare URLs, sizes, and hashes.No missing critical asset.Asset report.
V-04BlockingMetadata and schemaCompare titles, descriptions, canonicals, robots, alternates, and JSON-LD.Approved parity.SEO crawl.
V-05BlockingSubmission lifecycleSubmit every form and upload path.Validation, storage, notice, and alert pass.Submission IDs.
V-06BlockingIndex coverageRun known-result and no-result queries.Required content is discoverable.Search matrix.
V-07BlockingRestricted routesTest anonymous and authorized access.No restricted content leaks.Access log.
V-08Responsive parityCompare key templates at approved breakpoints.Meaning and interactions match acceptance.Screenshot set.
09Post-migration cleanup

Remove the scaffolding safely.

Safe after: Seven stable production days, passed crawls, and owner sign-off.

  1. Archive Webflow exports and verification evidence.
  2. Revoke temporary tokens and integrations.
  3. Remove obsolete Webflow scripts and forms.
  4. Keep Webflow intact through the retention window.
  5. Cancel plans only after billing and recovery review.
  6. Schedule quarterly link, form, backup, and content validation.
Sources and maintenance

Built to be reviewed.

Tested 2026-07-19. Next scheduled review: 2026-10-19.

  1. Webflow: export site codeAccessed 2026-07-19
  2. Webflow: CMS CSV import and exportAccessed 2026-07-19
  3. Astro: migrate an existing projectAccessed 2026-07-19