Skip to content

Console · Migration Tool

What moves from Webflow

Last updated 18 November 2026

What moves from Webflow

Every feature a Webflow site can use, and whether the tool moves it to Insites. Use it before you start, to know what a site will need after the load. Webflow explains how the tool reads a site, and the plan names each case on your own site.

Moves The new site has it and behaves the same. Partly Some of it moves: the table says which part does not. Not yet The tool does not move it: the table says what to do instead.

Why the design moves whole. The tool reads each published page as a visitor gets it, with its stylesheet, Webflow's own script and every file it loads. So everything Webflow draws in the browser moves without the tool having to know about it: interactions and animations, sliders, tabs, menus, dropdowns and lightboxes. What needs work is what Webflow does on its own servers: the CMS, forms, search, passwords, languages, the shop and redirects.

CMS fields

In WebflowMovesWhat happens
Plain text, rich text, link, video link, email, phone, colorMovesA text column, shown the way Webflow's editor shows it. Links in rich text to the site's own pages are made relative.
Images in rich textMovesCopied to Assets, and the text names the copy.
Components placed inside rich textNot yetWebflow hands them over as its own component markup, which Insites does not draw. Rebuild the block in the rich text after the load.
Image, file and multi-imageMovesEach file is copied into the item, with the image uploader in the admin.
Alt text set on a CMS imagePartlyThe image moves, its alt text does not. A collection page whose images have a different alt text on each item is not rebuilt as data.
Number, date and time, switch, optionMovesA number, date, yes-or-no or dropdown column. Dates print in the site's own time zone, in the format Webflow used.
Reference and multi-referenceMovesPoints at the other collection's table, with a picker in the admin.
User fieldPartlyKept as the Webflow user's id. Webflow keeps no users to copy.
Required, help text and field groupsMovesKept on each field, and the groups become the admin's groups.
Length, minimum, maximum and pattern rulesNot yetOnly Required moves. Set the other rules on the field in the admin.
Drafts and archived itemsMovesCopied and marked, and kept off the site.
Items scheduled to publish laterNot yetThey move as drafts. Fill in the Published address on the day.

Collection pages

In WebflowMovesWhat happens
A collection's template pageMovesAn Insites CMS collection at the same addresses, checked word for word against every item's live page before it is used.
SEO title, description, sharing image and structured data from fieldsMovesRead from the item, as on Webflow.
A referenced item's fields, such as a post's author or categoryMovesRead from the referenced item, so changing the author's name changes it on every post.
A field two references away, such as the author's companyNot yetThe template is not rebuilt as data. You choose what happens to it on Transform.
A template whose item pages the tool cannot line upPartlyWith AI on, AI proposes the template and it is used only when every item still reads the same. Otherwise you choose on Transform: use the proposal, copy each item page as it is, or rebuild it yourself.

Collection lists

Webflow does not say how a list is set up, so the tool works out the order, filter and limit from what the live pages show. A list it cannot work out keeps showing what it showed on the day it was read, and the plan names it.

In WebflowMovesWhat happens
A list on any page, reading its collectionMovesIt reads its table, so items an editor adds show up.
Limit items and Start atMovesKept.
Sort by created, published or updated date, or by one text, number, date, option or switch fieldMovesKept.
Sort by two or more fieldsNot yetThe list keeps what it showed on the day it was read.
Random orderNot yetThe list keeps the order it had on the day it was read.
Filter on a switch or an option, or to one itemMovesKept.
Filter to the items that name the page's own item, such as a category page's postsMovesKept, by reference or multi-reference.
Filter by date against today, such as upcoming eventsNot yetThe list shows the items that matched on the day it was read, and does not move on with the date. Check every events list after the load.
Filter by “is set”, “is not set”, “does not equal”, a number comparison, a fixed category, or two conditions togetherNot yetThe list keeps what it showed on the day it was read.
Pagination, with Next and PreviousMovesKept, with Webflow's own links.
Page count, such as “2 / 5”Not yetIt keeps the text the first page showed.
Empty stateMovesShown when the list has nothing to show.
A list inside another listNot yetThe outer list keeps what it showed on the day it was read.
A list of the page item's own references, such as a post's tagsNot yetThe template is not rebuilt as data. You choose what happens to it on Transform.
A list of a multi-image field, such as a galleryMovesShows the item's images, in order.
Conditional visibility, outside a listPartlyOnly with AI on: AI proposes the rule, and it is used when every item still reads the same.
Conditional visibility inside a listNot yetThe list keeps what it showed on the day it was read.

Images, video and files

