121 Group
⚖️ Prepared for Matthew Eddy • v1.0 • 4 May 2026

Squarespace → WordPress
Migration Proposal & Feasibility Study

Your site is small enough to migrate cleanly, big enough to justify the move, and the content strategy we're about to roll out in Month 2+ will be fundamentally capped if it stays on Squarespace. This document is the evidence, the plan, and the price.

URLs audited
196
Live crawl · 4 May 2026
Published articles
32
Across 4 collections
Contact profiles
166
164 opted-in to marketing
Feasibility risk
LOW
Content-only, no commerce
Fixed fee from
$18,500
AUD ex-GST · Option 1
Go-live
6–8 wks
From sign-off
Executive Summary

One decision, two futures

Everingham Legal currently runs on Squarespace 7.1. It's a content-led brochure + thought-leadership site — no e-commerce, no members area, no gated transactions. The platform works today. The question is whether it works for what comes next.

Proceed with migration — but frame it as a Month 2–3 strategic project, not an emergency. The business case is content scale, SEO control, AI/automation readiness, and a materially lower long-term TCO. The Phase 2 growth engagement we're about to deliver is API- and automation-intensive. Squarespace is, by design, closed to that pattern.
MetricSquarespace (stay)WordPress (move)
Content-editing automationUI onlyFull REST + CLI + Git
Programmatic SEO capabilityNoneNative
Custom functionalityLimitedUnlimited
3-year platform + hosting cost (AUD)~$1,260~$2,060
Migration one-off investment (AUD ex-GST)$18,500–$27,500
Go-live from sign-off6–8 weeks
Expected organic-traffic impact @ 6moflat+15–35%
Content-ops velocity (posts/month)5–6 (current pace)20–30 achievable
Feasibility riskLOW
Current State Audit · evidence base

What's actually on everinghamlegal.com today

All figures below come from a live audit on 4 May 2026, via (a) the Squarespace Developer API key 121 Agent, (b) a crawl of /sitemap.xml (196 URLs), and (c) HTML inspection of every sitemap URL. Raw data available on request.

Platform

Squarespace 7.1

Site ID68598842a03f32330b164646
Identifiersquid-emu-s7rl
Domaineveringhamlegal.com (apex + www)
Currency / localeAUD / en-US / Australia/Sydney
Commerce activity0 products · 0 orders · 0 customers
Detected planBusiness or Commerce Basic
Integrations detected

Tracking & third parties

  • Calendly — booking widget
  • HubSpot — tracking & likely forms capture
  • reCAPTCHA — forms protection
  • LinkedIn Insightpx.ads.linkedin.com
  • ⚠️ GTM / GA4 / Meta Pixel — to verify in Config

Content inventory

Content typeCountTotal wordsNotes
Static pages (home, about, contact, services, landing pages)3825,538Services, Capabilities, Lawson Intelligence, 4 segment pages, AI Readiness Pack, ebook, workshops
Blog articles (og:type=article)3233,675Across 4 topic collections
Auto-generated tag / category / index pages~126~35,000Mostly thin — regenerated by WordPress
Total URLs crawled196~93,773per sitemap.xml
Image references~670Hosted on images.squarespace-cdn.com · must be re-hosted
Contact profiles166164 opted-in · 98% growth Dec 2025 → Mar 2026

Content architecture — 4 topic collections

