1. Home
  2. Answers
  3. Website and email

New website,
same email?

Plan to keep your email working while the website changes. Give the person launching the site a record of how email is set up before they change domain settings.

  • Separate services
  • Keep records
  • Test delivery

The details.

Are my website and email the same service?

They can share a provider, but they do different jobs. A website serves pages; an email service handles mail for your address.

Before a rebuild, identify both providers and the account that controls the domain. Do not assume that moving the website means moving the mailbox.

What needs checking before launch?

Record the current domain settings, the email provider and who has access to those accounts. Tell the designer which addresses must keep working.

Ask for a plan that changes only the records needed for the website. If a wider domain change is required, ask how the email settings will be carried over and checked.

Can I keep my current email address?

Make that a requirement in the project brief. A new design does not by itself call for a new email address.

If the email provider is also changing, treat mailbox access, existing messages and delivery as a separate migration task. Get that plan agreed before the launch.

How should email be tested?

After the change, send to the business address from an outside account and reply back. Check the mailbox you actually use rather than only a success message on the website.

Test the contact form separately. A form submission reaching a confirmation screen does not prove that its notification reached your inbox.

What should I hand over to the designer?

Give them the provider names, the intended domain and the email addresses that must stay active. Share account access through a secure invitation or password manager, not in a public project brief.

Keep an owner-controlled way into the accounts. Ask for a record of the changes and the test results when the site launches.

The checklist.

  • Current domain and mail records saved before anything changes
  • Website provider, email provider and domain account each identified, with a named owner for each login
  • Every address that must keep working listed in the project brief
  • A launch plan that changes only the records the website needs
  • Mailbox access and existing messages covered in writing if the email provider is also moving
  • After launch, delivery tested from an outside account, and the contact form tested on its own

For example.

A shop moves its website to a new host and keeps its mailbox exactly where it is, because the launch plan changed only the records the website needed.

A business switching email providers treats it as a second project with its own migration plan, agreed before the website launch.

An owner tests by sending from a personal account to the business address and replying back, instead of trusting a success screen.

Want a fixed number? Ask.

Send a few lines about your project and get a fixed quote back, usually within a day.