You know the current website relationship is not working, but changing providers feels risky. The old designer may control the domain, hosting, email, forms, or analytics. You may not know what was purchased in your name, what can be transferred, or whether a change will make the website disappear.

That uncertainty keeps many small-business owners stuck longer than necessary. Switching web designers should be a controlled handoff, not a leap into the dark. The safest approach is to identify every account, preserve the current site, separate website changes from email changes, and agree on a launch plan before anyone touches live settings.

I am Casey Keown, the Grayson County resident behind Twin Lakes Web Co. I work directly with local businesses and organizations on website design and development. If you are trying to learn how to switch web designers, this is the checklist I would use to protect the business first.

Start With the Reason You Want to Change

A new designer cannot fix a problem that has not been defined. Write down what is failing in practical terms.

Common reasons include:

  • Updates take too long or never get completed
  • The website looks dated or works poorly on phones
  • Nobody can explain the recurring charges
  • The business does not control important accounts
  • Leads are not reaching the right person
  • The site is difficult to edit or maintain
  • The designer has stopped responding
  • The business has outgrown the current platform

Separate relationship problems from website problems. Slow communication may be solved with a clearer support agreement. A broken mobile layout, inaccessible forms, poor service pages, or an unsupported platform may require a rebuild. My website redesign guide explains when a full replacement makes sense and when focused repairs may be enough.

This first step also gives the new provider a real goal. "Make it better" is vague. "Preserve our search traffic, simplify quote requests, and give us control of the domain" is a useful project brief.

Build an Account Inventory Before Giving Notice

Do not begin by canceling services. First, learn what the current website depends on and who controls each part.

Create an inventory of:

  • Domain registrar
  • DNS provider
  • Website hosting
  • Content management system or website builder
  • Business email provider
  • Form delivery service
  • Google Analytics
  • Google Search Console
  • Google Business Profile
  • Image, video, font, and plugin licenses
  • Online booking, payment, or ecommerce accounts
  • Social media and directory logins connected to the site

The domain, DNS, hosting, and email may all be with different companies even when one invoice appears to cover everything. My small-business hosting guide explains how those services fit together.

For every account, record the login email, owner, billing contact, renewal date, multi-factor authentication method, and recovery process. Do not send passwords through ordinary email. Use account invitations or a secure password manager when access must be shared.

Confirm Who Owns the Domain

The domain is the public address for the website and often the foundation for business email. Losing control of it can affect both.

Sign in to the registrar and confirm that the business has administrative access. Check the registrant contact, recovery email, renewal status, and payment method. If the current designer registered the domain, ask whether the business is listed as the registrant and how control will be transferred.

The ICANN Registrant Rights and Responsibilities explain that registrants should receive information about pricing, renewals, support, and domain transfers. Do not wait until a contract ends or an account is closed to ask these questions.

Changing designers does not normally require changing the domain. A new website can launch at the same address. Keeping the established domain avoids unnecessary changes to email addresses, printed materials, customer bookmarks, and incoming links.

If you are still sorting out registration and renewal details, use my guide on choosing and managing a business domain as a companion checklist.

Protect Email Before Changing DNS

The website and business email may share the same domain, but they are separate services. A DNS change made for the website can interrupt email if mail records are removed or replaced.

Before anyone edits DNS, document the existing records. Identify the email provider and confirm which records it requires. Test incoming and outgoing email before the change, immediately after the change, and again after DNS updates have had time to spread.

Make a list of every address that matters, including individual mailboxes, shared inboxes, aliases, and forwarding rules. Confirm that contact forms deliver to a monitored address.

If the project does not require an email migration, leave email in place. Moving the website and moving email at the same time creates more ways for the handoff to fail. Handle each change separately unless there is a clear reason and tested plan to combine them.

Save a Complete Copy of the Current Site

Before editing or replacing anything, preserve what exists. A backup should include more than screenshots.

Depending on the platform, collect:

  • Website files and database
  • Page copy and blog posts
  • Original images, logos, and downloadable documents
  • Form settings and recent submissions, when appropriate
  • Redirect rules
  • Page titles and meta descriptions
  • Current URL list
  • Analytics and Search Console access
  • Plugin, theme, and platform information

A screenshot can show how a page looked, but it cannot restore a database, recover a form workflow, or preserve page addresses. Ask whether the backup has actually been tested or can be restored.

Some hosted builders do not provide a complete portable export. In that case, the new designer may need to rebuild the site while manually preserving content and URL structure. That limitation should be identified before the old subscription is canceled.

Preserve Search Visibility During the Handoff

An established website may already have pages indexed by Google, links from other sites, and search queries that bring potential customers. A redesign should improve the experience without carelessly discarding those signals.

