Migration Guide
The complete guide to migrating your email sending from Campaign Monitor to dedicated IPs — with full IP warming support, zero downtime, and measurable inbox placement improvements.
Migrating from Campaign Monitor by Marigold to Dedicated Infrastructure
Campaign Monitor by Marigold is an email marketing platform popular with agencies and mid-market brands. It works well at lower volumes and for teams that want managed sending without infrastructure decisions. But senders who reach a certain scale — or who've experienced blacklisting, shared IP contamination, or deliverability plateaus — find that the lack of IP isolation and control becomes the bottleneck. This guide covers the complete migration process from Campaign Monitor by Marigold to dedicated email infrastructure.
Quick facts: Campaign Monitor vs. dedicated infrastructure
| Feature | Campaign Monitor | Cloud Server for Email |
|---|---|---|
| IP type | Shared with thousands | Dedicated — yours only |
| IP reputation control | None — shared pool | Full — isolated per client |
| Blacklist monitoring | Basic or none | 50+ lists, every 4 hours |
| Sending volume visibility | Aggregate only | Per-IP, per-pool detail |
| IP warming | Auto/shared | Guided, per-use-case |
| ISP postmaster access | Limited | Full Postmaster Tools access |
| PowerMTA / Acelle / MailWizz | Not available | Available |
| Custom PTR records | No | Yes — per IP |
Why senders leave Campaign Monitor
The most common reasons senders at 100K–5M emails/month outgrow Campaign Monitor:
- Campaign Monitor uses shared sending infrastructure
- No per-campaign IP control or ability to assign dedicated IPs to specific campaigns
- Limited technical support for deliverability issues beyond general guidelines
- Template-focused platform doesn't expose underlying sending configuration
- Per-email pricing model becomes costly for large lists and frequent sends
Key benefits after migration
IP control
Assign specific IP pools to campaigns, use cases, or client brands
Agency multi-client
Separate IP pools per client — contamination between brands eliminated
Authentication
Your own DKIM keys on your domain, not Campaign Monitor's
Agency economics
Reseller pricing available — offer dedicated infrastructure to your clients at margin
Migration process: 2–4 weeks
Export Campaign Monitor data
Export subscriber lists from each of your Campaign Monitor client accounts. Export unsubscribes and bounces from Reports → Subscribers.
Configure dedicated infrastructure
For agency migrations, we typically configure separate IP pools per client brand. This eliminates cross-client contamination and provides independent reputation tracking.
Per-client DNS configuration
Configure DKIM for each client's sending domain. Update SPF records per domain. Each client's DMARC policy is configured independently.
Import suppressions per client
Import suppression lists per client account. Maintaining client suppression data separately is important for multi-client setups.
Client-by-client warm-up
Warm each client's IP pool separately based on their sending volume and engagement profile. Higher-volume, better-engaged clients warm faster.
Full transition
Migrate remaining clients to dedicated infrastructure and discontinue Campaign Monitor sending. Provide clients with new SMTP credentials or API integration details.
Ready to migrate from Campaign Monitor?
Our team manages hundreds of migrations per year. We'll review your current setup, configure your dedicated infrastructure, and guide your IP warm-up. Most clients see measurable inbox placement improvements within 30 days.