mailexodus
home/migrations/to Flodesk
// migrate to

move to Flodesk without rebuilding by hand.

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

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

bring your data into Flodesk.

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

analyzing Klaviyo…
source modeAutomated adapter
source exports8
Flodesk imports3
destination gapslists, tags, suppressions, campaigns, templates, automations
data leaves machineno · dry-run
$npx mailexodus@latest migrate --from klaviyo --to flodesk --dry-run
agentUse mailexodus skill: Klaviyo → Flodesk playbook
running…open the Klaviyo migration guide →
// fit

when Flodesk is the right move.

Flodesk is a strong fit for teams that want flodesk teams moving subscribers, segments, and subscriber custom fields 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 Flodesk objects.

// inbound

what Flodesk receives.

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

// before you switch

plan the move to Flodesk.

  1. Authenticate your sending domain in Flodesk (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 Flodesk.
  3. QA migrated templates and segments inside Flodesk, and send seed tests before any live campaign.
  4. Keep your current platform active until in-flight automations finish and Flodesk 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 flodesk

playbook

agent playbook

Ask mailexodus for a migration_playbook with to=flodesk

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