Website planning

What Should You Plan Before Changing Web Designers?

Plan a provider handoff around account access, backups, email, redirects, launch checks, and rollback before changing DNS or retiring old services.

Wild Article 019, 2026-11-12: What Should You Plan Before Changing Web Designers?

Before changing web designers, make sure your business controls the domain, DNS, email, hosting, website content, and key accounts, and that you have a complete backup. Then plan the switch in order: set up and test the new site, change DNS carefully so email keeps working, add redirects if any URLs change, and remove the former provider's access only after you have confirmed your own.

Wild Logic's website ownership checklist covers the account-by-account inventory. This guide covers the sequence and timing.

Start by confirming what you control

Start with an account inventory:

  • Sign in to your domain registrar account yourself. Confirm the domain is registered to your business and note the renewal date.
  • Find out where DNS is managed. It may be a different company from the registrar.
  • Confirm you have your own administrator login to hosting and the content management system.
  • Confirm your business has owner or administrator access to analytics and Google Search Console.
  • Read your contract for ownership, handoff, notice, and any fees tied to ending the relationship.

If the provider controls an account you need, agree on the handoff process, notice period, and responsibilities before making changes.

The domain: registrar, DNS, and whether to transfer at all

You may not need to move the domain

Changing designers rarely requires moving your domain to a new registrar. You can usually point the existing domain at new hosting by updating DNS. ICANN notes that you may be able to change web-hosting providers instead of registrars "to avoid the inter-registrar transfer process (and lock) altogether" (ICANN registrant FAQs). If the domain is already in your own account, leave it there.

If you do transfer: confirm the process first

Ask the registrar whether you need an account move, a change of registrant, or a transfer to another registrar. These are different operations. ICANN's registrant FAQ describes authorization codes and transfer lock periods that can affect a transfer. Confirm the rules for your domain and its current status before promising a date. Country-code domains can have different rules.

Protect email before touching DNS

Protect business email during a website switch. Your domain's DNS holds MX records that route email, and other records that verify services and help your mail get delivered. If someone replaces the DNS zone or moves nameservers without copying every record, email can stop.

Before any DNS change:

  • Export or screenshot every DNS record, not only the website ones.
  • Identify which records belong to email, which verify services (Google, Microsoft, payment tools), and which point to the website.
  • Change only the website records unless you are also moving email on purpose.

DNS changes also take time to spread. Google Workspace, for example, says MX record updates can take up to 72 hours (Google Workspace Admin Help). Google's hosting-move guide suggests lowering your DNS records' time-to-live (TTL) value ahead of the move so changes propagate faster (Google Search Central).

Get a complete backup and your content

Ask for a full backup before the relationship ends, and confirm what it contains: site files or code, the database, uploaded images and documents, and configuration. A code repository alone may not include your content or database. Store a copy in an account your business controls. The FTC advises small businesses to back up important files regularly and keep backups in the cloud or on an external drive (FTC). Also collect original logos, photos, and editable design files, and ask which fonts, themes, plugins, or stock images are licensed to the provider rather than to you.

Keep analytics and Search Console in your hands

Your traffic history lives in analytics and Search Console, and you will need both to spot problems after launch.

  • Google Analytics: make sure someone at your business has the Administrator role. Permissions depend on whether access is granted at account or property level; have an existing administrator confirm the scope you need (Google Analytics Help).
  • Search Console: verify your own ownership. Google's help says that if you are taking over a site, you can verify ownership and then unverify previous owners by removing their verification token (Search Console Help).

List forms and integrations

List every form, booking tool, payment link, chat widget, newsletter signup, and tracking script, and where each one sends data. These often depend on accounts, API keys, or email settings that the old provider set up. Plan to test each one on the new site.

Redirects: only if URLs change

If your page addresses stay the same and only the hosting changes, you do not need redirects. Google's guide for hosting changes is to prepare and test the new hosting, update DNS, monitor both old and new, and shut down the old hosting only when you are confident no one is still reaching it (Google Search Central).

