Email domain migration: preparing campaigns for a rebrand

The new domain is live and the logo has changed, yet order confirmations still arrive from the old brand. Replacing the sender address can feel like the final finishing touch. An email programme, however, has its own infrastructure, interaction history and recipient expectations. Those need to move with the name.

In its rebranding guide dated August 4, 2026, Litmus treats a domain change as a deliverability event. The practical question is how to change the sender’s identity while preserving working notifications, permissions and the ability to detect deterioration.

Decide what is actually moving

A rebrand does not always require immediately replacing every address. Map your senders: marketing campaigns, transaction confirmations, account recovery, invoices, reminders and employee email. Record the system, current domain, reply address, purpose and owner for each stream. Identify links, images and click-tracking domains separately.

Consider a company changing its name and moving its website. Transactional messages should not be treated as another marketing campaign: a missing payment notification creates a different problem from an unread newsletter. The transition sequence therefore depends on the importance of each stream, its volume and infrastructure readiness. Agree which senders will temporarily remain on the old domain and how recipients will recognise the relationship between the brands.

Check every system that sends on the company’s behalf, including small scripts. The Mailgun and Google Apps Script architecture illustrates how notifications can connect to Forms, Calendar and Sheets. It provides context for an inventory; the published description does not establish a new-domain migration or the project’s current operation.

Verify authentication for each stream

The new sender needs settings agreed with the email service. SPF identifies authorised sending sources, DKIM supports signature verification, and DMARC relates those checks to the visible sender domain and specifies a handling policy. Records existing in DNS do not establish that an actual message is configured correctly.

Send a test from every participating system and inspect its headers, authentication results and domain alignment. Do not copy an article’s DNS example without substituting your service’s details. Existing records and sending sources matter: introducing a strict policy before completing the inventory can affect legitimate mail.

Litmus also recommends collecting aggregate DMARC reports to see sending sources. Decide who reviews those reports and how a finding becomes an assigned task. The infrastructure operating plan should include saved settings, owners and a clear configuration rollback procedure. Email checks belong in rebrand acceptance alongside website checks.

Preserve recipient relationships

Migrating a list means more than copying addresses. Retain unsubscribe records, suppression reasons, permitted topics, frequency choices, consent history and segment membership. A new platform or domain does not justify contacting somebody who opted out.

Warn the current audience through a familiar sender. Explain the new name, future address and official website. If account access changes, specify the action that is actually necessary. Do not invent a need to reset passwords simply to announce a brand change. Recipients should understand the transition without suspicious links or further searches.

An email preference centre matters here: topics and frequency should survive the rebrand. Test old unsubscribe links and new forms with several test contacts. If one system retains permission while another has recorded a withdrawal, the migration is incomplete.

Separate changes and observe the launch

Avoid simultaneously introducing a new domain, another sending service, entirely different templates and a sharp increase in volume. If results deteriorate, identifying the cause becomes difficult. Preserve familiar elements in the initial message, and change design and segmentation separately where the brand plan allows.

Start with a limited stream and recently engaged recipients. Agree initial volumes and the rate of growth with your service, using your own history: numerical examples in Litmus are not a universal safe schedule. Establish pause criteria before launch, including authentication failures, unusual bounces, complaints or problems with critical notifications. Identify somebody who can stop the campaign before sending starts.

In its deliverability article dated July 20, 2026, Litmus distinguishes server acceptance from inbox placement. A “delivered” report therefore does not complete the check. Compare bounces and complaints by mailbox provider, available observations of placement, and completion of the action linked from the message. Treat opens cautiously: they are not equivalent to reading or a commercial result.

Keep a verifiable migration record

Maintain a transition log containing the stream, switch date, configuration used, test messages, observed deviations and the owner’s decision. Compare equivalent segments rather than aggregate success rates before and after changing the audience. The historical Mailwizz analytics project illustrates bounce processing and exclusions; its report’s delivered status was not independent evidence of inbox placement.

If the migration affects a sending-service API, add integration contract checks. Changes to delivery events, identifiers and links can break reporting while sending still works. Verify that a new event belongs to the correct message and does not create a duplicate record.

The transition is complete when the agreed streams use the expected addresses, opt-outs remain effective, critical messages pass their checks, and the team can see and respond to deviations. A successful first campaign is one check. A rebrand also requires observation of later sends and continued ownership after the design project ends.

Sources

• Litmus: protecting email during a rebrand, August 4, 2026.
• Litmus: understanding deliverability, July 20, 2026.