Changing Your Business Domain? Keep the Old Email Addresses Working

Your salon has a new name and a new domain. The website is ready, but clients still write to the address saved after their last appointment. Publishing the new brand does not update their phones, invoices, or old conversations.

This is different from changing mail providers while keeping an address. Here you are changing the part after the @ sign, and you need both identities to coexist. We recommend preparing the new mail setup before asking anyone to use it.

Inventory the addresses and systems that use the old domain

List staff mailboxes, shared addresses, aliases, forwarders, groups, and automated senders. Include booking software, invoice systems, contact forms, newsletters, and accounts that use email for recovery. A mailbox list alone will miss services that send on your behalf.

For each address, record who receives it, whether it sends replies, and whether its message history must be retained. Our business email guide helps you plan recognizable addresses; record the receiving mailbox for each address separately.

Choose how old addresses will reach the new mailboxes

Ask your mail provider whether it supports both domains in the same account, domain aliases, or individual address mappings. Decide whether the old and new versions should reach one inbox or separate mailboxes. Do not assume the word “alias” means identical behavior across providers.

Google Workspace, for example, distinguishes user alias domains and secondary domains. Those options do not mean the same thing as changing the primary domain. Confirm the arrangement for your service before renaming users.

Keep the old domain and its mail service active

You must retain control of the old domain if you want its addresses to keep working. A web redirect does not forward email, and an active registration alone does not supply mail delivery. Keep the old domain's MX records and receiving service correct for the chosen arrangement.

If you cancel an old hosting package, check whether its mailboxes or forwarders disappear with it. Separate website retirement from mail retirement. Assign renewal responsibility to both domains and maintain working recovery contacts.

Prepare the new domain before publishing addresses

Register and secure the approved name, then verify it with the mail provider using its documented method. Add the required records without disturbing the old domain's working setup. A new website can go live before the new email is ready, but do not advertise a mailbox that has not passed delivery tests.

Create the new addresses and set permissions for shared mail. Confirm how staff will sign in after any account rename. Email aliases do not necessarily change login names, file ownership, calendar identities, or connected application accounts.

Authenticate each domain that will send mail

Identify every service allowed to send using the new domain. Configure the applicable SPF, DKIM, and DMARC settings according to those providers' instructions. Retain appropriate authentication for the old domain while it still sends replies or automated messages.

Forwarding can interact with authentication and filtering, so test it rather than assuming delivery. Our email authentication guide explains the roles of these records. Do not copy one provider's values into every domain without checking the actual sending setup.

Test replies, forwarding, and application messages

Test from accounts outside your organization. Send to an old personal address, an old shared address, and their new equivalents. Reply from the receiving mailbox and check the visible sender and reply-to address.

Also test attachments, contact forms, booking confirmations, invoices, password resets, and calendar invitations. Confirm which account holds old message history. Routing a new message to another inbox does not migrate the archive.

If you are also moving providers, make that an explicit second workstream. Our email provider comparison includes migration considerations. Copying old data and changing delivery providers do not happen automatically because the business adopted another domain.

Announce the change in controlled stages

Tell staff and regular customers after the tests pass. Update signatures, invoice templates, booking systems, and public profiles in a planned sequence. Use the old, trusted route to explain the change before expecting an unfamiliar sender to be recognized.

Be especially clear around payment instructions. A rebrand should not look like an unexpected demand to send money somewhere else. Give customers a known contact route if they want to verify the announcement.

Monitor old addresses and plan their long-term role

Watch for messages that still arrive at old addresses, bounced replies, and applications that continue using the previous sender. Keep a record of what you have updated and who owns the remaining changes. Review real use before deciding whether to reduce the old mail service.

There is no universal safe date to let an old domain expire. Printed material, long-term clients, account recovery, and the sensitivity of expected mail can justify keeping it. If you eventually retire an address, review those dependencies first and avoid leaving business recovery tied to it.

Change the name without losing the conversation

At SoxDomains, we help you compare and manage domains as your business changes. Secure the new identity while keeping the old one under control, then coordinate the email configuration with your provider.

Let the public name change after the delivery paths work. Clients should be able to reach you even if they reply to a message you sent before the rebrand.