Migration Guide
The complete guide to migrating your email sending from Amazon SES to dedicated IPs — with full IP warming support, zero downtime, and measurable inbox placement improvements.
Migrating from Amazon SES to Dedicated Infrastructure
Amazon SES is a low-cost email delivery service from AWS designed for developers. It works well at lower volumes and for teams that want managed sending without infrastructure decisions. But senders who reach a certain scale — or who've experienced blacklisting, shared IP contamination, or deliverability plateaus — find that the lack of IP isolation and control becomes the bottleneck. This guide covers the complete migration process from Amazon SES to dedicated email infrastructure.
Quick facts: Amazon SES vs. dedicated infrastructure
| Feature | Amazon SES | Cloud Server for Email |
|---|---|---|
| IP type | Shared with thousands | Dedicated — yours only |
| IP reputation control | None — shared pool | Full — isolated per client |
| Blacklist monitoring | Basic or none | 50+ lists, every 4 hours |
| Sending volume visibility | Aggregate only | Per-IP, per-pool detail |
| IP warming | Auto/shared | Guided, per-use-case |
| ISP postmaster access | Limited | Full Postmaster Tools access |
| PowerMTA / Acelle / MailWizz | Not available | Available |
| Custom PTR records | No | Yes — per IP |
Why senders leave Amazon SES
The most common reasons senders at 1M–100M emails/month outgrow Amazon SES:
- Amazon SES provides infrastructure but no deliverability support or guidance
- No dedicated account manager — when things go wrong, you're debugging alone
- SES sandbox restrictions and account review process creates operational risk
- Limited visibility into per-IP reputation and ISP relationship data
- Shared IPs on SES standard plan; dedicated IPs require additional configuration
- No blacklist monitoring — listings go undetected until delivery problems surface
Key benefits after migration
Dedicated support
Named account manager and technical contact vs. AWS support tickets
Active monitoring
Continuous blacklist and reputation monitoring included — SES provides none
Faster resolution
Deliverability incidents resolved in minutes, not hours of debugging
API compatibility
Mailgun-compatible endpoint — minimal code changes from SES SDK
Migration process: 1–2 weeks
Export SES suppression list
Use the AWS CLI or console to export your SES account-level suppression list: aws sesv2 list-suppressed-destinations. This step is critical before any sends.
Review current SES configuration
Document your SES identities (domains and email addresses), configuration sets, and any dedicated IPs. Note your current sending limits and reputation metrics.
Provision dedicated infrastructure
We configure dedicated IPs, monitoring dashboards, and SMTP/API credentials. For SES migrations, the technical setup typically completes in 24 hours.
Update DKIM and SPF
Remove the SES DKIM CNAME records and add your new DKIM TXT records. Update SPF to replace SES includes with your dedicated IP SPF record.
Import suppressions and test
Import your SES suppression list. Send test messages to Gmail, Outlook, and Yahoo and verify authentication headers show pass on all three.
IP warming
For SES migrations, warming is typically faster than cold starts because senders often have established domain reputation. Your account manager will calibrate the warm-up schedule based on your domain age and history.
Ready to migrate from Amazon SES?
Our team manages hundreds of migrations per year. We'll review your current setup, configure your dedicated infrastructure, and guide your IP warm-up. Most clients see measurable inbox placement improvements within 30 days.