> ## Documentation Index
> Fetch the complete documentation index at: https://www.courier.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Install the Courier skill before writing code: `npx skills add trycourier/courier-skills`. It carries the verified SDK shapes and the rules you cannot get wrong.
> Authenticate every request with `Authorization: Bearer <API_KEY>`. A workspace has several environments and each has its own keys, which are plain `pk_` strings with no environment prefix. Start with Test.
> Send with `client.send.message` from the Node SDK (`@trycourier/courier` v7 and later, where the client is the default import). Reference a template by its `nt_` id or its alias.
> A send accepts a bare Elemental element list, but storing content on a template requires the top-level elements wrapped in a channel element.
> To translate a template, write one locale at a time with `PUT /notifications/{id}/locales/{localeId}`, which merges into the existing translations. `PUT /notifications/{id}/content` and `PUT /notifications/{id}/elements/{elementId}` overwrite translations along with the content, so send each element's `id` and `locales` back, and first remove every `checksum` and any `locales` key that starts with an underscore.
> Templates and journeys can be built in the Courier app or created through the API. Either way they live in the workspace and are referenced by ID when you send.
> The hosted MCP server is https://mcp.courier.com. For a briefing on what Courier is and when to use it, read https://www.courier.com/llms.txt.
> Prefer the Guides tab for how-do-I questions and the Docs tab for how-does-it-behave questions. The API reference lives under /api-reference.

# Migrate to Courier

> Move from in-house code, Knock, Novu, SuprSend, Braze, OneSignal, SFMC, Intercom, or Customer.io: map concepts, move users and content, then cut over.

Every migration follows the same shape: map your concepts to Courier's, move recipients and content, then cut over sends.

## How a migration maps

Most notification platforms share the same building blocks.

| Your current platform | Courier |
| - | - |
| Delivery channels / provider connections | [Integrations](https://www.courier.com/docs/integrations/overview.md) (bring your own provider, with [failover](https://www.courier.com/docs/send/routing.md)) |
| Workflows that bundle content and logic | [Templates](https://www.courier.com/docs/design/templates/overview.md) for content, [journeys](https://www.courier.com/docs/journeys/overview.md) for orchestration |
| Recipients / subscribers | [Users & profiles](https://www.courier.com/docs/recipients/overview.md) |
| Segments | [Lists & audiences](https://www.courier.com/docs/recipients/lists-and-audiences/overview.md) |
| Notification preferences | [Preferences](https://www.courier.com/docs/recipients/preferences/overview.md) |
| Multi-tenant accounts | [Tenants](https://www.courier.com/docs/tenants/overview.md) |
| In-app feeds | [Inbox](https://www.courier.com/docs/in-app/overview.md) |

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

1. Connect your providers as [integrations](https://www.courier.com/docs/integrations/overview.md).
2. Move recipients into [profiles](https://www.courier.com/docs/guides/import-your-users.md) and rebuild segments as [lists or audiences](https://www.courier.com/docs/recipients/lists-and-audiences/overview.md).
3. Recreate content as [templates](https://www.courier.com/docs/design/templates/api.md) and orchestration as [journeys](https://www.courier.com/docs/journeys/build.md).
4. Move preferences and, if you use them, tenants.
5. Cut over sends and verify in [logs](https://www.courier.com/docs/monitor/overview.md).

## Migrate from your platform

> [card] [From an in-house system](https://www.courier.com/docs/guides/migrate/from-in-house.md)
>
> Replace homegrown notification code, one type at a time.

> [card] [From Knock](https://www.courier.com/docs/guides/migrate/from-knock.md)
>
> Map workflows, recipients, and preferences from Knock.

> [card] [From SuprSend](https://www.courier.com/docs/guides/migrate/from-suprsend.md)
>
> Move subscribers, templates, and channels from SuprSend.

> [card] [From Novu](https://www.courier.com/docs/guides/migrate/from-novu.md)
>
> Map subscribers, workflows, and layouts from Novu.

> [card] [From OneSignal](https://www.courier.com/docs/guides/migrate/from-onesignal.md)
>
> Move users, segments, and push from OneSignal.

> [card] [From Braze](https://www.courier.com/docs/guides/migrate/from-braze.md)
>
> Map user profiles, segments, and campaigns from Braze.

> [card] [From Salesforce Marketing Cloud](https://www.courier.com/docs/guides/migrate/from-salesforce-marketing-cloud.md)
>
> Move data extensions, journeys, and triggered sends.

> [card] [From Intercom](https://www.courier.com/docs/guides/migrate/from-intercom.md)
>
> Map contacts, series, and in-product messages from Intercom.

> [card] [From Customer.io](https://www.courier.com/docs/guides/migrate/from-customer-io.md)
>
> Map automations, transactional messages, and preferences from Customer.io.

## Upgrade Courier React

Already on Courier and moving off React v7? The [React v8+ migration guide](https://www.courier.com/docs/sdk-libraries/courier-react-v8-migration-guide.md) covers the Inbox, Toast, and Preferences components.
