Migration

Migrando do Resend pro Mailmundo.

Resend é um ótimo ESP developer-first. Se você é uma empresa de cleaning saindo da postura genérica dele — precisando de tracking branded, marketing campaigns, AI Copywriter que conhece seu vocabulário — aqui está como a migration funciona.

Por que operadores migram

  • Resend's audience is generic SaaS — not cleaning industry. AI assist generates marketing fluff that doesn't speak operator.
  • Single-region only. No automatic regional failover for international cleaning brands operating across borders.
  • Limited audit log. Recent activity view, not SOC 2 ready append-only chain.
  • Single API key with no scopes — you either grant everything or nothing.

O que continua igual

  • Same SES underneath (Resend uses AWS SES, just like Mailmundo).
  • Same DKIM/SPF/DMARC discipline — your sender reputation transfers.
  • Same React Email + MJML rendering option (we support both).
  • Same idempotency-key pattern for safe retries.

O que melhora

  • Branded tracking on your own domain (or tracking.mailmundo.com fallback).
  • Multi-region SES routing (US · EU · APAC · LATAM) with automatic geo-routing.
  • AI Copywriter that knows cleaning vocabulary (deep clean, move-out, post-construction, recurring).
  • Per-key API scopes + IP allowlist + hash-chained audit log.
  • Trilingual UI + 12-locale templates + EN/PT-BR/ES marketing site.
  • Send pricing model that scales with sends, not contacts.

Passos da migration

  1. 1. Verify your sending domain in Mailmundo

    Add 5 DNS records (DKIM × 3 + custom MAIL FROM + SPF). Same flow as Resend; takes ~10 minutes plus DNS propagation.

  2. 2. Generate a Mailmundo API key

    Create at /app/api-keys/new with scope send:transactional. Test in staging by swapping the bearer token in your existing client.

  3. 3. Update your client SDK

    Mailmundo's API surface mirrors Resend on transactional/send. Most existing client code works with just a new base URL + new bearer token.

  4. 4. Mirror traffic for 1 week

    Send each transactional email through both Resend and Mailmundo. Compare deliverability via Postmaster Tools. Resolve any DKIM/SPF differences before cutover.

  5. 5. Cutover & decommission

    Flip 100% of transactional traffic to Mailmundo. Keep Resend account active for 30 days as fallback. Cancel after 30 clean days.

Fala com a gente primeiro

Conversar sobre migration