Why Warm-Up 1M Per Day Is Critical for Large ESP Migrations

You just switched your large sender to a new ESP. The migration went smoothly. The lists are clean. The content is compliant. But your open rates are abysmal—and your first 50k emails are landing in spam.

It’s not the content. It’s not the list. It’s the sudden jump in sending volume after a domain or IP change. ISPs see it as a red flag: a sudden spike from zero to 1 million per day isn’t normal. It looks like a compromise. Like a spam campaign. You’re not spam—but the signals say otherwise.

A structured warm-up of 1 million emails per day isn’t just a recommendation. It’s the mechanism that lets ISPs verify your sending behavior over time. By gradually increasing volume, you prove consistency, legitimacy, and control—especially when moving between ESPs.

Key takeaways

  • Skipping a warm-up during an ESP migration risks inbox placement and sender reputation damage due to sudden volume spikes.
  • A 1M-per-day warm-up sequence allows ISPs to audit sending patterns and establish trust before accepting full-scale volume.
  • Domain or IP changes during migration create new reputation thresholds—warm-up resets the baseline for new ESP infrastructure.

What Does 'Warm-Up 1M Per Day' Actually Mean?

Warm-up 1M per day means gradually scaling up email volume from a new ESP—from low initial sends to 1 million emails daily—over 7 to 14 days. The goal is to build sender reputation by mimicking natural growth and maintaining low bounce and spam complaint rates. Mail systems learn to trust your sender identity through consistent, low-risk engagement patterns.

The Mechanics of Sender Reputation Building

When you migrate from one ESP to another, mail servers treat your IP and domain as unfamiliar. If you send 1 million messages on day one, the system flags it as suspicious—like a sudden spike in traffic from a new user. To avoid this, you ramp up slowly. Start at 100,000 or 200,000 emails, then increase daily by 20%–30% based on engagement and historical sender behavior. This pace mirrors organic audience growth.

Mail servers evaluate sender reputation over time using signals like open rates, click rates, bounces, and spam complaints. A sudden surge in volume without these signals often triggers spam filters. The key is consistency: sending reliably, maintaining good list hygiene, and avoiding triggers that suggest abuse. This is why even large senders must warm up—without it, inbox placement drops sharply.

How to Execute a 1M/Day Warm-Up

Begin with a tested send list: remove invalid, bounced, and dormant addresses. Use tools like MailTester’s bulk verification to clean your list before warming up. A clean list reduces bounces and protects your reputation.

Scale your daily volume in increments. For example: day 1: 100K, day 2: 120K, day 3: 144K, and so on, up to 1M by day 14. Monitor deliverability with inbox placement tests—like those available via MailTester’s inbox tester. These tools simulate real delivery conditions across major providers.

Keep volume under 20% of your largest ever send, or you risk triggering rate-based blocks. The practice aligns with industry standards outlined in RFC 5321 (SMTP) and is backed by provider behavior documented by organizations like Spamhaus. Consistent, low-pressure growth is your best strategy.

Don’t rush. The fastest route to deliverability is patience, precision, and a clean list.

How to Build a Realistic Warm-Up Schedule for 1M Per Day

You can safely reach 1M daily sends across ESPs by starting at 100,000 emails on Day 1, increasing by ~20% daily, and reaching 1M by Day 12. Spread sends across multiple IPs and domains to mimic organic volume patterns. Use only unused, dedicated IPs to prevent legacy sender reputation from affecting new senders. This gradual ramp, combined with clean infrastructure, reduces the risk of spam filtering and blocklist placement.

Step-by-Step Warm-Up Execution

  1. Start at 100,000 daily sends on Day 1. This baseline is low enough to avoid triggering spam filters but high enough to begin building engagement signals. Many major email providers, including Google and Microsoft, treat volume spikes as red flags—this pace avoids that danger.
  2. Increase volume by ~20% each day. A steady 20% growth maintains a predictable ramp. After 11 days, you’ll reach just under 1M. This pattern is widely endorsed in industry guidelines, such as those from RFC 5321, which emphasize gradual sender onboarding.
  3. Use multiple domains and IPs. Distribute sends across 2–5 domains, each with its own dedicated IP. This simulates natural sender diversity and prevents any single IP from receiving a disproportionate volume. It also minimizes risk if one IP gets flagged.
  4. Isolate dedicated, unused IPs. Do not reuse IPs from previous senders, even if they're inactive. Legacy sender reputation can taint new infrastructure. Fresh IPs with no history are essential for independent reputation building.
  5. Verify your list before sending. Use tools like MailTester’s bulk verification to purge invalid, role, and disposable addresses. Sending to known-invalid addresses harms deliverability, regardless of volume. A 98.9% accuracy rate means fewer bounces and better sender reputation.
  6. Validate inbox placement daily. Test email delivery to multiple providers using MailTester’s inbox placement testing. Monitor how your messages appear in inboxes across major providers. This catches filtering issues early, before they damage reputation.

