why teams leave Zoho Campaigns.
- →Zoho Campaigns migrations need an explicit boundary around what the API exposes.
- →Teams want a dry-run report before rebuilding subscribers, lists, segments, custom fields.
- →Raw campaign HTML and template retrieval are unclear in public docs. Workflow import/export was not verified as a public API surface. API rate limits require batching
what mailexodus pulls from Zoho Campaigns.
- +subscribers
- +lists
- +segments
- +custom fields
- +campaigns
- ?segments
- ?campaigns
- xtags
- xsuppressions
- 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
Partial automated adapter
Lists map to lists. Contacts map to subscribers. Segments map to segments. Fields map to custom attributes. Campaign details map to campaigns when body content is available
Raw campaign HTML and template retrieval are unclear in public docs. Workflow import/export was not verified as a public API surface. API rate limits require batching
how an agent migrates Zoho Campaigns → Sequenzy.
This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from Zoho Campaigns, map it to the portable schema, write it to the destination. mailexodus never writes; your agent does, with this report in hand.
Create a Zoho OAuth token with Campaigns contact and campaign read scopes. Paste DATA_CENTER|ACCESS_TOKEN, for example com|TOKEN or eu|TOKEN, or JSON with dataCenter and accessToken
- tags
- suppressions
- templates
- automations
- sender reputation and domain warmup
- historical analytics, revenue attribution, and aggregate reporting
- 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: Create a Zoho OAuth token with Campaigns contact and campaign read scopes. Paste DATA_CENTER|ACCESS_TOKEN, for example com|TOKEN or eu|TOKEN, or JSON with dataCenter and accessToken
provider coverage
npx mailexodus@latest info zoho-campaigns
agent playbook
npx mailexodus@latest guide --from zoho-campaigns --to sequenzy
Use mailexodus skill: Zoho Campaigns → Sequenzy playbook