Switching from Mailforge to Puzzle Inbox: SMTP to GWS Migration Guide

By Puzzle Inbox Team · May 21, 2026 · 7 min read

Migrating cold email infrastructure from Mailforge SMTP to Puzzle Inbox Google Workspace and Outlook. Step-by-step migration process.

Why Switch from Mailforge to Puzzle Inbox

Migrating from Mailforge (SMTP infrastructure) to Puzzle Inbox (Google Workspace and Outlook 365) typically delivers significant deliverability improvements:

Inherit Google IP reputation instead of building SMTP reputation from zero
Skip 4-6 week IP warming required for new dedicated SMTP IPs
Better Gmail deliverability through real Google Workspace accounts
Real Microsoft 365 deliverability for Outlook prospects (Mailforge is SMTP-only)
Lower technical complexity (no MTA config, no IP management)

The Deliverability Math

Cold email reply rates by infrastructure type:

Mailforge shared SMTP: 1.5-2.5% reply rate
Mailforge dedicated IP (after 4-6 week warming): 2-3%
Puzzle Inbox Google Workspace pre-warmed: 4-5%
Puzzle Inbox Outlook 365 pre-warmed: 3-4%

Migration to Puzzle Inbox typically doubles reply rates within 30 days.

Cost Comparison for 30 Inbox Equivalent

Mailforge SMTP (Self-Managed)

SMTP service: $79-199/month
Domains and DNS configuration
MTA management overhead
4-6 weeks of low-output warming
Operational time: 10+ hrs/month

Puzzle Inbox

30 pre-warmed inboxes mixed Outlook + GWS: $50-130/month
DNS pre-configured
No MTA management
Ready to send in 24-72 hours
Operational time: 1-2 hrs/month

The Migration Process

Step 1: Audit Mailforge Setup

Document current sending domains
Note current dedicated IPs (if any)
Record current MTA configuration
Inventory active sending platform connections

Step 2: Order Puzzle Inbox Replacement

Decide migration target:

Dual-platform: 30% Outlook + 70% Google Workspace for diversification
Outlook-heavy: Cheaper at $0.35/inbox if ICP includes Microsoft prospects
Google-heavy: $3-4.50/inbox for Gmail-using prospects

Order via puzzleinbox.com. Receive credentials in 24-72 hours.

Step 3: Configure DNS for New Domains

If using new domains with Puzzle Inbox:

SPF, DKIM, DMARC configured by Puzzle Inbox automatically
Verify in MXToolbox before sending

If keeping old domains (less common):

Update SPF to include Google or Microsoft
Add new DKIM records
Coordinate with Mailforge to avoid conflicts

Step 4: Connect Puzzle Inbox to Sending Platform

Instantly, Smartlead, Lemlist all OAuth-compatible
Connect new inboxes
Configure sending limits (15-20/day per inbox)

Step 5: Validate Deliverability

Send test emails to seed addresses
Verify primary inbox placement
Compare to Mailforge baseline metrics

Step 6: Gradual Traffic Migration

Same as other migrations — 25%, 50%, 75%, 100% over 4 weeks.

Step 7: Decommission Mailforge

After all Mailforge sequences complete
Cancel Mailforge subscription
Free up dedicated IPs (if applicable)
Maintain DNS for 30 days post-decommission

Special Considerations for SMTP → GWS Migration

1. Sending Volume Limits Differ

Mailforge SMTP could push higher per-IP volume. GWS limits to 15-20 cold emails per inbox per day.

For high-volume operations, you need more inboxes than you had Mailforge IPs.

2. Reputation Reset

Old Mailforge dedicated IP reputation doesn't transfer to Google. You're effectively starting fresh — but Google's reputation is much higher than zero, so it's an upgrade.

3. DNS Changes

SPF must include Google (_spf.google.com) instead of Mailforge SMTP servers. Don't leave both — clean DNS migration.

4. Loss of Custom MTA Behavior

Custom Mailforge MTA settings don't transfer. Google handles MTA logic differently.

When Mailforge Stays Better (Rare)

Sending 100K+ emails/day where dedicated IP scale matters
Compliance requirement for private infrastructure
Existing dedicated IP with established reputation
Technical team committed to SMTP management

For 95%+ of cold email operations under 5,000/day, Puzzle Inbox migration improves results.

Migration Success Metrics

Track 30 days post-migration:

Reply rate (target: 2x improvement vs Mailforge)
Bounce rate (under 2%)
Inbox placement (target: 85%+ primary inbox)
Cost change (typically 30-60% lower than Mailforge)
Operational time (typically 80% reduction)

Common SMTP → GWS Migration Mistakes

Not adjusting volume expectations (need more inboxes than IPs)
Keeping old DNS records pointing to Mailforge SMTP
Not waiting for Mailforge sequences to complete
Migrating mid-sequence (breaks thread continuity)
Forgetting to cancel Mailforge subscription

Migrating from Mailforge SMTP to Puzzle Inbox typically doubles cold email reply rates. Real Google Workspace and Outlook 365 inboxes inherit Google/Microsoft IP reputation that custom SMTP can't match at typical cold email volumes. Migration completes in 4 weeks.