Skip to main content

​
Core difference

Mailjet combines transactional sending with sender identity management, stored templates, contact lists, and campaign workflows. MailChannels focuses on governed delivery for platforms with many senders: authenticated API delivery, runtime personalization, webhooks, DKIM, Domain Lockdown, suppression handling, and sender boundaries. Audience storage and campaign orchestration need a separate replacement.

​
Feature mapping

​
Send payload notes

Mailjet’s v3.1 API supports nested messages and variables. In MailChannels, model each recipient through personalizations and place merge values in dynamic_template_data.

​
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:

​
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 permission-based messages through MailChannels when they need governed delivery and sender-risk controls.

​
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.