Minimizing Downtime: Manual Domain Migration Strategies for Squarespace Sites

25 Apr

This post may include affiliate links. If you buy through these links, I earn a small commission at no extra cost to you. This supports me in delivering useful content. Thanks for your support!

The Squarespace manual site migration process

1. Change the Built-In Domains

In my experience, when you’re working on two sites at a time it’s easy to accidentally make changes to the wrong site. One way of reducing this risk is to change the built-in Squarespace domain for each site. Use something like current-mysite.squarespace.com and new-mysite.squarespace.com.

I often give the new site a custom logo with BETA or STAGING in red letters so that I can easily visually confirm which version I’m working on.

2. Redirect Management

If the content structure of your new site differs from that of the old site you should also add URL mappings on the new site in the format:

/currentpagename -> /newpagename 301

Check out my URL mapping guide for a more detailed view of redirects.

You should also copy across any URL Mappings (Settings → Developer Tools → URL Mappings) from the current site to the new site.

URL mapping will help to maintain SEO rankings and user experience. Set up 301 redirects for all changed URLs to guide visitors and search engines to the correct pages on your new site.

Need help with a site migration?

Drop me a line or Schedule a free call

3. Ensure the new site has a paid subscription

Obvious really, and you can’t migrate the custom domain without it, but you’ll need a Squarespace paid subscription for your new site.

Check my guide to Squarespace promo codes and discounts to get the best subscription pricing. .

If you have an annual subscription on your current site that has a long time to run there may be a way of getting a pro rata refund. Contact me to find out how.

4. DNS Preparation

Before the migration, make Domain Name System (DNS) updates to ensure that changes propagate quickly during the transition, reducing the chance of downtime.

Go to your DNS provider and examine the Time To Live (TTL) values for the Squarespace related DNS entries (CNAME, A and possibly TXT records). Write down the highest TTL value and then change all relevant TTL values to the minimum allowable (probably 600).

5. Waiting Period

After adjusting your DNS settings, allow enough time for the changes to take effect globally. The TTL value you noted down is in seconds, so divide it by 360 to see how many hours you will need to wait. This waiting period ensures that once you switch over to the new site, the DNS changes have already propagated, reducing errors or access issues.

6. Preflight Checks

You’re now ready to move the domain over. I recommend soft launching the new site on its built in domain (behind a password) so that you can fully test it.

If you’ve created a custom logo (as per point 1 above) replace it with the proper version.
If you have ecommerce run some test orders.
Test your redirects.
Review this prelaunch checklist from the Squarespace Help Centre.

7. Domain Transfer

When your new Squarespace 7.1 site is ready, disconnect the domain from your current site and connect it to the new site. This critical step officially shifts traffic to your new site.

8. Expect Disruption

Despite careful planning, some disruption is inevitable due to DNS propagation. Until the DNS changes have propagated around the Internet some people will see the old site, some will see the new site and, annoyingly, some will see pages from both. The TTL changes you made will speed up propagation but can still take a day or so for everything to settle down.

Consider performing the transfer on a Friday so that the propagation has all weekend to stabilise.

Additional Tips:

Data Handling: Certain data types, like customer and member accounts, cannot be migrated directly between these versions and will require users to re-register on the new site. This is crucial for e-commerce sites where customer interaction is frequent.
Content Audit: Use tools like Semrush or SE Ranking to perform detailed audits of your site both before and after the transfer. This helps identify missing elements or broken links that can affect your site’s SEO performance.
Manual Content Transfer: For a manual migration, it’s advisable to prepare your content systematically. Organize text, images, and other media so that they can be easily moved to the new site layout, which might require different configurations due to the new 'sections' feature in 7.1.
Using Migration Tools: Tools like the SquarespaceWebsites Tools Extension PRO can automate some of the manual processes, saving time and reducing the risk of errors during content transfer.

By carefully planning and using the strategies outlined above, you can effectively manage the migration from Squarespace 7.0 to 7.1, minimizing downtime and maintaining a seamless user experience. Always ensure that you test the new site thoroughly before going live to prevent any potential issues that could affect your site’s performance and visitor satisfaction.

FAQs

What is manual migration in Squarespace? Manual migration refers to the process of manually transferring content and design elements from one Squarespace site to another, often used when automatic tools are unavailable or insufficient.
Why might I need to manually migrate my Squarespace site? You might need to manually migrate your site to update to a new version of Squarespace, to overhaul the site design, or to restructure the site for better performance and SEO.
What are the first steps in manually migrating a Squarespace site? Begin by planning your site structure on the new site, then manually copy and paste content such as text, images, and video. Ensure you have backups of all data before starting the migration.
How can I ensure my SEO isn't affected by migration? Maintain URL structures where possible, use 301 redirects for changed URLs, and update your metadata and sitemap post-migration to minimize impacts on SEO.
Can I migrate my Squarespace site to another platform manually? Yes, manual migration to another platform involves exporting your Squarespace content (where possible), then importing it into the new platform, and adjusting design and functionality to match the new environment.

Why a manual Squarespace site migration might be necessary or desirable

Squarespace 7.0 to 7.1

Squarespace recently released a native tool to help users upgrade & migrate a Squarespace website from version 7.0 to 7.1. However, this tool has some limitations:

It’s not suitable if you will be making content structure changes as well as style changes. The pages editor is locked for the 7.0 and 7.1 version of the site while the migration is performed.
It only works for sites using the Brine or Bedford template families
It is not suitable for very large sites with over 100 pages
Using the tool involves some downtime while the migration is in progress

If your 7.0 site doesn't meet the requirements, or you want to avoid downtime, you'll need to migrate your content manually. This checklist also applies if you're redesigning an existing 7.1 site.

Squarespace 7.1 template change

Unlike previous versions, Squarespace 7.1 operates on a unified template system rather than multiple distinct templates. This structure restricts the capability to switch to a traditional "new theme" and requires using built-in style and design options for any significant changes.

Live Changes: It takes significant time to apply a new theme to a live Squarespace 7.1 website. Unlike Squarespace 7.0 there are no downloadable Style Packs that can be used to instantly update the look and feel of the site. You'll be making live changes that are visible to visitors. This will compromise the user experience, as visitors might see a site under construction with potential design flaws and functionality issues.
Holding page: There is the option to put up a holding page while you apply the style changes. However, this will introduce potentially significant downtime while the update is applied and tested. This is not acceptable to many site owners.
No way back: There is no straightforward way to revert to the original design if the new changes fail, which further risks your site's stability and professional appearance. The only rollback option is to manually reapply the original design, and that is unlikely to go smoothly.

Bearing the points above in mind, creating a new Squarespace trial and manually swapping from your current site can be the least disruptive strategy.

Colin Irwin

I’m Colin Irwin, a freelance Squarespace Designer & Developer based in London, UK, with clients in the USA and around the world.

I’m a recognised Squarespace expert. I design and build Squarespace sites for everyone from charities and start ups to major established brands.

https://www.silvabokis.com