A Melbourne business owner sent me a Squarespace migration quote last month. Two pages, $14,500, a vague Gantt chart, no mention of the existing site at all. I asked the obvious question: did the agency log into the existing Squarespace account before quoting? They had not.

That's the norm, not the exception. Most migration quotes are estimates of a generic move, not assessments of a specific one. The result is that a few weeks into the build, the agency discovers something — orphaned blog posts that still rank, a member area nobody mentioned, eight years of redirects in the URL Mappings panel — and the timeline blows out or corners get cut.

My position: a proper Squarespace migration audit takes a day. Sometimes two. It costs the agency between $800 and $2,000 in time and it should be the first deliverable, not buried in the proposal. The eleven things below are what a real audit catches and why each one materially affects the quote, the timeline, or the SEO outcome.

The case for migrating (and the case against doing it cheaply)

Squarespace isn't a bad platform. For a single-person service business with a handful of pages and modest growth ambitions, it's genuinely fine. The hosting works, the templates are competent, the editor is one of the best in the builder category.

The reasons to migrate off are specific:

You've outgrown the structure. Squarespace's site structure is fixed: pages, collections, a member area, a store. Once your business needs a more complex content model — multiple service categories with reference fields, a custom directory, a partner portal — you're fighting the platform.
Page speed is a problem. A typical Australian small business Squarespace site lands in the 60 to 75 range on mobile Lighthouse. For sites that depend on Google traffic, that's a meaningful disadvantage against custom-built competitors hitting 95+.
The monthly cost has crept up. The Plus plan is $69 AUD/month, plus the agency you paid to set it up wants $200 to $400/month to maintain it. That's $3,200 to $5,600 a year for a managed Squarespace site, which makes a custom build with no monthly fees pay back in 18 to 30 months.
You don't actually own the front end. You own your content. You don't own the rendered HTML, the JavaScript, or the hosting. That's fine right up until it isn't.

If any of those describe you, migrating makes sense. What I'm arguing against is migrating without a proper audit, because the unaudited migration is what causes the 30 to 50 percent traffic drops you hear about.

What an audit should check

1. The real URL inventory

Squarespace doesn't expose a clean URL list anywhere in the admin. You have to crawl the live site with Screaming Frog (free for sites under 500 URLs) and cross-reference with 16 months of Google Search Console data to catch URLs that exist but don't appear in the sitemap, plus URLs that don't exist anymore but still receive backlink traffic.

For a typical small business Squarespace site, that's 30 to 150 URLs. For a Squarespace site with a Memberspace add-on or an active blog, it can be 500+. The audit produces a spreadsheet with every URL, its current ranking position for relevant terms, and the total clicks it's received in the last 16 months.

2. The existing URL Mappings

Squarespace's URL Mappings panel — found under Settings → Advanced → URL Mappings — often contains years of accumulated redirects nobody's looked at since the site was first set up. Some of these are still passing traffic. If the migration ignores them, the new site inherits broken inbound links from external sites that pointed at the old URLs the redirects were catching.

The audit exports this panel and figures out which mappings still matter. Anything with non-zero traffic in the last 12 months stays.

3. The actual content model

Squarespace pretends to have a clean content model and it does not. Pages, blog posts, products, events, and gallery items all behave slightly differently. Custom code blocks live inside pages. Some sites have content nested inside summary blocks that pull dynamically. A faithful migration has to replicate the dynamic relationships or the new site breaks the user journey that was working before.

The audit documents which content types exist, how many items of each, and which content is dynamic versus static.

4. Custom code injection points

Squarespace exposes three injection points: site header, site footer, and per-page custom code. Plenty of agencies use these to inject analytics, schema markup, custom CSS, or quirky JavaScript hacks. If the audit doesn't capture every injection, the migration will silently lose tracking, schema, or rendered behaviour.

The audit pulls the contents of every code injection and decides what's still needed.

5. Forms and form submissions

Squarespace forms either send to email, an external service like Mailchimp, or a connected Google Sheet. The audit needs to inventory every form, what endpoint each connects to, and what fields each captures. Common gotcha: a form that's been going to a deactivated Mailchimp list for six months and the business doesn't realise the enquiries have been disappearing into the void.

6. The SSL and domain setup

Squarespace handles SSL automatically via Let's Encrypt. The migration needs to plan for SSL on the new host (Vercel and Cloudflare do this automatically too) and the DNS cutover sequence. The audit confirms current DNS configuration — A records, CNAME records, MX records for email, TXT records for verification — so the cutover doesn't accidentally break email or third-party integrations.

7. The Squarespace-specific tracking

Squarespace's analytics is decent but locked. If the business has been relying on the built-in analytics rather than Google Analytics, the audit either backs that data up before migration (because you'll lose access when you cancel the subscription) or sets up GA4 properly on the new site to capture forward.

