Move off Mailgun without stopping sending.

How the move goes

1. Connect or upload. Paste a read-only key, or upload your contacts and unsubscribes as CSV. Nothing is written until you have seen what we found.
2. Unsubscribes first. Every unsubscribe, bounce and complaint is written before the first contact, so nobody who opted out at your old provider can be emailed from Notix.
3. Your lists and fields. Contacts land in lists you choose, with your custom fields mapped. Anyone suppressed arrives unsubscribed.
4. Add Notix to your domain. Publish our records alongside your old provider's. Both keep sending; DNS has room for both.
5. Move volume gradually. A four-week plan, 15% to 100%, so mailbox providers see a sender that grows steadily. Switch the old provider off at the end, not the start.

What you need from Mailgun

Suppressions → Export unsubscribes, bounces and complaints.

Nothing of yours is held afterwards: the uploaded files are kept for one hour while the import runs and dropped when it finishes.

Your SPF record keeps both

A domain may only have one SPF record, so you add Notix to the line you already have rather than replacing it. Keep include:mailgun.org while Mailgun is still sending, add include:_spf.usenotix.dev beside it, and remove Mailgun's once you have switched off.

What it costs

What does not come over

Send history, analytics and A/B test definitions stay at Mailgun — your reporting starts fresh at Notix. Templates and webhook events are matched up where we can, and anything we cannot convert is named rather than quietly dropped. A migration is one direction, once: Notix does not keep the two accounts in step.