10 the most notorious and painful migrations

Scrolling through LinkedIn (as one does when avoiding real work) I stumbled across the story of The Trade Desk’s migration disaster. Turns out painful migrations in AdTech are less of a rare exception and more of a rite of passage. And no, size doesn’t protect you. Google and Microsoft both have the scars to prove it.

Let’s see our subjective list (random order) of most notorious and painful platform migrations.

1.Amazon Ads & Sizmek Ad Server painful migrations with no lesson learned

Chapter 1: Sizmek was a major independent ad server competing with DoubleClick. Between 2014–2017 it acquired Peer39 (brand safety), PointRoll (rich media), RocketFuel (AI-driven DSP), and others. Each ran on its own codebase. The attempt to consolidate these into a single platform consumed massive engineering resources. Technical debt piled up, the platform became unreliable, and clients left. The consequence of this painful migrations was that in March 2019 they filed Chapter 11. 

Chapter 2: Amazon bought Sizmek’s ad server and related tech, inheriting two separate ad server platforms: a legacy one (kept for big, complex clients) and a newer platform. For years they were effectively running two ad servers in parallel at high cost while trying to move customers to the newer stack. Many large clients resisted because the new system lacked advanced attribution features they relied on. In 2023-2024, Amazon rebranded to Amazon Ads Server and then decided to sunset the ad server entirely by end of 2024, forcing clients to migrate again to other ad servers (Google, Flashtalking, Adform, etc.)

Where it hurt:

• Agencies and advertisers had to do multi-month emergency migrations of tags, tracking and reporting to alternative ad servers. 
• There were reported tracking outages and conversion drop-offs during backend changes related to the rebrand/migration, leaving agencies “effectively running blind” across multiple clients.
• For Amazon, the cost was years of engineering on a stack they ultimately killed, plus reputational damage with sophisticated advertisers who’d been migrated twice.

2.Google: DFP + AdX → Google Ad Manager (GAM) & ongoing control changes

Google long ago fused its publisher ad server (DFP) with AdX into what is now Google Ad Manager (GAM). This tight bundling and migration path is at the center of the DOJ antitrust case, with courts finding that it effectively locked publishers into Google’s stack. On top of the original migration, Google keeps changing how access and controls work: 

• AdX Seller API → Ad Manager API migrations. 
• Shifts in MCM (Multiple Customer Management) relationships and AdSense / AdX review behavior that can suddenly push sites into “under review” status with reporting drops and unfilled spikes when publishers change networks or contracts. 
• 2025-26 changes to Authorized Buyers / blocking controls and broader Google Ads changes that coincided with many publishers reporting 30–80% revenue drops, even with stable traffic.

Where it hurt
For publishers outside the Google mothership, every structural change in this painful migrations has meant: 

• Risky migrations of setup (AdSense → GAM, or MCM partner changes). 
• Sudden revenue cliffs when accounts or AdX become inactive or go into review in the middle of a migration window.
• The DOJ case documents how tightly Google’s integration made it extremely hard (and expensive) to migrate away from GAM/AdX at all, because you’d lose Google demand and face unknown yield on alternatives.

3.AppNexus (Xandr): internal data update → global outage

In 2013, AppNexus (now Xandr) rolled out a data update from an internal database to the “impression bus” cluster – the core component that receives ad requests and runs auctions. The update passed validation but triggered a crash of around 900 servers worldwide at almost exactly the same time, fully halting ad serving, then partially degrading it, for about 2.5 hours.

Where it hurt

• This wasn’t a vendor-to-vendor painful migrations, but a classic internal painful migrations / config change that rippled through the whole stack. 
• For clients (DSPs, networks, direct buyers), this meant no ads delivered during a peak window – i.e., millions in lost media delivery and opportunity cost compressed into a couple of hours. 
• It’s often cited internally in adtech as a lesson in:
  • staggered rollouts and canary deployments, 
  • stronger config validation, and 
  • having real kill-switches and backout plans.

4.AppNexus (Xandr) once again: AT&T → Microsoft

