ESP migration

Switching ESPs shouldn't mean starting over with Gmail.

One stale SPF include or a missed DKIM selector and your first week on the new provider lands in spam. Migrate with a baseline, verified DNS before cutover, drift detection during it, and placement proof after.

Baseline my domain freeSee guided DNS
The migration playbook

Five steps to a cutover nobody notices.

Step 1

Baseline before you touch anything

Add your domain and IPs and capture the starting point: the 0-100 reputation score with per-source breakdown, plus Gmail domain and IP reputation, spam rate and auth compliance from the Google Postmaster integration. If something dips later, you will know it was the migration.

Step 2

Generate the new provider's DNS, verified

ESP-aware guided DNS knows 51 providers by their SPF includes, DKIM selectors and MX signatures. Generate the new records, publish in one click to Cloudflare, GoDaddy, Name.com or Dynadot, and live-verify them before you cut a single message over.

Step 3

Watch for drift during the cutover

MX change detection and SPF/DKIM/DMARC validation keep watching while both providers are in play. If a record gets edited, dropped or overwritten mid-window, you hear about it from an alert, not from a customer.

Step 4

Prove placement before and after

Run inbox placement tests from your own SMTP (presets for Gmail, M365, Yahoo and Zoho) to seed inboxes across Gmail, Workspace, M365, Yahoo, Zoho and AOL. Folder-level results, Primary, Promotions, Spam or missing, plus per-seed SPF, DKIM and DMARC. Re-check after cutover and compare.

Step 5

Tighten rechecks for the window

During the migration window, scheduled rechecks at up to 15-minute resolution catch a new listing across all 48 sources almost as soon as it happens. Score-drop alerts fire to email, Slack or a signed webhook.

  • Nothing in your mail path: we read public signals, never your ESP account
  • One-click publish of generated records to Cloudflare, GoDaddy, Name.com or Dynadot
  • Manual re-scan anytime right after each DNS change, with a short cooldown
  • New sending subdomain? Build its reputation with Inbox Boost before production traffic
Features doing the heavy lifting

The parts of the platform this plan leans on.

Feature

Guided DNS setup

Generate, verify and publish SPF/DKIM/DMARC records in one click.

Learn more Feature

Deliverability monitoring

SPF, DKIM, DMARC, MTA-STS, BIMI, TLS, MX and PTR, checked continuously.

Learn more Feature

Inbox placement testing

See whether you land in Primary, Promotions or Spam across providers.

Learn more
See it play out

A cutover with nothing left to luck.

The four checkpoints of a safe ESP switch. Click any step or let it play.

pre-cutover · send.acme-corp.com
reputation score96 / 100
Gmail spam rate0.02%
placement testPrimary across seeds
Questions

Migration questions, answered.

Does SenderSignal work with my ESP?
The ESP detection catalog covers 51 providers by their SPF includes, DKIM selectors and MX signatures, and that catalog powers ESP-aware DNS generation. And because monitoring reads public signals, DNS records, blacklists, reputation feeds, it is ESP-agnostic: whatever you send through, we can watch it.
Will you touch my sending during the migration?
No. SenderSignal never sits in your mail path and never needs access to your ESP account. We monitor from the outside: your DNS, your blacklist status, your reputation score, and where your test messages land.
What if my new ESP wants a fresh sending subdomain?
Common, and a good practice. Use guided DNS to publish the subdomain’s SPF, DKIM and DMARC correctly, then use Inbox Boost to build its sending reputation with an automated ramp and real engagement before you point production volume at it. Entry schedules ramp to 250 messages per day and the top tier to 3,000 per day.
How do I know the cutover did not break anything?
Three ways. Live DNS verification confirms the new SPF include and DKIM selectors resolve before you flip traffic. MX and SPF/DKIM change detection watches for drift during the cutover window. And inbox placement tests, sent from your own SMTP to seeds across Gmail, Workspace, M365, Yahoo, Zoho and AOL, show folder-level results plus per-seed SPF, DKIM and DMARC, before and after.
How closely can you watch things during the migration window?
Scheduled rechecks run daily to every 15 minutes depending on plan, and you can trigger a manual re-scan anytime with a short cooldown. At 15-minute resolution, a listing or an auth failure during cutover surfaces while you can still act on it, with alerts to email, Slack or an HMAC-signed webhook.
Baseline first, cut over second

Get your before picture today.

Start free, add the domain, capture the baseline. Cut over when the records verify, not before.

Start freeMore playbooks