Webflow gave you design without compromise. Editing and limits are another story.
The designer loves it, the team is afraid to touch it. I move pages, CMS collections and Google rankings to a custom website with an editor built for you, not for a designer.
Where it starts to cost. Not on day one, but as the business grows.
- Cost
A plan per site, limits per plan
Webflow is paid per site, and every plan caps the number of CMS items. When the blog or catalogue grows, the answer is a higher plan, not a better site.
- Editing
A tool for designers, not for your team
The Designer is powerful and therefore complex. Client-side editing is simpler, but any change outside the preset fields sends you back to the designer.
- Dependence
A code export without what makes the site work
Static pages can be exported as code, but CMS content, forms and anything else that relies on the platform doesn't work outside Webflow. In practice, ownership is rent.
What moves and what you don't lose on the way.
- Content
CMS collections and the references between them
I take collections, items and their references through the Webflow API or CSV export, and rewrite pages and interactions in code. Links between items (a post's author, a project's category) stay links, not copied text.
- URLs
Every old URL leads to a new one
Page and CMS item URLs get 301 redirects wherever they change, with meta titles, descriptions and Open Graph images. Your Google rankings stay.
- Switchover
The old site runs until the new one is ready
I build the new site alongside, on a preview address. Once you approve it, only the DNS records change. You cancel your Webflow plan once everything is checked.
Send me your website. You'll get advice and two time slots.
Enter your address and a few details. An email with advice for your platform and two open slots for a call arrives straight away, and I'll look at your site personally and get back to you.
- Advice for your platform you can act on right now, without me
- An idea of what a website could do in your line of business
- Two open slots for a 30-minute call, one click to book
Frequently asked questions
Yes. Webflow sites are often carefully designed and there's no reason to throw that away. The design moves over as it is, and interactions and animations are rewritten in code, so they behave the same.
You or your team, without a designer. The editor has only the fields your pages and collections have, and nothing can be moved by accident.
Forms become part of the site and send data where it needs to go, to email, a CRM or a spreadsheet, with no middleman. Integrations that now run through outside automation tools can often be connected directly.
Not if the migration is done properly. Every old URL gets a 301 redirect, meta titles and descriptions move with it, and after the switch I watch Search Console until the index settles. A drop in traffic after a migration is a sign nobody did that work, not a consequence of the migration.
It depends on the scope and on whether a redesign comes with it. Roughly the same as a build: a website 3–6 weeks, a web shop 6–12 weeks. The exact timeline is in the proposal, before work starts.
No. You cancel the old platform only once the new site is live and we've checked that content, redirects and, for a shop, orders are all in place. Until then the old site runs as it always has.
Because migrating a five-page website and a shop with thousands of products are not the same job. After a call and a look at your site you get a fixed proposal, and that figure holds until the end of the project.
The site comes with maintenance: updates, security monitoring, daily backups and uptime monitoring. Alongside it comes SEO + AEO, so after the move the site doesn't stand still but gets found by search engines and AI models.