why teams leave Constant Contact.
- →Constant Contact migrations need an explicit boundary around what the API exposes.
- →Teams want a dry-run report before rebuilding subscribers, lists, tags, custom fields.
- →OAuth token scope controls campaign and segment visibility
what mailexodus pulls from Constant Contact.
can migrate
- +subscribers
- +lists
- +tags
- +segments
- +custom fields
- +suppressions
- +campaigns
needs review
- ?OAuth token scope controls campaign and segment visibility
cannot migrate
- xtemplates
- xautomations
- xsender reputation and domain warmup
- xhistorical analytics, revenue attribution, and aggregate reporting
- xcontacts already mid-flight inside active automations
- xA/B test results and provider-specific experiment history
- xprovider-native design blocks, product widgets, coupons, and private assets that are not exposed by API
source adapter
// the playbookAutomated adapter
Contacts map to subscribers. Contact lists map to lists. Tags and custom fields map directly. Campaign activities map to draft campaigns when HTML is available
OAuth token scope controls campaign and segment visibility
how an agent migrates Constant Contact → Sequenzy.
This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from Constant Contact, map it to the portable schema, write it to the destination. mailexodus never writes; your agent does, with this report in hand.
01 · authenticate
Paste a Constant Contact V3 access token with permission to read contacts, lists, tags, custom fields, segments, campaign content, and email status data
01subscribersmigrates
readGET /v3/contacts (Read subscribers from Constant Contact.)
mapContacts map to subscribers. Contact lists map to lists. Tags and custom fields map directly. Campaign activities map to draft campaigns when HTML is available 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 /v3/contact_lists (Read lists from Constant Contact.)
mapContacts map to subscribers. Contact lists map to lists. Tags and custom fields map directly. Campaign activities map to draft campaigns when HTML is available 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 /v3/contact_tags (Read tags from Constant Contact.)
mapContacts map to subscribers. Contact lists map to lists. Tags and custom fields map directly. Campaign activities map to draft campaigns when HTML is available mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_tag (Write or stage tags in Sequenzy.)
04segmentsmigrates
readGET /v3/segments (Read segments from Constant Contact.)
mapContacts map to subscribers. Contact lists map to lists. Tags and custom fields map directly. Campaign activities map to draft campaigns when HTML is available mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_segment (Write or stage segments in Sequenzy.)
05custom fieldsmigrates
readGET /v3/contact_custom_fields (Read custom fields from Constant Contact.)
mapContacts map to subscribers. Contact lists map to lists. Tags and custom fields map directly. Campaign activities map to draft campaigns when HTML is available 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.)
06suppressionsmigrates
readGET /v3/contacts?status=unsubscribed (Read suppressions from Constant Contact.)
mapContacts map to subscribers. Contact lists map to lists. Tags and custom fields map directly. Campaign activities map to draft campaigns when HTML is available 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.)
07campaignsmigrates
readGET /v3/emails (Read campaigns from Constant Contact.)
mapContacts map to subscribers. Contact lists map to lists. Tags and custom fields map directly. Campaign activities map to draft campaigns when HTML is available 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
- templates
- automations
- sender reputation and domain warmup
- historical analytics, revenue attribution, and aggregate reporting
- contacts already mid-flight inside active automations
- A/B test results and provider-specific experiment history
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.
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: Paste a Constant Contact V3 access token with permission to read contacts, lists, tags, custom fields, segments, campaign content, and email status data
inspect
provider coverage
npx mailexodus@latest info constant-contact
guide
agent playbook
npx mailexodus@latest guide --from constant-contact --to sequenzy
agent
Use mailexodus skill: Constant Contact → Sequenzy playbook