Protect the appointment path first
A redesign can wait. A booking failure cannot. Before moving a site, write down every route a customer uses to schedule: buttons on the site, links in email, links on social profiles, QR codes, Google Business Profile, and staff messages. Then identify which calendar is the real source of availability.
Many businesses keep the same booking provider during a website move. That can make the first launch safer because the calendar, customer records, and confirmation messages keep their existing home.
Sort each piece of the old site
| Piece | Stays | Moves | Must be tested |
|---|---|---|---|
| Domain name | It can stay at its current registrar. | Only move it when account ownership is clear. | Website and email records after any DNS change. |
| Booking calendar | Keep the existing provider when it works. | Move only with a customer and data plan. | Availability, confirmation, reminder, cancellation, and staff view. |
| Pages and images | Keep the facts and approved media. | Rebuild the pages for the new system. | Links, search titles, and contact details. |
| Forms and notifications | Keep the business inbox. | Replace the form setup. | Provider receipt, inbox delivery, and reply coverage. |
Use a controlled launch sequence
- Build and review away from the live domain. Check content, mobile layout, and the primary booking action before launch day.
- Run a test appointment under the provider’s rules. Confirm availability, confirmation, reminders, staff visibility, and cancellation. Cancel the test cleanly.
- Test the contact path. A browser thank-you message is only the first signal. Confirm the provider, inbox, and human reply path.
- Point the domain only after the test list passes. Keep a record of current DNS settings before editing.
- Check every public route after launch. Test the main button, old booking links, Google profile, and a phone-sized screen.
What to tell returning customers
Keep the booking wording familiar during the move. If the customer uses the same calendar, say so. If anything changes, explain the action in one sentence and keep the old link redirected or updated where possible.
Read the platform rules before exporting
Squarespace documents its current site export limits. Some content and features will need a planned rebuild, so export is a record of content rather than a promise that a new site will be identical.
Use the double-booking guide to map calendar ownership. The form guide covers the second common failure point. A custom website scope should name the test plan and handoff before the domain changes.
Talk to Little Fight.
Send a website link, an error message, or a few lines about the work. We’ll take a free first look and explain what we can help with.
9am–9pm Eastern. After hours, leave a message.