mailexodus
home/migrations/to SendPulse
// migrate to

move to SendPulse without rebuilding by hand.

mailexodus normalizes your current platform into one portable schema, then checks what SendPulse can actually import. You get a route report before your agent writes anything.

agentUse mailexodus skill: your source → SendPulse playbook
// try it

bring your data into SendPulse.

Pick the platform you're leaving and generate a route playbook. The report shows what maps cleanly into SendPulse's model and what needs review — before you approve writes.

analyzing Klaviyo…
source modeAutomated adapter
source exports8
SendPulse imports6
destination gapssegments, templates, automations
data leaves machineno · dry-run
$npx mailexodus@latest migrate --from klaviyo --to sendpulse --dry-run
agentUse mailexodus skill: Klaviyo → SendPulse playbook
running…open the Klaviyo migration guide →
// fit

when SendPulse is the right move.

SendPulse is a strong fit for teams that want sendpulse teams moving address books, contacts, tags, variables, blacklist entries, and campaigns into a cleaner operating model. The migration risk is rarely the CSV — it is the automation graph: triggers, delays, branches, template references, and consent state. mailexodus puts a portable schema in the middle so those objects are inspected before they become SendPulse objects.

// inbound

what SendPulse receives.

can import
  • +
    subscribers
  • +
    lists
  • +
    tags
  • +
    custom fields
  • +
    suppressions
  • +
    campaigns
needs review
  • ?
    destination mappings still need final operator review
not exposed for import
  • x
    segments
  • x
    templates
  • x
    automations
destination 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 Dry-run the report first, then approve writes when the counts and destination gaps look right.

// before you switch

plan the move to SendPulse.

  1. Authenticate your sending domain in SendPulse (SPF, DKIM, DMARC) and plan a warmup window — sender reputation is earned here, it does not transfer.
  2. Bring consent and suppression state across first, so unsubscribes and bounces are honored from the first send in SendPulse.
  3. QA migrated templates and segments inside SendPulse, and send seed tests before any live campaign.
  4. Keep your current platform active until in-flight automations finish and SendPulse is warmed and trusted.
// migrate it

start with the route playbook.

The agent prompt returns a route report with source exports, destination imports, skipped objects, and manual-review tasks. When it looks right, wire credentials and approve writes from a controlled machine.

inspect

destination coverage

npx mailexodus@latest info sendpulse

playbook

agent playbook

Ask mailexodus for a migration_playbook with to=sendpulse

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