mailexodus
home/migrations/from Postmark
// migrate from

leave Postmark. keep the work.

mailexodus reads Postmark over its API and normalizes suppressions, templates into one portable schema — so you move with a report, not a 40-item checklist.

agentUse mailexodus skill: Postmark → Sequenzy playbook
// try it

see what moves out of Postmark.

A live route check, computed from Postmark's real API surface. Pick any destination to compare import support — nothing is written.

analyzing Postmark…
source modePartial automated adapter
source exports2
Mailchimp imports8
destination gapsautomations
data leaves machineno · dry-run
$npx mailexodus@latest migrate --from postmark --to mailchimp --dry-run
agentUse mailexodus skill: Postmark → Mailchimp playbook
running…open the Postmark migration guide →
// why teams leave

why teams leave Postmark.

  • →
    Postmark migrations need an explicit boundary around what the API exposes.
  • →
    Teams want a dry-run report before rebuilding suppressions, templates.
  • →
    Postmark has no native marketing subscriber, list, segment, campaign, or automation export
// transfer boundary

what mailexodus pulls from Postmark.

can migrate
  • +
    suppressions
  • +
    templates
needs review
  • ?
    suppressions
  • ?
    templates
cannot migrate
  • x
    subscribers
  • x
    lists
  • x
    tags
  • x
    segments
  • x
    custom fields
  • x
    campaigns
  • x
    automations
  • x
    sender reputation and domain warmup
  • x
    historical analytics, revenue attribution, and aggregate reporting
  • x
    contacts already mid-flight inside active automations
  • x
    A/B test results and provider-specific experiment history
  • x
    provider-native design blocks, product widgets, coupons, and private assets that are not exposed by API
source adapter

Partial automated adapter

Suppressions map to suppression records. Templates map to transactional templates

Postmark has no native marketing subscriber, list, segment, campaign, or automation export

// the playbook

how an agent migrates Postmark → Sequenzy.

This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from Postmark, map it to the portable schema, write it to the destination. mailexodus never writes; your agent does, with this report in hand.

01 · authenticate

Create a Postmark server token with suppression and template read access. Paste the server token, or JSON with serverToken

01suppressionsneeds review
readGET /message-streams/{stream_id}/suppressions (Read suppressions from Postmark.)
mapSuppressions map to suppression records. Templates map to transactional templates mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePATCH update_subscriber.status (Write or stage suppressions in Sequenzy.)
02templatesneeds review
readGET /templates (Read templates from Postmark.)
mapSuppressions map to suppression records. Templates map to transactional templates mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_template (Write or stage templates in Sequenzy.)
stays behind
  • subscribers
  • lists
  • tags
  • segments
  • custom fields
  • campaigns
guardrails
  • Sender reputation is earned at the destination — set up SPF/DKIM/DMARC and a warmup ramp; it does not transfer.
  • Keep the source platform active until authentication, warmup, and in-flight automations have finished.
  • Honor suppressions before the first send.
  • After writing, verify counts per object type against the source before switching live sends.
// run it

guide your agent, or follow it yourself.

Pull the full playbook from the skill prompt, CLI, or MCP server, then work the steps. Start by confirming credentials: Create a Postmark server token with suppression and template read access. Paste the server token, or JSON with serverToken

inspect

provider coverage

npx mailexodus@latest info postmark

guide

agent playbook

npx mailexodus@latest guide --from postmark --to sequenzy

agentUse mailexodus skill: Postmark → Sequenzy playbook
compare Postmark alternatives →browse every migration page →