Move your site from Squarespace to Webflow
A plan for moving from a Squarespace template to a custom Webflow site when the company needs more structure than the template gives. Your existing URL mappings carry over, and every changed URL gets a 301 redirect.
When the move makes sense, and when it doesn’t
Move to Webflow if:
•
You need page types Squarespace doesn’t have built in, such as case studies, integrations or a changelog, each with its own template.
•
Your content would work better as collections that link to each other, such as posts, authors and topics.
•
You want the design built exactly as drawn, with precise control over layout and motion.
•
Your CRM, scheduling and product tools already live outside Squarespace.
Stay on Squarespace if:
•
Squarespace Commerce, Acuity Scheduling, Email Campaigns or member areas run part of your business.
•
You want to keep building and running the site yourself.
•
The site does its job today and nothing about the business is changing soon.
What moves over and what gets rebuilt
Pages
Rebuilt in Webflow. Squarespace templates, sections and custom CSS don’t import.
CMS content
Squarespace exports a WordPress-format XML file that covers basic pages, one blog and text and image blocks. We convert the blog to CSV, map each field and import it into a Webflow collection.
Content that doesn’t export
Store, calendar and portfolio pages, extra blogs and several block types stay behind. The inventory lists them, and we copy what you need by hand.
SEO and redirects
Titles, descriptions and social images are copied for every page and post. Every URL that changes gets a 301 redirect in Webflow.
Forms
Squarespace form blocks are rebuilt as Webflow forms and connected to your inbox, CRM or automation tool.
Integrations
Scheduling, email and commerce features are replaced with tools that work on Webflow, or kept on a separate platform.
Media
Images, video and files are downloaded and uploaded to Webflow’s asset library, so nothing depends on the old site.
Domain
Wherever your domain is registered, you point it to Webflow by updating its DNS records.
The plan, step by step
01
Site review
We list every live URL and check Search Console and analytics for the pages that bring traffic, leads and links.
02
Content inventory
Every page, post, form, file and existing URL mapping goes into one sheet, marked keep, merge, rewrite or retire.
03
Redirect map
Each old URL gets its new address, including the redirects you already set up in Squarespace’s URL mappings. If your posts live at /blog/post-name, a Webflow collection with the slug “blog” keeps them there. Retired pages point to the closest relevant page, since search engines can treat a redirect to the homepage as a missing page.
04
Rebuild
We set up the class system, components and templates in Webflow, then import the blog and other content.
05
QA
We check every page on desktop and mobile, test every form and redirect, and compare metadata against the inventory.
06
Launch
We publish, point the domain to Webflow, confirm the redirects are live and submit the new sitemap in Search Console.
07
Post-launch checks
For the period agreed in the scope, we watch Search Console for missing pages and indexing changes, and fix what slipped through.
Risks and how we avoid them
Rankings
Some movement is normal while Google recrawls a moved site, and new URLs can take a few weeks to settle. Keeping URLs the same where possible, and using permanent redirects for the rest, gives search engines the clearest signal.
Old redirects
Redirects saved in Squarespace stop working once the domain moves. We carry each one into the Webflow redirect list, so older links keep working. Keep the redirects in place for at least a year.
Content left behind
Squarespace’s export skips several page and block types. The inventory covers the whole live site, so nothing is lost because it didn’t export.
Date-based URLs
If your posts use dates in their URLs, those paths change. Webflow redirects can match patterns, so one rule can cover the whole group.
CMS limits
We count posts and other content against Webflow’s plan limits before you commit.
How we handle it
We design in Figma and build in Webflow and Framer. Leaving Squarespace is a good moment to rethink how the site explains your product. Daniel G. Bright leads strategy, creative direction and the relationship on every project, with specialist designers and developers on production and build.
We scope and price each move as a flat-fee website project, agreed in writing before work starts. See Webflow websites for what a build includes.
Questions
Daniel G. Bright
Founder, BrightStudios
Still have a question?
Book a call with me to talk through your project and agree the next step.
Keep exploring
Webflow to Framer
For teams whose designers want to publish changes themselves.
Framer to Webflow
For sites whose content and CMS have outgrown Framer.
WordPress to Framer
For marketing sites where every change waits on a developer.
WordPress to Webflow
For content-led sites that want a hosted CMS with no plugin upkeep.
Wix to Framer
For companies that have outgrown a template and need a site built around the product.
Squarespace to Framer
For companies that need page types and design control beyond a template.
Wix to Webflow
For growing sites that need a structured CMS and full design control.
Plan your move
Bring your current site to the call and tell us why you’re thinking of moving. We’ll tell you whether a move is worth it and what it involves.