INFRASTRUCTURE — CASE STUDY

38 inboxes changed platforms. Not one got burned.

Our own sending estate

38 of 38inboxes connected, tagged and warming on the new platform
38 of 38inboxes connected at completion
23Microsoft inboxes in the estate
15Google inboxes in the estate
12blocked Google inboxes transferred in to finish the job
50/daylimit set on every Google sender
25/daylimit on every Microsoft sender

How it worked

STEP 1

Full inventory of 38 inboxes by provider, tenant and program

STEP 2

Tags by provider and program on every inbox

STEP 3

Per-provider limits, Microsoft 25 a day and Google 50 a day

STEP 4

Warmup switched on across the whole estate

OUTCOME

38 of 38 inboxes connected, tagged and warming on the new platform

Meet the estate

Our own sending estate: the inbox pool behind the campaigns we run, spread across Microsoft and Google, several tenants, and more than one client program. On the old platform it sat as 29 working inboxes, 15 Google and 14 Microsoft.

The challenge

Changing sending platforms is where inbox estates go to die. Warmup state lives in the old tool. Tags and limits get rebuilt from memory. One missed setting and a warmed inbox starts cold sending at full volume, which is exactly how good senders get burned.

The migration had to happen in stages, while campaigns were already running on the senders that had moved.

The solution

Inventory before touching anything

Every inbox was listed first: which provider, which tenant it lived on, which program it served, and what limit it ran at. The count moved in stages: 12 of 38 connected by November 7, then 26 of 38 by November 10 (all 23 Microsoft plus 3 Google), with warmup on for 26 of 26 connected senders.

Limits set per provider, by decision

Microsoft inboxes were cut from 75 to 25 sends a day on November 10, a deliberate tightening, which set the Microsoft campaign ceiling at 575 a day across its 23 senders and 3,172 prospects. Google inboxes were set to 50 a day, matching how each provider treats its own senders.

The blocked twelve

The last 12 Google inboxes would not connect directly. They were transferred in by the provider on November 11 and verified in the senders list that evening, landing on a default limit of 20 a day before being raised to the estate standard of 50. That transfer completed the set: 38 of 38.

With all 15 Google senders attached, the Google campaign's daily ceiling rose from 225 to 750, and the estate's prospect pool reconciled at 6,523: 179 already contacted, plus 3,172 and 3,172 across the two split campaigns.

The results

38 of 38 inboxes connected on November 11, 2026. Every inbox tagged by provider and program, every limit set per provider, warmup running across the whole estate. The 29 inboxes on the old platform were left exactly as they were, nothing deleted, so the estate could fall back at any point during the move.

The return: the estate got more valuable the day the migration finished. The Google campaign daily ceiling rose from 225 to 750 once all 15 of its senders were attached, 3.3 times the capacity, on the same inboxes. And because the 29 old-platform inboxes were never deleted, the move carried no cutover risk at any point.

FAQ

What breaks most often in a platform migration?

Warmup and limits. People reconnect inboxes and forget that the new platform does not know the old warmup state or the old daily caps, so day one on the new tool becomes an accidental volume spike.

Why are Microsoft and Google limits different?

The providers police their own senders differently. In our operating experience Microsoft accounts stay safer at lower daily caps, while Google accounts in good standing carry more. This estate runs Microsoft at 25 a day and Google at 50.

How do you verify a migration is complete?

Count and state, inbox by inbox: connected, tagged, limit set, warmup on. 38 expected, 38 confirmed. Anything less is a partial migration wearing a finished label.

What happened to the inboxes on the old platform?

Nothing. All 29 were left untouched and undeleted, so the move was reversible at every stage.

By the numbers

inboxes connected at completion38 of 38
Microsoft inboxes in the estate23
Google inboxes in the estate15
blocked Google inboxes transferred in to finish the job12
limit set on every Google sender50/day
limit on every Microsoft sender25/day

Bars are scaled so very small and very large numbers fit on one chart. The values printed are exact.

THE ROI
3.3x

daily sending ceiling on the Google campaign, 225 to 750, unlocked by finishing the migration

Completing the migration tripled the Google campaign daily ceiling, 225 to 750, with no campaign paused.

What was built

The concrete pieces this engagement shipped, in one list.

Your mail is being sent unauthenticated. Here is the full fix.

Lower stack cost. Back in the inbox. Built to send at any scale.

We rebuild it properly: secondary domains, inboxes, SPF, DKIM and DMARC set to enforcement, warmup and safe sending limits, blacklist monitoring on top. Send-ready in about 17 days. No campaigns, no copy, no lead lists. Infrastructure only.

Almost a decade building cold outreach infrastructure, including his own sending and verification stack built from scratch. 20+ B2B clients at companies worth $10M and above, all in tier one countries.

Free · Written plan + fixed price · No sales call required

More case studies

Lead dataA US M&A advisory firm (name withheld)
46,000

prospects matched on LinkedIn, 93% of the final list

151,218 rows in. 49,373 decision-makers out.

READ CASE STUDY →

ROIValid decision-maker leads at $0.067 each in the pilot, then all 49,373 scored for $1.54 total.

InfrastructureA US advisory firm's cold email program (name withheld)
100%

sender health at the end of the wave, with 1 hard bounce in the final campaign

30 inboxes. 1,596 sends. Zero burned.

READ CASE STUDY →

ROIZero inboxes burned: 1,596 sends delivered and the pool ended at 100% health, ready for the next wave.

OutreachPartner outreach for a US advisory firm (name withheld)
Step 2

the follow-up, not the first touch, produced the first interested partner reply

The first yes did not come from the first email

READ CASE STUDY →

ROI958 sends across the wave produced an interested partner and a $1,000 logged opportunity.

Copied
Free tools Get an inbox plan