The short answer
You can leave Wix or Squarespace at any time, and you keep the things that matter most: your domain, your words, your photos and, if you do it carefully, your place on Google. What you don't keep is the site itself. Builder pages only run on the builder, so the new site is a rebuild, using your old content as the starting point.
The part that protects your search traffic is unglamorous: a list of every page address on your current site, a matching address on the new one, and a 301 redirect for every address that changes. Do that, and Google follows you to the new site. Skip it, and people who click your old search results land on an error page.
Moving isn't always the right call. If your builder site is doing its job and you enjoy running it, stay. Our platform comparison lays out when a builder is the better fit.
What moves and what doesn't
Here's every piece of a typical builder site and what happens to it in a move.
| Does it move? | How | |
|---|---|---|
| Your domain | Yes | It's yours if it's registered in your name. Keep it, and point it at the new site on launch day |
| Your words | Yes | Copy every page's text into a document you keep. Don't rely on the old site staying up |
| Your photos | Yes | Download them, or better, find the originals, which are usually sharper than what the builder serves |
| Blog posts | Yes, with work | Squarespace can export one blog in an .xml file meant for WordPress. Otherwise copy posts out one by one |
| The pages and design | No | Rebuilt on the new platform. A Wix site runs on Wix and a Squarespace site runs on Squarespace |
| Store pages and products | Mostly no | Squarespace's export leaves out store pages. Plan to set products up again |
| Form submissions and customer lists | Download them | Export whatever records you need before the old plan ends |
| Google rankings | Yes, if you redirect | Map every old address to a new one and set 301 redirects on launch day |
| Google Business Profile and reviews | Untouched | It's separate from the site. Update the website link if the address of your home page changes |
| Apps and add-ons | No | Replaced with whatever the new site uses: forms, booking, reviews, payments |
Squarespace export details are from Squarespace’s own help article, checked November 2026: it exports layout pages, one blog, text and image blocks and gallery pages, and does not export store pages, portfolio pages, index pages, extra blogs, product, video and audio blocks, or headers and footers. We couldn't confirm Wix's export options, so plan to copy Wix content out yourself.
The single most useful thing you can do before anything else: copy your content out now, into documents and folders you control. Text from each page, original photos, blog posts, testimonials, the answers on your FAQ. It takes an afternoon, and it means the move never depends on the old site staying up.
If you're leaving because you want a site you own outright, it's worth reading rent vs own first, so you know exactly what to ask the next provider about.
Before you start: check the domain and email
Two things trip up more builder moves than anything else, and both are about the domain, not the website.
- Where is the domain registered? If you bought it through the builder, it's registered through them. You can keep it there and point it at the new site, or transfer it to a registrar you choose. If someone else registered it, get it into your name first.
- Where does your email run? If your email is on Google Workspace or Microsoft 365, it's separate from the site, but its settings live in the same DNS. If the email was set up through the builder, find out exactly where it runs before anyone changes DNS.
- Who can log in? Make sure you can get into the builder account, the domain and the email admin yourself, not only a past designer.
Before any DNS change, export or screenshot every DNS record, especially the MX and TXT records your email depends on. Our domain, hosting and email guide explains each record and how to get control of a domain someone else holds.
How to keep your Google rankings
Google ranks pages, and it knows them by their address. When a page's address changes and nothing tells Google, the old address stops working and the ranking it earned goes with it. A 301 redirect is the instruction that says "this page has moved permanently, here's the new address." Google follows it and generally carries the old page's standing across.
What keeps a move safe:
- Keep the same domain. Changing the platform and the domain at the same time is two moves at once. Do one at a time if you can.
- Keep the pages that bring in traffic. If a service page ranks and brings calls, rebuild it with the same topic and at least the same depth. Better is fine. Thinner is risky.
- Redirect every changed address. Not only the main pages. Old blog posts, gallery pages and anything other sites link to.
- Send retired pages somewhere relevant. A retired service page should go to the closest service you still offer, not to the home page.
- Carry over titles and descriptions where they were working, and write proper ones where they were defaults.
- Tell Google. Submit the new sitemap in Search Console on launch day and check for errors over the next weeks.
Rankings can move around a little for a few weeks after any rebuild while Google recrawls the site. That's normal. Big, lasting drops nearly always trace back to missing redirects or pages that were dropped. If your site isn't ranking well now, a move is a good moment to fix why, and why you're not showing up on Google covers the usual causes.
Build the URL map
The URL map is a two-column list: every address on the old site, and where it goes on the new one. It's the most important document in the whole move, and you can start it yourself.
- Get every old address. Builders publish a sitemap at yourdomain.com/sitemap.xml. Open it and copy out every address. Add any you know get links from other sites, like an old promotion or a page printed on your truck.
- Check Search Console. If you have it set up, the Pages and Performance reports show which addresses Google knows and which get clicks. Those are the ones that must not break.
- Decide each page's fate. Keep it at the same address, move it to a better one, merge it with another, or retire it to the closest relevant page.
- Write the new address next to each old one. Use clear, short addresses with real words: /drain-cleaning, not /services-1.
- Turn changed rows into redirects. Every row where the address changes becomes a 301 redirect on the new site. Our free 301 Redirect Generator turns a list like this into redirect rules.
| Old address | New address | Why |
|---|---|---|
| /services-1 | /drain-cleaning | Builder page names often end up generic. Use the service name |
| /about-us | /about | Shorter, same page. Redirect it |
| /blog/spring-checklist | /blog/spring-checklist | Same address on the new site, so no redirect needed |
| /gallery-2 | /projects | Two old gallery pages merged into one |
| /old-promo | / | Page retired. Send it to the closest relevant page, not always the home page |
An example map for a small service business. Your real one lists every address in your current sitemap. Every row with a different new address becomes a 301 redirect.

