How to Hand Off a Squarespace Site as Static Files Without Losing Essential Services

You can hand off a Squarespace site as static files when the recipient needs the published pages, design, assets, and client-side behavior—not Squarespace’s server-side services. The safe path is to export the live site, verify the static copy, and give every form, checkout, member area, search feature, and redirect an explicit owner before the DNS cutover.

You will need access to the published Squarespace URL, a destination host, and one person who can answer for each dynamic service. This workflow uses ExFlow’s Squarespace exporter, which exports the published pages, CSS, JavaScript, and media into a static package.

Aurora-lit Squarespace website package flowing into portable static hosting

1. Define what the handoff must preserve

Start with a short inventory. A static handoff is a good fit for a marketing site, portfolio, documentation site, or an archived campaign where the main job is to serve pages quickly and reliably. It is not a drop-in replacement for services that run on Squarespace’s servers.

List every public URL, navigation path, downloadable file, form, payment path, gated page, and search behavior. If you have CMS-like content such as blog posts, product pages, or galleries, include representative URLs from each type. A useful companion is this Webflow CMS URL inventory workflow: the platform differs, but the discipline of listing routes before export is the same.

Expected result: you have a route list and a named owner for the few behaviors that are not simply files.

2. Make a service-ownership ledger

Before exporting, label each feature as portable, replace, or retain. This prevents the common handoff mistake: a beautiful static copy that looks complete until a visitor submits a form or tries to check out.

Feature Static handoff decision Owner before cutover
Pages, blog posts, galleries, media Portable Hosting owner
Contact or newsletter form Replace with an endpoint or form provider Marketing/ops owner
Commerce checkout Retain or replace with the chosen commerce platform Store owner
Member areas and scheduling Retain or replace Product/operations owner
Site search Replace, remove, or document as unavailable Content owner
Old URLs Redirect at the new host Technical owner

ExFlow documents the same boundary: its Squarespace export can include rendered pages, styles, scripts, images, and other public assets, while server-run features such as form submissions, Commerce checkout, member areas, scheduling, and search need their own plan. Do not infer that an exported button equals a working backend.

Static website connected to separately owned dynamic services

3. Export the published Squarespace site

Open the Squarespace exporter and enter the published site URL or its custom domain. Enable CSS, JavaScript, images/media, and all pages. If the public site has a front-end password, provide it in the export settings; unpublished or fully private content should not be treated as part of a public-site export.

Run the export and download the ZIP, or connect the approved destination—Git, S3, FTP, or ExFlow Hosting—when the team wants repeatable deployments. ExFlow says it crawls the published site, gathers served assets, and rewrites links for local files; that is why the published URL, rather than an editor preview, is the right input.

Expected result: a dated export package with HTML, asset folders, and a file list that matches the scope you wrote in step 1. Keep the ZIP even if you deploy immediately; it is the rollback snapshot for the handoff.

4. Test the package before pointing the domain

Deploy the static output to a staging URL first. Test on desktop and a real phone, using the original inventory rather than only the homepage. Check these five things in order:

  1. Open representative pages from every route type and confirm images, fonts, and galleries load.
  2. Click primary navigation, footer links, buttons, and downloadable files; note every 404 or unexpected external jump.
  3. Test the contact flow, newsletter signup, cart/checkout links, account links, and search. Each should either reach its new owner or display the intentional replacement.
  4. Inspect titles, descriptions, social images, canonical URLs, and robots.txt/sitemap behavior at the destination.
  5. Add redirects for high-value old paths, then retest them with a private browser window.

Luminous export checklist for links assets metadata forms and redirects

For a compact testing pattern, borrow the animation and breakpoint pass from this Framer static-export guide. The specific effects differ, but a staged test beats discovering a missing asset after the domain moves.

5. Record the cutover decision

Use one short release receipt before DNS changes:

Export date: 2026-11-19
Static host: [host and project]
Test URL: [staging URL]
Portable pages checked: [count and route types]
Replaced services: [form, search, or other]
Retained services: [checkout, member area, or other]
Redirect owner: [name/team]
Rollback package: [ZIP or Git tag]

This is more useful than a vague “site migrated” note. It tells the recipient what works as files, what is intentionally delegated, and how to recover if the launch needs to be reversed. For a more hosting-focused decision, see how to choose static hosting without guessing; the host should match the team’s deployment and ownership model.

6. Cut over only after the ledger is green

When every row is portable, replaced, or deliberately retained, publish the static site and change the domain only after the staging checklist passes. Monitor the highest-value landing pages and conversion paths after cutover, then retain the dated package and release receipt with the client handoff.

Verified static site package passing through a deployment gate

ExFlow also offers dedicated exporters for Webflow and Framer, but keep this handoff platform-specific: Squarespace’s static copy is only one half of the delivery; the service ledger is the other.

A Squarespace static handoff succeeds when the receiving team gets a tested portable site plus clear responsibility for everything that cannot travel as a file. Start by making the ledger, run a staging export with ExFlow, and do not schedule DNS changes until each dynamic feature has an owner.