Migrating an email sending domain effectively requires careful planning and execution, focusing on preserving sender reputation, minimizing disruptions, and maintaining deliverability. Experts and marketers advise against creating entirely new domains, as it can lead to consumer confusion, potential phishing risks, and loss of existing sender reputation. Subdomains are the preferred alternative. Key steps involve updating SPF, DKIM, and DMARC records to authenticate the new sending platform, gradually warming up new IP addresses, and continuously monitoring deliverability metrics like bounce rates and spam complaints. Segmenting email lists for phased migration, exporting and testing email templates, and informing subscribers about the change are also essential. DNS delegation to providers is discouraged due to security concerns. A rollback plan, using multiple IPs for high-volume sending, setting up feedback loops, and regularly reviewing email authentication settings all contribute to a successful migration. Switching MX records needs to be carefully considered as the records can only point to one provider at a time.
15 marketer opinions
Migrating an email sending domain involves several key steps to ensure deliverability and maintain sender reputation. Experts recommend against creating entirely new domains due to potential brand confusion and loss of existing reputation. Instead, using subdomains is favored. Setting up the same subdomain for both providers during migration is possible, but MX records can only point to one provider at a time. Gradual IP warming and monitoring deliverability metrics like bounce rates and spam complaints are crucial. It's also important to export and test email templates, segment email lists for phased migration, and inform subscribers about the change. DNS delegation to providers is discouraged due to security concerns. Utilizing multiple IPs for high-volume sending, setting up feedback loops, and having a rollback plan are also recommended. Regularly reviewing email authentication settings is essential for maintaining a positive sender reputation.
Marketer view
Email marketer from Email Geeks says that they do not encourage to delegate their subdomains and that DNS plays a critical role in security, and delegating a part of it is convenient, but might be dangerous. He suggests contacting them and tell them you want a double-run.
8 Jun 2023 - Email Geeks
Marketer view
Email marketer from Email Geeks shares that you can choose to switch MX the day you start with provider B, or the day you start sending more emails with B than with A, or the day you stop sending with A entirely and that it depends on your plan, and he's not sure there's a perfect solution for that.
9 Dec 2024 - Email Geeks
5 expert opinions
Migrating an email sending domain effectively requires careful planning and execution, focusing on preserving sender reputation and minimizing disruption. Experts strongly advise against creating new domains to avoid consumer confusion and potential phishing risks, recommending subdomains instead. Subdomain warming is still necessary, although to a lesser extent than a full domain. Maintaining existing sender reputation by warming up the new IP and monitoring deliverability is essential. Using different return paths at two different providers simultaneously is possible, with minimal customer-visible changes. A detailed migration timeline and assessment of current setups are vital for a smooth transition.
Expert view
Expert from Email Geeks explains that creating a new domain causes more consumer confusion and can train them to be phish victims, so she generally doesn’t recommend it. She prefers to use subdomains when migrating.
18 Dec 2024 - Email Geeks
Expert view
Expert from Email Geeks explains you’ll also need to do a piece of subdomain warming, not as much, but Google does look at IP / domain combo.
14 May 2024 - Email Geeks
5 technical articles
Migrating an email sending domain requires careful configuration of DNS records and adherence to email authentication protocols to ensure deliverability. Updating SPF records with the new platform's sending IP addresses or domain names is crucial to authorize email sending. Implementing DKIM records adds a digital signature to authenticate emails and prevent tampering. DMARC policies define how receiving servers should handle emails that fail authentication checks. Correctly configuring all necessary DNS records (SPF, DKIM, DMARC, MX) is paramount to avoid deliverability issues. Setting up Feedback Loops (FBLs) is important for identifying and removing subscribers who mark emails as spam, which improves sender reputation.
Technical article
Documentation from AWS explains that carefully updating DNS records is crucial for a smooth migration. Ensure that all the necessary records (SPF, DKIM, DMARC, MX) are correctly configured in the new platform's DNS settings. Incorrect DNS settings can lead to deliverability issues.
7 Sep 2022 - AWS Documentation
Technical article
Documentation from Google Workspace Admin Help explains that you should update your domain's SPF records to include the sending IP addresses or domain names of the new email platform to authorize it to send emails on behalf of your domain. This helps prevent your emails from being marked as spam.
24 Jan 2024 - Google Workspace Admin Help
Are custom sending domains worth the money and effort?
Can I use the same sending domain with multiple ESPs?
Can I use the same subdomain for multiple email sending platforms?
Do I need an IP warm-up when moving to a new ESP with shared IPs?
How do I set up SPF and DKIM records for new subdomains when using third-party email services?
How do I transition to a new ESP while maintaining sends on my current platform using the same domain?