Why Dutch operators are moving away from legacy IPTV

For the better part of two decades, the Dutch TV market shared a familiar architecture: a managed STB stack, an EPG service, a head-end in a Tier-3 datacentre, and a vendor relationship that few operators valued but most felt unable to replace. In 2026 that arrangement is reaching its limits.

Three forces have converged. Subscriber expectations have shifted from "television that works" to "television that works on the phone, the LG set, the second living-room screen, and the display in the kitchen." Margins on traditional linear have compressed to the point where a single migration project can absorb a full year of operating profit. And the engineers who originally built the legacy stack are retiring or leaving the operator altogether.

The result is not a sudden exodus. It is a measured, deliberate transition, and across the market operators are reaching three consistent conclusions.

Device coverage is now the contract

The customer of a Dutch ISP is largely indifferent to whether the television experience is delivered over coax, an OTT application, or a managed STB. What matters to them is that the channel they want is available on every screen they own, that the EPG is identical across each, and that pause-and-resume functions reliably between a phone on the train and a Smart TV at home.

That single requirement - cross-device parity - is precisely where most legacy stacks fall short. They were designed when "the television experience" meant the box beneath the set. Adding a mobile application and a Smart TV application afterwards typically yields three competing applications, three competing roadmaps, and three distinct sets of EPG defects.

The replacement is a single content platform that ships first-party applications for Smart TVs (Samsung, LG, Android TV, Apple TV), mobile, web, and the STB, all driven by the same CMS, the same EPG, and the same entitlement service.

Managed outperforms build for all but the largest operators

The Dutch market contains roughly three operators at the scale where building a television platform in-house is economically defensible. For everyone below that threshold - regional ISPs, MVNOs adding television, alt-nets, and hospitality groups - building is no longer the obvious choice.

The decisive factor is staffing. A modern television platform requires specialists in DRM (Widevine, FairPlay, PlayReady), CDN economics, EPG ingestion, server-side ad insertion (SSAI), Smart TV certification cycles, and GDPR-compliant subscriber management. Assembling that team in the Netherlands in 2026 is difficult, slow, and costly, and once assembled it must be kept fully utilised to justify the investment.

A managed TVaaS deployment exchanges that staffing burden for a vendor relationship governed by an SLA. The operator retains the customer, the brand, and the commercial model, and is no longer obliged to recruit and retain a Widevine specialist.

The migration is the project, not the platform

The platform decision proves to be the straightforward half. The demanding half is the migration: transferring between 50,000 and 200,000 active STB customers without interrupting service, preserving entitlements throughout, and managing the long tail of devices sold in 2014 that remain in daily use in households across the country.

The approach we see succeed consistently combines a parallel-run period of 60 to 90 days, an opt-in early-access cohort to surface edge cases, a controlled cutover for the bulk of the base, and a planned end-of-life timeline for the oldest STBs communicated to subscribers six months in advance. Operators that attempt to omit the parallel run almost invariably come to regret it.

What this means if you are facing one of these decisions

For an operator approaching the next renewal cycle of a legacy contract, the question is no longer whether to modernise. It is whether to modernise through a build, a purchase, or a managed service, and on what timeline.

The answer is rarely "all at once." The pattern that works in the Netherlands in 2026 is to engage a managed TVaaS partner for the long-term platform, commit to a migration window of 6 to 12 months, and treat the legacy stack as a depreciating asset whose role is to remain operational until the replacement is fully cut over.

This is the conversation we are having with operators across the country today. If your team is beginning it, we would welcome the opportunity to talk.