7 min read

Twilio Notify was Twilio's unified notification API used by developers to send SMS, push notifications, and other messages through a single interface. It simplified multi-channel messaging by handling the complexity of different notification providers behind one API.

Unfortunately, Twilio deprecated Notify in 2022, and the service reaches its end-of-life on December 31, 2025. After this date, the Notify API will cease to function entirely.

If you're still using Twilio Notify, it's critical to begin your migration now. In this post, we'll show you exactly how to migrate to Courier, the same platform Twilio chose for their own multichannel orchestration needs.

Let's get started.

Why Twilio chose Courier

When Twilio needed a true multichannel orchestration solution for their own operations, they didn't expand Notify’s capabilities, they chose Courier. As they put it:

As a customer engagement platform, we at Twilio know how important it is to meet your customers at their preferred channels. Courier gives us the power to fully personalize our customer touchpoints in one easy-to-use, centralized tool.

— Product Lead, Twilio

Twilio, a leader in communications infrastructure, recognized that modern notification orchestration requires specialized capabilities beyond basic messaging APIs and they decided Courier was the best path forward for them.

Why you should consider evolving your notification infrastructure strategy

As user expectations evolve and messaging environments grow noisier, developers need systems that punch through with critical notifications. When building notification systems, developers focus on several key requirements.

• Cross-channel orchestration
• Advanced template management for non-technical teams
• Robust user preference management
• Real-time observability and analytics
• Delivery optimization including scheduling and digests
• Multi-tenant architecture
• In-app notification center called Inbox

Notify vs. Courier: Feature comparison

Twilio Notify provided a foundation for unified messaging, but since its launch, user expectations have evolved dramatically. Today's users expect in-app notification centers, granular preferences, and seamless experiences across every channel. Here's how the platforms compare:

Key concepts: Notify to Courier

To migrate successfully, you'll need to know some key concepts and differences between Notify and Courier. The main differences are:

• Users and identities → User profiles with channel data
• Sending notifications → Workflow-based orchestration
• Tags → Objects and subscriptions

Let's walk through each mapping:

Users and identities

Twilio Notify used bindings to link user identities to specific channels and addresses, whereas with Courier, addresses are a property of the user.

• Identities → Courier user IDs (your stable database ID or UUID)
• Bindings → Channel address data stored on user profiles

Sending notifications

Twilio Notify required specifying the service type for each send while Courier uses workflows to handle multi-channel orchestration automatically:

Tags vs. Objects and Subscriptions

Twilio Notify uses flat tags for grouping, while Courier provides structured objects with subscriptions.

Here’s a rollup of each of these concepts

Migration plan

Now that you’re up-to-speed on some of the differences, here's a step-by-step migration guide that gets you off Notify safely before the December 31, 2025 shutdown:

Step 1: Configure your Courier workspace:

1. Sign up for Courier (10,000 free notifications/month)
2. Configure channels:
   
   • SMS: Connect your existing Twilio account
   • Email: SendGrid, SES, or your provider of choice
   • Push: FCM and APNs credentials
   • In-app: Install Courier’s Inbox SDK
3. Transfer users to Courier with our Profiles API

Step 2: Rebuild workflows

Build Courier workflows for each Notify message type, using the visual editor for adding advanced logic like:

• Inbound Event Triggers. Including a native integration with Twilio Segment
• Scheduling
• If/Then controls
• Step logic for fetching data or adding delays.

Step 3: Gradual cutover

1. Run Parallel Testing
2. Start with 10% of traffic
3. Monitor delivery rates and user feedback
4. Increase to 50%, then 100%
5. Keep Notify as fallback initially

Step 4: Complete migration

1. Switch all production traffic to Courier
2. Export any remaining Notify data
3. Update documentation
4. Disable Notify APIs before December 31, 2025

Final thoughts

Twilio Notify's shutdown doesn't have to be a setback. It's a chance to upgrade to a platform that handles modern notification requirements: visual workflows, user preferences, in-app messaging, and team collaboration.

When Twilio needed multichannel orchestration for their own operations, they chose Courier. That endorsement speaks for itself.

Start now, and you'll be ready well before December 31, 2025.

Start your migration today

1. Create your free Courier account - 10,000 notifications included
2. Audit your Notify usage - Document for a more informed technical consultation
3. Schedule a technical consultation - Get personalized migration support

Quick start guide

We’ve put together a comprehensive quick start guide in our docs which includes:

• Quick Start Code ( in your preferred language)
• Platform Deep Dive
• API References
• Tutorials

Courier is trusted by thousands of companies including Twilio, LaunchDarkly, and Workleap. Read more of their stories:

LaunchDarkly migrated from their legacy solution due to security concerns and the need for advanced features as they scaled.

Twilio uses Courier for their own multichannel orchestration needs—the strongest possible endorsement.

Workleap relies on Courier for to improve team engagement notifications across multiple channels including Microsoft Teams, Slack, and email.