Loading...
Loading...
Webflow → Sanity port
Move your Webflow site to a simpler Sanity CMS on Vercel, without a redesign. Your marketing or operations lead can then publish routine updates without waiting for a developer.
Indicative budget: €4,000–€6,000 + VAT for a straightforward port. I inventory your current site first, then send the expected effort, risks and decision points in writing. You approve the range before work starts. It is not a fixed quote.
Three routes
The smallest change that removes the publishing block is the right one. I will tell you which one I think it is after I look at your site.
Your Webflow build is untidy, but Webflow is not the real problem. Clean up the pages and the blog template, and stay where you are.
Ask for a range.
Your design is fine and your team is blocked on publishing. Move the site as it looks today onto Sanity and Vercel, with the fields your team actually edits.
€4,000–€6,000 + VAT, indicative.
You need new pages, a block system, permissions and a publishing process, not a copy of what you have. This is a project, not a move.
Ask for a range.
Who does the work
Scope
The process
Every effort figure below is indicative. The written estimate comes after step 2, and you approve it before step 3 starts.
You and I agree the pages in scope, the changes out of scope, who decides, and what AI may do.
Output: A written scope and a set of control rules.
I list the pages, components, forms, integrations, redirects and known defects. You mark what the business cannot lose.
Output: A migration map, an issue list and my route recommendation.
I set up the CMS structure, the reusable sections, the permissions, a staging site and a backup. You supply the access.
Output: A working system, ready for your content.
I move the approved content and fix the agreed structural problems. I do not rewrite your copy or redesign your pages.
Output: A complete staging site with a visible change log.
I test the layouts, forms, links, metadata and redirects. You review staging and send one consolidated list.
Output: An acceptance checklist and acceptance fixes against the agreed migration map.
I record the rollback point, launch, check production, and show you how to edit, approve and restore a previous version.
Output: A live site, an editor guide and a rollback point.
If you want AI in it
The CMS works with AI switched off, and most teams start that way. If you include it, these controls become acceptance requirements in the written scope.
Safeguards
A migration puts your search results, your forms and your launch at risk. Here is what holds each one down.
Questions
Stay if a clean-up fixes your publishing problem. Move only if the tool itself blocks the work. I will tell you which one I think it is after the inventory, and a repair is a valid answer.
Sanity is my default because I know it well and it separates content from design cleanly. Contentful and Storyblok do a similar job. I pick against your workflow, not against a vendor list.
Page copy, images, blog and news posts, navigation, SEO fields, and the approved page sections. We agree the exact list in step 1, and it is in the written scope.
A new content type and its block, a change to how a block looks, a login area, or a new integration. Those are hourly jobs after launch. I do not recommend a monthly retainer for a site that changes a few times a month.
No. The CMS works with AI switched off. If you do use it, it prepares changes and you approve them. It never publishes on its own.
Not in a port. The point of a port is that the design does not change. If you want a redesign or a rebrand, that is separate work and I can run it or bring in designers.
It is the main risk, so it gets the most attention. I inventory the URLs, metadata and redirects before the move, test them on staging, and monitor search performance after launch. I cannot guarantee rankings. The scope controls the migration risk; it does not promise a search result.
You own the site, the code and the accounts. You get a 30-day warranty on defects. After that, changes are hourly, or you self-serve on the repo. There is no lock-in and no subscription to me.
Paste your Webflow address and tell me who edits the site today. I will come back with what I see, which of the three routes fits, and what it would take.
Send me your Webflow URL