Re-platforming Without the Re-org Theater

Replacing a 20-year-old martech stack usually triggers a year of politics. Here’s how a transformation engagement moved a client off Adobe Campaign Classic onto a modern stack while realigning the team — on purpose, not in panic.

The client was running Adobe Campaign Classic — a platform that had been in place for two decades. The mandate was to modernize: Salesforce Marketing Cloud for orchestration, Snowflake as the system of record. The technical migration was the easy part. The hard part is always the people.

Over a year-long engagement we drove a 30% headcount reduction — but the headline number misses the point. This wasn’t cutting. It was capability realignment: the skills that ran a 20-year-old batch platform are not the skills that run a modern, data-driven stack.

Re-org theater vs. capability realignment

Re-org theater is when you reshuffle boxes to look decisive and call it transformation. Capability realignment starts from the work the new platform actually requires, maps it against the people you have, and is honest about the delta. The first is about optics. The second is about whether the thing runs in eighteen months.

A platform migration that doesn’t change who does the work isn’t a migration. It’s a very expensive rename.

The Snowflake decision was the quiet hero. Making it the system of record — rather than letting the marketing platform own the data — meant the org’s truth lived somewhere durable and tool-agnostic. The next platform change, whenever it comes, won’t require excavating the data out of a vendor’s basement.

The lesson

Treat the human realignment as the project and the software as a dependency, not the other way around. The teams that get this backwards spend their budget on licenses and their next two years on rework.