Migration guidePostmark to Sendcorex

Migrate from Postmark. Keep your deliverability.

A step-by-step plan for moving off Postmark — mapping message streams, 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

Rename the fields, swap the header — no SDK needed

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 Postmark account active — you'll run both in parallel for a few weeks, not cut over instantly. Before you start, list every server and message stream you use, plus every template alias your code calls. Export suppressions from each stream so you can load them into Sendcorex before the first real send.

  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 Postmark's DKIM record and its Return-Path CNAME (typically on a pm-bounces subdomain) in place — they sit on their own hostnames, so they won't conflict with Sendcorex's records.

  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

    Postmark authenticates with an X-Postmark-Server-Token header and PascalCase fields (From, To, Subject, HtmlBody). Swap that for a Bearer token and lowercase from, to, subject and html, and drop MessageStream. If you send over SMTP, change the host from smtp.postmarkapp.com to smtp.sendcorex.com and use your new API key as both username and password. Postmark templates don't carry over: render the HTML in your own code and send it as html.

  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. Move one message stream at a time, starting with your lowest-risk mail.

  6. 6

    Cut over fully, then retire Postmark's DNS records

    Once 100% of volume runs cleanly through Sendcorex for a few days, remove Postmark's DKIM record and Return-Path CNAME, then delete the servers and cancel. Export any message history you need first — Postmark only keeps it for a limited time.

Step 4 in practice

The code change, side by side

Before — Postmark
import { ServerClient } from 'postmark';
const client = new ServerClient('POSTMARK_SERVER_TOKEN');
await client.sendEmail({
  From: 'hello@yourdomain.com',
  To: 'customer@example.com',
  Subject: 'Welcome!',
  HtmlBody: '<h1>You are in.</h1>',
  MessageStream: 'outbound',
});
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

  • Sendcorex's SPF and DKIM records are published alongside Postmark's, not replacing them yet

  • 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 every Postmark message stream and loaded into Sendcorex

  • Postmark bounce and spam-complaint webhooks replaced with a handler for Sendcorex events

  • Any template-alias sends now render HTML in your own code

  • 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 Postmark, that IP's reputation stays behind — your domain's reputation moves with you, which is why the ramp matters.

Ready to move off Postmark?

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

Get started free

No credit card required