Skip to main content
Migrate from MagicBell to Novu by replacing the MagicBell notification feed with the Novu Inbox component, rebuilding notification workflows, and connecting your existing delivery providers.

​
Why migrate to Novu?

  • Multi-channel from one platform: MagicBell focuses on in-app feeds; Novu handles in-app, email, SMS, push, and chat
  • Workflow orchestration: Delays, digests, throttles, and multi-step logic in one workflow
  • Open source: Deploy on Novu Cloud or self-host for full control
  • Headless and prebuilt UI: Use the drop-in Inbox or build custom UI with @novu/react hooks
Compare platforms on Novu vs MagicBell.

​
How do MagicBell concepts map to Novu?

MagicBell ConceptNovu EquivalentNotes
Notification feedInboxPrebuilt React component with bell, feed, and preferences
UsersSubscribersIdentified by subscriberId
Categories / TopicsTopicsGroup subscribers for broadcast notifications
PreferencesPreferencesBuilt into Inbox and manageable via API
Channels (external)Integrations + WorkflowsNovu workflows deliver to email, SMS, and push providers

​
What are the migration steps?

1

Phase 1: Set up Novu

  1. Create a Novu Cloud account.
  2. Connect delivery providers if you send email, SMS, or push alongside in-app notifications.
2

Phase 2: Replace the in-app feed

Remove MagicBell feed components and add the Novu Inbox. Follow the React quickstart to install @novu/react and render <Inbox />.
3

Phase 3: Migrate notification triggers

Replace MagicBell API calls with Novu Trigger event requests. Create workflows in Novu for each notification type you previously sent through MagicBell.
4

Phase 4: Migrate user preferences

Export MagicBell preference data and import via Update subscriber preferences, or let users reconfigure through the Novu Inbox preferences UI.
5

Phase 5: Validate and cut over

Run Novu alongside MagicBell during testing. Verify unread counts, real-time delivery, and preference behavior before removing MagicBell from production.