
The short answer
You can often redesign a website while keeping its domain and current business email service. Existing hosting may also remain if it supports the proposed solution. Assess the services and their dependencies separately, preserve the required settings, and verify the website, email and enquiry route before retiring an old plan.
You want a better website, but the current address is already on business cards, invoices and customer records. Your team uses email at the same domain every day. Does a redesign mean replacing all of it?
Often, you can keep the domain and existing email service while changing the website. You may also be able to keep the hosting. The right arrangement depends on the proposed build, the services in your current plan and who can manage them.
Start by asking which parts actually need to change. A useful redesign proposal explains what will remain, what needs work and how the business will verify that the agreed services still function after launch.
Separate the website from the services around it
Several services can appear on one invoice while performing different jobs:
- Domain registration maintains the registration of the name your business uses, such as
example.com. - DNS holds records that direct requests for the domain's services to their destinations. It may be managed by the registrar, host or another provider.
- Website hosting runs or serves the website customers visit.
- Business email provides the mailboxes, aliases and related mail service your team uses.
Your website builder, booking tool and form-delivery service may add further dependencies. One login does not necessarily control them all, and one provider does not necessarily supply every service.
Ask the developer to identify the existing arrangements before recommending a move. Our website developer handover checklist covers collecting the relevant access and project material.
Keep the domain unless the business needs a different one
A new layout does not by itself require a new domain name. A redesign may be built on the same platform, moved to different hosting or rebuilt with another editing system while retaining the public domain.
Changing the company that manages the registration is another decision. If a transfer is proposed, ask what problem it solves, who will control the account and how renewal and support will work. Do not assume it is required simply because a different developer is building the site.
ICANN's guidance explains that a hosting change needs arrangements with the relevant hosting companies and domain registrar. Establish the responsible accounts and permissions so the agreed changes can be coordinated.
Keeping the domain is useful, but individual page addresses deserve attention too. A familiar domain with missing service pages or broken links still creates problems. Retain useful URLs where appropriate and plan relevant redirects for any that change; our redesign and SEO guide explains that work.
Assess whether the current hosting can support the redesign
Keeping existing hosting can be sensible when it supports the agreed website, required functions, administration and ongoing care. Ask for an assessment of those requirements instead of treating a new hosting purchase as an automatic part of every redesign.
The answer can differ between a straightforward service website and a system with bookings, payments or custom operations. A hosted website builder may also have its own publishing and export limits. The developer should explain whether the proposed solution can run in the current arrangement and what would be involved in maintaining it.
If a move is needed, compare the responsibilities and continuing charges. Record who supplies hosting, who supports the website, what backups and recovery cover, and which third-party subscriptions remain. The hosting selection guide covers those questions in more detail.
Google provides a separate process for changing hosting without changing public URLs: prepare and test the new environment, switch the required settings and monitor the transition. A hosting change and a domain change are not the same project.
Confirm where the business email actually lives
Ask who provides the mailboxes, which account pays for them and whether they depend on the current hosting plan. Include shared addresses, aliases, forwarding and any other mail services the business relies on.
If the email service is independent of the website host, retaining it may be straightforward with the appropriate account and domain settings preserved. If mail is included in the hosting being replaced, the proposal needs to address that dependency before cancellation.
Keeping the same email address and keeping the same mailbox provider are different outcomes. A provider move may be possible without changing the address, but the contents of mailboxes, settings and user access need their own migration plan. Do not assume pointing the website somewhere new also transfers messages or creates the required accounts.
For incoming mail, MX records identify where messages should be delivered. Google's Workspace guidance explains this lookup. Cloudflare's documentation also describes mail and authentication records and stresses that their exact values depend on the email provider. A redesign is not a reason to replace working mail settings with a generic set of values.
Do not cancel the old plan just because the new website opens
Consider a hypothetical business whose old hosting plan supplies its website, mailboxes and DNS. The redesigned website moves to another host, while the mailboxes and DNS remain with the old plan. Seeing the replacement website does not establish that the old plan is no longer needed.
Before cancelling an old plan
The website can leave while other services still depend on the plan.
- What changed
- In this example, the website moves to a new host.
- What still depends on the old plan
- The mailboxes and DNS service remain there.
- Before cancellation
- Verify continuing services or their agreed replacements with the responsible provider.
A working replacement website does not, by itself, confirm that the old plan can be retired.
Ask the responsible provider to confirm what cancelling or downgrading the plan would remove. Keep the required services active until their continuing arrangement or agreed replacement has been verified. Plan changes and bundled services vary, so the decision needs the actual account details.
The same question applies if the domain registration is bundled with another service. Record its renewal separately and confirm how it will continue. Avoid closing an account simply because its invoice is labelled “website” when it still supports something the business uses.
Ask which domain settings will change
Have the technical team record the relevant current settings, their owners and the intended changes. The business should understand whether the work changes only the website destination or also moves DNS management or email.
Changing the provider responsible for DNS needs particular care because the new service must retain the records needed by the domain's continuing services. The administrator should confirm the complete requirements with the actual providers, including mail authentication and any verification records in use.
This is a planning discussion, not an instruction to edit records from an example. Do not publish account credentials or private configuration in a general project brief. Arrange appropriate access through the agreed secure handover process.
Ask for a production transition and recovery plan, including who makes the change, who checks the outcome and who can respond if a required service does not work. Continuous availability should be assessed and planned; it cannot be guaranteed merely by keeping the same domain.
Check the website, email and enquiry form independently
A successful homepage view is useful evidence for that page. It does not prove that mail is arriving or that the website's enquiry process reaches the right team.
Agree checks that match the actual services:
- Open the public website at its intended addresses over HTTPS. Follow important pages, navigation and downloads, including retained links.
- Send an agreed non-sensitive message from an external account to a business mailbox and confirm receipt. Check sending and replies as appropriate for the retained service.
- Check important aliases, shared addresses or forwarding arrangements where they are part of the scope.
- Follow an agreed website enquiry into its receiving record or destination, then verify the staff notification and follow-up route.
- Confirm that the business can use the editing and account access it is meant to retain.
The form may use its own sending provider or store submissions separately. Keeping ordinary mailbox email working does not automatically verify the form. Our lead capture guide explains the difference between the visible success message and the receiving-system evidence.
For a site receiving new enquiries, orders or other records during the transition, agree how that activity will be retained. Reverting to an older copy does not automatically include new activity received by the replacement. Use the staging review guide to record what can be tested before launch and what still needs a production check.
Put the retention decisions in the proposal
Ask the provider to state which services will stay, which will move and which will be retired. For each change, record the reason, the responsible person, the acceptance check and any continuing cost.
Useful questions include:
- Can we retain the domain and current email provider?
- Can the proposed website run on the hosting we already have?
- Does the old plan still supply mailboxes, DNS, domain renewal or another required service?
- If email must move, what happens to existing messages, aliases and team access?
- Which page addresses will remain and how will necessary changes be handled?
- Who verifies the live website, business email and enquiry delivery before a service is cancelled?
This gives you a clearer comparison than a proposal that says only “new website and hosting”. If a fixed date is part of the decision, our redesign timeline guide explains how access, approvals and integrations affect the schedule.
Discuss what your redesign actually needs
You can ask for a website redesign assessment while explaining that you would prefer to retain the domain, email and hosting where suitable. Those preferences help frame the review; they do not remove the need to assess compatibility and dependencies.
Share your current website URL, the changes you want and the providers or plan names you already know. Keep passwords and private customer material out of the initial enquiry. We can discuss the existing arrangement and what needs assessment before proposing a suitable scope.
Use the project enquiry form to send those details. The proposal should make the required changes and continuing responsibilities clear before the work is agreed.
Sources and scope
Primary sources checked on 17 November 2026:
- ICANN: changing a web hosting provider.
- Google Search Central: changing hosting without changing URLs.
- Google Workspace: incoming-mail MX records.
- Cloudflare: email and authentication records.
The bundle illustration is hypothetical. Provider plans, account permissions and technical requirements need assessment for the actual website. This guide does not promise uninterrupted service, a standard cost saving, unchanged rankings or a completed client migration.
Tell us about your project
Start with your details. We’ll discuss the right next step.
Questions covered in this guide
Do we need a new domain for a website redesign?
A redesign does not by itself require a new domain. Confirm whether the current name and useful page addresses can remain. Any proposed registration transfer or URL change should have a clear reason and its own plan.
Can we keep the hosting we already pay for?
Possibly. The developer needs to assess whether it supports the proposed website, required functions, administration and ongoing care. The proposal should explain why a move is needed rather than assuming every redesign requires new hosting.
Does keeping the same email address mean email does not need review?
No. Confirm the mailbox provider, account and plan dependencies, aliases and required domain settings. Retaining an address does not automatically transfer mailbox contents or verify sending, receiving and website-form delivery.
When can the old hosting plan be cancelled?
After the responsible team verifies that it no longer supplies a required service, or that agreed replacements work. Check mailboxes, DNS, domain renewal and other dependencies as well as the website. Confirm the actual plan's cancellation effects with its provider.
Sources and project context
- ICANN: changing a web hosting provider Checked 17 November 2026
- Google Search Central: changing hosting without changing URLs Checked 17 November 2026
- Google Workspace: incoming-mail MX records Checked 17 November 2026
- Cloudflare: email and authentication records Checked 17 November 2026
Turn the question into a clear next step.
Tell us about your current setup, the people using it and what needs to improve.
