By Mehdi HassanHow much does a website migration cost?
A website migration usually costs between about $1,500 and $25,000 when an agency or experienced freelancer does it, based on the quotes we see in 2026. Small brochure sites sit at the bottom of that range, content-heavy or multilingual sites sit near the top, and complex headless or ecommerce replatforms can go well beyond it.
The spread is wide because "migration" covers very different jobs. Moving a six-page site from Wix to Framer with no blog is a small rebuild. Moving a 300-post WordPress blog in three languages to a headless Next.js stack is a content, engineering and SEO project. This hub breaks the cost down by platform pair, site size and driver, then links to the detailed guides for each part. If you're short on time, start with the migration quote checklist so you can compare proposals like for like.
- Typical range of website migration quotes we see, by size and complexity
- $1.5k–$25k
- Designify website: up to 6 pages, custom design, Next.js, CMS
- $8,000
- Designify, per page beyond six
- +$500
What does a website migration cost by platform pair?
The source and destination platforms set the baseline, because they decide how much can be exported and how much is rebuilt by hand. The table shows typical quotes and timelines we've seen for common moves. Treat them as starting points that vary by provider, region and scope.
Migration | What's typically quoted | What makes it harder |
|---|---|---|
Wix or Squarespace to Framer or Webflow | From about $4,000 for Wix to Framer | Wix blog URLs under /post/, apps with no equivalent |
Webflow to Framer | Within the $1.5k–$25k range by size | Webflow CMS features Framer lacks, image re-hosting |
Framer to Webflow | Often 2–5 weeks of work | Rebuilding interactions and relational CMS |
WordPress to Webflow | Within the $1.5k–$25k range by size | Plugins, shortcodes, category and date URLs |
WordPress to headless Next.js | About £13,000–£30,000 and 6–12 weeks | Content model, CMS setup, preview and redirects |
HubSpot CMS to another platform | Often 6–10 weeks of work | Forms, smart content and CRM wiring |
Shopify storefront to headless | €100,000–€150,000 and up | Checkout, inventory, app replacements |
For pair-specific detail, see WordPress to Webflow migration cost, Webflow to Next.js migration cost, Framer to Next.js migration cost and HubSpot CMS migration cost and timeline.
How does site size change the price?
Site size changes the price, but page count alone is a poor predictor. What really scales cost is the number of unique templates, the number of CMS items that need cleaning, and the number of URLs that must be mapped and redirected. A large site built from a handful of templates can be cheaper than a small site where every page is bespoke.
Site profile | Typical shape | Where it usually lands |
|---|---|---|
Small brochure site | Up to about 10 pages, no blog, one form | Low end of the $1.5k–$25k range |
Startup marketing site | 10–30 pages, blog under 100 posts, a few integrations | Middle of the range |
Content-heavy site | Hundreds of posts, several collections, authors and tags | Upper part of the range |
Multilingual site | Any of the above in 2+ languages | Upper part of the range or beyond |
Headless or ecommerce | Custom CMS, checkout, accounts or apps | Often well beyond the range |
For example, suppose a site has 12 marketing pages and 200 blog posts. The 12 pages drive design and build time, but the 200 posts drive content export, image re-hosting, metadata checks and 200 redirect rows. That's why a quote that only asks for page count is usually missing half the job.
What drives the cost of a website migration?
Six things drive almost every migration quote: rebuild scope, content volume, CMS complexity, languages, integrations and SEO protection. Knowing which ones apply to you is the fastest way to get an accurate number.
- Rebuild scope. A one-to-one rebuild of the current design costs less than a redesign. Our framework on migrating and redesigning at the same time explains when combining saves money.
- Content volume and quality. Hundreds of posts with inline images, shortcodes or page-builder markup take real cleanup time. Webflow's CSV export, for example, turns rich-text images into placeholders that need fixing.
- CMS complexity. References, multi-references, filters and dynamic templates are where builders differ most and where rebuilds slow down.
- Languages. Every locale multiplies content, metadata, redirects and QA. See the multilingual website migration playbook.
- Integrations. Forms, CRM, analytics, scheduling, gated content and search each need to be rebuilt and tested.
- SEO protection. URL inventory, a redirect map, metadata and structured data checks, and post-launch monitoring.
Do AI coding agents make migrations cheaper?
Yes, for the build. Coding agents now rebuild templates and import content far faster than a person, and the model cost is small. Vellum described migrating off Webflow with coding agents in about a week, and cursor.com was reportedly rebuilt in three days for about $260 in usage. Teams have also moved thousands of pages to static frameworks this way.
What agents don't do is own the outcome. The expensive part of a migration was never typing out components. It's deciding what to keep, mapping every URL, checking that titles, schema and forms survived, and catching problems after launch. AI lowers the build portion of a quote; it doesn't remove the SEO and QA portion. Our guides to AI-assisted website migration and AI migration vs agency compare the models in detail.
How we use AI on migrations
We use coding agents for the volume work: rebuilding repeated templates, transforming CMS exports into the new content model, generating redirect candidates from a crawl and checking for missing metadata.
A person still owns the decisions and the checks: which pages stay, what every old URL maps to, whether the copy still works, and whether forms and analytics fire. That split keeps the speed of agents without handing your rankings to a tool that won't notice when a redirect points at the wrong page.
What does Designify charge for a migration?
Our prices are fixed. A website is $8,000 for up to six pages with custom design, copy, a Next.js build, a CMS and animation, plus $500 for each extra page. A single landing page is $6,000. Migration work, such as content import, redirects and SEO checks, is scoped on the intro call rather than assumed to be inside those prices.
Offer | Price | When it fits a migration |
|---|---|---|
Website | $8,000 up to 6 pages, +$500 per extra page | Rebuild and redesign of a marketing site on Next.js |
Landing page | $6,000 | Moving one high-value page first, or a campaign page |
Brand & design sprint | $3,000 | Redesign explorations in Figma before deciding to migrate |
Trial week | $1,000 | Audit, URL inventory or a pilot template before committing |
Monthly retainer | $6,000/month | Ongoing design and development after the move |
For example, suppose your site has 10 marketing pages. The website package covers six, and four extra pages add $2,000, for $10,000 in design and build. Blog import and redirects are then scoped separately based on how many posts and URLs you have. We include redirects and SEO checks in any migration we take on.
How long does a website migration take?
Timelines follow the same drivers as cost. Quotes we've seen run about 2–5 weeks for Framer to Webflow, 6–10 weeks for leaving HubSpot CMS and 6–12 weeks for WordPress to headless Next.js, while agent-assisted rebuilds of simple sites can be much faster. Content cleanup and stakeholder review usually take longer than the build.
Our guide to how long a website migration takes walks through realistic schedules by site size, and the website migration project plan template gives you owners, milestones and go/no-go gates you can copy.
What will the site cost to run after the migration?
The running cost after a migration can matter more than the project fee. A builder adds a site plan, editor seats and add-ons such as localization; a headless setup adds hosting, a CMS plan and developer maintenance. Platform pricing moves too: Webflow's May 2026 change merged its CMS and Business site plans into a single Premium plan.
Compare two-year totals, not monthly prices. Add the project cost, two years of subscriptions and seats, and the time or retainer cost of making changes. Our breakdown of ongoing costs after a migration lists every line item, and the guides to website hosting cost and website maintenance cost give the detail. If a price increase is what's pushing you, read migrate or optimize your plan before committing.
For example, suppose you compare a builder and a headless setup over two years
Hypothetical example: for each option, add the one-off project fee, 24 months of platform and CMS plans, 24 months of seats for every editor, any per-locale or add-on fees, and an estimate of change requests.
A builder often wins when marketers make most changes and the site has few languages. A headless setup often wins when there are many locales, heavy content or custom logic, because per-seat and per-locale fees don't grow with it. Neither wins by default; the math depends on your team.
Should you hire an agency, a freelancer or do it yourself?
Do it yourself if the site is small, has few ranking pages and you have someone who can own redirects and QA. Hire a freelancer when the scope is clear and mostly build. Hire an agency when content, design, SEO and integrations all change at once, or when nobody internally can own the outcome.
Our comparison of DIY vs freelancer vs agency for a migration sets out the trade-offs, and the guide to hiring a Webflow or Framer migration agency gives you a scorecard and the questions to ask. If accessibility is part of the brief, budget for it explicitly; our accessibility audit cost guide shows what that adds.
How do you get an accurate migration quote?
Give every provider the same facts, and ask for the same breakdown back. Accurate quotes need numbers you can pull in an afternoon.
Export a URL list
Crawl the site and count URLs by type: pages, posts, collection items and locales.
Pull traffic and rankings
Export Search Console data so providers know which pages carry the most risk.
List integrations
Forms, CRM, analytics, chat, scheduling, search, gated content and anything else that has to keep working.
Decide redesign scope
One-to-one rebuild, refresh, or full redesign. This one decision moves quotes more than any other.
Ask for a line-item quote
Design, build, content import, redirects, SEO checks, QA and post-launch support, each priced or explicitly excluded.
