Migrating from another platform

You can rebuild everything by hand, but you don't have to. An AI agent connected to Pombo can do the move for you: contacts, custom fields, templates, and sequences, with your unsubscribes preserved and your merge tags remapped. Most teams are sending within a day.

Walkthrough: Migrate from another platform covers both the agent-driven path and the manual one.

What comes across

• Contacts, including custom fields, with unsubscribed, bounced, and complained statuses carried over so you never re-email someone who opted out.
• Templates. HTML and MJML come across as-is; the agent can also rebuild them as editable blocks.
• Sequences, recreated step by step with their delays and triggers matched to Pombo's model.
• Merge tags, remapped from the source platform's syntax to Pombo's {{ first_name }} style.

How to do it

1. Connect an AI agent (Claude, Cursor, or any MCP client).
2. Point it at your current tool and ask it to migrate the account. Give it read access to the source, usually an API key or an export.
3. Review what it built. Nothing sends during a migration.
4. Verify your sending domain and go live.

Doing it yourself

If you'd rather not use an agent: import your contacts from a CSV with a status column for unsubscribes, then recreate templates and sequences in the app. The raw MJML import keeps existing designs pixel-for-pixel.