Outgrown Squarespace? Keep everything it earned.
Templates get you live fast, then box you in. We rebuild your site page for page, on brand, on a codebase your team updates by asking its AI agent, with every URL kept or redirected.
In short
Squarespace exports some content but not all of it, so a Squarespace migration is part export, part recovery. ZINC moves your pages, blog, and media onto Astro or Next.js, rebuilds the design without template limits, and maps every URL before launch.
From launch day, your team updates the site by asking its AI agent, with Dispatch handling previews and approvals.
25+ years of strategy, design, and digital delivery for brands including:
When the brand outgrows the template.
Design without a ceiling.
Layouts, components, and interactions built for your brand, not bent around a template’s blocks.
Content that scales.
Structured content for case studies, resources, and service pages, so the site can grow without getting messy.
Changes by asking.
Your agent makes the update, you preview it, you approve it. The template stops being the bottleneck.
Every Squarespace feature gets a destination.
Before cutover, each thing your site does has an agreed replacement, an owner, and a test.
| On Squarespace | After the move |
|---|---|
| Pages and design | Rebuilt page for page, then refined only where you agree to it. |
| Blog and pages | Moved from Squarespace’s export, with anything the export leaves behind recovered from the live site. |
| Galleries, products, and events | Recovered and rebuilt as structured content or moved to a dedicated service, case by case. |
| Forms and newsletter blocks | Rebuilt and connected to your CRM or email platform, tested to the inbox. |
| Commerce | Assessed honestly. Serious commerce usually moves to Shopify; light sales may not need a platform at all. |
| URL mappings | Carried into your host’s redirect rules and verified before launch. |
Your design, content, and URLs come with you.
The site moves page for page onto Astro or Next.js on Cloudflare, Vercel, or Netlify. We recommend the stack because we sell none of them.
- Design preserved and verified at representative pages and viewports
- Pages, posts, images, PDFs, and media
- URLs preserved where possible, every other one mapped with a 301
- Forms, CRM delivery, analytics, and consent, each tested end to end
- Your code in your own repository, on your own hosting account
- Dispatch connected at cutover, so every agent change is previewed and approved
Nothing gets designed until every URL has a plan.
The same six steps on every move, written down while we moved our own website. The boring part comes first, because the boring part is what protects your traffic and your leads.
- Step 01
Inventory every URL.
We crawl the live site and list every page by template before anything is designed or built.
On our own moveOur site: 49 live URLs across six templates, each with a destination before a line of code.
- Step 02
Keep the URLs.
Same paths, same slugs. An address only changes when a 301 redirect is in place for it.
On our own move44 kept their exact address. 5 retired pages got 301s. Our highest-traffic page never moved.
- Step 03
Export everything.
CMS content, every file on the old platform’s CDN, and the rendered HTML of every page as the reference copy.
On our own move549 files moved off the old CDN. 4 CMS collections, 45 items, imported and checked.
- Step 04
Parity first. Then improve.
The first version is a faithful copy: same pages, same copy, same metadata. Changes come after sign-off, so any traffic shift has one cause to look at, not ten.
On our own moveOur first complete build took one day, compared page by page against the original by screenshot.
- Step 05
Prove the business paths.
Forms, CRM delivery, notifications, analytics, and consent are tested end to end, from the visitor’s click to the right person’s inbox.
On our own moveLesson we learned: a form that saves a lead is not a form that tells anyone. We test to the inbox now.
- Step 06
Govern, launch, and watch.
Dispatch is connected before the agent touches production. Redirects go live at cutover, the sitemap is submitted, and 404s and indexing are watched closely.
On our own moveSince our launch: 36 reviewed changes in six weeks, each one previewed before release.
We moved our own website first.
wearezinc.com moved from Webflow to Next.js in August 2026, using the same six steps. Here is what that looked like.
- live URLs kept or redirected
- 49 of 49
- files moved off the old CDN
- 549
- to the first complete build
- 1 day
- reviewed changes in the first six weeks
- 36
When staying on Squarespace is the right call.
A move should pay for itself. Sometimes it will not, and we will tell you.
- Your site is a simple portfolio that rarely changes
- Commerce is central and the built-in store does the job
- Your team is happy with the editor and nothing is holding you back
See your Squarespace site without the template.
Give us your URL. We rebuild two pages on an agent-ready stack, run one real change through Dispatch, and send back a stack recommendation and a feature-by-feature migration map. No commitment.
Questions about leaving Squarespace.
No. Its export covers core pages and blog posts but leaves some content types and blocks behind. We inventory the live site first, use the export where it helps, and recover the rest so nothing is quietly lost.
Yes, two ways. Move first with the same design, then improve, which is safest for traffic. Or redesign and migrate together. Either way, the URL map and page signals are locked before design starts, so the redesign cannot break what ranks.
Not if the move is done with discipline. Rankings slip after a migration for three reasons: URLs that break, page signals that get dropped, and crawl problems after launch. We keep URLs wherever we can, redirect the rest one to one, carry over every title, description, and heading before changing anything, and watch 404s and indexing closely after cutover. Some fluctuation while search engines re-crawl is normal, so we do not promise unchanged rankings. We do promise not to guess.
You do. The code lives in your own repository, the hosting account and domain stay in your name, and the content is yours. Turn Dispatch off and the website keeps running.