How to Migrate from Braze to Tradly
Treat a move from Braze as a controlled rebuild, not a bulk contact import. First verify that Tradly supports the journeys and channels you need; then move one use case at a time with consent, suppression, and delivery checks in place.
Inventory the current system
Record Braze audiences, custom fields, event sources, segments, templates, integrations, consent status, suppression lists, active journeys, and reports. Mark which items are essential, which can be retired, and which depend on capabilities you have not confirmed in Tradly.
- Export or document contact fields and data definitions.
- Draw each active journey, including branches, delays, and exit conditions.
- Record sending domains, authentication, integrations, and reporting owners.
Map data, consent, and workflow behavior
Define how each source field and event maps to the new audience and workflow model. Preserve permission and unsubscribe status. Keep transactional and marketing communication rules distinct, and decide how duplicate records and missing values will be handled.
Pilot one email journey
Choose a low-risk journey with a clear trigger and measurable outcome. Rebuild it with a limited test audience, verify rendering and links, confirm suppression rules, and test delivery, failures, and analytics before sending to customers.
Cut over in stages and monitor
Set a cutover plan that prevents contacts from receiving duplicate messages. Keep the old journey available during the agreed rollback window, monitor delivery and engagement, and expand only after the pilot meets your acceptance criteria.