Website migration
Website Migration Cost: Prices, Scope and Timeline
A website migration with us starts at $1,500, at a fixed price agreed before we start. The final cost comes down to what you already have and what it has to do once it lands. The platform you are leaving changes how hard the export is, but the price is set by how many pages and templates there are, what data has to move, what it has to connect to, and how much testing the launch needs. There is no minimum project size, and the code, design files and accounts are yours at the end. Use those terms to check any quote you receive.
Starting tiers are our published terms. Outside facts below link their source and show the month they were last read.
Hassan Jamal·Published ·Updated ·13 min read
Owners and developers on the platforms this page covers, quoted in their own words, with a link to each original post so you can check the context yourself.
Every time you load a page or post, WP wants to retrieve info from the database. While that may have made sense in the beginning, we are long since past the point where the content on pages (and posts for that matter) don't change enough to matter. WP architecture should really have switched over to treating the site cache as the primary site, with the database being treated as the backup.
u/user_number_666 · r/Wordpress · Apr 14, 2026 · 103 upvotes on 160-upvote thread · Verify source
Honestly pretty basic stuff. Having multiple sized fonts and varied text formatting in one text box, changing line height on one section of one page rather than across the entire website, making sure photos stay in place and the correct size rather than getting all wonky when you change the screen size. I could go on.
u/WholeHuckleberry7081 · r/squarespace · Apr 7, 2026 · replying in their own thread about what they wanted to change · Verify source
SEO migration control loop
A deliberate decision for every old URL
URL inventory
Crawl and baseline
Disposition map
Keep, redirect, or retire
Staged QA
Crawl, forms, consent, and speed
Monitor
Indexing, queries, and errors
Reduce technical risk. Do not promise rankings.
The short answer: what a website migration costs
First work out which job you're buying. Moving the same site to a new host is a small job that many hosting companies do when you buy a plan, often free or for a small fixed fee. Moving to a different platform is a rebuild. Its price is set by how many pages, templates and records have to move, how much the old platform lets you export, what the site connects to, and whether your current URLs and rankings have to survive. Our own migrations are priced on those inputs, at a fixed price agreed before we start:
- ✓Starter, from $1,500: up to 7 pages, for a small, well-defined migration.
- ✓Growth, from $3,500: 8 to 20 pages, a content model built around your own collections, and a full migration with a redirect map.
- ✓Scale, from $5,000: more than 20 pages, a large catalogue, subscriptions or custom commerce logic, or more than one language.
- ✓Anything larger or unusual is quoted after a scoping call, and the written proposal sets the price before work starts.
Inventory
Every page, template, image and file you actually have.
Map
Where each URL lands, and who owns what.
Accept
How you sign it off: it works, it ranks, people can use it, it is fast.
Operate
What it costs to keep running once it is live.
The seven-platform migration matrix
No platform hands you a complete, portable site. What each one exports sets the floor on what a migration costs, because whatever the export misses has to be rebuilt by hand. The acceptance-risk column is where sign-off usually fails, and it's different for every source platform. The last column links the full cost guide for each one.
| Source | Export or extraction | Common replacement work | Key acceptance risk | Our starting point | Full cost guide |
|---|---|---|---|---|---|
| WordPress | XML, database, files, APIs or controlled extraction | Theme, plugins, blocks, forms, search, users and hosting behavior | URL, content, media, shortcode and plugin-equivalent coverage | Starter, from $1,500, for a small site on a few templates | WordPress migration cost |
| WooCommerce | Products CSV plus orders, customers and extension-specific data | Checkout, tax, fraud, inventory, fulfillment, accounts and subscriptions | Financial and order-flow reconciliation | Starter, from $1,500, for a small catalogue; subscriptions or a large catalogue mean Scale, from $5,000 | WooCommerce migration cost |
| Webflow | Code ZIP plus separate CMS or ecommerce CSV exports | CMS, forms, search, localization, ecommerce, users and code components | Feature gaps beyond exported HTML, CSS, JavaScript and assets | Starter, from $1,500 | Webflow migration cost |
| Wix | CMS exports and other feature-specific exports or APIs where available | Pages, media, blog, forms, bookings, members, apps and commerce | Complete feature and content inventory before extraction | Starter, from $1,500 | Wix migration cost |
| Squarespace | Partial WordPress XML, a separate product .csv, plus manual work | Excluded layouts, store pages, portfolio, product images, media, forms and styles | Export exclusions and design recreation | Starter, from $1,500 | Squarespace migration cost |
| Shopify | Product and other admin exports plus APIs | Storefront, checkout boundary, accounts, search, apps, analytics and consent | Commerce continuity and app compatibility | Headless builds start at Scale, from $5,000 | Headless Shopify cost |
| GoHighLevel | Documented APIs, exports and controlled recreation | Keep CRM or replace it; forms, funnels, calendars, automation and attribution | Lead capture and workflow continuity | Starter, from $1,500, for a site that keeps the CRM | Keeping GoHighLevel, replacing the site |
Two of those rows, in the platforms' own words, read in October 2026: Squarespace's export guide describes a WordPress-format export that leaves out some content, including album, cover, index, portfolio and store pages, and Webflow's code export guide describes a ZIP of pages, styles, scripts and images, without CMS, User Accounts or Ecommerce content and functionality; CMS Collections, Ecommerce Collections and User Accounts can be exported separately as CSV.
A worked example: scoping a 12-page Squarespace site
An invented 12-page Squarespace site: a home page, six service pages, a blog with 40 posts, a portfolio page, a contact form and a small store with eight products. The owner wants a site their team can edit, and to keep the blog's search traffic.
- ✓Comes across in the export: the blog posts and the basic text of standard pages. They still need checking and reformatting once they land in the new editor.
- ✓Has to be rebuilt by hand: the portfolio page and the store pages, because Squarespace's export guide lists portfolio and store pages among the content that doesn't export, plus the layouts and the form.
- ✓Can come across separately: the eight product records. Squarespace's product export guide, read in October 2026, covers physical and service products, up to 10,000, to a .csv file, without featured images, variant images, image alt text, customer reviews or additional product information. The images, alt text and reviews are moved by hand.
- ✓Has to be planned whatever the platform: a redirect for every old URL, especially the 40 blog posts, and a check that each page keeps its title and description.
- ✓Where it lands with us: 12 pages and a content model for the blog put it in Growth, from $3,500, which covers 8 to 20 pages and a full migration with a redirect map. Eight products don't settle the store's scope on their own: checkout, shipping, tax and any connected services are scoped on the call, and a large catalogue, subscriptions or custom commerce logic would move it to Scale.
We do not publish a market median or a cross-agency price range for these migrations. Ranges like that mix unlike project types, scopes, regions and levels of finish, so a figure stated without a defined sample and scope definition is not something a buyer can plan against. The only prices we stand behind are our own, and your written quote sets the final one.
Our own tiers are at the top of this page. Which one a migration lands in is driven by page count, content volume, custom functionality and integrations rather than by which platform you are leaving, so the same source platform can land in any of the three. The price is fixed for the scope written into the accepted project terms, and every build carries a 90+ Lighthouse handover target on phone and desktop for the pages named in your quote, tested three times. Current tiers are always on the pricing page; if this article and that page ever disagree, the pricing page is correct.
Are you changing hosts, or changing platforms?
These are two different jobs. Moving a WordPress site from one host to another keeps the same software, the same theme, the same plugins and the same database. Nothing is rebuilt. Many hosting companies will do that transfer for you when you buy a plan, so check what your new host includes first. Read in October 2026, Hostinger advertised migration as free, for an unlimited number of websites, and Kinsta as free and unlimited. If the host's included move covers your site, use it, and don't pay platform-migration prices for a host change.
When the included move doesn't cover it, or the site runs a store, business email or connected services, we quote a host move separately from any rebuild. That work is the backups, a compatibility check on the new host, DNS and email coordination, checks at cutover, and a rollback plan if something breaks.
A platform migration is the other job: the content comes out of one system and has to be rebuilt in another that works differently. Templates, plugins, forms, search, checkout and editor workflow do not transfer, they get reproduced, and the URLs have to be mapped so the search traffic survives. That is what the rest of this page prices. Published figures that mix the two jobs into one range are the reason migration quotes look wildly inconsistent: a $0 host transfer and a five-figure replatform are both truthfully called a “website migration”.
A third case sits between them. Staying on the same platform but rebuilding the design is a redesign, not a migration, and it is priced differently again; our website redesign cost guide covers that scope, and what a website costs to build from scratch covers the case where replacing beats moving.
The platform you are leaving changes how hard the export is. It does not set the price.
What drives website migration cost on every platform
Every published migration range is wide because it is averaging jobs that have nothing in common. Three answers collapse most of that range, and any quote given without them is a guess wearing a number.
- ✓The platform pair, not just the destination. WordPress to Next.js and Wix to Next.js are different jobs: WordPress exposes its database and a REST API, so content extraction is scriptable. Wix does not give you the same access, so more content is moved by hand and the same page count costs more.
- ✓The countable unit, and which one applies. Brochure sites price per page or per template; stores price per product, per variant and per historical order. A 40-page site and a 4,000-product catalogue can carry the same design work and differ by an order of magnitude on data.
- ✓Whether your web addresses have to survive. If the site has search traffic worth keeping, someone has to list every live address, decide where each one goes, forward them, and check them after launch. On an established site this is often the single largest line item, and it is the one most commonly missing from a cheap quote.
That third one is where cheap migrations turn expensive. A 301 redirect tells Google the page moved permanently and passes its ranking signals to the new URL. Skip the mapping and the old URLs return 404s, the accumulated signals are lost, and the traffic does not come back on its own. Recovering it afterwards costs more than mapping it correctly would have, because by then the rankings have to be re-earned rather than transferred. What that looks like in practice is covered in what a migration does to search visibility.
Before asking anyone for a number, write down three things: the platform you are on and the one you are moving to, your page count or product count, and whether you need existing URLs and rankings preserved. A quote given without those is not a quote. A quote that omits the the link forwarding is not cheaper than one that includes it. It just moves the cost to later, when it is worse.
Go straight to your platform
The rest of this page is the shared method. If you already know which platform you are leaving, the dedicated guide will be faster: WordPress, WooCommerce, Webflow, Wix, Squarespace, or the triggers that usually start a Webflow move. If you are moving to Next.js specifically, the WordPress to Next.js walkthrough covers the mechanics, and what a migration does to your search traffic covers the risk everyone actually asks about first.
How long does a website migration take?
Long enough that the schedule is set by approvals and content, not by build time. The technical work on a bounded brochure migration is the smaller half of the calendar; the larger half is inventorying what exists, deciding what does not come across, getting content reviewed and signed off, and testing every journey before the switch. A store adds reconciliation of orders, customers and payments, which cannot be rushed because the numbers have to match.
The parts that reliably take longer than people plan for: finding every URL that exists rather than every URL someone remembers, waiting on content decisions, and the freeze-and-cutover window where data must stop changing. The parts that go faster than expected are usually templates, because a site with forty pages often has six real layouts. Ask any provider for the schedule broken into listing what you have, building, moving content, testing and launching, with what each stage waits on, rather than a single duration. A quote that gives one number for the whole thing has not been planned.
What is inside a migration price?
Seven workstreams, and only two of them look like building a website. Discovery, content extraction and reshaping, rebuilding the things that were features rather than pages, search continuity, testing, and the launch and handover work. A quote that names only design and development has not priced the other five.
- ✓Working out what you have, what you need, and what you are building.
- ✓Deciding how the site is organised, building the reusable pieces, and making it work on every screen.
- ✓Getting your content out of the old system, reshaping it to fit the new one, moving the images, and checking nothing was lost.
- ✓Rebuilding the things people use: forms, search, logins, checkout, analytics, the cookie banner, and whatever else you connect to.
- ✓Protecting your search traffic: listing every URL, carrying the metadata across, setting canonicals, keeping the structured data, mapping redirects, and regenerating the sitemap.
- ✓Testing it properly: can everyone use it, is it secure, does it work in every browser and on every device, does it do what it should, and is it fast.
- ✓Going live: shipping it, freezing the data, making the switch, watching it, being able to undo it, handing it over, and supporting you afterwards.
The platform summaries below give our starting point for each source platform and send you to the full guide for it. The figures are PandaCodeGen's own published tiers, listed in full on the pricing page, and the accepted scope sets the final number. They are not a market rate for the industry.
Migration cost by platform
The method above applies to every platform. What changes from one platform to the next is how much the export gives you and which features have to be rebuilt by hand. Each summary below names that and our starting point, and the full guide for each platform has the inventory, the tier table and the redirect work.
WordPress
WordPress exposes its database and a REST API, so content extraction can be scripted. The cost sits in what the export can't carry: page-builder layouts, plugins, shortcodes, custom fields, forms and search all have to be rebuilt or replaced. A small site on a few templates starts at Starter, from $1,500; structured content or a heavy plugin footprint moves it up a tier.
The full WordPress migration cost guide, including why a host change is a different job
WooCommerce
A store carries obligations a brochure site doesn't: products and variants, customer and order records, tax, shipping, payments, refunds and extensions, all of which have to reconcile before and after the move. A small, bounded catalogue can start at Starter, from $1,500. Subscriptions, a large catalogue or custom commerce logic put it in Scale, from $5,000, or a custom quote.
The WooCommerce migration cost guide: moving the data versus rebuilding the store
Webflow
Webflow's code export gives you the front end, not a working site: CMS, ecommerce, forms, search and localized content need to be rebuilt or moved separately, and User Accounts ended in January 2026, so a members area moves to a separate provider. Page count has to be turned into templates and systems before a tier means anything. Small, well-defined migrations start at Starter, from $1,500.
The Webflow migration cost guide, with what the export leaves out
Wix
Wix lets you export some data separately, such as CMS collections, but not the site itself, so most of the work is rebuilding pages and features from an inventory. Bookings, members, stores, apps and custom code each need their own decision. A small marketing site starts at Starter, from $1,500.
The Wix migration cost guide and the four routes people take, cheapest first
Squarespace
Squarespace's export is partial: store and portfolio pages, product and video blocks, drafts, style settings and custom CSS are among the documented exclusions, so the design and those systems are recreated rather than moved. A small presentation site starts at Starter, from $1,500. If search is your reason for leaving, read whether Squarespace is really bad for SEO before you price the move.
The Squarespace migration cost guide, including the redirect line most quotes miss
Shopify and headless Shopify
The first decision is whether Shopify stays as the commerce backend. A headless storefront still needs search, accounts, analytics, consent, app compatibility, preview and monitoring rebuilt around it. Replacing Shopify entirely also makes you responsible for checkout, tax, fraud, orders and operations. Our headless builds start at Scale, from $5,000.
What headless Shopify costs, line by line
GoHighLevel
Most operators keep GoHighLevel for the CRM, calendars, automation and pipelines and replace only the public site. The work is in the joins: forms, contacts, attribution, webhooks, failure handling and who owns each account. Don't accept a promise of an unchanged CRM bill or an uninterrupted workflow that hasn't been tested. A site that keeps the CRM starts at Starter, from $1,500. If speed is the reason you want to move, check what can be fixed inside GoHighLevel first.
How to keep GoHighLevel and replace only the website
Is a migration worth it? How to build the business case
A migration is worth it when the measured cost of staying exceeds the cost of moving plus the cost of running the replacement, over a horizon you pick in advance. Compare current direct costs, internal hours, incidents and measured limitations with migration cost, target providers, maintenance, support and risk. Build low, central and high scenarios. Do not multiply an assumed speed loss or promise a predetermined commercial or search outcome.
Costs that must be visible in the proposal
These six belong in the proposal rather than in discovery, because each one is a decision someone has to fund. Content cleanup, vendor charges, compliance and accessibility work, your own team time, ongoing maintenance, and exiting the old platform. If a proposal is silent on one, assume it is excluded and ask what happens when it appears.
- ✓Tidying up the content, rewriting what needs it, replacing images nobody can find, and dealing with the records that do not fit.
- ✓What your vendors charge: the plan, the licences, what you use, and fees on payments and messages.
- ✓Fixing accessibility problems, having someone review the security, and any compliance work you are required to do.
- ✓Your own team's time: reviewing it, getting legal to approve it, learning the new system, and helping everyone adjust.
- ✓Keeping it running after launch: maintenance, monitoring, someone on call when it breaks, and upgrades.
- ✓Leaving the old platform properly: archiving it, cancelling the plan, and keeping whatever you are required to keep.
How to budget the migration
Build the number before you request quotes, so you can tell which quote is wrong. Six ordered steps: inventory, define the target and the responsibilities, agree what done means, separate one-time from recurring, write down the assumptions and exclusions, and hold contingency against identified unknowns rather than an arbitrary percentage.
- List everything you have: pages, templates, content, data, integrations and user accounts.
- Define target journeys, editor workflow and operating responsibilities.
- Agree what “done” means: it works, it still ranks, everyone can use it, it is secure, and it is fast.
- Separate one-time agency work from third-party and ongoing costs.
- Write down what you assumed, what is not included, how changes get approved, what you are waiting on, and when each part happens.
- Keep a contingency tied to identified unknowns, not an arbitrary percentage.
PandaCodeGen terms
A common payment option is 30 percent at onboarding and 70 percent at the delivery milestone, and another written schedule may be agreed. A refund is tied to failure to deliver the signed scope, not a change of preference after work starts. Starter includes 15 calendar days of launch defect support; Growth and Scale include 30. Ownership, licenses and accounts follow the accepted project terms.
Frequently asked questions
How much does a website migration cost in 2026?
Why can two migration quotes differ so much?
Will I lose my Google rankings during migration?
How long does a website migration take?
What does the migration price include?
Can I migrate without losing customers or sales?
What happens to my Webflow CMS data during migration?
Do I need to keep paying for Shopify apps after migration?
What is the cheapest way to migrate from Wix?
What is the typical Shopify to headless cost?
Is migrating a website worth it in 2026?
Is it hard to move a website to another hosting provider?
Can you do the website migration for me?
How do I get a migration price for my own site?
Primary sources
- WordPress export
- WooCommerce product CSV
- Webflow code export
- Wix support: CMS and content export
- Squarespace export
- Shopify product export
- HighLevel API
Get a platform-specific migration plan
We will inventory the actual site and map it to a tier or custom scope. Additional pages and features can be discussed after the core migration is defined.
Related Articles
WooCommerce Migration Cost in 2026: Data, Scope and Tiers
Price a WooCommerce migration from products, customers, orders, payments, subscriptions, extensions, content, SEO, acceptance, cutover and operating responsibility.
Can You Export Your Website? What 8 Platforms Let You Take
What Wix, Squarespace, Webflow, Shopify, WooCommerce, GoHighLevel and WordPress let you export, from their own help pages, and what to save before you cancel.
Lovable Site Not Showing on Google? A 2026 Diagnostic
Lovable apps now support SSR or crawler pre-rendering. Check publishing, indexing, canonicals, metadata, content and Search Console before any rebuild.