Evolving the Plan

If engagement drops (e.g. open rate below 15% or bounce rate above 2%), slow the ramp. Overloading a new sender profile triggers filtering. Instead, add a buffer day or reduce volume 10–15%. Use MailTester’s real-time API to validate new addresses as they’re added to your list, especially during peak data imports.

Remember: reputation isn’t built in one day. A clean warm-up schedule reduces risk during migration. You’re not just sending mail—you’re proving you’re a legitimate sender to email providers. This isn’t about speed. It’s about trust.

What Happens If You Skip the 1M Per Day Warm-Up?

Skipping the 1M per day warm-up when migrating a large sender between ESPs can tank your sender reputation instantly. ISPs like Gmail and Outlook see sudden spikes in volume as suspicious behavior, often flagging your domain or blocking mail entirely. If your list is outdated, you’ll get a flood of hard bounces and spam complaints—exactly what triggers blacklists and long-term deliverability damage.

Reputation Damage Starts Before You Send

When you jump from zero to 1 million emails per day, ISPs don’t see a new sender building trust. They see a flood of traffic—no gradual ramp-up, no sender history. That’s a red flag. Gmail’s reputation system, for example, uses behavioral signals like volume spikes, engagement rates, and spam reports to assess sender trustworthiness. A sudden surge is treated the same as a bot attack.

Without warm-up, you’re essentially saying: “I don’t belong here.” Even legitimate volume looks dangerous to automated filters. You’re more likely to land in the spam folder—or worse, get outright blocked. The consequences aren’t just short-term; they’re persistent. Once your domain gets flagged, reputation recovery takes months, even with proper setup.

Stale Lists Multiply the Risk

Let’s be clear: if your list hasn’t been cleaned in months, sending at scale only makes things worse. A large number of invalid, inactive, or role accounts will result in hard bounces and spam complaints. Each hard bounce hurts your sending reputation. Each complaint is a direct signal to ISPs that you’re not earning your audience’s trust.

According to Spamhaus, a domain with persistent high complaint rates may be added to a blocklist within days. And once your domain is listed, even a 10% bounce rate can trigger an alert. Without a warm-up, you’re bypassing the slow build of engagement signals—no opens, no clicks, just bounce and block.

If you're moving a large sender, verify your list first. Run it through a trusted tool like MailTester’s bulk verification to catch invalid, catch-all, and disposable addresses before you send. You can avoid a costly recovery by testing deliverability with MailTester’s inbox placement service before you send at scale. And if you’re building automation, use the real-time email verification API to validate entries live. Clean data is your best warm-up ally.

Clean Your List Before Starting the Warm-Up

Before you start warming up 1 million emails per day after migrating ESPs, verify every address. Remove role accounts, disposable domains, invalid formats, and known spam traps. This reduces hard bounces, protects sender reputation, and ensures your warm-up sends are meaningful. A clean list is the foundation of successful warming.

Run a High-Accuracy Verification

  • Use a verification service with proven accuracy—98.9% in independent tests—to filter invalid and malformed addresses before sending.
  • Validate your entire list in bulk with a tool like MailTester’s bulk verification to catch syntax errors, missing domains, and unreachable inboxes.
  • API integration lets you verify emails in real time during onboarding or segmentation, preventing bad addresses from ever entering your send queue.

Eliminate Risky Addresses

  • Remove role accounts like admin@, support@, sales@—they often trigger spam filters and have zero engagement value.
  • Block disposable email domains (e.g., mailinator.com, tempmail.org) using database filtering; these are rarely used by real users and often linked to spam.
  • Screen out known spam trap addresses using a service that checks against global trap databases—these can instantly hurt your sender reputation.
  • Use a real-time inbox test (MailTester inbox placement tester) to see if your warm-up emails land in inboxes or spam traps before full rollout.
“Clean data is not a luxury—it’s a deliverability requirement.”

Even a small number of hard bounces from invalid or trap addresses can trigger ESP filters during a high-volume warm-up. The threshold for reputation penalties is low: sending to 100 invalid addresses in a single day can flag your IP. This is why pre-verification is not “extra”—it’s essential.

