How to migrate from Webflow, and which sites should stay put
Webflow gives designers fine control over layout and interactions, and some teams find they're paying for more control than they use. To migrate from Webflow to something simpler, know what you give up: there's no import, Anticode's design engine lays pages out in one of seven design systems rather than reproducing your canvas, and scroll-driven interactions don't come across. For a straightforward business site that's often a fair exchange.
Should you move at all?
Answer these honestly before rebuilding anything.
| If your site… | Then |
|---|---|
| Depends on custom scroll or hover interactions, animation files or a bespoke grid | Stay on Webflow; those don't carry over |
| Sells products with stock tracking and shipping | Stay, or move the shop to a dedicated platform; Anticode has buy buttons with payment links only |
| Has member logins or gated content | Stay; published Anticode sites have no visitor accounts |
| Is several pages of services, a team list, a blog and a contact form | A good candidate |
| Is edited weekly by someone who finds the Designer daunting | A good candidate |
Inventory the Webflow project
- Static pages: list each with its address and whether it gets visits or inbound links.
- CMS collections: list each collection, its fields and its item count. If your plan lets you export items, export them; otherwise you'll copy from the live pages.
- Forms: note each form's fields and where submissions go.
- Assets: download the images you own and any fonts you've licensed (you'll be choosing a design system's own type family on the other side, so note the look you're after).
- Integrations: anything embedded, any scripts in custom code, any analytics.
Rebuild
- Pick the closest design system. Anticode has seven: Editorial, Technical, Luxury, Playful, Brutalist, Organic and Swiss, each with one type family, one action colour and radius by role. Choose the one nearest your current brand and the action colour nearest your main button. Accept that it will look related, not identical.
- Start from the live Webflow address. Describe the business and paste the link. The Architect reads it once, summarises it into the brief, asks up to three questions and shows a plan.
- Recreate each CMS collection. In the Anticode dashboard a collection has typed fields: text, rich text, number, date, image and reference. Map your Webflow fields to these. Each entry is served at
/<collection>/<slug>, so keep the same slugs where you can. - Add the items. There's no CSV or Webflow import, so enter them in the dashboard. For a large collection, decide which items are worth carrying over.
- Rebuild forms. Built-in forms have fixed fields: contact (name, email, message), booking (service, day, time, name, phone, email) and newsletter (email). A form with other fields becomes a custom form tied to a site function, up to 30 plain-text fields. Point submissions at email or a connector.
- Adjust layout in the layout editor: drag elements within a section, resize against the column grid.
- Run the release checklist before anyone else sees it.
Cut over
Publish to the anticode.dev address and have someone who knows the old site click through every page. On a paid plan, add your domain in Anticode, then change the DNS record at whoever hosts it (if Webflow told you to point records at it, those are the ones to replace). Wait for HTTPS on the new site, send a test enquiry, then end the Webflow site plan. Anticode doesn't redirect old addresses, so where a URL had to change, update the links you control and accept that some old links will land on a not-found page.
What you gain and lose
You gain pages with no scripts to slow them down, a security check before every publish, an editor most people can use, and change requests in plain words. You lose pixel-level layout control, custom code embeds, interactions, and any Webflow app integrations. For a team that mostly edits copy and adds CMS items, that's often worth it; for a design studio whose site is its portfolio of motion, it usually isn't.
Limits
No Webflow or CSV import, no custom code or embeds, no interactions beyond the design systems' own motion, no e-commerce inventory, no member areas, no redirects. For side-by-side detail see Anticode vs Webflow and Webflow alternatives; for the collection side, CMS collections.
Questions people ask
Can I import my Webflow CMS?
No. Recreate each collection's fields in the dashboard and add the items there.
Will my Webflow interactions work?
No. Published pages run no scripts, and layout comes from Anticode's design systems. Expect a calmer page.
Can I keep my URLs?
Collection items can keep their slugs under the collection's path. Where an address has to change, Anticode won't redirect the old one.
How long does it take to migrate from Webflow?
For a site of ten pages and a small blog, a few days of work, most of it on collection items and checking copy.