NewBase
Send your site
astro

Compare

Squarespace vs Astro

Squarespace is a good answer for a site built once and edited occasionally. The question is whether the template is still helping you or has become the reason three things on your list cannot be done.

Send your site
Price
From $5,000
Timeline
Typically 4–6 weeks
Included
30 days of hypercare
Code
In your name

Price and what it includes. The move I make is to Astro, The NewBase Stack.

Input

Your Webflow URL

Paste a Webflow URL. The trace stays a sample. Only the site check can go live.

Sample URL: https://northwind.example

Sample address

https://northwind.example

The trace and the pull request card are drawn for this reserved example. They do not change for the URL you paste.

Trace
Three finished steps. Replay run redraws them.
Pull request
The NewBase Stack. Sample only. This page does not open one.
Live
The site check, on an address this page can read.
Otherwise
The box says so and offers Send your site.

Output

Migration trace

Sample run

northwind.example

  1. 01 Read the Webflow site
  2. 02 Map pages, CMS fields and redirects
  3. 03 Draft an Astro pull request

Pull request

The NewBase Stack

Astro, Sanity and Cloudflare. Sample only. This page does not open a pull request.

Site check

Not live

Not run on the sample

This trace is a sample of a migration. The site check has not run. Paste a Webflow URL and only this pane can go live.

Send your site

Reasons

Move to Astro, The NewBase Stack, when

  1. The marketing site has outgrown the template while commerce or scheduling can be separated out behind it.

  2. The same facts are retyped across nine pages because nothing relates them.

  3. Code injection has become an undocumented dependency list nobody reads.

Differences

Four things that change when the site becomes a codebase.

  1. Blocks

    Content stops being an arrangement of blocks

    A Squarespace page is blocks on a page, so the words and the layout are the same object. That is why the export flattens it and why every page built with the editor as a layout tool is rebuilt by hand.

    Afterwards the content is separate from what renders it, which is what lets the same fact appear on nine pages and be changed once.

  2. Code injection

    The integrations come out of the shadows

    Analytics, chat, pixels and the odd fix accumulate in header and footer injection over years, added by people who have moved on.

    In a codebase each is a deliberate integration that somebody reviewed, and the audit on the way across routinely finds half of it loading nothing.

  3. Templates

    The layout stops being a negotiation

    Squarespace templates are opinionated on purpose, which is why they look coherent, and the opinions stop being negotiable at a point every growing site eventually finds. Custom CSS is where teams discover where that point is.

    Past it, writing the layout is cheaper than fighting one.

  4. Content model

    Your content model is yours

    The built-in collections are blog, events, products and gallery, and what you publish either fits one of those or gets forced into it.

    A designed model holds what the site actually has, with relationships the build can check rather than a naming convention somebody has to remember.

Compare

Capability by capability.

What is being compared Squarespace Astro
Design control Squarespace A template, with the settings it exposes Astro Components, styled in code Squarespace templates are opinionated on purpose, which is why they look coherent. The trade is that the opinions are not negotiable past a point, and custom CSS is where teams discover where that point is.
Content model Squarespace Collections: blog, events, products, gallery Astro Collections somebody designed for this site
What the export contains Squarespace Partial. WordPress XML carries some pages, one blog and basic content; the layout system, the styling and several Squarespace content types stay behind Astro The repository is the site: components, routes, styles and configuration in code your team controls This is the row that decides the shape of the project. The export is real, and it is partial in ways worth knowing before anybody quotes.
Blocks versus structure Squarespace Pages assembled from blocks on a page Astro Content separated from the layout that renders it
Third-party code Squarespace Code blocks and code injection Astro Integrations in the codebase, reviewed
Who maintains it Squarespace Squarespace, including hosting and updates Astro Your team owns the build, the deploy and the dependencies

Questions

Squarespace and Astro, answered.

Can I export my Squarespace site?

Partly. Squarespace exports to WordPress XML, which carries pages and one blog and leaves behind products, galleries, audio and video blocks. It is a real export and a partial one, and knowing which half is missing before anybody quotes is the difference between a smooth project and a surprise.

What about my store?

Commerce does not come out in the export, and moving a working store is usually the wrong project. If the store matters, the honest answer is to keep selling where you sell and move only the marketing site, which is the same boundary I recommend on Shopify.

Will my URLs stay the same?

Page slugs and the blog structure stay. Squarespace also serves several address shapes for the same page, including older ones nothing links to any more, and those are inventoried from analytics and Search Console rather than from a crawl, because a crawl only finds what the site links to now.

How long does it take?

Four to six weeks for a typical site, then 30 days of post-launch checks. Where a site lands in that range depends mostly on how many pages used the editor as a layout tool: those are rebuilt individually, while standard pages move through a handful of shared templates.

If you do decide to move, here is what it involves

Next step

Let me plan your next step.

Send your site

I can scope a migration. Send a brief and I will reply by email with next steps.