The audit also checks whether Google Search Console is verified for the property and what verification method (TXT record, HTML file, or Google Analytics) — because the verification doesn't carry across automatically when the site moves.

8. The actual structured data

Squarespace adds basic schema.org markup automatically but it's not always complete or correct. The audit captures what schema is rendered on each page type and figures out what's worth replicating versus what can be improved.

9. The Memberspace, Acuity, or third-party app dependencies

Squarespace ecosystems often include Acuity Scheduling, Memberspace, or a payment processor for products. These integrations don't migrate. The new site either rebuilds the integration or replaces it with something different. Either way, the audit needs to document which add-ons exist, what they cost monthly, and what they're handling.

10. The performance baseline

The audit captures current Lighthouse and Core Web Vitals scores so the new site has something to be measured against. A typical Squarespace site has LCP between 3.2 and 4.8 seconds on mobile, INP around 250 to 400ms, CLS around 0.05 to 0.2. The new build should beat all of these — that's literally the point — so the baseline is the proof.

11. The actual reasons traffic exists

This is the audit step almost nobody does. Pull the top 20 ranking keywords. For each one, look at what's on the page that ranks. Was it a long, useful piece of content? Was it the URL slug that exactly matched the search term? Was it three specific internal links from other pages? Without understanding why each page ranks, the new build can accidentally strip the thing that was working.

What the audit changes about the quote

Once the audit is done, the migration quote should look meaningfully different to a generic one. Specific line items that show up:

Custom code injection migration — explicitly costed because someone has to read the existing injection and decide what stays.
Third-party integration rebuild or replacement — Memberspace, Acuity, payment processor, each costed.
Form endpoint migration — every form's destination either preserved or replaced.
URL Mapping import — the legacy redirect rules need a new home.
Content model replication — the structure of the new CMS specifically matches what existed.
301 redirect map — every URL from the audit has a destination, in writing, before the build starts.

If the migration quote in front of you doesn't have these line items, either the agency hasn't audited the site or they're planning to discover problems mid-build and renegotiate.

The cost of skipping the audit

The unaudited migration causes one of three outcomes, sometimes all three. First, the timeline blows out — what was quoted as eight weeks becomes fourteen because of mid-build discoveries. Second, the SEO craters because the redirect map is incomplete. Third, post-launch you're paying for change requests to add the features the audit would have caught.

I've seen the change requests on a $14,000 migration push the final bill to $22,000. The audit would have cost $1,800 and prevented all of it.

What the audit produces as deliverables

A proper Squarespace migration audit produces six tangible deliverables that should be handed over at the end. These become the foundation documents for the build phase.

The URL inventory spreadsheet. Every URL, current ranking position, total clicks over 16 months, top three ranking keywords, planned destination on the new site, redirect type. This is the source of truth for the migration plan.

The metadata export. Title tags, meta descriptions, H1 headings, and any structured data for every page. This feeds directly into the new CMS as content is migrated.

The integration map. Every third-party service connected to the existing site, what it does, what it costs monthly, and the plan for whether it stays, gets rebuilt, or gets replaced. This determines whether the migration includes integration rebuild scope or not.

The redirect map. A working spreadsheet of old URLs to new URLs with redirect types, ready to be implemented as next.config.js redirects or equivalent on whatever platform the new site lives on.

The performance baseline report. Current Lighthouse scores, Core Web Vitals, page weights, and load times for the priority pages. The new site's performance gets measured against this.

The risk register. Specific items the audit identified that could affect the build — orphaned content with backlinks, integrations that don't have clean migration paths, custom code injection that needs replacing. Each risk has an owner and a mitigation plan before the build starts.

The audit isn't useful unless these documents exist. If the agency claims to have audited the site but can't produce these deliverables, the audit didn't happen in any meaningful way.

The honest version

Migrating off Squarespace is a sensible move for plenty of Australian businesses. The platform has limits, and growth eventually bumps against them. What I want to push back on is the idea that migration is a generic exercise where the agency can quote without looking at the site.

The audit is the difference between a migration that ships clean and a migration that bleeds traffic and budget. If you're scoping one and the quote doesn't include the audit as an explicit deliverable, ask for it as a separate paid engagement before you commit to the full build. Even if you take that audit to a different agency, it's the most valuable few thousand dollars you'll spend on the whole project.

Before you sign anything, get a read on what the existing site actually looks like under the hood. Drop your Squarespace URL into our audit and you'll get the performance baseline, the rendered SEO surface, and the specific accessibility gaps — in plain English, mobile and desktop. That's the same baseline a proper migration audit starts from, and it'll tell you immediately whether the agency you've been talking to has actually looked at the site they're quoting on.

Squarespace Migration Audit: 11 Things Agencies Miss