Understanding the Transition Process

The transition process involves several key steps, including rebuilding all cloud pages on the new domain, updating base email templates with new routing for unsubscribe links, and creating new sender profiles. It is also necessary to update any custom HTML, AMPscript, SSJS, etc. that contains old domain references in emails and templates.

In addition to these steps, it is also important to consider the impact of the transition on connected Salesforce orgs and API calls. If the connected Salesforce org is changing, or if API calls are being used to send emails, additional steps may be necessary.

IP Warming and Deliverability

IP warming is a critical step in the transition process, as it helps to establish a good deliverability reputation for the new sender domain. This is especially important when using a shared IP, as the deliverability reputation is based on both the IP and the domain.

The root cause of deliverability issues during a domain transition is often the lack of proper IP warming, which can lead to a poor deliverability reputation and increased risk of emails being flagged as spam.

To avoid these issues, it is recommended to perform a full IP warming, even when using a shared IP. This involves gradually increasing the volume of emails sent from the new sender domain over a period of time, to help establish a good deliverability reputation.

Additional Considerations

In addition to the steps mentioned above, there are several other considerations that teams should keep in mind when transitioning to a new SAP domain in SFMC. These include reuploading images to use the new domain, applying SSL certs to the new domain, and updating any custom code or scripts that reference the old domain.

example.html

<!-- Update image URLs to use the new domain -->
<img src="https://newdomain.com/image.jpg">

By following these steps and considering these additional factors, teams can ensure a smooth transition to a new SAP domain in SFMC and minimize the risk of deliverability issues.

Heads up: It is also important to note that SFMC support may be able to assist with updating image URLs and other tasks, so it is worth reaching out to them for guidance.

Checklist

• Rebuild all cloud pages on the new domain
• Update base email templates with new routing for unsubscribe links
• Create new sender profiles and update send classifications
• Perform full IP warming, even when using a shared IP
• Reupload images to use the new domain (if necessary)
• Apply SSL certs to the new domain
• Update any custom code or scripts that reference the old domain

Frequently Asked Questions

Do I need to reupload all images to use the new domain?

It depends on the specific configuration of your SFMC instance. In some cases, SFMC support may be able to update image URLs for you.

How long does the IP warming process take?

The length of time required for IP warming can vary depending on the volume of emails being sent and the specific requirements of your SFMC instance.

Do I need to update my connected Salesforce org?

If your connected Salesforce org is changing, you may need to update your SFMC configuration to reflect the new org.

Can I use API calls to send emails during the transition?

Yes, but you will need to update any API calls to reference the new sender domain and ensure that the API is configured correctly.

How do I ensure a good deliverability reputation during the transition?

By performing a full IP warming and following best practices for email sending, you can help establish a good deliverability reputation for your new sender domain.