Migration Guide
The complete guide to migrating your email sending from HubSpot to dedicated IPs — with full IP warming support, zero downtime, and measurable inbox placement improvements.
Migrating from HubSpot Marketing Hub to Dedicated Infrastructure
HubSpot Marketing Hub is a CRM and marketing automation platform with integrated email sending. 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 HubSpot Marketing Hub to dedicated email infrastructure.
Quick facts: HubSpot vs. dedicated infrastructure
| Feature | HubSpot | 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 HubSpot
The most common reasons senders at 100K–5M emails/month outgrow HubSpot:
- HubSpot uses shared IP infrastructure for email sending
- Email sending is tightly integrated with the CRM — separating them requires API integration
- Limited control over DKIM signing and PTR records
- No per-IP blacklist monitoring or proactive deliverability management
- Email sending cost is bundled with CRM pricing — expensive when you only need sending
Key benefits after migration
CRM integration
Use HubSpot as CRM while routing sends through dedicated infrastructure via SMTP relay
SMTP relay integration
HubSpot supports custom SMTP — point it at your dedicated relay for immediate IP control
IP reputation control
Your sending reputation is independent of all other HubSpot users
Cost optimization
Pay for CRM features only, not bundled sending markup
Migration process: 4–6 weeks
Audit your HubSpot email setup
Document all active email workflows, lists, and sending domains. Note current suppression lists and contact engagement metrics.
Choose integration approach
Option 1: Use HubSpot as CRM + route sends via SMTP relay to dedicated infrastructure. Option 2: Full migration to MailWizz or Acelle with API integration to HubSpot CRM for contact sync.
Configure SMTP relay in HubSpot
For Option 1: In HubSpot, navigate to Settings → Marketing → Email → Sending Configuration. Set custom SMTP to your dedicated relay credentials.
Export suppressions
Export all unsubscribes and hard bounces from HubSpot Contact Records. Import these to your infrastructure before enabling new sending.
DNS update
Add new DKIM records for your sending domains. Update SPF to authorize your dedicated IPs. Maintain existing DMARC policy.
Test and warm-up
Test authentication from HubSpot → dedicated relay → recipient. Begin warm-up with most engaged contacts.
Ready to migrate from HubSpot?
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.