Slingshot Bio
Roboto converged Slingshot Bio's WordPress and Shopify sites into one headless Shopify build on Next.js and Sanity, instrumented end to end and AI-ready.
View case study
From Craft CMS to Webflow
We are the Craft CMS to Webflow migration experts
Last verified:
The process
How we migrate from Craft CMS to Webflow
- 01
Access and gating audit
First we check the existing Craft CMS and see whether the data is clean enough to move straight over to Webflow, and plan around any auth walls or bot protection in the way.
- 02
Rendering assessment and extraction
Then we work out how Craft CMS renders its pages and pull the content out, even without CMS access.
- 03
AI-assisted sanitization
Everything extracted runs through our sanitization pipeline, which flags slop, normalizes structure, and leaves us clean content to work with.
- 04
Content-model design with the client
Before anything moves, we agree the Webflow content model with you, shaped around how your editors actually work.
- 05
Transform and soft-migrate
We transform the content to the agreed schema and run a full dry run, so mappings and edge cases prove out before production.
- 06
Execute the real migration
Once the dry run is clean, everything moves into Webflow in one controlled cutover.
- 07
Redirect mapping and throttled sitemap submission
Every old URL gets mapped to its new home with the right redirect, so rankings and link equity survive the move.
- 08
Agentic-browser QA
Finally, automated browsers sweep the new site for data issues, design regressions, and missing SEO signals.
- Ready when you are. We'll bring the moving boxes.Start my migration
Challenges with Craft CMS
Key pain points
The elephant in the room is PHP. Craft requires a traditional LAMP-style hosting setup with PHP 8.2+ and MySQL or Postgres, which immediately rules out the serverless and edge-first hosting that modern JavaScript frameworks thrive on. You're managing servers, configuring OPcache, tuning database connections, and dealing with all the operational overhead that comes with self-hosted PHP applications. For teams already working in the JavaScript ecosystem, this is a hard sell.
Major version upgrades are genuinely painful. Craft doesn't support skipping major versions, so migrating from Craft 2 to 5 means stepping through every version in between. Each jump brings breaking changes to Twig templates, PHP requirements, and plugin compatibility. We've seen agencies spend weeks on upgrades that should have been straightforward. The Team tier starts at $279 per project and the Pro tier costs $399, plus $99 annual renewals for both. A free Solo tier exists for single-user projects, but costs still add up for agencies, especially when you factor in plugins and the recent trend toward stricter licence enforcement in the control panel.
The community, while passionate, is relatively small compared to WordPress or even newer headless CMS platforms. When you hit an edge case or need help with a niche plugin, you may find yourself digging through GitHub issues rather than finding a ready answer. And while Craft Cloud exists as a managed hosting option, it's still maturing and doesn't yet match the deployment experience you'd get with platforms like Vercel or Netlify.
PHP hosting requirements
You need a traditional server with PHP 8.2+, MySQL or Postgres, and proper configuration. No serverless, no edge deployment, no modern hosting shortcuts.
Painful major version upgrades
You can't skip major versions, so upgrades mean stepping through each release with breaking Twig, PHP, and plugin changes along the way.
Smaller community and ecosystem
The community is dedicated but small. Finding answers to niche problems often means digging through GitHub issues or waiting on forum responses.
Licence costs add up
The Team tier is $279 per project and Pro is $399, both with $99 annual renewals, plus paid plugins on top. A free Solo tier exists for single-user projects, but costs add up quickly for agencies managing multiple client sites.
Learning curve for non-developers
Craft assumes your team includes developers. Content editors coming from WordPress or simpler tools will need time to adjust to the more structured interface.
Twig templating limitations
Twig is clean but limited compared to modern component frameworks. Complex UI logic gets awkward, and you're locked into whatever Twig version Craft supports.
Benefits of Webflow
Key advantages
We're really trying to think of a good reason to love Webflow, and if you’re building a simple marketing site, a portfolio, or a 10-page brochure site, it works. Designers get pixel-perfect layouts without touching code, the HTML it spits out is clean, hosting is included, and nobody has to panic over plugin updates or random server outages. In that world, Webflow is for you.
One of the Reddit users who likes Webflow states that it has global CDN, SSL handling, and 99.99% uptime without touching a server or updating a single plugin. But to be real, Webflow isn't a platform to build on top of, it's a "one and done" kind of thing. Honestly just go to fiverr and find somebody who's designs don't suck.
But if you are dead set on it, connect with us, and we will try to develop the best solution for you.
Visual design without coding
Designers can build the site they see in their heads without waiting on a dev or translating Figma to HTML. You just drag, drop, animate, and publish. If you can design it, Webflow will render it.
Global CDN infrastructure
Your site gets served fast everywhere, without you configuring servers or worrying about uptime charts. Webflow handles delivery at scale, and pages load like they’ve had three shots of espresso.
Automatic SSL management
You don't need any certificates, renewals, or late-night expiration scares. SSL is handled out of the box, so security stops being a chore and starts being standard.
Clean semantic HTML output
Unlike many no-code builders, Webflow doesn’t produce spaghetti markup. The code it generates is tidy, semantic, and Google-friendly, which is why performance is generally strong.
Built-in SEO optimization
Webflow gives you proper SEO controls with meta titles, descriptions, alt text, structured data, and Open Graph. You don't need plugins or setup. It has native tools that keep your site search-friendly.
Plugin-free architecture
Webflow ships with most essentials built in, so you’re not babysitting 12 plugins just to keep the lights on. Fewer moving parts means fewer things blowing up.
Common questions
Craft CMS to Webflow migration FAQs
Answers to the most common questions about Craft CMS to Webflow migration
The costs add up quicker than most agencies expect. The Solo tier is free for single-user projects, Team is $279 per project, and Pro is $399 per project. Both paid tiers carry a $99 annual renewal fee. If you're running 10 client sites on Pro, that's $3,990 upfront plus $990 per year in renewals before you've paid for a single plugin. Popular plugins like SEOmatic, Blitz (caching), and Navigation run $99-$199 each. Factor in PHP hosting ($20-$100/month per site depending on traffic) and the total per-project cost lands between $500 and $1,500 in year one. It's reasonable for individual projects but the aggregate cost across a portfolio is where agencies feel the squeeze.
Get in touch
Tell us what you're building. We reply within one working day. Jono or someone on the team picks up every message personally.
