Migrate from Customer.io to Send & Retain
Move the email parts of your journeys. Your agent rebuilds them as paused automations, from your exports and notes.
✓Free to start. Unlimited contacts on every tier.
Inventory before cutover
Inventory
Source material read
Rebuild
Created paused
Verify
Real inbox test
Switch
One trigger first
Destination automation
Paused until validation and explicit cutover
[ 01 / 05 ]Step by step
How do I migrate from Customer.io?
There's no Customer.io connector. Your agent rebuilds each journey from screenshots, exports, or what you describe.
List the journeys worth moving
Pick the email-only journeys first. Leave any journey that leans on push, SMS, or in-app steps until you've decided what replaces them.
Import unsubscribes, then people
Export unsubscribed and bounced people and import them as your block list. Then import everyone else as contacts; attributes come with them.
Send your events here too
Send the same product events you send Customer.io, like signup or trial started, to the Send & Retain events API.
Rebuild email journeys as paused automations
Share a screenshot or describe each journey. Your agent rebuilds it as an automation triggered by those events, paused until you turn it on.
Test, then switch one journey
Send each email to your own inbox, turn the new automation on, and stop the Customer.io journey's email steps.
[ 02 / 05 ]Example prompts
What can I ask my agent to do?
Paste these into any agent connected to Send & Retain.
Rebuild
“Here's a screenshot of our Customer.io onboarding journey. Rebuild the email steps here as a paused automation.”
Events
“Find where we call Customer.io's track API and send the same events to Send & Retain.”
Scope
“Which of these journeys are email only, and which depend on push or SMS?”
Review
“Walk me through the rebuilt journey step by step before I turn it on.”
[ 03 / 05 ]Customer.io vs Send & Retain
What changes when I leave Customer.io?
Channels
Email, push, SMS, in-app, and more
Email only
Journeys
Visual multichannel journeys
Email automations triggered by product events, always created paused
Pricing
Grows with the number of profiles
Priced on sends. Unlimited contacts on every tier
Transactional email
A transactional API alongside journeys
Same API and contact record as your automations
Who does the work
A marketing team in the dashboard, or an agent over its MCP server
Your AI agent over MCP, with your approval
[ 04 / 05 ]Honest limits
What doesn't move from Customer.io?
People, unsubscribes, events, and email journeys move. Some things stay behind.
- Push, SMS, and in-app steps. Send & Retain sends email only.
- Journeys themselves. There's no connector, so your agent rebuilds them from what you share.
- Open and click history stays in Customer.io.
- If cross-channel journeys are central to your business, Customer.io may still be the better fit.
[ 05 / 05 ]Related
Related pages
Questions people ask us
Move one email journey first.
Import your unsubscribes, send your events, and rebuild one journey as a paused automation.