.png)
Key takeaways
1. A Webflow migration and a Webflow redesign are different scopes with different price points - getting clear on which one you need before scoping saves a lot of back-and-forth.
2. Page count is rarely the biggest cost driver - redirect volume, integration complexity, and review cycles tend to move the budget more than raw page numbers.
3. A scoping call with the right questions - site crawl, CMS audit, integration inventory - should produce a reliable ballpark.
A Webflow migration for a B2B SaaS site typically costs between €6,000 and €50,000, depending on site size, CMS complexity, and how many integrations need to be rebuilt. Smaller sites - under 20 pages with minimal integrations - sit at the lower end. Enterprise sites with 200+ pages, HubSpot or Salesforce integrations, and years of accumulated URL debt are at the higher end. Here is what drives the difference.
How much does a Webflow migration cost?
Budget questions come up early in almost every migration conversation, and they should. A migration touches a lot of moving parts - redirects, CMS structure, integrations, metadata - and the cost varies more than people expect depending on what's actually under the hood of the existing site.
The ranges below come from migrations we've scoped and run. They're not meant to be exact quotes - every site is different - but they should give you a solid sense of where your project is likely to land and what tends to push costs in either direction.
What does a Webflow migration actually include - and what affects the cost?
One thing worth clarifying before getting into numbers: a migration and a redesign are not the same project. They get conflated a lot, and sorting out which one you actually need up front saves a fair amount of confusion.
A migration is a platform move. The design, information architecture, and content stay largely the same - what changes is the underlying platform and the technical infrastructure around it. The scope typically covers:
- Content migration - moving pages, blog posts, and CMS items from the source platform into Webflow's CMS structure
- URL mapping and redirects - crawling the live site, exporting every URL, mapping old to new, and getting 301s in place before launch
- CMS structure rebuild - recreating your collections, fields, and templates in Webflow to match the source platform's content model
- Metadata transfer - exporting title tags, meta descriptions, and Open Graph data from the source CMS and mapping them into Webflow
- Integration reconnection - rebuilding connections to HubSpot, Salesforce, Intercom, analytics, and any other tools wired into the current site
- QA and launch - cross-browser and device testing, redirect verification, pre-launch checklist, DNS transfer, and post-launch monitoring
A redesign adds a layer on top of all that: new design system, new information architecture, new visual direction, often new copy. Bigger scope, longer timeline, higher cost.
Quick way to tell them apart: if the brief is "move our site to Webflow," that's a migration. If the brief is "rebuild our site in Webflow," that's a redesign. They share some work, but they're different projects. Everything below covers migration pricing only.
How much does a Webflow migration cost by site size?
The table below reflects ranges from migrations we've scoped and run. These are migration-only figures - they don't include redesign work, new copywriting, or post-launch support beyond the standard snag period.
These ranges cover migration only. If the project includes a redesign - new design system, new IA, new copy - add 40 to 80% depending on scope.
What drives migration cost up?
Page count is the number most people focus on when budgeting a migration. It matters, but it's rarely the biggest variable. Here are the things that more consistently push costs higher.
Integration complexity
There's a big difference between a HubSpot form embed and a full HubSpot integration. A basic form connection takes a few hours. A full integration with custom field mapping, workflow triggers, CRM property syncing, and marketing attribution tracking can add 20 to 40 hours to a project.
The same logic applies to Salesforce, Intercom, Segment, and any other tool that's deeply wired into the current site. Before scoping, we ask for a full list of every connected tool - including the ones added quietly by a previous developer and never properly documented. Those tend to be the ones that surface mid-build otherwise.
Redirect volume and URL debt
Sites that have been running for several years accumulate URL debt: old campaign landing pages, renamed blog posts, legacy product pages that redirected to other redirects. These all need to be mapped before the migration starts.
On a mid-size migration, a thorough pre-launch crawl typically surfaces two to three times more URLs than the sitemap contains. Each one needs a destination. For sites with large redirect maps, that mapping, verification, and implementation work is one of the biggest time inputs on the project.
CMS structure complexity
Webflow CMS is flexible, but the structure needs to be designed before content is migrated into it. A site with a single blog collection is quick to set up. A site with five or six collections - case studies, team members, integrations, glossary terms, events - each with their own field structures and cross-reference relationships, takes significantly longer to architect.
CMS complexity also affects template count. More content types means more collection templates, more field bindings, more QA combinations to verify.
Custom code from the source platform
Most sites have some custom JavaScript - a pricing calculator, a custom filter, a specific animation. Some of it ports directly into Webflow. Some of it needs to be rewritten. And occasionally something that looked like a small custom component turns out to be load-bearing infrastructure that takes a week to rebuild properly.
We flag custom code as a risk item in every scoping conversation, because it's the variable most likely to expand once someone actually looks at what's in the source site.
Review cycles
Projects with a single decision-maker and a 48-hour review turnaround run on schedule and on budget. Projects where feedback takes longer or goes through multiple rounds run longer - and when timelines extend, costs follow.
Getting clear on the review process at kickoff - who approves, by when, what counts as done - is one of the most practical things you can do to keep a migration predictable.
What is not included in a standard migration price?
A few things that come up regularly as questions, so worth listing clearly:
- New copywriting. We migrate existing copy as-is. If pages need to be rewritten, that's a separate workstream.
- New illustrations. If the current site's visuals are being replaced, that work is scoped separately.
- SEO strategy. We preserve your existing SEO - redirects, metadata, URL structure - as part of the migration. A new keyword strategy, content audit, or link-building work is outside migration scope.
- Post-launch support beyond the hypercare period. Migrations include a hypercare period (typically 2 weeks) for fixing anything that surfaces after launch. Ongoing support after that runs on a separate retainer.
- Extended training. We include handoff sessions on managing and updating the site in Webflow. Additional training for larger teams is scoped separately.
- Design changes. A migration is a like-for-like rebuild. Significant design changes alongside the platform move need to be scoped as part of a redesign.
How do Webflow migration costs compare to a full redesign?
The short version: a migration is a platform move, a redesign is a rebuild. Different scope, different timeline, different price.
A useful question to ask before scoping: is the website underperforming because of the platform, or because of what's on it? If the platform is the bottleneck - slow to update, dev-dependent, disconnected from your tools - a migration fixes that. If the messaging or structure is the problem, a migration moves those problems to a new platform without solving them.
Some projects start as migrations and turn into redesigns once a proper audit surfaces how much the site actually needs to change. That's fine - better to find that out at the start than four weeks into a migration build.
How do you scope a Webflow migration accurately?
The inputs that produce a reliable estimate are consistent across every migration we scope. Here's what we look at:
- Site crawl. We crawl the live site before scoping, not after. This gives us a real URL count, surfaces redirect debt, and often flags technical issues that affect the migration plan.
- CMS audit. How many content types are there? How many fields per type? Are there cross-references between collections? This determines the CMS architecture work and the template count.
- Integration inventory. Every tool connected to the site, not just the obvious ones. We ask clients to pull their GTM container and HubSpot connection list - that usually surfaces things that weren't in the brief.
- Redirect export. We cross-reference the crawl against Ahrefs or Semrush to identify which URLs have backlink equity and need priority treatment in the redirect map.
- Stakeholder map. How many people need to review and sign off? Who's the final decision-maker? This directly affects timeline and therefore cost.
With those inputs, we can give a scoping estimate - usually a range with a clear explanation of what pushes it toward the top or bottom - within 48 hours of an initial call.
Want to know what your migration would cost?
We scope Webflow migrations for B2B SaaS teams from 40-page sites to 300-page platforms. Tell us about your site and we'll give you a straight estimate within 48 hours.
