Squarespace and Wix are great until you realize you're paying $20–30/month for a site that costs $2.50 to host elsewhere. Here's how to migrate without breaking your domain, losing your content, or tanking your SEO. The whole thing takes 1–2 weeks if you're methodical.
When to consider migrating
Signals it's time:
- Monthly bill has crept above $20/month and you're not using half the features
- The site loads slowly and Google rankings have softened
- Their builder is fighting you on a design choice you really want
- You've outgrown the included store/scheduling and want to swap to specialized tools
- You want to own the source files (Squarespace and Wix don't really let you)
- Your business is on the LLC track and you want infrastructure that doesn't tie you to a single vendor
Signals it's NOT time yet:
- You hate one specific feature but otherwise the platform works fine
- You don't have time to manage hosting yourself and don't want to pay someone
- You're under $20k revenue and the $200/year savings doesn't matter
What you can vs. can't take with you
You CAN take:
- Your domain. Always — it's yours by law, regardless of who registered it.
- Your content — text and images (with effort)
- Your email if you're using Google Workspace through Squarespace's bundle
- Your SEO juice if you handle redirects properly
You CANNOT take:
- Themes/templates. Their proprietary CSS doesn't transfer. Practically: this is a rebuild, not a "copy."
- Built-in form submission archives — export them before you cancel
- Built-in store data (orders, customers) — varies by platform; export carefully
- Their analytics history — Squarespace/Wix analytics doesn't transfer. Start fresh in Plausible/GA4.
The 4-stage migration
Inventory your content
Before touching anything, build a list of what you have:
- Every page URL on the current site (use a free crawler like Screaming Frog or just walk the nav)
- Every image at full resolution (download them all)
- Every form submission you want to keep
- Your blog posts, exported as XML if possible (Squarespace: Settings → Advanced → Import/Export. Wix: no good export, plan to copy/paste)
- Anything you customized: custom code blocks, CSS injections, integrations
Choose new hosting
For most small businesses moving off Squarespace/Wix, the answer is Porkbun Static Hosting ($2.50/month). It's the cheapest real option, and it's where I send every client. Read our static hosting guide for the setup.
Other options:
- WordPress hosting (Bluehost, Cloudways, $10–30/mo) if you need a real CMS for ongoing content
- Netlify or Cloudflare Pages (free tier available) if you're technical and want git-based deploys
Rebuild the site
This is the part where you decide DIY vs. hire (see our guide on that). Either way:
- Match your existing URL structure where you can
- Preserve all the content (text, images, page hierarchy)
- Don't try to redesign everything at once — copy first, then improve
- Build it locally or in a staging subdomain so you can test before going live
Cutover (the DNS swap)
The actual migration moment. Plan it for low-traffic time (Sunday morning typically).
- 24 hours before: drop your DNS TTL to 300 seconds at Squarespace/Wix. This makes the swap cut over fast.
- Day-of: change A records to point at the new host (Porkbun's static hosting IP, or wherever)
- Within 5–30 min: SSL provisions on the new host (Let's Encrypt). HTTPS should resolve cleanly.
- Test thoroughly: homepage, every nav link, contact form (does it actually email you?), mobile
- Wait 48 hours before canceling Squarespace/Wix. Confirm the new site is solid; have the old one as a fallback.
Domain handling — two paths
Path A: Keep domain at Squarespace, point DNS elsewhere
Easier and faster. Your domain stays registered with Squarespace; you just change DNS records to point at your new host. The downside: you keep paying Squarespace for the domain (~$20/year, sometimes bundled into your plan, sometimes separate).
Path B: Transfer the domain to Porkbun
Saves money long-term and consolidates billing. The process:
- Unlock the domain at Squarespace (Settings → Domains → click the domain → Unlock)
- Get the auth/EPP code (Squarespace will email it to the registered owner)
- Initiate transfer at Porkbun: Domain Management → Transfer Domain
- Approve the confirmation email
- Wait 5–7 days for the transfer to complete
- Do this BEFORE the cutover if possible — domain transfers are slow and you don't want them stuck mid-migration
Email migration
Three scenarios:
- You're using Squarespace/Wix's basic forwarding (info@yourdomain.com → your gmail) — set up new forwarding at Porkbun (free), update at the same time as DNS
- You're using Squarespace's Google Workspace bundle — Workspace migrates with you. Update payment to direct-with-Google when you cancel Squarespace.
- You have a separate Workspace or Microsoft 365 — nothing changes. Just update MX records on your new DNS to keep email pointing at Workspace/365.
See our email guide if you want to switch provider while you're at it.
Squarespace-specific gotchas
_redirects file or hosting panel.Wix-specific gotchas
FAQ
Will I lose my SEO rankings?
Not if you redirect properly. Match URL structure where you can; set up 301 redirects for any URL that changes. Expect a 1–2 week dip in rankings during the transition while Google re-crawls; rankings typically recover.
How long does the whole thing take?
1–2 weeks for a small business site if you're focused. Content inventory: half a day. Rebuild: 3–5 days. Cutover and verification: a day. Domain transfer (if you do it): 5–7 days running in parallel.
Will my site be down during the switch?
If done right, no — there's a few minutes of cutover where DNS propagates, but most visitors hit one or the other (not both, not nothing). Old Squarespace/Wix site stays up until you cancel.
Can I keep my email address?
Usually yes — it depends on what email you're using. Workspace and Microsoft 365 follow you. Squarespace/Wix native email forwarding doesn't, but you can set up new forwarding at Porkbun.
What if my Squarespace/Wix site has weird custom code?
Make a list of every custom code block, CSS injection, and integration. Most are easy to recreate on a static site (often easier — no platform restrictions).