# Migrate from Sparkpost

## Integration
Integration is the same whether we choose Mailgun or Sendgrid.
It happens through Iterable.
Given this and the fact that we are unlikely to interface with the service directly, I'd lean towards Mailgun due to the:
- 99.99% uptime SLA
- 24/7 support

It seems like our main issues with Sparkpost was their neglect and unwillingness to work with us to resolve an email reputation issue. Having support available would alleviate that.

## Questions

### What DNS Changes need to be made?
- We can remove Sparkpost from our DNS records when the migration is complete (only used to send marketing emails through Iterable).

### How does an IP warmup actually work?
It gradually sends emails from the new IP but is that automated?
Does this happen through Iterable?
If Iterable is initiating the request that an email be sent to a user, how does it select Sparkpost or Mailgun during the IP warmup?

### How does the Iterable + ESP (email send provider) integration work?
Looks like we need to reach out directly to see what this would look like:
https://support.iterable.com/hc/en-us/articles/360021284071
Maybe consists of:
- adding an ESP in Iterables interface
- create API key on ESPs platform
- add API key for that ESP into Iterable
- ensure our DNS records reflect that ESP can send emails on behalf of our domain