CollectionArticlesCategory/tag pagesTrajectory
/legal-technology/*1340Fastest-growing · includes AI Terminology (5,883 words), Claude Guide (3,280 words)
/legal-process/*1043Operationally-focused long-form
/legal-skills-and-coaching/*838People / hiring / culture
/law-firms-marketing-growth/*15new channel opened for 121 Group's Phase 2 work

Top 5 most valuable pages (by depth)

URLWordsImgsRole
/legal-technology/ai-terminology5,8832Flagship pillar — ranking asset
/legal-technology/claude-guide3,28020Instruction guide — high intent
/legal-process/blog-post-title-four-52x572,6422"How Manufacturing Changed Legal Process Forever" — default slug, SEO leak
/legal-technology/10aitermslegalshouldknow1,7952Companion to pillar
/legal-process/process-optimization-competitive-differentiator1,6612Top-funnel

Several article slugs are Squarespace defaults (e.g. blog-post-title-four-52x57) — these are actively hurting SEO and will be fixed during migration. Free win.

Why Squarespace caps the strategy

The platform is fine. The strategy won't fit.

We tested every relevant Squarespace API endpoint with the 121 Agent developer key on 4 May 2026. The limitations below are not workarounds, not fix-able, not “coming soon.” They are architectural.

Hard limitations of the Squarespace API

Capability needed for Phase 2+API supportImpact
Create / edit / publish blog posts programmaticallyno endpointBlocks AI-assisted publishing, batch rollouts
Edit page copy / headings / CTAs via scriptno endpointBlocks A/B testing, programmatic landing pages
Manage navigation / menusno endpointManual only
Upload / manage imagesno endpointManual only
Manage SEO meta (title, description, canonical)no endpointBlocks programmatic SEO
Manage forms / form logicno endpointEvery form built in UI
Version control / rollbacknoneNo change history to audit
Staging environmentpreview onlyNo safe "test before publish"
Custom data models (Lawyer, Case Study, Industry)noneShoehorn into 4 built-in types
Custom backend logic / server integrationsclient-side onlyCode Injection runs in browser, not server
AI content generation pipelinesUI onlyCannot scale content with LLMs
1
Template rigidity soft
Structural page changes mean rebuilding in the block editor. No component reuse across pages. Every "new service page" starts from zero.
2
SEO tooling ceiling soft
Relies on Squarespace defaults plus manual meta. No structured-data templates, no programmatic schema.org, no automated internal linking.
3
Platform lock-in soft
Content, templates, URLs and media are Squarespace-native. Migration gets harder — and more expensive — every year you wait.
4
Analytics depth minor
Built-in analytics are thin. You've already added HubSpot + LinkedIn Insight, but GTM-driven event tracking is constrained by Code Injection limits.
What Squarespace is good at (and we'll keep using until cutover)
  • Low-skill editorial workflow — Matt can publish today without a dev.
  • Fine for 5–10 posts/month content cadence.
  • Handles SSL, DNS, uptime, backups without touching anything.

None of those advantages are unique to Squarespace. A well-built managed WordPress stack gives you all of them, plus the capabilities above.

Target State

WordPress, built for Phase 2

Not stock WordPress. A purpose-built, managed, Git-deployed, headless-ready stack that matches the ambition of the marketing engagement.

Recommended stack

LayerChoiceRationale
CMSWordPress 6.x (self-hosted)40%+ of the web · open source · huge ecosystem
HostingKinsta (AUS region) or WP Engine APACManaged, Cloudflare-backed, staging + Git, daily backups, PHP 8.3
ThemeCustom child theme of GeneratePress or KadenceLightweight, fast, block-editor first — avoids Elementor/Divi bloat
Page builderNative Gutenberg + ACF blocksAPI-addressable, version-controllable, no proprietary lock-in
SEORank Math ProSchema.org control, programmatic meta, content-AI hooks
FormsFluent Forms (or keep HubSpot embed)API-driven, HubSpot/Zapier/Webhook native
Caching / perfCloudflare APO + host-level RedisSub-200ms TTFB at APAC edge
SecurityWordfence + host WAF + 2FA + auto-updatesQuarterly audit included
CI/CDGitHub → Kinsta staging → productionEvery template change reviewable as a PR
BackupsHost daily + weekly off-host to 121 Group S330-day retention · 1-click rollback

Content models — custom post types

WordPress CPT / TaxonomyMaps from SquarespaceNew capability unlocked
post (Insights)All 4 /legal-* collectionsUnified blog with categories + tags (preserves current taxonomies)
service/transformation-partner, /legal-consultant, /fractional-growth-officerTemplated service pages, easy to add
segment5 team-size + in-house pagesIndustry/size landing pages
resource/ebook, /ai-readiness-pack, /legal-ops-tech-scorecardGated downloads tied to HubSpot
case_study newNew content type for Month 2+
workshop new/ai-innovation-workshop, /ai-discovery-decision-readiness-workshopEvent-like structure with scheduling
Feasibility Study

Technical risk: LOW

Scoring the 12 classic migration risk factors for this specific site. Content-only · 1 editor · no commerce · modern CMS to modern CMS — near-ideal migration profile.

Risk factorWeightRiskEvidence
Site sizeHighLOW196 URLs, 94k words — tiny by migration standards
Commerce migrationHighN/A0 orders · 0 products · 0 customers
User accounts / members areaHighN/ANot present
Custom backend integrationsMedLOWHubSpot + Calendly only — both embed-based
URL preservationHighMEDIUMSome auto-slugs must be fixed · 301s for 32 articles + 38 pages
Media re-hostingMedLOW670 image refs, all downloadable from Squarespace CDN
Forms migrationMedLOW≤ 6 forms (Contact, Online Enquiry, Newsletter, Ebook, etc.)
SEO preservationHighMEDIUM32 articles have ranking signals — careful 301 map + schema parity
Analytics continuityMedLOWRe-add GTM / HubSpot / LinkedIn Insight in WP head
DNS / email impactHighLOWOnly A/AAAA change · MX stays (Google Workspace)
Training / adoptionMedLOWMatt is only editor · Gutenberg ≤ 1 hour training
Rollback pathHighLOWSquarespace kept active 90 days post-launch as hot fallback

Migration approach

Step 1
Automated extraction
Week 3
  • Squarespace Import/Export → WordPress XML (preserves categories, tags, dates)
  • Custom crawler for static pages → WP REST API
  • Squarespace API /profiles → HubSpot (already proven — pulled 166 today)
Step 2
Media pipeline
Week 4
  • Walk every images.squarespace-cdn.com URL
  • Download, upload to WP Media Library
  • Rewrite all references
  • ~2 hours scripted for 670 assets
Step 3
Redirect map
Week 5
  • Every old URL → new URL
  • Implemented at Cloudflare edge (zero-latency 301s)
  • Not in PHP — avoids WP overhead
Step 4
SEO parity QA
Week 6
  • Title / meta / canonical / H1 / schema checked per URL
  • Search Console change-of-address pre-staged
  • Pre-migration snapshot of top queries

Risk register

RiskLikelihoodSeverityMitigation
SEO ranking dip post-cutoverMediumMediumFull 301 map at edge · preserve URL shape · Search Console change-of-address · pre-migration query snapshot
Article formatting drift (Squarespace → Gutenberg)MediumLowAutomated markdown pass + visual QA on 32 articles (2 hrs)
HubSpot form cutover breaks lead flowLowHighRebuild forms first in WP staging · parallel run 7 days before DNS flip
Calendly embed breakageLowLowEmbed code is portable · 15-min task
Domain / email downtimeVery lowHighOnly A/AAAA change · MX untouched · 5-min TTL on cutover
Client change-of-mind post-launchLowMedSquarespace subscription kept active 90 days as failsafe
Matt's learning curveLowLow60-min handover · recorded Loom · quick-reference PDF
The site is near the ideal migration profile — content-only, small, modern-CMS-to-modern-CMS, 1 primary editor. The real question isn't "can we?" — it's "when, and in what shape?"
Scope of Work · Deliverables

What we build, in four phases

Phases run over 6–8 weeks depending on the option chosen. Phases C (content) and B (build) overlap.

Phase A
Discovery & design
Week 1–2
  • Current-state audit (this document)
  • Content & URL mapping sheet (196 URLs → new structure)
  • IA review workshop with Matt (90 min)
  • Design direction chosen (Option 1/2/3)
  • Technical architecture doc
Phase B
Build
Week 3–5
  • WP staging site on Kinsta
  • Custom child theme matching chosen design
  • 4 CPTs + associated taxonomies
  • Gutenberg block patterns (top 6 page sections)
  • Rank Math + schema.org for Article/Service/Org/Person
  • Forms + HubSpot integration verified
  • Calendly + LinkedIn Insight + GA4/GTM + Meta Pixel
  • Perf baseline: PageSpeed mobile ≥ 85, LCP ≤ 2.5s
Phase C
Content migration
Week 4–6 · parallel
  • 32 articles imported, reformatted, images re-hosted
  • 38 static pages rebuilt using block patterns
  • 670 images migrated
  • 166 contact profiles exported → HubSpot tagged list
  • Full 301 redirect map at Cloudflare edge
Phase D
QA, launch, handover
Week 6–8
  • SEO parity QA (per URL)
  • WCAG 2.1 AA accessibility pass
  • Cross-browser + mobile device QA
  • Lighthouse + Core Web Vitals report
  • 7-day parallel forms run
  • DNS cutover (≤15 min, Saturday AEDT)
  • Search Console change-of-address + sitemap
  • Handover: 60-min + recorded Loom + PDF
  • 30-day post-launch monitoring
Out of scope (initial migration)
  • ✗ Brand redesign (+$8.5–15k if needed)
  • ✗ New functionality (member area, LMS, portal)
  • ✗ Content rewriting / new content production (sits in ongoing retainer)
  • ✗ Non-WordPress integrations (Salesforce, custom CRM)
Client responsibilities
  • → Single decision-maker (Matt) for approvals
  • → Brand assets (logo SVG, fonts, colours, photo library)
  • → HubSpot admin access
  • → Cloudflare DNS access (or delegate authority)
  • → Google Search Console ownership
  • → Sign-off on redirect map + staging site before cutover
Pricing · AUD ex-GST

Three options — pick one

All fixed-fee. Payment 40% on kickoff, 30% on staging approval, 30% on go-live. Ongoing maintenance is covered by the existing Month-to-month retainer — no separate "WordPress care plan" needed.

Option 1
$18,500
6 weeks · like-for-like
  • Preserves current design
  • Phase A Discovery — $2,500
  • Phase B Build — $8,500
  • Phase C Content migration — $4,500
  • Phase D QA, launch, handover — $3,000
  • All risk mitigation included
  • 30-day post-launch monitoring
Option 3
$27,500
8 weeks · full growth engine
  • Everything in Option 2
  • case_study CPT + template
  • Resource-gate flow → HubSpot nurture
  • Programmatic-SEO landing page template
  • Blog-to-lead CTA engineering
  • Schema.org FAQ + HowTo templates
  • Ready for Month 2+ ramp on day 1

3-year TCO comparison

Cost itemSquarespace (stay)WordPress (move)
Platform subscription~$1,200 (3 yr @ $33/mo Business)$0 (open source)
Managed hosting (Kinsta Starter, APAC)~$1,400 (3 yr @ ~$40/mo)
Premium plugins (Rank Math Pro, ACF Pro, Fluent Forms Pro)~$600 (3 yr)
Domain$60$60
3-year run-rate total~$1,260~$2,060
One-off migration (Option 2)$25,500
One-off Squarespace customisation over same period (estimated)$5,000–$15,000$0 (in build)

Run-rate delta is ~$800 over 3 years — commercially trivial. The real cost is the one-off migration; the real benefit is unlocking Month 2+ strategy.

Timeline

8 weeks, zero drama

Weeks are sequential for the activity-column; some phases overlap (content migration runs in parallel with build QA).

WeekActivityPhaseMilestone
W0Sign-off + kickoff callProject begins
W1Discovery · IA workshop · content mappingAMapping sheet v1
W2Architecture + design direction lockedADesign sign-off
W3WP build starts · CPTs + theme · migration scripts draftedB / CStaging URL live
W4Content migration scripts run · articles importedCAll 32 articles in staging
W5Forms + integrations · staging review #1B / CReview checkpoint
W6QA · 301 map · staging review #2 · parallel-forms runDGo / no-go decision
W7(Options 2/3 only) Design refresh finalisationBPixel-perfect approval
W8Cutover (Saturday AEDT) · handover · Search Console change-of-addressDLIVE
W8+30-day monitoring · SEO watchlist · bug-fix windowDRetainer hand-off
Decision Framework

Five questions for Matt

If you agree with ≥ 3 of the statements on the left — migrate. If ≥ 3 on the right — stay put. Based on what you've described of the Phase 2 growth ambition, we strongly lean left.

Move to WordPress if ≥ 3 true
  • 1. Content cadence needs to go from ~5/month to ≥ 15/month within 6 months.
  • 2. AI-assisted content production should be part of Month 2–3.
  • 3. SEO is a primary pipeline source — we want programmatic control.
  • 4. Prefer to invest once in a platform you own vs renting a closed one.
  • 5. Want flexibility to add case-study hub / resources / member area later without a rebuild.
Stay on Squarespace if ≥ 3 true
  • 1. Matt publishes everything himself and prefers a visual editor over any editorial workflow.
  • 2. Content will stay at ≤ 5 posts/month for the foreseeable future.
  • 3. Organic/SEO is a lower priority than paid or referral channels.
  • 4. No plan to add structured content types (case studies, industries).
  • 5. The ~$800 saving over 3 years matters more than the $18.5k one-off.
"Hyper growth for a professional services firm" is what you said you want. That phrase, combined with ambitions for AI-driven content and programmatic SEO, tells us the answer is Option 2 — migrate with a light design refresh — and do it as a Month 2–3 project.
What changes for you, day-to-day

Same ease of use, way more headroom

Matt, day-one after launch, this is what is identical and what is better.

TaskToday (Squarespace)After (WordPress)
Publish a blog postSquarespace editorGutenberg (very similar UX)
Edit a service pageSquarespace editorGutenberg + locked block patterns (safer)
Update a menuSquarespace UIWP Menus UI
See contact form submissionsSquarespace UI + HubSpotHubSpot only — single source of truth
Add a new pageSquarespace UIGutenberg UI
Add an imageSquarespace uploadWP Media Library upload
Roll back a bad editnot possibleone-click restore
Test a big changelimited previewfull staging clone
A/B test a headlinenot possiblesupported
Publish 20 posts in a week via AInot possiblesupported
Next Steps

From here to signed SOW in 4 moves

1
Matt reviews this document
Target: end of week of 5 May 2026. Flag any obvious gaps or concerns for the call.
Time
~30 min
2
30-min walkthrough call
Q&A, confirm preferred option (1 / 2 / 3), resolve any scope questions.
3
Sign SOW referencing chosen option
Fixed fee, fixed timeline. 40% deposit triggers kickoff.
Value
$18.5–27.5k
4
Week 0 kickoff
Scheduled the Monday after sign-off. IA workshop in Week 1, staging live in Week 3, go-live Week 6–8.
Go-live
6–8 wks