This is a common question;
I'm maintaining a large Webflow project that is now outdates. It's been iterated on for a couple of years, and the class structure has become inconsistent over time. I also want to completely restyle it.
I'm trying to decide between two approaches:
- Gradually refactor and standardize the existing setup
- Start over and rebuild the site from a blank project, possibly using a different system like Lumos
Why "migrate" is the best answer
Even 1 year ago, this was a real decision- but today we have Claude and the Webflow MCP, and that changes everything.
If you're at all familiar with Webflow's MCP and how to setup skill files, you could easily configure an AI workflow to fully migrate your existing content 100%, but using a new framework, class naming conventions, variables, and/or even do full restyling.
If you've never fully embraced components, you can do that now too- components, props, variants and binding all through the MCP.
The main advantage of migrating is you can make major changes if you want to, and then see how you like the result before you commit.
The biggest decision is whether to clone the site and refactor the clone, or to start with a blank page and do a full rebuild. Depends on the extent of the changes I think, e.g. if you're going to a full variable + component-base architecture, I'd probably want a clean destination.
And currently, Jun 2026, the MCP team is adding new features every week.
Approach
Think of your build workflow as 4 parts-
- you, the artist, driving the choices
- the Agent which is a power tool to build faster
- the MCP, which is a toolbox. this is pretty much a box of drillbits that enable your power tool. Webflow has drillbits for most of the things you'd want to build, and is adding more every week
- the site, your project
Make sure the setup is solid first, then work on your prompting skills, that space between 1 and 2. As your processes and techniques develop, encode them in skill files, which strengthens the connection/efficiency between 2 and 3.
Use a good model for 2- Opus is good, I also get a lot out of Sonnet.
Examples
Most of the work I'm doing in this space is professional client site migration work. Give me a shout if you need help with a migration project.
Meanwhile, I'll endeavor to do a few that I can share publicly to demonstrate some of the cool capabilities I'm seeing with AI workflows that involve Webflow's MCP.
Plezy ( Experimental )
Migration from HTML to Webflow.
I migrated most of the Plezy site for fun to test out some of my pipelines and skill setups.
Here's my first proto build. All of this was done through the MCP, except for one single Lottie element I added manually.
The two parts I focused on completing are at the bottom- the reviews section and FAQs, since I migrate a lot of these.
Reviews has a nice smoothscroll and pause-on-hover effect. FAQs is an accordion, but the interesting thing is that the toggle is a Lottie. I wanted to have full animation control there- it plays frames 0 .. n on open, n .. 0 on close. It's using the Webflow Lottie element, in SVG render mode so the coloring is handled by Webflow vars. Also, the Lottie itself was created by Claude based on the original toggle art.
The point is, not only is Claude + Webflow MCP a wildly powerful setup- but the manual parts of migrating a site are getting vanishingly small.
