Understanding the Upgrade Process

The upgrade process from Stack 4 to a newer version of SFMC is similar to a migration from one Enterprise to another. This process can be complex and requires careful planning to ensure a smooth transition. One of the key considerations is the impact on email sending and tracking data.

Teams running SFMC have reported that one of the most challenging aspects of the upgrade process is the migration of engagement and interaction tracking data. This data may not transfer directly and may require manual storage in a data extension (DE) or external system for reference.

IP Warmup and Dedicated vs Shared IPs

Another critical consideration during the upgrade process is IP warmup and the decision between dedicated and shared IPs. A community member asked about the implications of moving to a shared IP, and the response was that it may not be the best option, especially for senders with low email volumes.

A dedicated IP may be a better option for senders with low email volumes, as it eliminates the risk of IP warmup issues and potential deliverability problems associated with shared IPs. However, for medium to high-volume senders, a shared IP may be a more suitable option, as it can provide better deliverability and reduce the risk of IP warmup issues.

The root cause of IP warmup issues and deliverability problems during an SFMC upgrade is often the result of inadequate planning and consideration of email sending and tracking data. It is essential to carefully evaluate the email sending volumes and audience to determine the best IP option and develop a strategy for IP warmup and deliverability.

Best Practices for a Successful Upgrade

To ensure a successful upgrade from Stack 4 to a newer version of SFMC, it is crucial to follow best practices and carefully plan the migration process. This includes evaluating email sending and tracking data, determining the best IP option, and developing a strategy for IP warmup and deliverability.

Example Code

/* Example code for evaluating email sending and tracking data */
var emailSendingData = [/* email sending data */];
var trackingData = [/* tracking data */];

/* Evaluate email sending and tracking data to determine the best IP option */
if (emailSendingData.length > 1000) {
  // Medium to high-volume sender, consider shared IP
} else {
  // Low-volume sender, consider dedicated IP
}

Heads up: It is essential to carefully evaluate the email sending and tracking data to determine the best IP option and develop a strategy for IP warmup and deliverability.

Checklist for a Successful Upgrade

Pre-Upgrade Checklist

• Evaluate email sending and tracking data to determine the best IP option
• Develop a strategy for IP warmup and deliverability
• Consider the implications of moving to a shared IP
• Evaluate the need for a dedicated IP
• Plan for manual storage of engagement and interaction tracking data
• Consider the use of package manager and other tools to assist with the migration process
• Develop a plan for testing and quality assurance after the upgrade

Frequently Asked Questions

What is the best IP option for low-volume senders?

A dedicated IP may be a better option for low-volume senders, as it eliminates the risk of IP warmup issues and potential deliverability problems associated with shared IPs.

How do I determine the best IP option for my email sending volumes?

To determine the best IP option, evaluate your email sending volumes and audience to determine the best IP option and develop a strategy for IP warmup and deliverability.

What are the implications of moving to a shared IP?

Moving to a shared IP may result in IP warmup issues and potential deliverability problems, especially for low-volume senders.

How do I plan for manual storage of engagement and interaction tracking data?

Plan for manual storage of engagement and interaction tracking data by evaluating your current data storage needs and developing a strategy for storing and referencing this data after the upgrade.

What tools are available to assist with the migration process?

Tools such as package manager and other migration tools are available to assist with the migration process and make it more efficient.