Can I Change Web Designer Without Losing My Website?

There are several different kinds of “switch”: changing the person who maintains the site, moving hosting, moving platform, redesigning the site, or doing several of those things together. The risk increases when multiple layers change at once.

If the existing website is sound, a simple takeover may be cheaper and safer than rebuilding it.

Before the handover, establish control of the domain registrar, hosting/control panel, CMS administrator account, backups, analytics, Search Console and any services that affect forms, email or payments.

The incoming provider should know what they have before the outgoing provider is cancelled.

For WordPress this normally means both the site files and the database. For other platforms, use the best available export or backup route. Keep a copy somewhere independent of the hosting account being replaced.

A backup is not only for disasters: it gives the incoming provider a stable reference point if something changes during the handover.

Business email is frequently the hidden dependency in a website move. If mail is on Google Workspace or Microsoft 365, it may stay exactly where it is while the website moves. If mailboxes are part of the existing hosting account, they may need a separate migration plan.

Never change nameservers without first recording the DNS entries that keep email and other services working.

If the same website and URLs remain in place, changing provider alone should not require Google to relearn the whole site. If URLs do change, create a URL map and permanent redirects, preserve useful content and metadata, and monitor Search Console after launch.

A change of supplier is not a good reason to casually rename every page.

Where possible, build or copy the new setup first, test it away from the live domain and only switch DNS when the replacement is ready. For live businesses, a planned overnight migration can reduce disruption during normal trading hours.

A good handover ends with the business knowing where the domain is registered, where the website is hosted, who has administrator access, where backups live and which company to contact for support. The new provider should also have tested forms, email-related DNS records and any important third-party integrations before the old arrangement is closed.

If the outgoing designer is cooperative, this can be very straightforward. If they are not, the same checklist becomes a recovery plan: identify each missing piece and deal with it separately rather than treating “the website” as one mysterious object.

Ask whether they intend to keep or rebuild the current site, whether the domain will remain in your account, whether hosting is changing, how email will be protected, whether URLs will change and what happens if the migration fails. You should also know how future support is charged and whether you can leave again without another complicated handover.

A provider who can explain those points before touching the live site is usually giving you a much safer start than one who simply asks for the domain login and promises to “sort it”.