ESP migration

Confirm your sends are landing correctly after cutover

An ESP migration is one of the highest-risk periods for email reliability. Routing logic changes, authentication configurations shift, and journey behaviour can change in ways that only show up at the inbox.

Every paid plan includes the Telltide Card, the status light for your customer email journeys.

The problem

Migration risk is invisible without inbox-side checks

Your new ESP may confirm a successful send. That doesn't mean the email arrived correctly in the inbox. Authentication misconfigurations, routing errors, and journey logic differences can all cause inbox failures that your new platform won't surface.

1

Authentication gaps

SPF, DKIM, or DMARC misconfigurations on the new platform cause emails to fail inbox delivery or land in spam. The ESP reports a successful send.

2

Journey logic differences

Automation rules that behaved one way on your old ESP behave differently on the new one. Triggers fire at the wrong time or not at all.

3

Routing errors

IP warming, subdomain configuration, or routing table differences cause delivery failures on specific mailbox providers or segments.

How it works

Inbox-side confirmation before and after cutover

1

Monitor on your existing ESP first

Establish a baseline. Add Telltide monitoring to key journeys on your current ESP so you have a reference point for expected delivery behaviour.

2

Run parallel monitoring during migration

During cutover, monitor the same journeys on the new ESP. Telltide checks whether sends are arriving correctly on the new routing from day one.

3

Confirm stability post-cutover

After migration, continue monitoring to detect any delayed issues, authentication drift, IP warming dips, or behaviour changes that emerge over time. When multiple monitors degrade together on the new ESP, Telltide tags every related alert with that cross-monitor context, so a platform-side outage is recognisable on the first alert rather than after correlating seven of them by hand.

Most ESP migrations look successful on day one. The new platform is sending. The dashboards show deliveries. But two weeks later, a re-engagement sequence stops reaching a key segment because a filter condition behaves differently on the new platform. Or an IP warming issue quietly suppresses delivery to a particular mailbox provider. These failures are invisible to the sending side. Telltide confirms from the inbox, during the migration window and after it, that the emails you expect are actually landing, and correlates simultaneous failures across monitors so a platform outage looks like a platform outage and not a thousand unrelated alerts.

Monitor through your migration

Start with one monitor free. Paid plans from $49 USD per month. Upgrades kick in when your team grows or you scale past 7 flows, never to unlock a feature.