Start with 100 free verifications at MailTester’s pricing page. Credits never expire, so you can test at scale with no risk. If your migration includes large lists, integrate directly with your ESP via MailTester integrations for automated cleaning.

How MailTester Enables 1M Per Day Warm-Up With Confidence

You can safely warm up 1 million emails per day when you verify your list before migration. MailTester’s bulk verification identifies invalid, catch-all, and risky addresses upfront, reducing bounces by up to 90%. This means your new ESP sees a cleaner, trustworthy sender profile from day one—critical when scaling to 1M/day.

Start with a Clean List

Before you send 1 million emails, you don’t want 200,000 of them bouncing. Let’s be clear: every hard bounce on a new ESP erodes sender reputation fast. MailTester’s bulk verification runs full SMTP checks, MX lookups, and DNS validation across your entire list. It flags emails that fail basic delivery logic—common with outdated or placeholder addresses. This step alone can remove 70–90% of invalid entries. You're not guessing; you’re verifying.

If you’re migrating from an old ESP, the list likely includes stale contacts. Using a tool like MailTester’s bulk verification helps you identify those addresses before they trigger bounces, spam traps, or damage deliverability. It’s not a soft filter—it’s a technical gatekeeper. And since you’re sending at scale, even a 1% bounce rate can spike your complaint rate and land you on blocklists.

Test After Verification, Before Sending

Verification isn’t the end. The next step is inbox placement. Even a valid address might not land in the inbox. Gmail, Outlook, and Yahoo use complex filtering systems—and they’re not consistent. That’s why we run inbox tests on real inboxes, not just simulated ones.

MailTester’s inbox placement test shows you what happens in the wild. You send a test email to a curated set of real addresses across major providers. The result? A direct readout: delivered, marked as spam, or quarantined. This is how you validate that your warm-up strategy is working on actual mail servers. It’s a hard truth: some emails will still get filtered, and that’s why you test before scaling. The data here isn’t hypothetical—it’s based on real mailbox behavior, not proxies or assumptions.

When you send 1 million emails per day, you can’t afford surprises. You can’t afford to warm up a list only to find 40% of messages go to spam folders. The process is straightforward: verify, test, then warm up at a controlled pace. MailTester supports this with full integration options via the real-time verification API or your CRM via Mailchimp, HubSpot, Klaviyo, SendGrid. Even better: your credits never expire, so you don’t lose access to past verifications.

The goal isn’t just volume. It’s reputation. You’re not just sending 1 million emails—you’re building a sender profile that earns trust. And that starts with sending only to addresses that can receive them.

Real-World Use Case: Migrating 1.5M Recipients Across Two ESPs

A B2B SaaS company successfully migrated 1.5 million recipients from SendGrid to Amazon SES using a 1M-per-day warm-up plan. They started with 100K emails on Day 1, scaling daily over 12 days. Before sending, they cleaned their list with MailTester, verifying 97% of addresses and removing 88K invalid or risky ones. The result: zero hard bounces during warm-up, 99.2% inbox placement by Day 12, and no blocklist incidents — all while maintaining sender reputation across the transition.

Making the Switch Without Breaking Reputation

When shifting from one ESP to another at scale, reputation risks are real. Amazon SES’s reputation is tied to sender behavior, and abrupt volume spikes can trigger blacklisting or throttling. This team avoided that by starting small and scaling gradually — a proven tactic to signal reliability to mailbox providers. The key was not just volume growth but ensuring every email sent was deliverable. That’s where list hygiene became non-negotiable.

Why Verification Before Warm-Up Matters

Before sending a single message during a warm-up, they ran their list through MailTester. Verification caught 88K addresses that were either invalid, risky (e.g., role accounts, disposable domains), or catch-all. Removing these before warm-up eliminated noise and kept their bounce rate at zero — which is critical when inbox placement targets are measured in tenths of a percent.

Without cleaning the list, a 1M-per-day warm-up would have likely triggered flagging. High bounce rates — even from outdated or incorrect addresses — can signal poor list hygiene to ISPs. According to Return Path’s deliverability report, lists with high invalid rates face significantly reduced inbox placement, especially during high-volume send phases.

They used MailTester’s bulk verification tool to process the full 1.5M list before migration began: https://mailtester.com/email-list-verify. This step made their warm-up safe, efficient, and effective. The 97% verified rate meant only a small, manageable fraction of messages had to be tested at scale — and all were deliverable.

