How a migration maps
Most notification platforms share the same building blocks.
One difference to plan around: Courier separates content (templates) from orchestration (journeys). A PM can change copy while an engineer changes timing.
The general plan
- Connect your providers as .
- Move recipients into and rebuild segments as .
- Recreate content as and orchestration as .
- Move preferences and, if you use them, tenants.
- Cut over sends and verify in .
Migrate from your platform
From an in-house system
Replace homegrown notification code, one type at a time.
From Knock
Map workflows, recipients, and preferences from Knock.
From SuprSend
Move subscribers, templates, and channels from SuprSend.
From Novu
Map subscribers, workflows, and layouts from Novu.
From OneSignal
Move users, segments, and push from OneSignal.
From Braze
Map user profiles, segments, and campaigns from Braze.
From Salesforce Marketing Cloud
Move data extensions, journeys, and triggered sends.
From Intercom
Map contacts, series, and in-product messages from Intercom.