If URLs change, map each old URL to its closest new page and use permanent (301 or 308) server-side redirects (Google). Google's site-move guide says to keep redirects "for as long as possible, generally at least 1 year," and to expect temporary ranking fluctuation while Google recrawls (Google Search Central). Search Console's Change of Address tool is for moving to a new domain or subdomain, not for hosting changes (Search Console Help). Wild Logic's guide to planning URL changes during a redesign covers URL mapping in more detail.

Pick a launch window

Choose a time when traffic and inquiries are usually low, when both the new provider and someone from your business are available for a few hours afterward, and not right before a busy season, a promotion, or a holiday. Avoid launching on the same day as other big changes, such as a new email provider.

Access: rotate and remove in the right order

Removing the former provider's access protects your business, but order matters:

  1. Confirm your own administrator access works on every account, using your own login and multi-factor authentication.
  2. Change shared passwords and move them into a password manager. CISA recommends long, random, unique passwords stored in a password manager (CISA) and turning on multi-factor authentication (CISA).
  3. Remove the former provider's user accounts, API keys, and verification tokens once the handoff is complete.
  4. Update recovery emails and phone numbers that still point to the old provider.

Do not remove the only working administrator account, and keep in mind that Google Analytics will not let the last Administrator remove themselves (Google Analytics Help).

Rollback plan and validation checklist

Before the switch, write down how you would go back: which DNS records to restore, and confirmation that the old hosting stays active until the new site is verified. After the switch, check:

  • The site loads on desktop and phone over HTTPS, without certificate warnings.
  • Key pages, menus, and downloads work.
  • Every form delivers to the right inbox, and the confirmation is accurate.
  • Email sends and receives, including from outside your domain.
  • Booking, payments, and integrations work.
  • Analytics records visits.
  • Redirects (if any) go to the right pages.
  • The new site is not blocked from search engines by leftover staging settings.

After launch

Keep the old hosting account active until you are sure no traffic reaches it, then cancel it and confirm no automatic renewals remain. Watch Search Console for crawl errors over the following weeks. Update your records of who owns each account and when each service renews.

A timeline you can adapt

A timeline you can adapt
PhaseTasks
Before handoffConfirm registrar, DNS, hosting, CMS, analytics, and Search Console access; read the contract
HandoffFull backup; content and licenses; DNS export; list forms and integrations; resolve domain transfer if needed
Before cutoverNew site built and tested; redirect map (if URLs change); lower TTL; rollback plan; launch window chosen
CutoverUpdate website DNS records only; run validation checklist
First weekRotate passwords; remove former provider access; monitor email and forms
First monthsWatch Search Console; keep redirects; cancel old hosting when safe

A low-pressure next step

Start with the inventory. Wild Logic's website ownership checklist lists what to confirm for each account, and it works whichever provider you choose next. Once you know what you control, the rest of the plan gets much simpler.

Evidence

Sources

  1. FAQs for Registrants: Transferring Your Domain Name - ICANNwww.icann.org · Retrieved
  2. Set up MX records for Google Workspace  |  Domain management  |  Google Workspace HelpGoogle · Retrieved
  3. Changing Your Web Hosting and SEOGoogle · Retrieved
  4. Cybersecurity for Small BusinessFederal Trade Commission · Retrieved
  5. Add, edit, and delete Analytics users and user groups - Analytics HelpGoogle · Retrieved
  6. Managing owners, users, and permissions - Search Console HelpGoogle · Retrieved
  7. Redirects and Google SearchGoogle · Retrieved
  8. Site Moves and MigrationsGoogle · Retrieved
  9. Change of Address tool - Search Console HelpGoogle · Retrieved
  10. Require Strong PasswordsCISA · Retrieved
  11. More than a PasswordCISA · Retrieved

A useful next step

Keep a useful record

Use the ownership checklist to organize the accounts and people involved in your site.

Open the ownership checklist