when Benchmark Email is the right move.
Benchmark Email is a strong fit for teams that want benchmark email teams moving contacts, lists, custom fields, suppressions, templates, and campaign content 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 Benchmark Email objects.
// inboundwhat Benchmark Email receives.
- +subscribers
- +lists
- +tags
- +custom fields
- +suppressions
- +campaigns
- +templates
- ?destination mappings still need final operator review
- xsegments
- xautomations
Partial automated adapter
Contact lists map to lists. Contacts map to subscribers. Fields map to custom attributes. Campaign details map to campaign content
Some accounts require legacy API authentication Dry-run the report first, then approve writes when the counts and destination gaps look right.
plan the move to Benchmark Email.
- Authenticate your sending domain in Benchmark Email (SPF, DKIM, DMARC) and plan a warmup window — sender reputation is earned here, it does not transfer.
- Bring consent and suppression state across first, so unsubscribes and bounces are honored from the first send in Benchmark Email.
- QA migrated templates and segments inside Benchmark Email, and send seed tests before any live campaign.
- Keep your current platform active until in-flight automations finish and Benchmark Email is warmed and trusted.
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.
destination coverage
npx mailexodus@latest info benchmark-email
agent playbook
Ask mailexodus for a migration_playbook with to=benchmark-email
Use mailexodus skill: your source → Benchmark Email playbook