Squarespace Migration Cost in 2026: Scope Before Price

1. Inventory what Squarespace will not export

Squarespace exports certain content to a WordPress-format XML file, not a complete portable copy of the site. Its current guidance lists layout pages, one blog and selected blocks as exportable while excluding store pages, portfolio and other page types, product and video blocks, drafts, style settings and custom CSS.

• ✓
  Crawl every public URL and retain status, canonical, metadata, headings and structured data.
• ✓
  Inventory unlinked, draft, gated and localized content through authorized account access.
• ✓
  Export the available XML and independently capture excluded pages, products, media and settings.
• ✓
  Write down what depends on forms, past submissions, newsletters, members, scheduling, the store and payments.
• ✓
  Confirm who owns the domain, the DNS, email, analytics, ad accounts and every third-party login.

The same inventory-before-price sequence applies on every builder. Our website migration cost guide runs it across platforms, and Squarespace compared with a custom website covers the requirements that decide whether to move at all.

2. Price page systems, not raw page count

Five drivers set the price, and each one has to be evidenced rather than asserted. Templates are priced from an annotated route and component inventory, content from a field map with an exception count, features from accepted requirements and workflow tests, integrations from a data-flow and responsibility map, and quality from an acceptance matrix with a named test profile. The third column is the point of the table.

The tiers above and what each includes are listed on our pricing page, and what a website costs to build applies the same scope drivers outside a migration.

"How many pages you have is the wrong first question. What kind of pages they are is the right one.

3. Know what pushes a Squarespace move to the top of its range

Two sites with the same page count can be very different projects. These are the drivers that move a Squarespace migration up a tier, and each one should appear in the inventory before a number is discussed.

• ✓
  Blog and archive volume. Every post needs a URL decision, a content transformation and a tested redirect, so a long archive is a bigger job than the page count suggests.
• ✓
  Commerce data. Products, variants, images, inventory, discounts, tax and shipping rules each need a field map and a parity check, and customer or order history brings its own retention and privacy decisions.
• ✓
  Platform-native features. Squarespace Scheduling, member areas, native forms, email campaigns and portfolio pages have no direct equivalent in a custom stack, so each is a retain, replace or retire decision before it is a build task.
• ✓
  Design intent. Replicating the current design is a different scope from improving it during the move, and the contract should say which one it is buying.
• ✓
  Redirect history. A site that has already moved once can carry redirect chains and legacy URLs, so audit what is actually indexed rather than trusting the current sitemap alone.

4. Decide honestly whether to stay

A renewal increase, a disappointing mobile score or a feature you cannot reach is a prompt to run the numbers. On its own it is not a reason to rebuild. Staying put is the right answer more often than a web studio tends to admit, and it costs nothing to test that first.

• ✓
  Stay when the site is small and stable, has no content growth planned, and the plan cost is comfortably absorbed.
• ✓
  Stay when organic search is not how the business wins work, because search continuity risk then buys you nothing.
• ✓
  Stay when whoever edits the site values the visual editor more than the control a custom stack offers.
• ✓
  Move when unmet requirements, portability, integration needs or cumulative platform cost justify both the transition and the ongoing responsibility it creates.
• ✓
  Move when the constraint you have hit is architectural rather than a configuration problem, confirmed by measurement instead of assumption.

5. Preserve search signals without promising rankings

Six controls protect search visibility across a Squarespace migration, and the first two carry most of the weight: keep existing URLs where practical, and map every changed one to a relevant destination with a permanent redirect tested on the new host. Google warns that significant moves can cause temporary ranking fluctuations while URLs are recrawled and reindexed, so no agency can guarantee unchanged rankings, complete reindexing or a fixed recovery date.

• ✓
  Keep existing URLs where practical.
• ✓
  Map every changed URL to a relevant new destination and test permanent redirects on the new host.
• ✓
  Preserve or intentionally improve metadata, headings, content, canonicals and internal links.
• ✓
  Render crawlable content and accurate structured data.
• ✓
  Verify robots, sitemap and Search Console production properties.
• ✓
  Monitor crawl, index and query changes after launch and retain rollback criteria.

Google warns that significant moves can cause temporary ranking fluctuations while URLs are recrawled and reindexed. No agency can guarantee unchanged rankings, complete reindexing or a fixed recovery date. We go through that period in more detail in what a migration does to search visibility, and the platform-side controls in what Squarespace gives you to work with for SEO.

6. Include launch risk and continuity

A parallel build can reduce disruption, but “zero downtime” is an outcome claim, not a planning step. Define DNS, cache, provider, form, payment and rollback procedures. Monitor synthetic availability, real errors, form delivery, checkout and analytics during the cutover. Where cutover sits in the wider schedule is covered in how long a custom website takes to build.

