mailexodus
home/migrations/from SendPulse
// migrate from

leave SendPulse. keep the work.

mailexodus reads SendPulse over its API and normalizes subscribers, lists, tags, custom fields into one portable schema — so you move with a report, not a 40-item checklist.

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

see what moves out of SendPulse.

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

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

why teams leave SendPulse.

  • →
    SendPulse migrations need an explicit boundary around what the API exposes.
  • →
    Teams want a dry-run report before rebuilding subscribers, lists, tags, custom fields.
  • →
    Automation360 content, reusable templates, and saved segments are not covered by the current canonical migration surface
// transfer boundary

what mailexodus pulls from SendPulse.

can migrate
  • +
    subscribers
  • +
    lists
  • +
    tags
  • +
    custom fields
  • +
    suppressions
  • +
    campaigns
needs review
  • ?
    suppressions
  • ?
    campaigns
cannot migrate
  • x
    segments
  • x
    templates
  • 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

Address books map to lists. Contacts map to subscribers. Tags map to tags. Variables map to custom attributes. Blacklist entries map to suppressions. Campaigns and templates map to content items

Automation360 content, reusable templates, and saved segments are not covered by the current canonical migration surface

// the playbook

how an agent migrates SendPulse → Sequenzy.

This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from SendPulse, 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 SendPulse REST API credentials with address book, contacts, blacklist, campaign, and Automation360 read access. Paste CLIENT_ID|CLIENT_SECRET, or JSON with clientId and clientSecret. JSON with accessToken is also accepted

01subscribersmigrates
readGET /addressbooks/{book_id}/emails (Read subscribers from SendPulse.)
mapAddress books map to lists. Contacts map to subscribers. Tags map to tags. Variables map to custom attributes. Blacklist entries map to suppressions. Campaigns and templates map to content items mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST add_subscriber (Write or stage subscribers in Sequenzy.) PATCH update_subscriber (Write or stage subscribers in Sequenzy.)
02listsmigrates
readGET /addressbooks (Read lists from SendPulse.)
mapAddress books map to lists. Contacts map to subscribers. Tags map to tags. Variables map to custom attributes. Blacklist entries map to suppressions. Campaigns and templates map to content items mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_list (Write or stage lists in Sequenzy.) POST add_subscribers_to_list (Write or stage lists in Sequenzy.)
03tagsmigrates
readGET /tags (Read tags from SendPulse.)
mapAddress books map to lists. Contacts map to subscribers. Tags map to tags. Variables map to custom attributes. Blacklist entries map to suppressions. Campaigns and templates map to content items mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_tag (Write or stage tags in Sequenzy.)
04custom fieldsmigrates
readGET /addressbooks/{book_id}/variables (Read custom fields from SendPulse.)
mapAddress books map to lists. Contacts map to subscribers. Tags map to tags. Variables map to custom attributes. Blacklist entries map to suppressions. Campaigns and templates map to content items mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePATCH update_subscriber.customAttributes (Write or stage custom fields in Sequenzy.)
05suppressionsneeds review
readGET /blacklist (Read suppressions from SendPulse.)
mapAddress books map to lists. Contacts map to subscribers. Tags map to tags. Variables map to custom attributes. Blacklist entries map to suppressions. Campaigns and templates map to content items 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.)
06campaignsneeds review
readGET /campaigns (Read campaigns from SendPulse.)
mapAddress books map to lists. Contacts map to subscribers. Tags map to tags. Variables map to custom attributes. Blacklist entries map to suppressions. Campaigns and templates map to content items mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_campaign (Write or stage campaigns in Sequenzy.)
stays behind
  • segments
  • templates
  • automations
  • sender reputation and domain warmup
  • historical analytics, revenue attribution, and aggregate reporting
  • contacts already mid-flight inside active automations
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 SendPulse REST API credentials with address book, contacts, blacklist, campaign, and Automation360 read access. Paste CLIENT_ID|CLIENT_SECRET, or JSON with clientId and clientSecret. JSON with accessToken is also accepted

inspect

provider coverage

npx mailexodus@latest info sendpulse

guide

agent playbook

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

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