Migrate from Webflow

Use an AI agent and the Import from URL recipe to adapt accessible Webflow content to a Typeroll Site. There is no dedicated Webflow account connector.

The agent is your own (Claude Code, Codex or another MCP client); the built-in AI assistant in the portal has no migration tools.

Start with Choose your migration approach: preserve the existing site or renew its design and content. Both paths use standard blocks first, custom block types when needed and rare documented HTML exceptions. Every old public URL must keep working or redirect to relevant content.

Choose your source

Publicly accessible HTML can supply rendered page content. If your Webflow plan provides code export, those files can also serve as input for the agent. Webflow’s code export does not include the CMS and ecommerce databases or all hosted functionality. Collection CSV exports are separate; plan their field mapping explicitly. See Webflow’s code export documentation.

What can move

The agent can extract page text, semantic structure and reachable images. For collection data, define the target Typeroll schema, map exported fields and references, then create Pages with that content type through the Pages tools.

Webflow classes, layout rules and interactions are not a guaranteed editable Typeroll block structure. Rebuild shared headers, footers and page templates in Typeroll. Forms, ecommerce, account features, search and external scripts require separate decisions and testing.

Migration steps

1. Create the target Site, design settings and shared layout. Inventory static static and detail routes to the appropriate Page content types.
2. Provide public URLs or source files to the agent. If using CSV, agree the content type schema and URL mapping before importing records.
3. Import one static page and one collection item as drafts. Transfer media and replace source-specific styling with the target design.
4. Review the result in the editor. Request blocks for sections that clients need to edit; HTML import alone does not create them.
5. Import remaining content, check relationships, rebuild dynamic functions and create redirects for changed paths. Report missing records and media.
6. Save approved content and verify a deployment with your publishing accounts before preparing the production-domain switch.

Import these Webflow pages and the supplied collection CSV into this Typeroll Site.
Propose the content type schema and URL mapping first. Rebuild shared layouts as
Typeroll templates, preserve image alt text, and keep the content as drafts.

Verify forms, filtering, navigation, media paths and metadata independently. A successful content import does not prove the old site’s interactive features have been recreated.

Check it

Work through the migration SEO checklist. Before you move the domain away from Webflow, verify_migration_urls finds no missing addresses on the new deployment and get_migration_launch_report returns launch_ready: true.