AT&T paid approximately $1.6B for AppNexus in 2018, rebranding it Xandr. The plan was to fuse AppNexus’s programmatic capabilities with AT&T’s first-party subscriber data and WarnerMedia content. In practice, it was painful migrations: AT&T’s telecom IT infrastructure and AppNexus’s AdTech stack were worlds apart. Privacy constraints on AT&T subscriber data limited the original vision significantly. After AT&T spun off WarnerMedia, Xandr lost its strategic rationale. Microsoft acquired it in 2022 for roughly $1B – a significant loss on AT&T’s original investment – primarily to integrate with Netflix and other CTV supply.

What went wrong: 

• The strategic thesis (telecom data + premium inventory + programmatic pipes) was painful migrations – never technically achievable at scale given telecom data privacy constraints. 
• The integration between legacy AT&T systems and AppNexus was poorly scoped.

5.Facebook/Meta: Atlas & LiveRail → acquisition, rebuild, shutdown

Microsoft bought aQuantive (including the Atlas ad server) for $6.3B in 2007, then wrote most of it off. Facebook then bought Atlas from Microsoft in 2013 for a relatively small amount (~$30–100M) and tried to rebuild it into a Google DoubleClick competitor. Facebook also bought LiveRail, a video ad platform, to expand its external Adtech footprint. It was another painful migrations – both products struggled to gain adoption, with: 

• functional gaps (no full bidding platform, limited inventory coverage), 
• publisher distrust about letting Facebook control their data, and 
• high integration cost for marketers already on DoubleClick. (theinformation.com)

Facebook eventually shut down the ad serving side of Atlas and parts of LiveRail around 2016-2018, pivoting focus back to its own walled garden products.

Where it hurt:

• Marketers who migrated to Atlas/LiveRail as a Google alternative had to migrate back to other ad servers within a few years – effectively paying twice in implementation and data/attribution churn. 
• Microsoft and Facebook both absorbed huge write-offs and sunk R&D, making this one of the most expensive long-running painful migrations in AdTech history.

6.Verizon / AOL / Yahoo / Oath painful migrations: ad stack unification that never really unified

Verizon acquired AOL ($4.4B, 2015) and Yahoo ($4.5B, 2017) with ambitions to build a third adtech giant to rival Google and Facebook. The attempt to merge fundamentally incompatible ad stacks – ONE by AOL, Yahoo Gemini, BrightRoll DSP, Yahoo’s DMP – into a unified “Oath” platform was not just painful migrations lub catastrophic. Each system had different data models, bidding logic, and identity graphs. In practice, buyers and ops people described it as a “Frankenstein” platform:

• separate UIs for display, video and reporting, 
• bugs where changes didn’t save, 
• reliability issues and inconsistent integration across components.

Engineers spent years trying to reconcile them. In 2018, Verizon took a $4.6B goodwill write-down. They eventually sold the whole thing to Apollo Global for $5B in 2021 – after spending roughly $9B buying it.

Where it hurt:

• For Verizon/Yahoo: massive integration cost over years, yet they never achieved a truly competitive, cohesive stack. The assets were eventually sold off (Verizon Media → Apollo, rebranded as Yahoo again). 
• For agencies and advertisers who migrated spend into the Oath/Verizon stack, the operational overhead of dealing with non-unified tech and reliability problems often outweighed benefits – many ended up routing money back to Google, The Trade Desk, etc.

7.MediaMath – Painful migrations “Project Origin” & bankruptcy 2023

MediaMath was one of the original DSPs, founded in 2007. For years they ran on aging infrastructure, and around 2019–2021 they attempted a complete platform rewrite called “Origin” -intended to be a transparent, clean-room, supply-path-optimized next-gen DSP. The rewrite was perpetually delayed. They burned through capital, couldn’t close a restructuring deal, and filed Chapter 11 in June 2023. Hundreds of publishers were left owed money. This is an example of painful migrations where the bankruptcy was sudden enough that campaigns went dark mid-flight for many advertisers.

What went wrong: 

• Technical leadership turnover during the project was severe.
• Classic “big rewrite” problem – trying to rebuild everything from scratch while keeping the existing business running – here you can read about proper project management.
• Origin promised too much (clean data, transparent supply chains, new architecture) and delivered too slowly. 

