mailexodus
home/migrations/from Flodesk
// migrate from

leave Flodesk. keep the work.

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

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

see what moves out of Flodesk.

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

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

why teams leave Flodesk.

  • →
    Flodesk migrations need an explicit boundary around what the API exposes.
  • →
    Teams want a dry-run report before rebuilding subscribers, segments, custom fields.
  • →
    Official docs do not expose campaign or template body export
// transfer boundary

what mailexodus pulls from Flodesk.

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

Subscribers map to subscribers. Segments map to segments. Custom fields map to custom attributes

Official docs do not expose campaign or template body export

// the playbook

how an agent migrates Flodesk → Sequenzy.

This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from Flodesk, 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 a Flodesk API key under account integrations. Paste the key, or JSON with apiKey

01subscribersmigrates
readGET /v1/subscribers (Read subscribers from Flodesk.)
mapSubscribers map to subscribers. Segments map to segments. Custom fields map to custom attributes 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.)
02segmentsneeds review
readGET /v1/segments (Read segments from Flodesk.)
mapSubscribers map to subscribers. Segments map to segments. Custom fields map to custom attributes mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_segment (Write or stage segments in Sequenzy.)
03custom fieldsmigrates
readGET /v1/custom-fields (Read custom fields from Flodesk.)
mapSubscribers map to subscribers. Segments map to segments. Custom fields map to custom attributes 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.)
stays behind
  • lists
  • tags
  • suppressions
  • campaigns
  • templates
  • 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 a Flodesk API key under account integrations. Paste the key, or JSON with apiKey

inspect

provider coverage

npx mailexodus@latest info flodesk

guide

agent playbook

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

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