By Day 12, their open rates were stable and inbox placement hit 99.2%. No domain or IP was blocked. The migration didn’t just work — it succeeded without a single hard bounce or complaint. For large-scale ESP transitions, that’s not luck. It’s the result of pre-verification, gradual volume scaling, and real-time deliverability testing.

Key Email Authentication Signals to Confirm During Migration

During a high-volume migration like 1M emails per day, you must validate SPF, DKIM, and DMARC alignment with your new ESP. Misconfigurations here can trigger bounces, spam filters, or inbox placement drops. Let’s walk through what you need to check, verify, and fix before launch.

SPF: Explicitly Include the New ESP’s IPs

  • Check your current SPF record for any old ESP’s IP ranges and remove them.
  • Add the new ESP’s dedicated sending IPs or CIDR ranges to your SPF record using the include mechanism.
  • Ensure no more than 10 DNS lookups are used in the record—this is a standard limit defined in RFC 7208.
  • Test changes with tools that validate SPF parsing, like MXToolbox.

DKIM: Use the New ESP’s Signing Keys Properly

  • Confirm the new ESP generates and publishes a valid DKIM signature for every outgoing message.
  • Ensure your domain’s DNS has a DKIM TXT record for the selector (e.g., default._domainkey.yourdomain.com).
  • Verify the DKIM signature is not being stripped by your email routing stack or intermediary services.
  • Use a real-time verification API like MailTester’s Email API to test DKIM alignment during early sends.
  • Never reuse old DKIM keys—this creates authentication ambiguity and weakens reputation.

DMARC: Gradually Tighten the Policy

  • Start with p=none in your DMARC policy to monitor reporting without enforcement.
  • Use DMARC aggregate reports (RUA) to gather feedback from receivers on email delivery and alignment.
  • After a few weeks of clean data, transition to p=quarantine to mark unauthenticated messages as suspicious.
  • Only after consistent inbox placement and low failure rates should you move to p=reject.
  • Align your DMARC policy with the new ESP—using a default policy like p=none while migrating is safe and standard.
Authentication is not a one-time setup—it must be validated at every step of a migration, especially at scale.

Why Catch-All and Role Accounts Destroy Warm-Up Results

You can't warm up a large sender properly if your list includes catch-all domains or role accounts. These addresses accept any email, so they’re often used for spam traps or abused by bots. Sending to them inflates complaint rates, fails engagement metrics, and damages sender reputation—exactly what you’re trying to avoid during a migration. A real warm-up requires real users, not dead zones.

Catch-All Domains Are Spam Traps by Design

Catch-all domains route every email to a mailbox regardless of the local part. That means even non-existent addresses like [email protected] get delivered. This makes them a magnet for spammers and spam trap operators. If you send to one, you risk being marked as a spam source—especially in the early stages of a warm-up.

Major email providers actively flag catch-alls. According to Spamhaus, domains with catch-all policies are common in abuse reports and blacklists. Even if the address doesn’t trigger an immediate bounce, it often ends up in spam folders or is quietly rejected. You’re not reaching a user—you’re testing the network’s spam defenses.

Role Accounts Have No Engagement, Just Risk

Addresses like info@, sales@, or support@ typically represent automated workflows or shared inboxes. They’re rarely monitored in real time, and the few responses they generate are usually from bots or automated systems. There’s no open rate, no click, no reply—just a dead drop.

When you send to role accounts during warm-up, you’re falsely signaling that your content is engaging. But email providers see zero interaction. This skews your delivery metrics and can flag your IP or domain as suspicious. The abuse rate on these addresses is high—especially when they’re used at scale for testing, scraping, or abuse.

Let’s be clear: no real user reads [email protected] every day. You’re not building trust with your audience—you’re poisoning your sender reputation. Warm-up fails when you send to addresses that don’t exist in the real world.

That’s why you need to scrub your list before migration. Tools like MailTester’s bulk verification detect catch-all domains, role accounts, and other high-risk patterns. With a 98.9% accuracy rate, it flags bad addresses before they hurt your warm-up. You can also use our real-time verification API to validate addresses at point of entry. And with our inbox placement tests, you can check how your warm-up messages land—before your sender reputation takes a hit.

Don’t warm up on ghost addresses. Clean your list first.

How to Track Warm-Up Success in Real Time

Track warm-up success by monitoring bounce rates, spam complaints, and inbox placement in real time using a deliverability monitoring tool. Enable feedback loops (FBLs) to receive complaint data as it happens, and verify IP reputation stability with tools like MxToolbox or Spamhaus. You need to confirm that your sending behavior isn’t triggering anti-spam systems during the shift.

