Migration guideAmazon SES to Sendcorex

Migrate from Amazon SES. Keep your deliverability.

A step-by-step plan for moving off Amazon SES — swapping the AWS SDK, publishing new DNS records, and the parallel-sending window that keeps your sender reputation intact.

No credit card required · Migration usually takes 1–2 weeks end to end

Code changes

Minutes

Swap the AWS SDK call for one REST request

DNS propagation

24–48h

SPF, DKIM and DMARC records need time to settle

Full migration

1–2 wks

Includes the parallel-sending warm-up window

Typical timeline for a mid-size sender. Larger lists or dedicated IP warm-up can take longer.

The migration

Six steps, in order

Get started free
  1. 1

    Create your Sendcorex account and API key

    Sign up free and generate an API key from the dashboard. Keep your Amazon SES account active — you'll run both in parallel for a few weeks, not cut over instantly. Before you start, list every sender: apps using the AWS SDK, services using SES SMTP credentials, and anything wired to a configuration set or SNS topic. Export your account-level suppression list too, so you can load it into Sendcorex and never re-mail an address SES already suppressed.

  2. 2

    Add and verify your sending domain

    Add your domain in Sendcorex, then publish the SPF, DKIM and DMARC records it gives you as new DNS entries. Leave SES's Easy DKIM CNAMEs and custom MAIL FROM records in place — DKIM selectors are per provider, so both can be valid at once. Merge Sendcorex's SPF include into your existing SPF record instead of adding a second one.

  3. 3

    Wait for DNS to propagate, then verify

    Give it 24–48 hours. Check verification status in the Sendcorex dashboard before sending anything — sending through unverified DNS is what causes the deliverability problems people blame on migrations.

  4. 4

    Update your code — drop the AWS SDK

    Replace the SendEmailCommand call with a plain REST request to Sendcorex. Nested SES fields like Destination.ToAddresses, Content.Simple.Subject and Body.Html.Data become flat to, subject and html fields. If you send over SMTP, change the host from email-smtp.REGION.amazonaws.com to smtp.sendcorex.com and use your new API key as both username and password.

  5. 5

    Shift volume gradually, not all at once

    Start with 10–20% of sends routed through Sendcorex, watch delivery and bounce rates in real time, then increase over 1–2 weeks. This lets Sendcorex's IPs warm up against mailbox providers instead of arriving as an unknown sender all at once. Keep an eye on SES's reputation metrics while it still carries most of the volume, and on Sendcorex's dashboard as its share grows.

  6. 6

    Cut over fully, then retire Amazon SES's DNS records

    Once 100% of volume runs cleanly through Sendcorex for a few days, remove the SES DKIM CNAMEs, custom MAIL FROM records and SPF include, then delete the verified identity, SNS topics and configuration sets, and retire the IAM users behind your SES credentials.

Step 4 in practice

The code change, side by side

Before — Amazon SES (AWS SDK v3)
import { SESv2Client, SendEmailCommand } from '@aws-sdk/client-sesv2';
const ses = new SESv2Client({ region: 'us-east-1' });
await ses.send(new SendEmailCommand({
  FromEmailAddress: 'hello@yourdomain.com',
  Destination: { ToAddresses: ['customer@example.com'] },
  Content: { Simple: {
    Subject: { Data: 'Welcome!' },
    Body: { Html: { Data: '<h1>You are in.</h1>' } },
  } },
}));
After — Sendcorex (plain REST, no SDK)
send.js
const response = await fetch('https://mail.sendcorex.com/v3.0/send', {
  method: 'POST',
  headers: {
    'Authorization': 'YOUR_API_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    to: 'customer@example.com',
    from: 'hello@yourdomain.com',
    senderName: 'Your Company',
    subject: 'Welcome!',
    body: '<h1>You are in.</h1>',
  }),
});
Before you cut over

Pre-flight checklist

  • SPF is a single record that includes both Sendcorex and Amazon SES for now

  • DKIM selector for Sendcorex shows as verified in the dashboard

  • Test send delivered to Gmail, Outlook, and Yahoo test inboxes without landing in spam

  • SES suppression list exported and loaded into Sendcorex before the first real send

  • Event handling moved off SNS and configuration sets to webhooks for Sendcorex delivery and bounce events

  • Bounce and complaint rate monitored daily during the ramp-up window

Before you switch

Common questions

Steps and timelines reflect typical migrations as of 2026 and may vary based on list size, DNS provider, and existing authentication setup.

Not if you run a parallel sending window instead of an instant cutover. Sender reputation lives on the sending domain and IP, so warming up Sendcorex's IPs for 1–2 weeks while gradually shifting volume avoids a deliverability dip. If you had a dedicated IP on SES, that IP's reputation stays behind — your domain's reputation moves with you, which is why the ramp matters.

Ready to move off Amazon SES?

Create your account, verify your domain, and start the parallel-sending window today.

Get started free

No credit card required