Upgrading Squarespace 7.0 to 7.1 in 2026: What Breaks, What It Costs, Whether to Bother
Squarespace 7.1 launched in early 2020. Six years later, a lot of sites are still on 7.0, most of them on Brine-family templates, and their owners keep asking whether they have to move.
Short answer: you don't have to yet, you probably should within a year or two, and it's a rebuild, not an upgrade.
Is 7.0 going away?
Squarespace has not announced an end-of-life date for 7.0. Existing sites keep working, keep getting security updates, and keep being supported. What 7.0 no longer gets is new features. Fluid Engine, the current section and layout system, most of the AI tools, AI Visibility, the newer commerce features, and the newer blocks are 7.1 only. The gap widens every quarter.
We treat 7.0 the way you'd treat an old car that still passes inspection: fine until you need something it can't do, and you'll want to plan the replacement rather than be forced into it.
What "upgrading" actually means
There's no in-place upgrade. 7.0 and 7.1 are different architectures. 7.0 has templates with distinct code bases, index pages that stack sub-pages, and template-specific style options. 7.1 has one underlying template, section-based pages, site-wide styles, and Fluid Engine's grid editor.
Squarespace offers an upgrade tool on eligible 7.0 sites (check under Settings; it's not available to every template). What it does: creates a new 7.1 site and copies your pages, blog posts, products, and content blocks into it. What it does not do: reproduce your design. Index pages become sections in roughly the right order; the header, footer, fonts, colours, spacing and any custom CSS have to be redone. Custom code written for 7.0's class names doesn't work on 7.1's.
If your template isn't eligible, or the automated copy makes a mess (it often does for sites with many index pages and custom code), the alternative is a manual rebuild: a new 7.1 site, content moved over by hand, design built fresh.
Either way, the outcome is a new site that looks like your old one, or better, on 7.1.
What you gain
Fluid Engine. Drag any block anywhere on a grid, with separate desktop and mobile layouts. 7.0's layout engine was row-and-column only. This is the biggest day-to-day difference for anyone who edits the site.
Sections. Reusable, movable page sections with their own backgrounds, padding and layout. Saved sections can be reused across pages. On 7.0 this was index pages and stacked sub-pages, which were awkward to reorder and impossible to reuse.
Site styles. Global colour themes and font sets applied to sections, rather than template-specific tweaks. Changing the brand colour is one change, not thirty.
Everything new. The commerce features from the last five years, member sites and courses, AI Visibility, the newer form and portfolio blocks, the design system improvements, and whatever Squarespace ships next.
Speed. 7.1 sites are generally faster than 7.0 sites of equivalent complexity, partly because the code base is newer and partly because rebuilding a site sheds a decade of accumulated custom code and heavy images.
What you lose
Developer Platform. 7.0 had Developer Mode, which gave full access to template files and let developers change the HTML structure. 7.1 does not. If your 7.0 site depends on custom template code, that functionality has to be recreated with CSS and JavaScript injection or rethought entirely. For most sites this doesn't matter. For a few, it's the reason they're still on 7.0.
Specific template features. Brine's parallax, banner overlays and index page behaviours; Bedford's sidebar; Pacific's stacked layout. Some are reproducible on 7.1, some aren't, and some don't need to be.
Custom CSS. All of it needs rewriting. Class names changed. Budget for this if your site has a long Custom CSS panel.
URLs, potentially. Page URLs copy over. Index page and sub-page URLs sometimes don't map cleanly. Blog post URLs usually do. You'll need a redirect map for anything that changes.
Muscle memory. Your team learned 7.0's editor. 7.1's is different and mostly better, but there's a week of "where did that go".
What it costs
This is a rebuild, and prices like one. For a typical 10 to 20 page 7.0 business site, moving to 7.1 with a refreshed design costs USD 5,000 to 12,000 with us, including content migration, redirect mapping, custom code rewrites and QA. Add a shop and it's higher. Add a large blog and it's higher again, mostly for the URL work.
A "like for like" rebuild that reproduces the old design exactly is possible and rarely worth it; if you're paying for a rebuild, take the opportunity to fix what didn't work.
DIY is possible with the upgrade tool and a lot of patience. Budget a full week for a small site and expect to redo the header, footer and every page's layout.
The process
Inventory. Every page, URL, form, integration, custom code block and third-party embed on the current site. Search Console's pages report for what actually gets traffic.
Decide what stays, what goes. Old pages nobody visits get redirected, not rebuilt.
Design on 7.1. Site styles, header, footer, page templates for each page type. Approve before migrating content.
Migrate content. Via the upgrade tool if eligible and clean, by hand if not. Blog posts and products via export/import where the tool falls short.
Rebuild integrations and code. Forms to CRM, booking embeds, analytics, custom CSS and JS rewritten against 7.1 classes.
Redirects. URL mappings for everything that changed, in the new site's Settings, then Advanced, then URL Mappings.
QA on desktop and mobile, every page. Fluid Engine's mobile layouts need a separate pass.
Cutover. Move the domain to the new site (both sites are in your account; it's a domain transfer between them, no DNS change if Squarespace manages the domain). Submit the sitemap. Keep the old site for 30 days.
Four to eight weeks, depending on page count and decision speed.
When to do it
Now, if: you're about to redesign anyway; you need a 7.1-only feature; your team edits the site often and Fluid Engine would save real time; your custom code is fragile and nobody remembers how it works; or the site is a shop and you want the current commerce tools.
Wait, if: the site is small, rarely edited, works fine, and money is better spent elsewhere. A brochure site on Brine that loads fast and converts is not a problem to solve.
Don't do it halfway. The worst outcome is a rushed automated copy that looks worse than the 7.0 site and never gets finished. If you're moving, plan it as a project.
A note on "Squarespace 7.2"
There isn't one. Squarespace's changes since 2020 have all shipped inside 7.1, which is why there's no version to wait for. 7.1 is the platform; the question is only when you move.
Questions we get
How do I know which version I'm on? In the Squarespace dashboard, the site's version is listed under Settings, then Site Availability, or at the bottom of the Design panel. 7.0 sites also show a template name (Brine, Bedford, Pacific and so on); 7.1 sites don't.
Will my SEO suffer? Not if URLs are preserved or redirected. Most page and blog URLs copy over unchanged. Index pages are the exception and get a redirect. We've seen rankings hold and often improve after a rebuild, because the new site is faster and cleaner.
Can I keep my 7.0 site running while the 7.1 site is built? Yes. The new site is built on a trial or a second subscription, and the domain moves when it's ready. Downtime at cutover is minutes.
Does the new site cost a new subscription? During the build, a trial is free for 14 days and can be extended. At launch, you either transfer the existing subscription's domain to the new site and cancel the old one (Squarespace credits the unused time) or keep both briefly.
What about my Acuity, Email Campaigns and Member Areas? Acuity is a separate product and reconnects to the new site. Email Campaigns lists export and import. Member sites on 7.0 (Member Areas) need rebuilding as Member Sites on 7.1, and members re-register; plan the communication.
My 7.0 site uses Developer Mode. What happens? The custom template doesn't transfer. We rebuild the functionality with 7.1's tools and code injection where possible, and tell you up front what can't be reproduced. This is the one case where a 7.0 site sometimes belongs on a different platform instead.
