Migrate from Courier to Novu

Learn how to migrate your notification infrastructure from Courier to Novu

This guide helps you plan and execute a migration from Courier to Novu. It covers how the two platforms compare, what changes when moving to Novu, and a step-by-step approach for migrating your notification workflows, templates, providers, and user data.

Why Novu?

  • Unified Workflows: Courier separates "Templates" (content) and "Automations" (logic). Novu unifies routing, timing (delays/digests), and content into a single Workflow, making it much easier to manage the entire lifecycle of a message.
  • Choose How You Build:
    • Visual Builder: A powerful drag-and-drop dashboard for teams that want a no-code UI to design content and orchestration.
    • Novu Framework: An optional code-first approach that lets developers write workflows in TypeScript, version-control them, and test them locally.
  • Unrivaled React Ecosystem: Novu's in-app Inbox comes with pre-built React components for a drop-in experience, plus powerful headless hooks if you want to build a completely bespoke UI.
  • Data Sovereignty: Because Novu is open-source, you can use our fully managed Cloud platform or self-host it on your own infrastructure to meet strict compliance requirements.
  • Translations: Novu supports translations for your notifications, making it easier to localize your notifications for your users. Use translation keys in channel step editor to localize your notifications and Novu will send the notifications in the subscriber's locale. Read more on how to use translations in the Novu Dashboard.
  • Multi-tenancy: Send notifications to different tenants or organizations within the same Novu project and let users manage their notification preferences for each tenant. Read more on how to use multitenancy in the Novu Dashboard.

Mapping Courier concepts to Novu concepts

Before you dive into the migration steps, here is a quick cheat sheet for translating your Courier setup into Novu's terminology.

Courier ConceptNovu EquivalentHow they compare
Automations + TemplatesWorkflowsNovu combines your message content and delivery logic (like delays or digests) into a single, easy-to-manage Workflow.
Profiles / UsersSubscribersThe core entity receiving the notification. Just like Courier, Novu allows you to pass user data inline, meaning you don't have to sync users beforehand.
Lists / AudiencesTopicsUsed for broadcasting. In Novu, you trigger a workflow to a Topic, and Novu automatically fans it out to all subscribed users.
PreferencesPreferencesNovu categorizes user opt-in/opt-out states natively by Workflow or via global channel settings. End user can manage their preference for each workflow or globally.
IntegrationsIntegrationsBoth platforms connect to external providers (Twilio, SendGrid, etc.). Novu lets you define multiple active integrations for each channel provider and set a primary integration per environment.
InboxInboxNovu's in-app Inbox comes with pre-built React components for a drop-in experience, plus powerful headless hooks, javascript and react native support if you want to build custom Inbox UI.
TenantsContextNovu supports multitenancy out of the box, the most simple way to implement tenant separation sending context information while triggering a workflow. Novu will automatically filter the notifications for the tenant and the end user will see only the notifications relevant to their tenant.

Migration steps

We recommend a phased approach to migrate safely without dropping any messages.

Phase 1: Set up your workspace and providers
  1. Create your workspace: Sign up for Novu Cloud. You'll automatically get isolated Development and Production environments.
  2. Connect your providers: In the Novu Dashboard, navigate to the Integrations Store. Reconnect the ESPs (SendGrid, Postmark), SMS gateways (Twilio), and Push providers (FCM, APNS) you were using in Courier.
Phase 2: Migrate audience data

You need to sync your Courier Profiles to Novu Subscribers. The easiest way to handle this is a Lazy Migration:

Instead of exporting and importing thousands of users manually, simply update your backend to pass the user's details (email, phone, name) inline when you trigger a notification. Novu will automatically create or update the Subscriber on the fly.

If you prefer to sync ahead of time, you can easily script it:

import { Novu } from '@novu/api';
const novu = new Novu({ secretKey: 'YOUR_NOVU_API_KEY' });
 
// Translating a Courier profile to a Novu subscriber
await novu.subscribers.create({
  subscriberId: 'usr_123', // Your internal user ID
  email: '[email protected]',
  phone: '+15551234567',
  data: {
    subscriptionTier: 'premium' // Custom data
  }
});

You can also use the Bulk Import API to import your subscribers in bulk.

Phase 3: Translate automations to workflows

In Courier, you link Automations to Templates. In Novu, you recreate these as Workflows. You have two great options for building them:

Option A: The Dashboard Visual Builder If your product or marketing team loves managing notifications visually, they will feel right at home in the Novu Dashboard. You can drag and drop Email, SMS, and In-App steps, add Delays and Digests, and edit message content directly in the browser. Read more on how to manage workflows in the Novu Dashboard.

Option B: Code-First with Novu Framework If your engineering team wants more control, you can use @novu/framework to define the same workflows directly in your codebase using TypeScript.

A simple code-first example:

import { workflow } from "@novu/framework";
 
export const weeklyDigestWorkflow = workflow('weekly-digest', async ({ step }) => {
  // Replaces Courier's digest node
  const digestResult = await step.digest('batch-events', () => ({ amount: 7, unit: 'days' }));
 
  // Replaces Courier's send node + template
  await step.email('send-summary', async (controls) => {
    return {
      subject: `Your Weekly Activity Summary`,
      body: `You have ${digestResult.events.length} new updates this week.`,
    };
  });
});
Phase 4: Swap out the in-app Inbox

If your app uses Courier's Inbox component, swapping it for Novu's is incredibly simple. Novu's Inbox provides out-of-the-box real-time updates and unread counts.

npm install @novu/react
import { Inbox } from "@novu/react";
 
export default function NotificationCenter() {
  return (
    <Inbox
      applicationIdentifier="YOUR_NOVU_APP_ID"
      subscriberId="usr_123"
      // We recommend using HMAC encryption in production for security
      subscriberHash="HMAC_HASH_GENERATED_ON_BACKEND" 
    />
  );
}
Phase 5: Update API calls

With your workflows ready and integrations connected, it's time to replace your courier.send() API calls with Novu trigger calls.

import { Novu } from '@novu/api';
const novu = new Novu({ secretKey: 'YOUR_SECRET_KEY' });
 
// Replaces courier.send()
await novu.trigger({
  workflowId: 'weekly-digest',
  to: { 
    subscriberId: 'usr_123',
    // Pass details inline for easy lazy migration
    email: '[email protected]' 
  },
  payload: {
    activityType: 'login'
  }
});

Final Validation: Send test events using your Novu Development API key. Monitor the Execution Logs in the Dashboard to verify everything works flawlessly. Once you're confident, switch to your Production API key and you're fully migrated!

API endpoint quick reference

Need to update your backend API requests? Use this mapping to find the Novu equivalent of your Courier endpoints.

ActionCourier EndpointNovu Equivalent
Trigger a MessagePOST /sendPOST /v1/events/trigger
Send to ManyPOST /bulkPOST /v1/events/trigger/bulk
Update UserPUT /profiles/:idPUT /v2/subscribers/:subscriberId
Fetch User DataGET /profiles/:idGET /v2/subscribers/:subscriberId
Modify Opt-InsPUT /users/:id/preferences/:topicPATCH /v2/subscribers/:subscriberId/preferences
Manage Lists/GroupsPUT /lists/:idPOST /v2/topics
View LogsGET /messagesGET /v1/notifications

Next steps

On this page

Edit this page on GitHub