New Website, Same Business Email: Check the Dependencies

· 6 min read

Published by AKSIS · general educational information

How AKSIS handles editorial review

AKSIS publishes practical website and search guidance for small business owners. Our editorial policy covers source support, claim boundaries, clarity, human responsibility, and small-business usefulness.

General information only—not legal, financial, medical, or platform policy advice.

Read the AKSIS editorial policy.

A new website can use your existing domain while your business email stays with its current provider. Whether a particular launch preserves that arrangement depends on the DNS records, the services behind them, and what the proposed move changes. Ask for a plan that identifies those dependencies before agreeing to a launch or canceling old hosting.

“We are keeping the email records” is a useful starting statement. It still leaves a question: will the mail server and mailbox service those records depend on remain available?

Name the four jobs behind one domain

Domain registration is where the name is registered and renewed. Website hosting runs the site. DNS publishes the records used to find services for the domain. Your email provider runs the mailbox service. One supplier may handle several jobs, but a website rebuild does not make them the same job.

For example, WordPress.com distinguishes connecting a domain from transferring its registration. Its connection options also distinguish updating nameservers from using A and CNAME records. The exact supported option depends on the destination platform and your current setup.

Start by having the proposed provider name the current registrar, active DNS provider, website host and mailbox provider. If a supplier is changing, ask which of its jobs is changing. An instruction to “move the domain” is too broad to establish that boundary.

Changing website records and changing nameservers have different scope

A website connection may involve changing particular A, AAAA or CNAME records at the existing DNS provider. Use the destination’s current instructions for the exact project and hostname. Vercel’s setup guide, for instance, directs users to the project’s recommended values and to their existing provider when DNS is hosted elsewhere. A value from an unrelated tutorial is not a substitute for that information.

A nameserver change moves responsibility for the domain’s DNS answers to a different set of nameservers. The destination needs the required records for retained services as well as the website. WordPress.com’s guide explicitly calls for comparing the current records with its copied records and adding anything missing before changing nameservers. An automatic copy needs verification too.

Worked example: the MX text stays the same, but a dependency changes

Consider a fictional business using example.com. Its website has its own address record. An MX record names mail.example.com as the mail destination, and that mail hostname has a separate address record. Assume its mailbox service runs at the old supplier. These are invented inputs for an explanation, not a client case, a performed migration or values to copy into DNS.

The same MX text can leave different questions unresolved
Proposed changeWhat happens to the mail dependency?Evidence still needed
Only the separate website address changesThe MX record, mail hostname’s address and mailbox service are retained in this example.Confirm the actual retained provider and records, then verify receiving and sending mail.
A new DNS zone copies MX but omits the mail hostname’s addressThe new zone has the mail destination’s name without this example’s required address record.Account for that missing dependency before treating the new zone as ready. Matching MX text does not establish it.
The old supplier’s service is proposed for cancellationThe records alone do not establish whether the assumed mailbox service is retained.Confirm exactly which services would end, and resolve the email arrangement before cancellation.

The dependency in the middle row is grounded in Cloudflare’s mail-record documentation: its example creates an address record for a mail hostname and an MX record pointing to that hostname. Your email provider supplies the actual values and required records. The example does not mean every business has this particular arrangement.

Receiving mail is one check; sending is another

MX records identify mail destinations. Email authentication also uses provider-specific records: SPF identifies permitted senders, DKIM supports signature verification, and DMARC communicates a policy for authentication failures. Cloudflare explains these separate roles. Preserving an inbox route does not by itself establish that outgoing mail authentication remains correct.

Have the responsible provider verify the actual mail and authentication records. After the agreed change, check a new message sent from an external account to the business mailbox and a reply in the other direction. Record what was observed and when. A successful website load is a different result from either mail check.

The website’s inquiry form is another journey. Its notification service can differ from the business mailbox provider. Our contact-form receipt guide explains why a “sent” message on a page does not establish inbox or human receipt. Test the agreed inquiry path separately when it is part of the launch scope.

Agree what must remain before removing the old service

Ask for a short explanation of what changes, which existing services remain, who can verify them, and what would be restored if the change fails. Preserve the current record set and identify the recovery path before an authorized change. Do not assume a provider transfer or hosting cancellation covers only the website.

If the wider question is what can move between website platforms, read our website export and working-copy comparison. For a new website or rebuild, explore AKSIS website design and describe the domain, email and connected tools that need to stay. We review the project and confirm the agreed work before it begins.