Move from Braze to Sendora.
Move Canvas + Catalog + audiences + BYOD email from Braze to Sendora Automation + Email + Push + In-App.
Step-by-step
- 1
1. Export Canvas + Catalog + audience segments
Braze REST API gives JSON dumps of Canvases (journeys), Catalogs (product / content metadata), and audience segments. Pull 90 days of campaign metrics for parity comparison.
1 day - 2
2. Migrate user data + traits
User export via Braze REST API maps to Sendora Customers profiles. Custom Attributes become Customer traits. Subscription groups port to Sendora preference center.
1 day - 3
3. Configure BYOD email + APNs + FCM
Reuse your verified domain — DKIM/SPF/DMARC stay valid. APNs (.p8 + key_id + team_id) + FCM service-account JSON upload to Sendora Push settings.
Half a day - 4
4. Rebuild Canvases as Sendora Automation journeys
Each Canvas becomes a Sendora Automation flow. Branching + delays + Holdouts + per-step A/B all port directly. AI step type can collapse Braze's branching logic into a single decide call.
1-2 days per major Canvas - 5
5. Map Catalogs to Customer traits + Data Sync
Braze Catalogs (product/content metadata for personalization) port to Sendora Customer traits + Data Sync for the dynamic-content joins. Liquid-style interpolation in templates remains.
1 day - 6
6. Migrate Content Cards + In-App Messages
Content Cards become Sendora In-App Messages (banners + modals). Variants from Experiments module + audience targeting from Customers.
1 day - 7
7. Side-by-side test + sunset
Parallel-run for 2-4 weeks. Compare delivery, open, click, conversion rates in Health module. Cut over once parity confirmed + cancel Braze.
2-4 weeks observation
Watch-outs
- Braze Sage predictive features port to Sendora AI step types but exact parity requires review per use case.
- Catalog deep-merge logic for personalization can be intricate — review per-template before migration.
- Enterprise procurement contract + global compliance review can extend the cutover by months — plan accordingly.
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.