A poorly communicated email address change causes bounces, lost correspondence, and, in a professional context, breaks in the validation chain. The notification itself is simple, but the technical sequence surrounding it determines whether the transition will be smooth or chaotic.
MX Records and DNS Propagation: The Invisible Prerequisite
When the email address change involves a professional domain (provider migration or domain name change), notifying contacts cannot precede DNS configuration. The MX records of the new domain must point to the correct server before any notification is sent, or else responses may be lost.
DNS propagation can sometimes take several hours. During this window, incoming messages may arrive indiscriminately in the old or new inbox. We recommend maintaining parallel monitoring of both inboxes during the propagation phase and only triggering the bulk send once receipt is confirmed at the new address.
For a personal account (Gmail, Outlook), the DNS constraint disappears. Gmail now offers, for certain accounts, the option to change the primary address without creating a new account: the old address remains as an alias, and the data is retained. Check this option in Google settings before initiating a full migration, as it can sometimes make the announcement unnecessary.
Automatic Forwarding and Aliases: What They Cover and What They Don’t
Automatic forwarding from the old address is a safety net, not a substitute for the announcement. It captures incoming messages, but it does not transfer the history or configured aliases. A sender replying to an old thread will have their message forwarded, without the new account retaining the context of the conversation.
When you have a change of email address to announce, forwarding should remain a temporary measure with a clear expiration date. We observe that redirects left active indefinitely generate deliverability issues: receiving servers eventually classify forwarded messages as suspicious.
Before announcing anything, three technical checks:
- Import the message history from the old inbox to the new one (IMAP or provider migration tool) to retain the context of past exchanges.
- Recreate aliases and filtering rules on the new account, especially if addresses like contact@ or billing@ were attached.
- Test sending from the new address to several providers (Gmail, Outlook, OVH) to ensure the message does not land in spam.
Recipient Segmentation and Sending Order
Sending a bulk message to the entire address book is the surest way to trigger spam classification. Anti-spam filters detect mass sends from an address without sending history. Segmenting contacts into smaller batches and spacing out sends over several days protects the reputation of the new address.
The order matters. Organizations that hold personal data (bank, insurance, administration) should be notified first, as their update times are the longest. The public service offers an online service to report a change of address to multiple organizations simultaneously, but the CAF, CPAM, and MSA are not included and require separate notification.
Recommended Sequence for Professional Sending
We recommend notifying first those contacts whose responses are expected (clients in ongoing projects, active providers), then institutional contacts, and finally the wider network. This prioritization avoids saturating the inbox on the first day with non-urgent automatic replies.
For professional use, the BCC (blind carbon copy) field is the standard. An email sent with visible recipients to several hundred contacts exposes everyone’s addresses, which poses a GDPR compliance issue if the recipients do not know each other.
Email Subject and Content: What Triggers Opening
The email subject determines the open rate. A vague subject (“Important Information”) will be ignored or filtered. An explicit subject works better: “New Email Address – [Your Name or Company Name]”. The recipient immediately identifies the subject and the sender.
The body of the message should contain four elements, no more:
- The old address (the one the recipient recognizes in their contacts).
- The new address, clearly stated and without a clickable link to avoid anti-phishing filtering.
- The date from which the old address will cease to function or redirect.
- A request to update the address book, phrased in one sentence.
Avoid attachments and embedded images in this type of notification. Anti-spam filters penalize messages containing multimedia elements sent from an address without history. A plain text or lightweight HTML message performs better.
Automatic Reply on the Old Address
Setting up an out-of-office message on the old inbox completes the active notification. This out-of-office message mentions the new address and remains active for the duration of the forwarding. Contacts who have not read or seen the initial notification are thus caught up during their next send.
Duration of the Transition Period and Final Cutoff
The forwarding should not last indefinitely. Setting a cutoff date from the initial announcement creates a clear constraint for recipients and protects long-term deliverability. An overly long transition period keeps two entry points active, complicating response management and fragmenting archives.
We recommend following up with contacts who have not acknowledged receipt after a few weeks. A second targeted send, only to addresses that have not interacted, is usually sufficient. Beyond two follow-ups, the contact may be considered inactive.
The last action before the cutoff: verify that all online services (SaaS platforms, social networks, two-factor authentication) have been successfully migrated to the new address. An oversight on this point blocks access to an account much more certainly than an unnotified human contact.
