IP Warmup Calculator
Build a staged sending schedule for a new setup or a move to a new ESP, adjusted for your infrastructure, your audience, and your current sending health.
- How much to send at each stage
- Which audience to start with
- When to hold, pause, or step back
| Week | Daily volume | Send to | Watch |
|---|---|---|---|
| 1 | ~2,000 | Most engaged (30-day) | Complaints under 0.1%, bounces under 2% |
| 3 | ~12,000 | 90-day engaged | Spam-folder placement |
| 6 | ~100,000 | Full list (target reached) | Steady state |
Need help with CRM deliverability?
How do you warm up a sending IP safely?
Start with your most engaged recipients, increase by at most 1.5× every 2–3 days, and pause if bounces approach 2% or complaints reach 0.1%. Shared IPs still need domain and audience discipline. Provider-managed dedicated IPs should follow the ESP's automatic ramp with your own sequencing and monitoring.
Example: warming a new dedicated IP to 100,000 emails a day over eight weeks
These volumes follow a 1.5× per stage ramp (2–3 day holds), aligned with Customer.io domain-warming guidance and the CRM implementation playbook. Most senders target less than this. Your pace depends on list size, engagement, and how metrics respond at each step.
| Week | Daily volume | Send to | Watch |
|---|---|---|---|
| 1 | ~100–225 | Most engaged (14–30 day) | Complaints under 0.1%, bounces under 2% |
| 2 | ~500 | 30 to 90-day engaged | Postmaster compliance status |
| 3 | ~1,100 | Active list majority | Deferrals or throttling |
| 4 | ~3,800 | Full active list | Spam-folder placement |
| 5 | ~8,600 | Full active list | Complaint rate holding |
| 6 | ~19,000 | Light inactive share (≤5%) | Bounce and deferral trends |
| 7 | ~65,000 | Near full list mix | Provider delivery by mailbox |
| 8 | ~100,000 | Full list (target reached) | Steady state; future jumps need their own ramp |
Dedicated vs shared, and moving to a new ESP
Dedicated IP
You or your ESP control the ramp. Use a day-by-day ceiling only when you manage the IP yourself. If your provider warms it automatically, treat the schedule as audience sequencing and monitoring alongside that mechanism.
Shared IP
There's no individual address to warm up. The pool already carries an established reputation. What moves the needle is domain reputation and who you send to first, not an individual IP warmup curve.
Moving to a new ESP
Use the same cold 1.5× staged curve as a new setup. Quarantine inherited lists first. If bounce is at or above 2% or spam is at or above 0.1%, remediate before ramping — a faster migration schedule will not help.
Deliverability resources
Benchmarks
- Spam complaints: < 0.1% (warning > 0.2%)
- Unsubscribes: < 1% (warning > 2%)
- Bounce rate: < 2% (danger > 5%)
- Open rate: > 25% (poor < 15%)
When You Need a Warm-Up
- CRM implementation or migration (for example to Customer.io)
- New sending subdomain (e.g.,
news.example.com) - Large list import or reactivation campaign
- Rebrand/domain change or >60 days inactivity
Seasonality Reference
- B2B SaaS: Low weekends, Q1 push
- E-commerce: Q4 surge; weekend promos
- Delivery/Logistics: Mid-week peaks
- FinTech: Month-end salary cycles
Frequently Asked Questions
/01What is IP warm-up and why do I need it?+
/02How long should an IP warm-up take?+
/03What are the key metrics to monitor during warm-up?+
/04Can I skip IP warm-up if my volume is low?+
/05What happens if I send too much too quickly?+
/06How do industry seasonality patterns affect warm-up?+
/07What's the warmup schedule for 100,000 emails?+
/08What if my ESP manages dedicated IP warmup?+
/09Should I warm up with inactive contacts?+
/10When should I pause or step back?+
Sources
- Customer.io domain warming — 1.5× stages, 2–3 day holds, up to 60-day broadcast ramp
- CRM Implementation Playbook — Deliverability — post-MPP thresholds and progressive warm schedule
- Google Postmaster Tools — domain reputation and user-reported spam rate
- SendGrid — dedicated IP warmup guidance (provider-managed IPs)
- Amazon SES — standard dedicated IP automatic ramp
- MXToolbox — DNS, SPF, DKIM, and blacklist checks
- DMARC monitoring — e.g. Postmark
- Seedlist testing — inbox vs spam placement