The move, step by step
Here's the order that keeps your site, email and rankings intact. The builder stays live until the very end.
- Copy everything out. Text, original photos, blog posts, testimonials, form records. On Squarespace you can also run its export to get an .xml file of what it supports.
- Confirm access. Builder account, domain registrar, DNS, email admin, Google Business Profile and Search Console, all in your name.
- Verify Search Console at the domain level if you haven't, using a DNS record. That keeps your search data through the platform change.
- Build the URL map from your sitemap, as above.
- Plan and build the new site on a preview link, using your content as the starting point. This is the moment to fix the pages that weren't working.
- Set up the redirects from the URL map on the new site, ready for launch.
- Export the DNS records and lower the TTL a day ahead so changes take effect quickly.
- Launch. Point the domain at the new site, changing only the website records. Leave the email records exactly as they were.
- Run the launch day checklist below, then submit the new sitemap in Search Console.
- Keep the old plan running for a short overlap, then cancel the builder once everything is confirmed.
If the domain was registered through the builder and you want it elsewhere, move it as a separate step, after launch has settled. Doing one change at a time makes any problem easy to trace.
Launch day checklist
Go through this on the day the domain points at the new site. Our Website Launch Checklist has a longer version you can work through on screen.
Launch day checklist
- Every old address from the URL map either exists on the new site or redirects with a 301.
- The redirects are tested: paste a sample of old addresses into a browser and watch where they land.
- Page titles and descriptions are written for every page, not left as defaults.
- Forms send to the right inbox, and a test submission has arrived.
- Email still works: send a test in and a test out from an outside address.
- The site loads over HTTPS, with and without www.
- The new sitemap is submitted in Google Search Console.
- Your Google Business Profile links to the right page.
- Analytics or tracking is on the new site.
- The old builder plan is still active until all of the above is confirmed.
Timing: how long it takes and when to do it
A move has three parts: preparing (copying content, confirming access, building the URL map), building the new site, and the launch itself. Preparing takes most owners a few evenings. The build depends on who's doing it and how many pages there are. With us, most projects run two to four weeks from signed-off design direction, depending on size and how quickly we get your content. Launch day is short, but plan to watch the site, email and forms closely for the following week.
A few timing tips:
- Check your builder renewal date. Annual builder plans renew in a lump. Start early enough that you're not forced into another year, but don't cancel before the new site is live.
- Avoid your busy season. A landscaper shouldn't launch in May, and a snow removal company shouldn't launch in December. Pick a quieter month.
- Don't change the domain at the same time unless you have to. One move at a time.
- Give Google a few weeks to recrawl. Watch Search Console for errors, and fix any broken addresses you missed.
For a fuller picture of build timelines, see how long it takes to build a website.
What a move costs
There are three ways to move, and they cost very different amounts:
- Do it yourself to another builder or WordPress. Your time, plus the new platform's plan. Cheapest in money, and fine for a small site, as long as you do the URL map and redirects.
- Hire a freelancer or agency. Quoted per project. Ask whether the quote includes copying the content, the URL map and the redirects, because some don't.
- Have us rebuild it. A custom-coded site on our Launch plan is $2,200 (or $1,000 on a 12-month care term) with care from $199 a month, for up to 20 core pages. Standard is $3,600 with $249 a month care. The URL map, redirects and content move are part of the build.
Worked example
A home inspection company in Maple Grove has a twelve-page Squarespace site on Core at $29 a month billed yearly. It ranks for a few service searches, and the owner hasn't updated it in a year. Moving to our Launch plan on the 12-month term is $1,000 upfront, then $199 a month, replacing the $29 Squarespace plan once the overlap ends. So the monthly cost goes up by $170, and in return the edits, new pages and upkeep are done for them. The ranked service pages are kept at the same topic, and every changed address gets a redirect.
If the owner was happy updating it themselves, the cheaper move would be to stay on Squarespace and fix the pages. That's a fair choice too.
Our full prices are on the pricing page, and the care term explains the lower build price. More on the whole process in the redesign cost and process guide.
A real rebuild, described accurately
Most of the moves we handle start on Wix, Squarespace or WordPress, and the steps are the same whichever it is. One example from our own work: DMP Awnings, a custom trailer awning maker in Little Falls, came to us on WordPress, not a builder. We rebuilt it as a custom-coded static site with a gallery and quote requests. The same principles apply whatever the starting point: keep the domain, carry the content across, and give every changed page address somewhere to go.
If you're weighing up a move, our redesign page explains how we take over an existing site, or send us your current site and we'll tell you honestly whether moving is worth it.
Common mistakes to avoid
- Cancelling the builder first. The old site and its content vanish before the new one is ready.
- No redirects. The most common cause of lost traffic after a move.
- Sending everything to the home page. Redirect each old page to its closest match instead.
- Changing nameservers without copying email records. Mail stops arriving, often unnoticed for a day.
- Dropping pages that ranked. A tidy new site with fewer pages can quietly lose the searches the old one won.
- Moving the domain and the site on the same day. Two changes at once make problems hard to trace.
Want a straight answer for your business?
Every Stonekept build is custom-coded, hosted on Cloudflare and kept on a monthly plan. Prices are public: builds from $2,200 with care from $199/mo. See pricing or tell us about your project and we'll give you an honest read, even if that's not us.
