Migration guideElastic Email to Sendcorex

Migrate from Elastic Email. Keep your deliverability.

A step-by-step plan for moving off Elastic Email — swapping the API call, 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

Flatten the nested payload and swap the API key header

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 Elastic Email account active — you'll run both in parallel for a few weeks, not cut over instantly. Note which API version your code calls (v2 or v4), whether you send over SMTP, and whether contacts or campaigns live in Elastic Email too. Export your contacts and your suppressions — bounces, unsubscribes and abuse reports — so opt-outs move with you.

  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 Elastic Email's SPF include, DKIM record and tracking CNAME in place, and merge Sendcorex's SPF include into your existing SPF record rather than 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 — endpoint and key only

    Elastic Email's v4 API nests content under Recipients and Content (From, Subject, Body) and authenticates with an X-ElasticEmail-ApiKey header; v2 sends form fields such as apikey, bodyHtml and to. Either way, flatten to a JSON body with from, to, subject and html, and use a Bearer token. If you send over SMTP, change the host from smtp.elasticemail.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. A percentage flag around your send function is the simplest way to split traffic.

  6. 6

    Cut over fully, then retire Elastic Email's DNS records

    Once 100% of volume runs cleanly through Sendcorex for a few days, remove Elastic Email's SPF include, DKIM record and tracking CNAME, export any contacts and logs you still need, and cancel the subscription.

Step 4 in practice

The code change, side by side

Before — Elastic Email API v4
await fetch('https://api.elasticemail.com/v4/emails/transactional', {
  method: 'POST',
  headers: {
    'X-ElasticEmail-ApiKey': 'ELASTIC_EMAIL_API_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    Recipients: { To: ['customer@example.com'] },
    Content: {
      From: 'hello@yourdomain.com',
      Subject: 'Welcome!',
      Body: [{ ContentType: 'HTML', Content: '<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 Elastic Email 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

  • Suppressions exported from Elastic Email and loaded into Sendcorex before the first real send

  • Elastic Email webhooks replaced with a handler 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.

Ready to move off Elastic Email?

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

Get started free

No credit card required