How to change website provider and keep your domain and email

You can rebuild the website and keep the address on business cards and in email inboxes. The first step is to find out who holds the domain, who renews it, where the website is hosted and where messages arrive. If you currently pay for everything on the same invoice, confirm which services would end on cancellation. Then decide what needs changing.

By Lyntev. Updated on .
About 6 minutes to read.

A request that stays connectedThe same reference follows the request and prevents duplicates.

Translation published on . Original Portuguese guide; source revision .

By the end, you can:

  • Identify who manages the domain, website and email
  • Test contact channels and addresses before the change
  • Define when to proceed and how to recover if something fails

What do I need to change to retain the domain and email?

Imagine replacing your website while the team keeps replying from its usual address. Whoever tests the new website needs to know whether only hosting changes, domain management changes too or mailboxes also move. You can combine these jobs in different phases. The table helps define the proposal and choose who validates each transition.

What do I need to change to retain the domain and email?
What you wantWhat to agree with providersEvidence it is resolved
Rebuild the website while keeping the domain and email with the current providerConfirm registration, DNS service and mailboxes stay active. Prepare the new website in a preview and identify only the records routing web traffic.The domain opens the new website with HTTPS. An external person writes to the team and receives a reply. A test form enquiry reaches the intended inbox.
Change who manages the .pt domain while keeping the website and mailConfirm registrant, renewal and managing entity. If DNS service also changes, prepare a copy of the records needed for operations beforehand.The registrant retains control, and the new entity confirms management and the next renewal. Website and mail pass the same tests as before.
Also change the mailbox providerInventory mailboxes, alternative addresses and history. Prepare new mailboxes, test copying and agree when to switch new-message delivery to the destination.Each person can send and receive in the new mailbox and find a known old message. Messages arriving at the source during the transition have been reconciled.

Three tests before cancelling the old service

MX records indicate where incoming mail is delivered. The website form may send through another service. Being able to reply from a phone therefore proves only part of the journey. Use fictitious messages with distinct, easy-to-find subjects. Record the time and destination inbox of each.

  • Receipt and reply. From an external inbox, write to the usual address and an alternative address in use. Reply from the business inbox and confirm arrival in the external inbox.
  • Website enquiry. Send through the preview form to the agreed test inbox. Repeat on the public website after the change and confirm recipient and reply address.
  • Recovery trial. Save the previous configuration and agree who can restore routing if contact channels fail. Preserve enquiries and messages received on both sides until checking is complete.

Separate visual changes, infrastructure and URLs

Describe what changes: presentation only, content management system, hosting, domain or path structure. If addresses can be preserved, do not change them without a clear benefit. Adding several simultaneous changes makes the cause of a problem harder to identify. Organise phases and approval criteria when operations allow.

Also identify functions absent from the page map: forms, payments, downloads, restricted areas, email and integrations. A migration can keep every page accessible and still stop receiving enquiries. For every function, define a test and owner. Keep a recoverable version of the previous state and clarify how to handle new data received during the transition.

Gather addresses from several sources

Combine the current catalogue, sitemap, internal links, published files and available information about pages used. Include addresses on printed materials, signatures, campaigns and known external links. A page outside the menu can still receive visitors. Mark the origin and importance of every entry without automatically deleting a path merely because it is absent from a visit sample.

Normalise variants for analysis but preserve the list requiring tests: HTTP/HTTPS, domain with or without www, trailing slashes and old paths may have different rules. Google’s migration documentation recommends preparing the mapping before the change. Use the inventory as a continuity contract, not just a list for creating the new sitemap.

Fictitious migration-map example

Fictitious company Norte Oficina reorganises services and documents. Address /servico1.html becomes /servicos/manutencao; /contactos stays; a PDF receives an equivalent version; an ended campaign without a replacement loses its page. These decisions precede programming rules. Each row has a reason and someone confirming the destination content.

Do not redirect every old address to the homepage. This prevents people finding the subject they wanted and may be an unsuitable match. If merging pages, confirm the new page genuinely covers the useful content. If removing without an equivalent, present an appropriate status and useful navigation without pretending the resource still exists.

Fictitious migration-map example
Old addressDecisionDestination or response
/servico1.htmlPermanent move/servicos/manutencao
/contactosPreserveSame address and journey tested
/ficheiros/preparacao.pdfReplace with an equivalentApproved document at the new path
/campanha-terminadaRemove without an equivalent404 or 410, according to the technical decision

Implement direct destinations and consistent signals

For permanent moves, the team should configure the appropriate HTTP redirect. MDN documentation distinguishes codes and method handling; do not apply page-navigation rules indiscriminately to endpoints receiving data. The aim for an old page is to reach the final equivalent without loops or an unnecessary series of hops.

Update internal links, canonicals, resources and sitemap to final addresses. A redirect bridges the gap for anyone still using the previous address; new navigation should point directly to the current destination. Also check images, documents and important anchors. A correct browser title does not demonstrate that every page resource came from the new environment.

Test the map and prepare the transition

Test each rule and a representative sample of pages and functions. Record starting address, response, final destination, content and essential action. Check that the preview retains its own protections and publication will use the correct indexing rules. A test environment must not accidentally send notifications or execute real payments.

Agree a change window, owners and criteria for stopping or restoring. If data is being updated, describe freezing, synchronisation or handling new entries. Before switching, confirm backups and access to the previous environment. Afterwards, test from a new session and confirm DNS, HTTPS and associated services. Rollback needs to consider data and configuration, not merely displaying an old design again.

Monitor errors and maintain the old bridges

After publication, monitor critical journeys, access errors and pages still receiving requests through old paths. Check the sitemap and correct Search Console property. For a domain change, assess the applicable change-of-address procedure; changing paths within the same domain is a different situation. Always record the date and scope to compare periods with context.

Google recommends retaining redirects as long as possible, generally at least one year. They may remain useful to someone who saved a link beyond that. Common errors include switching off the old domain early, forgetting PDFs and keeping old internal links. Update points you control and investigate actual failures before attributing any search variation to a single cause.

Record approval through evidence

A migration becomes verifiable when every important decision has an observed result. Keep the map, applied rules and tests. Separate outstanding content, infrastructure and indexing matters; each needs a different action. The worksheet should also state who follows operations after the move so the team does not finish work the moment the new website opens.

Worksheet for your project

What changes and what will be preserved:
Domain / registrant / managing entity / next renewal:
DNS provider / website hosting / email provider:
Services that would end on cancelling the current package:
Mailboxes and alternative addresses to retain / who validates receipt:
External sending and reply / time / result before and after:
Form / destination inbox / enquiry received / reply checked:
Mail in transit or history to reconcile / owner:
Address inventory and sources:
Old URL / decision / destination / owner:
Redirect rules and special cases:
Updated links, canonicals, resources and sitemap:
Business functions to test:
Recoverable backup and restoration trial:
New data during the transition:
Window, owners and stopping criteria:
Results before and after publication:
Open errors and corresponding action:
Domains/redirects to retain and future review:

Sources and criteria

Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.

Wellinton Oliveira

Written by

CEO of Lyntev

Technology with context, original analysis and sources you can consult.