Export or record the current page addresses. Match every useful old URL to its new equivalent. If an address must change, add a permanent redirect to the most relevant replacement. Do not send every removed page to the homepage.

Google's site move guidance recommends mapping old URLs to new ones, testing redirects, checking canonical tags, submitting the new sitemap, and monitoring both versions. That guidance is especially important when changing domains, but the same careful URL planning helps during any major rebuild.

Keep these items consistent where possible:

  • Primary domain and preferred www or non-www version
  • Important service and location page URLs
  • Page purpose and useful content
  • Canonical tags
  • Title and heading relevance
  • Internal links
  • Contact and business information

Do not add a noindex tag to the live site by accident. Staging sites should be protected from indexing, then checked again before launch. After publication, inspect key pages in Google Search Console and verify that the sitemap contains the correct addresses.

Transfer Analytics and Business Tools Properly

Historical data is useful when judging whether the new site helped. Creating fresh analytics accounts can separate the business from its earlier measurements.

Whenever possible, add the new provider as a user to the existing Google Analytics and Search Console properties instead of sharing the owner's Google password. The business should retain an owner-level account that is not tied solely to a vendor.

Do the same for the Google Business Profile. Add an appropriate manager or owner through the platform's access controls. Do not hand over the primary personal account just because someone needs to update the website link.

Review other connected tools, including booking systems, payment processors, newsletter platforms, call tracking, and form services. Remove the former provider's access only after the transition is complete and the business has confirmed that nothing still depends on it.

Understand What Can Be Reused

Do not assume that everything visible on the old site belongs to the business or can be moved freely. Review the agreement and licenses for the design, code, photos, fonts, themes, plugins, and stock assets.

The business should receive original materials it paid to own. Subscription themes, hosted-builder templates, and licensed stock images may have restrictions. Custom code may also be governed by the contract.

Ask the new designer to separate three categories:

  1. Assets the business owns and can reuse
  2. Licensed items that need to be purchased again
  3. Platform-specific parts that must be rebuilt

This prevents a launch-day surprise and makes the proposal more accurate. My website ownership checklist covers the questions a business should ask about domains, accounts, content, source files, and ongoing access.

Plan the Launch Before the Old Site Is Canceled

A responsible launch plan identifies who changes DNS, when the change happens, how the team tests the site, and what happens if something breaks.

Before launch, verify:

  • The new site works on phones and common browsers
  • Forms reach the correct inbox and show a useful confirmation
  • Phone numbers, addresses, hours, and service areas are accurate
  • Every important old URL has a matching page or redirect
  • Analytics and Search Console are connected
  • Canonical tags use the real public domain
  • The site uses HTTPS without certificate errors
  • A recent backup exists
  • Email records will remain intact
  • The old site can stay available until the new one is confirmed

Avoid canceling old hosting the moment DNS changes. Keep it active long enough to confirm the new site, redirects, forms, and email are working. The exact overlap depends on the platform and billing cycle, but a short period of duplicate expense is often cheaper than trying to recover a site that was deleted too early.

Keep the Exit Professional and Documented

Most transitions do not need to become confrontational. Review the contract, pay legitimate outstanding invoices, and request the specific access and files the business is entitled to receive.

Put the handoff request in writing. List the accounts, exports, assets, and deadlines. Ask the former designer to explain any recurring service that must remain active. A clear request is easier to complete than a message saying only, "Send us everything."

If the provider is unresponsive, document your attempts and contact the registrar, host, or platform through their official account-recovery process. Be prepared to prove the business identity and authority. Do not create duplicate accounts or change records blindly while ownership is disputed.

Questions to Ask the New Web Designer

Before approving the transition, ask:

  • What access do you need, and why?
  • Will the domain remain in our account?
  • Are you moving the website, email, or both?
  • How will you preserve current URLs and redirects?
  • What will happen to forms and stored submissions?
  • Which existing assets can be reused legally?
  • Who owns the finished site and source files?
  • What recurring costs will remain?
  • How will backups and updates be handled?
  • What is the rollback plan if launch testing fails?

The answers should be understandable without technical guesswork. A provider should be able to explain what changes, what stays in place, and what the business will control afterward.

A Better Website Relationship Starts With Control

Changing web designers is manageable when the business owns its essential accounts, the current site is preserved, and the launch is planned around continuity. The goal is not merely to replace one design with another. It is to leave the business with a website that works, records it controls, and a clear understanding of ongoing responsibilities.

For a Grayson County business, that may mean preserving years of local recognition while improving how customers in Leitchfield, Clarkson, Caneyville, and surrounding communities find and contact you. There is no need to invent a new identity or discard useful search history just because the provider changes.

If you need help reviewing your current setup or planning a careful handoff, request a quote from Twin Lakes Web Co.