Budget the domain move as its own line, and know the rule before someone quotes it at you as a penalty. Moving a domain between registrars is free, but ICANN's transfer policy requires a one-year extension of the registration, bought from whichever registrar you are moving to. Squarespace states this in its own words: "The transfer is free, but ICANN requires a one-year extension of your domain registration, which you'll purchase through Squarespace." The two things usually left out of that sentence when it is repeated: it is an industry rule, not a Squarespace one, so it applies in whichever direction you move and to whichever registrar you land on — and you keep the time already left on your registration, added on top of the extra year. So it is a year brought forward, not a year lost. Squarespace also notes that regular rather than promotional rates apply.

What we deliberately do not publish is a dollar figure. Squarespace's pricing page says only that the cost depends on the TLD and sends you to a live lookup; the "$20 to $70" range circulating in AI answers and forum threads is not stated on that page. Price your own TLD at the registrar you are moving to, on the day you move. A .com and a .io are not the same line item, and a range copied from a summary is not a quote.

7. Include current and future vendor cost

Squarespace plan families and features can differ by account and region, so read your own account rather than a published summary. Transaction and processing fees also vary by plan, product type, payment method and country. Use the account's current subscriptions and invoices. For the target stack, include hosting, CMS, email, database, search, monitoring, security, backups and maintenance.

8. Define PandaCodeGen commercial terms correctly

The signed scope controls all of this; what follows is the starting position, not the contract. A 30/70 split is a common option rather than the only schedule, refunds attach to failure to deliver signed scope rather than to a change of preference, and support days apply only where the accepted terms record them. Anything not written down is not included.

• ✓
  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 applies according to the accepted contract when PandaCodeGen fails to deliver the signed scope, not merely because preferences change.
• ✓
  Refund timing is contract-specific; PandaCodeGen normally initiates an approved refund promptly and publishes an outside expectation of 10 to 12 business days for bank processing.
• ✓
  Where the accepted terms include it, Starter carries 15 business days of post-launch defect support and Growth and Scale carry 30.
• ✓
  Minor accepted fixes can be included; new or expanded scope follows written change control and agreed pricing.

9. Define performance acceptance

Where contracted, PandaCodeGen targets a 90-plus Lighthouse score for agreed representative pages under recorded mobile and desktop profiles, using three consecutive tests per page and profile. The scope must record the environment and remedy. This is not a permanent guarantee for every route, visitor, consent state or future third-party change.

Core Web Vitals explained covers what those profiles record. Before accepting speed as the reason to move, work through our diagnostic sequence for a slow Squarespace site and the general method for speeding up a website.

10. Compare ownership and handoff

Client content and data remain the client's. Rights in fully paid custom deliverables, PandaCodeGen's reusable and pre-existing tools, and third-party components are defined in the accepted terms. Domain, hosting, repository and business accounts can be placed under client control as agreed, avoiding unnecessary agency lock-in. What that distinction means day to day is the subject of do you actually own your website.

11. Build a TCO scenario, not a payback promise

There is no universal second-year payback, so what you build is a scenario with visible inputs rather than a promise with a number on it. Six inputs go in, and two of them are the ones people leave out: internal time, and a risk range for schedule, data, SEO, integrations and adoption. Report measured post-launch benefits without assuming causation.

• ✓
  Current Squarespace subscriptions, add-ons, processing and internal administration.
• ✓
  Migration and one-time transition work.
• ✓
  Target providers, maintenance, monitoring and support.
• ✓
  Internal content, merchandising, training and engineering time.
• ✓
  Risk ranges for schedule, data, SEO, integrations and adoption.
• ✓
  Measured benefits after launch, reported without assuming causation.

For a sense of what a completed scope contains, see our project work and the MyCustomPatches case study. The delivery side of a move is described on our Squarespace migration service page.

12. Ask these before you sign anything

Two quotes are only comparable once both providers have priced the same inventory. Normalize the scope first, then compare the numbers: a higher quote often describes more of the work rather than more margin, and a lower one frequently has not found the work yet. Six questions expose the difference.

• ✓
  What is in scope, deliverable by deliverable? If redirect mapping, metadata migration, analytics and Search Console handover are not written down, treat them as excluded.
• ✓
  Which parts of the current site cannot be exported, and how will each of those be recreated?
• ✓
  What performance target is in the contract, on which named pages, under which profiles, and what is the remedy if it is missed?
• ✓
  Who holds the domain, repository, hosting and business accounts on the day after launch?
• ✓
  What is the change-control process, and how is additional scope priced once work has started?
• ✓
  Who monitors crawl, index and error behavior after launch, for how long, and what triggers a rollback?

Two quotes are only comparable once both providers have priced the same inventory. Normalize the scope first, then compare the numbers. A higher quote often describes more of the work rather than more margin, and a lower one frequently has not found the work yet.

Primary sources

• Squarespace: exporting your site
• Squarespace: URL mappings
• Squarespace: transaction and processing fees

Frequently asked questions