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.
