Move from Customer.io to Sendora.
Move journeys + audiences + templates from Customer.io to Sendora Automation + Email + Push.
Step-by-step
- 1
1. Export journeys + templates + audiences
Customer.io's Workspace Export ZIPs every campaign + Series + template + segment definition. Import into a local working dir. Map each Series to a Sendora Automation flow.
1 hour - 2
2. Rebuild audiences in Sendora Customers
Customer.io segments become Sendora audiences. Same nested AND/OR query shape; real-time membership instead of Customer.io's sync cadence. Audience-build over Sendora Analytics events directly — no Segment dependency.
Half a day - 3
3. Rebuild templates in Sendora Email + Push
Customer.io Liquid templates port nearly 1:1 to Sendora Email's Liquid renderer. Push payload shape is identical (title / body / data / actions). Subject-line variants + per-channel previews ship in the dashboard.
1-2 days depending on template count - 4
4. Rebuild journeys in Sendora Automation
Customer.io Series triggers (event / segment / schedule / webhook) all exist in Sendora Automation. Branching, delays, wait-for-event, holdouts all port directly. AI step type (generate / decide / extract) lets you collapse "check segment + send template" branches into one AI decision call.
Half a day per Series - 5
5. Migrate BYOD email setup
Sendora uses your verified domain via DKIM-signed BYOD (real Resend Domains integration). Add the DNS records Sendora generates — DKIM + SPF + DMARC. Customer.io's IP pool history stays with them; Sendora warms a new pool for you with the 30-day probation period for new senders.
1 hour + DNS propagation - 6
6. Plumb push providers
APNs (cert or token auth) + FCM service account. Upload via dashboard. Sendora handles APNs/FCM retries + invalid-token pruning automatically — same as Customer.io.
30 min - 7
7. Side-by-side test then cut over
Run Sendora workflows in parallel with Customer.io for 1-2 weeks. Compare delivery rates, open rates, click-throughs via Health + Analytics modules. Once parity holds, kill the Customer.io API integrations + cancel the subscription.
1-2 weeks calendar (mostly observation)
Watch-outs
- Customer.io Series with deep custom Liquid logic may need partial rewrites — Sendora supports Liquid but with a tighter feature set.
- Domain reputation transfer is real — warm gently. Sendora's probation pool handles the 30-day warmup automatically.
- Existing Customer.io webhook events your apps consume need re-pointing to Sendora's webhook taxonomy (different event-type names).
Automation
Event-triggered journeys with 8 step types — Email / Push / SMS / Webhook / Update Profile / Wait / Branch / AI — over the same event taxonomy every other module already emits.
Customer.io + Iterable + Braze run journeys but only over the data they have. Sendora journeys run over Sendora data — every event from every module (Analytics, Auth, Support, Push delivery, Email bounce, CSAT rating, KB view, anomaly detection) lands on the same event bus the workflow trigger reads. Branch on a profile trait, send via Email or Push or SMS, update a trait, fire a webhook, run an AI generate/decide/extract step, wait for a delay — 8 step types implemented in `step-executor.ts`. Trigger model is single: `{ eventType, filters }` with wildcard matching. Audience-join, CSAT detractor, KB view all become triggers because each emits a canonical event the workflow can subscribe to.
Read full Automation pageStuck on the migration? We'll help.
Launch partners get white-glove migration help direct from the engineering team. Free plan covers real product use during the parallel-run period.