This month Fortune Media posted a set of roles that quietly reveal what's happening under the hood: it's moving off Salesforce Marketing Cloud and evaluating a new customer-data platform. Poshmark surfaced the same shape from a different angle — a growth PM whose mandate is standing up the marketplace's new customer-engagement platform. On paper, two sensible, overdue modernizations. Underneath, both companies are about to walk through the one moment that quietly resets everything: the migration.
Here's the trap. You can migrate contacts, templates, journeys, automations, and reports. You cannot migrate reputation. The warmed IPs, the aligned DKIM signatures, the years of accumulated inbox trust that made your mail land — none of it transfers. The new platform starts you at zero, usually on new sending infrastructure, and no migration checklist has a row for it. Everyone's watching feature parity: does the new tool do everything the old one did? Nobody's watching the asset the new tool can't bring with it.
The reset happens in three places, and all of them fail silently. Authentication alignment: a new sending domain or subdomain means SPF, DKIM, and DMARC alignment have to be re-established, and a mismatch doesn't error — it just quietly stops passing. Warmth: new IPs and domains have no history, so blast your full list on day one and receivers treat you as a stranger sending in bulk. And trust: mailbox providers score the new sending identity from scratch, watching how the first days go before they decide where you belong.
So the story writes itself. The migration gets scoped as a feature-parity project. The team rebuilds the journeys, imports the segments, matches the dashboards, signs off. Then the first real campaign goes out on the new platform — full volume, because why wouldn't it — and it lands in spam. Right at the moment leadership is watching the shiny upgrade prove its ROI. The tool works perfectly. The reputation didn't come along, and now you're rebuilding it in public, under scrutiny, from behind.
A migration isn't a config swap; it's a warmup event. Re-audit authentication alignment on the new sending domain before the first send. Ramp volume on the new IPs and domain instead of opening the taps. And watch posture through the cutover, so a silent reset shows up as a line on a graph the day it happens — not as a mystery three weeks later when someone finally asks why open rates fell off a cliff. The companies posting these roles are ahead of most: they've at least put a human on the new stack. The trap isn't the migration. It's calling it done when the last journey is rebuilt, and forgetting that your good name is the one part of the move with no import button.