In WebflowMovesWhat happens
Responsive image sizes, on page images and CMS imagesMovesEvery size Webflow made is copied, and phones still get the small ones.
Lazy loadingMovesKept as Webflow set it.
Background images and background videoMovesCopied, from the stylesheet and from the page.
YouTube and Vimeo videoMovesStill plays from YouTube or Vimeo.
LightboxMovesIts images are copied, and Webflow's script opens it as before.
Lottie, Rive and Spline files hosted on WebflowPartlyThe file is copied. Not yet tried on a real site: check each animation plays on the new site.
The asset libraryMovesEvery file, in Assets.
Asset folders and asset alt textNot yetEvery file lands in one folder, and Assets does not show Webflow's alt text. Alt text on the page itself moves with the page.

Interactions, components and code

In WebflowMovesWhat happens
Interactions and animationsMovesWebflow's own script moves with the page, so they run as before, on item pages too.
Sliders, tabs, dropdowns and the navbarMovesSame.
ComponentsPartlyEach page looks the same, but carries its own copy. Changing a component later means changing it on every page, or asking a developer to make it a shared part.
Custom code in the site's settings, a page's settings or a code embedMovesKept as it is, such as analytics, a tag manager or a chat widget.
Webflow Analyze and OptimizeNot yetTheir scripts stay on the page and report to Webflow, for a site that is no longer there. Take them out in the code after the load.

Forms

How forms move explains the whole of it, and What the tool does not do with forms lists every limit.

In WebflowMovesWhat happens
Text, email, phone, number, password and text area fields, and hidden fieldsMovesRebuilt in the Insites form builder, and the page keeps its look.
Dropdown, checkbox and radio fieldsPartlyWhat people choose is saved, but the form builder shows the field as a text box with no choices. Set the choices in the form builder if you edit the form there.
File uploadMovesStays on the form and uploads to a private upload column of the form's table. Each past file is copied into it. How.
reCAPTCHAMovesReplaced by hCaptcha.
Success and error messagesMovesShown as before.
Redirect after sending, to a page such as /thank-youMovesKept.
Redirect written as a full address, or to another sitePartlyThe visitor sees the success message instead. Set the redirect in the form builder.
A form that sends to another service, such as Mailchimp or ZapierMovesLeft as it is, still sending there.
Who gets the form emailsPartlyWebflow does not say, so the Forms step asks you.
Past submissionsMovesEvery one, in the form's table, with its file. That includes submissions Webflow still holds for a form that was deleted, replaced by a copy, or is no longer on a page: they load into the table of the form with the same name.
Files people sent with past submissionsPartlyThe submission keeps the link to the file on Webflow. Download any you need before the Webflow plan ends.
Forms from JotForm, HubSpot, Typeform or Google FormsMovesKept as they are, or rebuilt as an Insites form if you choose.

Site settings

In WebflowMovesWhat happens
301 redirectsMovesRead from Webflow on an Enterprise plan. On any other plan found from outside, which cannot prove there are none, so it stays on the To do list until you add the CSV or confirm there are none. Redirects.
Redirect patterns no page address can answer, such as alternativesPartlyEach is named on the Redirects step and the plan, with why.
Page titles, descriptions, sharing tags and the canonical tagMovesKept on every page.
The sitemap, and pages left out of itMovesInsites serves /sitemap.xml, leaving out the same pages.
A sitemap written in Webflow's settingsPartlyReplaced by the one Insites makes. An entry only yours had is not kept.
robots.txtMovesIts rules are kept, pointing at /sitemap.xml.
404 pageMovesThe new site's not-found page. If redirects are set in Settings, the copied page is given the line that hands an unmatched address to them, so redirects answer instead of 404.
Favicon and webclipMovesCopied.
Uploaded fonts, Google Fonts and Adobe FontsMovesUploaded fonts are copied. Google and Adobe Fonts load as before, and the To do list says if an Adobe kit refuses the new address.
Custom domainsMovesThe To do list names each one to point at Insites.
Pages in folders, such as /services/designMovesSame address.
Draft pagesNot yetNot published, so there is nothing to read. Counted in the plan.
Password-protected pagesNot yetOnly the password prompt is public. Each is named in the plan, to rebuild on Insites.
Site searchNot yetThe search page is copied, but shows no results. Ask a developer to point it at the site's site search.

Languages, the shop and members

In WebflowMovesWhat happens
Other languages: their pages and CMS itemsNot yetOnly the main language moves. The plan names each other language left behind. The language switcher and the links between languages still point at pages that did not move: take them out, or rebuild those languages.
Products, categories, orders, cart and checkoutNot yetProducts are counted in the plan. The shop is not copied in this version.
User accounts and gated contentNot yetWebflow switched off its user accounts API on January 29, 2026, so there is nothing to read.