8.Oracle Marketing Cloud / Oracle Advertising: shut down 2024

Oracle spent over $2B across a decade acquiring AdTech assets – BlueKai (DMP, ~$400M, 2014), Datalogix (offline data), Crosswise (cross-device), AddThis (audience data), Moat (measurement), Grapeshot (contextual). The ambition was a full marketing and advertising data cloud. The technical challenge of integrating fundamentally different data architectures, identity systems, and customer bases proved too great. Painful migrations? Yeap, none of the products fully unified. Moat lost clients steadily to IAS and DoubleVerify. Oracle announced it was shutting down its entire advertising business in 2024.

What went wrong: 

• The “data cloud” vision required a common identity spine that was never built properly across acquisitions.
• Acquihired engineers had different visions for each product. 
• Enterprise Oracle sales culture clashed with adtech product-led culture. 

9.One/Nielsen ID/MRC Accreditation Collapse: ongoing, hundreds of millions in lost contracts

Nielsen attempted to transition from its legacy TV panel measurement to “Nielsen One,” a cross-platform currency that could measure audiences across linear TV, streaming, digital, and social simultaneously. The (painful) migrations was delayed repeatedly (announced ~2019, still incomplete by 2024). In 2021 the Media Rating Committee suspended Nielsen’s accreditation after discovering it had been undercounting TV viewers during COVID – largely because the pandemic disrupted their panel recruitment and the migration to new methodologies was incomplete. Broadcasters used this as a trigger to accelerate alternatives (VideoAmp, Comscore, iSpot.tv). Nielsen lost hundreds of millions in revenue.

What went wrong:

• Tried to maintain a legacy panel-based system while building a new identity-resolved measurement system simultaneously. 
• Underinvested in the legacy system during transition.
• The new system required cross-industry cooperation (streaming platforms sharing data) that was never fully secured.

10. For dessert: the origin point. The Trade Desk’s a textbook painful migrations (2024-2025)

TTD’s old platform (Solimar) worked. Users loved it. It was intuitive, stable, and battle-tested. Then they built Kokai – an AI-powered successor that required a fundamental UX overhaul. The migration has been painful:

• Agencies reported bugs causing failed campaign launches, missing audiences, and broken integrations – costing clients actual revenue during peak ad seasons.
• Buyers spending tens of millions annually found themselves locked out of workflows they relied on.
• The platform transition contributed directly to TTD’s first earnings miss in 8 years (Q4 2024, missing by $15M), causing a 27% single-day stock drop.
• The VP of Product resigned mid-crisis.

What went wrong:

• Migrating enterprise clients off a working legacy system onto a new architecture – without breaking their live campaigns, maintaining integrations, or losing institutional knowledge – is one of the hardest engineering problems in AdTech. 
• TTD had to run two platforms simultaneously, which drained engineering resources and slowed everything down.

The Common Threads

I’ve asked myself why in AdTech painful migrations (or replatforming) is so common. The answer is quite simple: AdTech industry runs on infrastructure which never sleeps. You can’t close it at 3cam like ecommerce or finance services.There is no tolerance for downtime. Campaigns don’t pause while your engineers wrestle with a broken data pipeline. And the dependencies- DSPs talking to SSPs, DMPs syncing with CRMs, measurement layers stitched on top of everything – mean that pulling one thread can unravel the whole fabric.

Moreover beneath every programmatic bid, every targeting segment, every real-time auction sits a stack of platforms, pipes, and integrations that took years- sometimes decades- to build. So when a company decides to move, to replatform, to “modernize,” the stakes are existential.

Across all of these, a few patterns repeat consistently in painful migrations: underestimating the complexity of merging identity graphs and data models from different sources; the “big rewrite” trap where companies try to replace working systems entirely rather than incrementally; adtech-specific speed requirements (sub-100ms auctions) that make poorly integrated systems fail in production in ways that wouldn’t matter in other software; and  cultural mismatches when large corporations (Verizon, AT&T, Oracle) acquire fast-moving adtech companies and impose enterprise processes on them.

“Let’s deconstruct these painful migrations models and architect the recovery. See you in a 5 models of failure platform migration and how to handle it.😛

Read also about best practices for upgrading.