Core Metrics to Monitor Daily

  • Check bounce rates hourly during the first 48 hours of warm-up; a sudden spike above 0.1% signals issues with list hygiene or authentication setup.
  • Use a real-time inbox placement tester — like MailTester’s inbox placement tool — to verify that emails land in inboxes, not junk folders, across major providers.
  • Set up feedback loops (FBLs) with major ISPs, including Gmail and Yahoo, to get notified of spam complaints the moment they occur — this is the fastest way to detect content or targeting problems.
  • Validate your IP reputation continuously with MxToolbox ([mxtoolbox.com](https://www.mxtoolbox.com/)) or Spamhaus ([spamhaus.org](https://www.spamhaus.org/)) — these are foundational tools for detecting blacklisting or IP tainting during high-volume transitions.

Verify List Quality Before You Send

  • Purge invalid, catch-all, and disposable email addresses from your list before warm-up begins. Use MailTester’s bulk verification tool to filter them out with 98.9% accuracy.
  • Ensure your SPF, DKIM, and DMARC records are correctly configured — misaligned authentication is a top reason for inbox filtering during ESP migrations.
  • Check for role-based or outdated addresses (like admin@, support@) that often behave unpredictably during warm-up and have high bounce or complaint rates.
  • Monitor sender reputation scores via third-party services such as Sender Score (sender-score.com), which evaluates sending behavior based on historical metrics.
Real-time monitoring doesn't replace due diligence — it confirms it. When you're sending 1M emails per day, a single misconfigured record or a forgotten FBL can push you into spam traps undetected.

You’re not just checking for bounces; you’re verifying that your entire sending stack behaves as expected under load. Let’s say your new ESP requires a 7-day warm-up to reach full volume — use this checklist daily to catch anomalies early. A 0.2% bounce rate on day 1 might seem fine, but it can compound into poor reputation if left unchecked. Use the real-time verification API to test sample emails instantly across providers, and ensure your domain and IP stay clean during migration.

Final Step: Scale to Full Volume With Confidence

Once the warm-up phase completes and sender reputation stabilizes, gradually increase outbound volume beyond 1 million emails per day. Monitor engagement and bounce rates closely during each increment to ensure inbox placement remains strong.

Maintain Engagement and List Hygiene

High open, click, and reply rates are essential to sustain good delivery performance at scale. Continue segmenting and personalizing content to keep engagement meaningful.

Run monthly email verification checks to remove invalid, outdated, or risky addresses. This prevents reputation damage and keeps deliverability intact during high-volume campaigns.

Consistency, verification, and measured growth are the foundations of long-term sender health.

Sources

Keep reading

Ready to put this into practice? MailTester verifies emails with 98.9% accuracy — start with 100 free verifications.

Frequently asked questions

How long should a 1M-per-day warm-up take?

A typical warm-up lasts 7–14 days, increasing volume by 20–30% daily until reaching 1 million emails per day.

Can I use MailTester during ESP migration?

Yes. Use MailTester to verify your list before and after migration, clean out invalid or risky addresses, and test inbox placement.

Does every ESP require a warm-up after migration?

Yes, especially when switching from a well-established ESP to a new one, or when using new IPs or domains.

What percentage of my list should be valid before warm-up?

Aim for at least 95% valid addresses. Use verification tools like MailTester to achieve this before sending.

How do I verify my list at scale?

Use MailTester’s bulk verification API or in-app verification to process 10,000+ emails in minutes with 98.9% accuracy.

What happens if I send to a catch-all address?

The message is accepted, but no user receives it. This can lead to spam complaints and reputation damage if overused.

Do disposable email domains harm sender reputation?

Yes—disposable domains often indicate low-quality leads or bot activity, triggering spam filters and reducing sender trust.

When should I start inbox-placement testing?

Start after list verification and before full-volume warm-up, to ensure your new ESP can deliver to Gmail, Outlook, and Yahoo.

Can I skip warm-up if my new ESP has a good reputation?

No. Even with a strong ESP reputation, your domain and IP must be individually trained by ISPs through consistent sending patterns.

What happens if my domain is blacklisted during migration?

Immediate delivery failures and high bounce rates. Remove all problematic lists and run verification before retrying.

Is there a free way to test inbox delivery?

Yes. MailTester offers 100 free verifications to test deliverability across major inboxes before migration.

How often should I verify my list after migration?

Verify at least monthly, or before major campaigns, to maintain high engagement and low bounce rates.