How to migrate from OneSignal to Novu
Technical infrastructure migrations vary a lot depending on the tool — these are the general steps that apply to most cases.
- 1
Export your configuration and data from OneSignal
Check OneSignal's documentation for exporting projects, configuration and integrations — the exact format depends on the service, but almost all offer some export path for paid accounts.
- 2
Prepare the Novu environment
Deploy Novu in a staging environment first (not production) and replicate the base configuration before moving any real data.
- 3
Migrate in pieces and validate each one
Move one project or integration at a time instead of all at once, checking that each piece works in Novu before moving on to the next.
- 4
Update integrations that depended on OneSignal
Any external service (CI/CD, webhooks, SDKs) that pointed at OneSignal needs to be reconfigured to point at your new Novu instance.
Before cancelling OneSignal
Before cancelling OneSignal, confirm no production service still depends on it by checking recent access logs.
Ready to deploy Novu?
Full profile with license, tech stack and ready-to-copy docker-compose.
View Novu's profileThese steps are a general guideline — the exact export menu can vary depending on OneSignal's plan and version.