How do I transition to a new ESP while maintaining sends on my current platform using the same domain?

Email marketer from StackOverflow emphasizes the importance of using include: statements in the SPF records as each ESP will have a different authentication domain. This will help email services identify your company's domain.

Email marketer from Email on Acid emphasizes maintaining synchronized lists. Ensure that unsubscribe requests are promptly reflected across both ESPs. Failing to do so may hurt your reputation and cause legal issues.

Email marketer from Email Vendor Selection blog advises running both ESPs in parallel for a while. Split your email list and send a portion through the old ESP and the rest through the new one. Monitor results from each ESP to find out if the new one is up to par. Make a full switch only once you have enough confidence.

Email marketer from Campaign Monitor recommends A/B testing your email campaigns on both ESPs to identify any performance differences. Test different subject lines, content, and sending times to optimize your results and ensure a smooth transition.

Email marketer from Quora answers to start by migrating a small segment of your audience to the new ESP, monitor performance, and gradually increase the volume as you gain confidence. Make sure to replicate your suppression lists in both ESPs to avoid sending to unsubscribed users during the transition.

Email marketer from Email Marketing Forum explains to transition gradually. Start by sending low-priority emails from the new ESP while continuing to send your main campaigns from the old one. This helps you build a sender reputation on the new platform without risking deliverability for critical emails. Monitor bounce rates and feedback loops closely.

Email marketer from Reddit user EmailPro shares that you should utilize different subdomains for your new ESP during the transition. This avoids DNS conflicts and allows for gradual warming up of the new domain while keeping your primary domain active on your old ESP. Once the new subdomain's reputation is strong, you can consider fully switching over or using both ESPs in parallel.

Email marketer from Litmus shares to closely monitor your key metrics such as open rates, click-through rates, and bounce rates on both ESPs. Pay special attention to any deliverability issues, such as emails landing in the spam folder. Use this data to adjust your sending strategy and optimize your email content.

Expert from Email Geeks defines SPF Domain as the Envelope From / Return Path / Bounce domain / 5321.from. The end user does not see this domain unless they go look for it. It is the domain that is checked by SPF and the one that must match the Visible From domain for DMARC to pass. It does not need to be a domain controlled by the sending entity. Defines Visible From domain as what most non-email-geek people think of as the From domain. This is what is visible to the end user when they read their mail (assuming their mail client doesn’t hide it like all too many of them do). This is what consumer filters use to help drive delivery to individual user inboxes. This is the domain that is verified by DMARC.

Expert from Word to the Wise recommends using different subdomains for the envelope from address (the bounce domain) when using multiple ESPs simultaneously. This ensures that each ESP can handle bounces correctly and maintains proper SPF alignment. You can, however, use the same subdomain in the visible from address.

Expert from Email Geeks explains to use the same domain/subdomain in the visible from address and collect any direct responses directly.

Expert from Word to the Wise responds that when migrating from one ESP to another, it's essential to handle IP address warm-up with care, especially if you are not using dedicated IPs. Use a phased approach, moving small batches of recipients to the new ESP over time and closely monitor performance metrics such as bounce rates and spam complaints. Maintain proper authentication and list hygiene throughout the transition to avoid deliverability issues.

Expert from Email Geeks shares an example of in your case, the SPF domain might be <http://esp1.bounce.wttwmail.com|esp1.bounce.wttwmail.com> for ESP1 and <http://esp2.bounce.wordtothewise.com|esp2.bounce.wordtothewise.com> for ESP 2

Expert from Word to the Wise responds that when changing ESPs to make sure you let the email providers know. Do this by enabling the feedback loop with the new ESP and make sure you are sending consistently. Finally ensure your DNS records are all correct.

Expert from Email Geeks shares that each ESP should have its own SPF record (e.g., esp1.domain.here v=spf1 include:_spf.esp1.here) because the envelope from is unique to each ESP, you can have a single SPF record for each subdomain.

Expert from Email Geeks explains that you must have different subdomains in the envelope from address so that each ESP can bounce handle mail correctly but you can have the same subdomains in the visible from address and recommends different subdomains in the d= for DKIM.

Documentation from SendGrid emphasizes the importance of IP warmup. Start by sending low volumes of emails to your most engaged subscribers and gradually increase the volume over time. This helps build a positive sender reputation with mailbox providers.

Documentation from Amazon Web Services suggests setting up separate subdomains for each ESP you intend to use. This allows you to maintain separate SPF and DKIM records for each, avoiding conflicts and ensuring proper authentication. Each subdomain should handle its own bounces and feedback loops.

Documentation from SparkPost advises creating unique DNS records for each ESP, particularly SPF and DKIM records. Use a subdomain for the new ESP to prevent conflicts with your existing domain's authentication settings. Also mentions setting up dedicated IP addresses for each ESP.

Documentation from Mailjet recommends warming up your new IP address and domain gradually by starting with low volumes and increasing over time. Monitor your sender reputation and engagement metrics to ensure deliverability.

Documentation from Google Workspace explains that domain reputation plays a critical role in email deliverability, especially with Gmail. Ensure you have properly configured SPF, DKIM, and DMARC records for all sending domains and subdomains. Monitor your sender reputation using Google Postmaster Tools to identify and address any deliverability issues.