- Organisation
- BT
- Predecessor
- an on-premises hardware-based video headend with manual capacity planning, hardware procurement and channel-build lead times measured in days or weeks
- Destination
- a cloud-based video headend using AWS Elemental MediaLive, AWS Elemental MediaPackage, Amazon S3 and AWS cost-management tooling
- Workload
- linear television channel encoding, packaging and over-the-top distribution
- Stage
- completed
- Retirement status
- The bounded 213-channel migration is complete; retirement of every wider BT TV or on-premises platform is not stated.
- Confidence
- High
- Next trigger
- A dated wider headend retirement, multi-region rollout or artificial-intelligence production milestone.
Programme context
BT operated a hardware-based on-premises video headend while serving a mix of IPTV and streaming services to more than 1 million subscribers. Hardware lifecycle, elasticity and support-cost constraints drove a move to a cloud-based headend on AWS.
Why this matters: The source provides a rare bounded infrastructure migration with a named production scope, a quantified 213-channel estate and a stated 12-month path from project start to production.
Migration timeline
| Date or stage | Milestone | What changed | Evidence status |
|---|---|---|---|
| Project start | phased migration begins | BT and AWS designed the target architecture, ran parallel workflows and validated channel migration before cutover. | Confirmed |
| Within 12 months | production migration completed | BT completed migration of 213 linear channels to cloud-based over-the-top distribution. | Confirmed |
| Future | planned expansion | BT describes artificial-intelligence and multi-region work as future direction rather than completed scope. | Planned |
Workload migration matrix
| Workload | Predecessor | Destination | Status |
|---|---|---|---|
| 213 linear TV channels | on-premises hardware video headend | AWS Elemental MediaLive and MediaPackage cloud workflows | completed |
| media assets and supporting storage | hardware-bound operating model | Amazon S3-backed cloud environment | operational within bounded solution |
| commercial cost insight | approximately one day to produce insights | AWS cost tooling producing insight in about ten minutes | operational outcome |
Implementation and architecture
- BT used AWS Elemental MediaLive for live video processing and AWS Elemental MediaPackage for packaging and distribution workflows.
- Amazon S3 supports storage within the target environment, while AWS cost tooling supports commercial insight.
- The programme used phased migration, parallel operation, validation and cutover rather than a single unsupported big-bang claim.
Known unknowns and contradictions
- The customer-story page does not state its publication date or the exact calendar date of final production cutover.
- The source does not identify every hardware product, retained broadcast component or dependent BT TV platform.
- Future artificial-intelligence and multi-region work is not part of the completed 213-channel claim.
No missing fact is inferred to broaden the source-supported event.
PlatformTrace analysis
AWS’s customer evidence supports completion of the bounded 213-channel video-headend migration and the stated operational service. It does not establish retirement of every BT TV platform, broadcast system or on-premises infrastructure component, and future AI and multi-region work remains planned.
The useful commercial signal is the completed migration of a quantified, production video estate—not a claim that every BT broadcast or infrastructure platform has moved to AWS.
Evidence ledger
- Amazon Web Services — BT customer success story
First-party vendor case study naming the predecessor constraint, AWS Elemental target architecture, 213 migrated channels, 12-month production path and bounded operating outcomes. The page does not state its publication date.
Approval: Issue #47 Lane 2 publication decision.
Corrections and updates
29 July 2026 — Initial Verified dossier published as a completed bounded 213-channel video-headend migration. Later wider-platform milestones will be appended rather than silently replacing this state.
Connected NeoLinks intelligence
Related evidence across the network
Curated because the records share an entity, platform, control, sector or procurement context. Each destination keeps its own evidence boundary.
AWS Lambda provided.al2 runtime deprecation
BT's video-headend migration is an enterprise adoption record; SchemaTrace tracks a distinct AWS runtime lifecycle that cloud-platform teams may need to plan around.