Core difference
Mailjet combines transactional sending with sender identity management, stored templates, contact lists, and campaign workflows. MailChannels focuses on authenticated API delivery, runtime personalization, webhooks, DKIM, Domain Lockdown, and suppression handling. Audience storage and campaign orchestration need a separate replacement.Feature mapping
| Mailjet concept | MailChannels concept | Migration approach |
|---|---|---|
| Send API v3.1 | /send payload | Rewrite transactional sends to MailChannels JSON payloads and authentication. |
| Messages and variables | personalizations and dynamic_template_data | Preserve recipient-specific merge values, but validate the new payload shape. |
| Stored templates | Application-managed Mustache content | Export templates and manage them outside MailChannels. |
| Sender identities | from identities | Keep valid sender addresses while shifting durable trust to domain authentication. |
| Sender domains | DKIM and Domain Lockdown | Recreate domain authentication with MailChannels DNS records. |
| Event callback URLs | MailChannels webhooks | Recreate callbacks and update consumers for MailChannels event schemas. |
| Campaign-excluded contacts | Suppression list | Treat as non-transactional suppressions by default. |
| Contact lists and campaigns | External audience and campaign workflow | Replace with an external list manager or campaign system. |
Send payload notes
Mailjet’s v3.1 API supports nested messages and variables. In MailChannels, model each recipient throughpersonalizations and place merge values in dynamic_template_data.
| Concern | Mailjet behavior | MailChannels behavior |
|---|---|---|
| Authentication | Mailjet API key and secret | MailChannels API key authentication |
| Sender setup | Sender identity and sender domain controls | Authenticated sender domain with DKIM and Domain Lockdown |
| Variables | Mailjet variables | Mustache data in dynamic_template_data |
| Tracking and callbacks | Event callback URLs and account settings | MailChannels webhook plus per-message tracking settings |
| Campaigns | Mailjet campaign product | External workflow with MailChannels as delivery API |
Template migration
Treat Mailjet templates as content assets to export, review, and re-home. Confirm whether each template depends on Mailjet-specific syntax or metadata and convert it to the rendering approach used by the new application.Suppression policy
Recommended defaults:| Mailjet source | MailChannels target |
|---|---|
| Campaign exclusions | Suppress as non-transactional. |
| Hard bounces or complaints from delivery history | Suppress as both transactional and non-transactional when available. |
| List-level unsubscribe intent | Preserve as non-transactional preference data in the external audience system. |
Marketing migration
MailChannels Email API does not replace Mailjet contact lists, newsletters, or campaign scheduling. Export list membership and campaign logic into an external audience workflow, then send through MailChannels only at delivery time.Cutover checklist
- Replace Mailjet authentication and send endpoint.
- Translate message variables into
dynamic_template_data. - Move templates out of Mailjet.
- Publish and validate MailChannels DKIM records.
- Recreate event callbacks as MailChannels webhooks.
- Move contact-list and campaign workflows outside MailChannels.
- Apply a non-transactional-first policy for campaign exclusions.