Skip to main content

Migrating to Mailofly

Whether you are scaling past rate limits, cutting exorbitant per-contact marketing fees, escaping complex legacy APIs, or looking for unified multi-account sending and developer-friendly tooling, migrating to Mailofly is straightforward. This guide outlines a proven 5-phase migration framework to switch your transactional, marketing, and broadcast email pipelines without losing delivery status data, missing inbound emails, or triggering spam filters.

Migration Framework at a Glance


Phase 1: Pre-Flight Audit

Before touching code or changing DNS records, audit your existing setup:
  1. Inventory Senders & Domains: Identify every root domain and subdomain sending email, their current SPF, DKIM, and DMARC settings, and custom tracking domains.
  2. Catalog Email Types:
    • Transactional: Password resets, OTPs, receipts, account notifications (high urgency, high open rate).
    • Broadcasts / Newsletters: Marketing campaigns, product updates, scheduled digests.
    • Inbound / Receiving: Inbound webhooks, support desk addresses, catch-all forwarders.
  3. Audit Templates & Variables: List dynamic templates, merge tags, and conditional logic used in transactional emails.
  4. Identify Integration Touchpoints:
    • Official SDKs (@sendgrid/mail, resend, postmark, boto3)
    • SMTP relays (WordPress, Laravel, Supabase, Nodemailer)
    • Webhook listeners (handling bounces, delivery confirmations, clicks)

Phase 2: Domain Verification & Sending Identities

Mailofly allows you to verify your domains with modern 2048-bit DKIM keys and SPF alignment without breaking your existing provider.
1

Add Your Domain to Mailofly

Navigate to Domains in your dashboard and click Add Domain. Enter your domain (e.g. mail.example.com or example.com).
2

Configure DNS Records

Add the generated DKIM (CNAME or TXT), SPF (TXT), and Return-Path records to your DNS provider (Cloudflare, Route 53, GoDaddy, etc.).
Coexistence Tip: Mailofly’s DKIM selector is unique (mailofly._domainkey.yourdomain.com). It will never collide with your existing provider’s DKIM selectors (such as s1._domainkey or resend._domainkey), allowing both services to sign valid emails simultaneously during migration.
3

Configure Sending Identities

Set up Identities for different apps, environments, or teams (e.g., Billing <billing@example.com>, Support <support@example.com>).

Phase 3: Export Suppressions & Audiences

Deliverability Rule #1: Never send to an address that bounced or marked your previous emails as spam. Doing so will immediately harm your domain reputation with Gmail, Yahoo, and Outlook.
  1. Export Suppressions from Old Provider:
    • Hard Bounces: Invalid addresses or rejected mailboxes.
    • Spam Complaints / Abuse Reports: Users who clicked “Report Spam”.
    • Unsubscribes: Contacts who opted out of promotional communications.
  2. Import Suppressions into Mailofly:
  3. Migrate Active Contacts:
    • Export verified active subscribers from your previous platform.
    • Import contacts into Mailofly using CSV import or the Audience API, mapping custom properties and subscription topics.

Phase 4: Dual-Sending & Gradual Cutover

Avoid a high-risk “all-at-once” switch. Instead, roll out Mailofly incrementally:

Phase 5: Warm-up & Post-Migration Monitoring

If you send over 10,000 emails per day or are sending from a brand-new subdomain, observe the Domain & IP Warm-up Guide:
  • Keep Hard Bounces < 2%: Watch your bounce rates in real time on the Mail Logs dashboard.
  • Keep Spam Complaints < 0.1%: Ensure one-click unsubscribe headers (List-Unsubscribe) are active on all marketing messages.
  • Inspect Webhook Events: Verify that email.delivered, email.bounced, and email.opened events are correctly ingested by your backend.

Platform Comparison Matrix


Platform-Specific Migration Guides

Select your current platform for dedicated step-by-step code examples, payload mapping tables, and gotchas:

Migrate from Resend

Drop-in SDK replacement, React Email compatibility, and Svix webhook migration.

Migrate from SendGrid

Escape nested personalizations JSON, migrate SMTP relays, and import suppressions.

Migrate from Mailchimp

Unify marketing & Mandrill transactional emails and eliminate contact storage fees.

Migrate from AWS SES

Replace complex SNS/SQS/Lambda pipelines with streamlined REST endpoints and built-in logs.

Migrate from Postmark

Convert message streams and server tokens into Mailofly identities and API keys.

Migrate from Mailgun

Transition from legacy multipart form-data to typed JSON and modern webhooks.