An EU-hosted transactional email API, evaluating Postmark?
A straightforward field-mapped migration, and EU data residency, price stability, and long log retention as the default, not an enterprise add-on.
EU-hosted by default
API, database, logs, and backups run in the EU. A signed DPA ships on every plan, including free, no sales call required.
24-month price lock
Your tier price is fixed at signup. Any change after that gets 6 months' notice and a grandfathering option, published, not buried in a contract.
90-day log retention
Debug a bounce from three months ago, not three weeks ago. Free tier gets 7 days, Pro gets 90, Scale is configurable up to 365.
What actually moves, and what doesn't
Is the migration automated?+
Not with a codemod, the field names genuinely differ (From, To, HtmlBody vs. from, to, html), so it's a mapped rewrite rather than a mechanical import swap. The field mapping is small and mechanical once you know the correspondence.
What about Message Streams?+
Envello doesn't have a named streams concept. The underlying goal, keeping transactional and marketing sending reputation separate, is handled architecturally: use a dedicated IP add-on and keep marketing sends on a different tool entirely.
Do server-side templates carry over?+
Simple variable substitution does. Templates using Handlebars-style loops or conditionals don't have a direct equivalent yet, render that logic in your own application code instead.
Full walkthrough: Migrating from Postmark to Envello