Player migration

# Player vendor shut down? Migrate in weeks, without interruption

Consolidation in this market is constant. Vendors are acquired, discontinued or repriced, and the teams that depended on them are left to replace a player under a deadline, with live services to keep running.

A player migration isn't as big as it looks. Your manifests, DRM servers and ad tags stay exactly where they are. Only the playback layer changes, and you can prove it on your own streams before you switch any traffic.

## Why teams migrate to Bradmax

### The vendor shut down or was absorbed

Brightcove, Vimeo, Kaltura and THEOplayer customers have all watched their vendor change hands or change terms. When the roadmap stops, the player has to be replaced.

### The pricing model changed

Usage tiers and per-stream multipliers make costs unpredictable as you grow. Bradmax is flat monthly pricing from EUR 99, published on the pricing page.

### The coverage is missing

A player that works on the web can still fail on Smart TVs, on older devices or with DRM. Those are the layers Bradmax maintains, including device-specific fixes.

### The plugin stack is a maintenance bill

DRM connectors, ad integrations, analytics and TV support each need an owner. One player with these built in removes the maintenance surface.

## The migration is smaller than it looks

The playback layer is a small part of a streaming stack. The manifest, the packaging, the CDN and the licence server don't change. Bradmax reads the same HLS, DASH or Smooth Streaming source and negotiates the same DRM licence.

That's why the migration guides are short. They map the concepts one by one: how the old player was configured, how DRM was wired, how events and analytics were reported, and what the equivalent is in Bradmax.

## A migration in four moves

### Inventory what you have

List the sources, the DRM systems and licence servers, the ad tags, the analytics events and the devices you support. The migration checklist walks through it.

### Point Bradmax at your own stream

Run the player against your manifest on the free plan. Confirm DRM, ads and analytics behave before touching production.

### Map the integration

Move the old configuration across using the migration guides: source setup, DRM, ad tags, events and UI map to their Bradmax equivalents.

### Retest the devices that matter

Recheck playback on the web, mobile and TV targets your audience uses. Where a specific model misbehaves, that is the kind of problem we fix on the device.

## TISA: a vendor shut down, six leagues kept streaming

TISA, a Swiss provider of digital platforms for sports organizations, lost its video player vendor with little notice, while already committed to Flutter across its products. Its clients, including Ekstraklasa and the Lithuanian Football Federation, needed live football to keep playing.

Bradmax delivered a custom integration in weeks, rolled out in phases across web, mobile, Smart TV and Android TV boxes, with no interruption to service. The full story is in the TISA case study.

## What changes, and what does not

| Criterion | Stays the same | Changes |
| --- | --- | --- |
| Source and packaging | Your HLS, DASH or Smooth Streaming manifests | Nothing |
| DRM | Your licence servers and endpoints | How the player is configured to reach them |
| Advertising | Your ad tags and VAST/VMAP setup | Where the player loads them |
| The embed | Your page and layout | The player reference |

## Start the migration

- [Player migration checklist](https://bradmax.com/site/en/guides/player-migration-checklist)

- [Migrate from hls.js](https://bradmax.com/site/en/guides/migrate-hlsjs-to-bradmax)

- [Migrate from Shaka Player](https://bradmax.com/site/en/guides/migrate-shaka-player-to-bradmax)

- [Migrate from Video.js](https://bradmax.com/site/en/guides/migrate-videojs-to-bradmax)

- [TISA case study](https://bradmax.com/site/en/case-studies/tisa)

- [Start free](https://bradmax.com/site/en/signup)

## Frequently asked questions

### How long does a player migration take?

The player layer is usually weeks, not quarters. TISA replaced a vendor that shut down with no interruption to its live sports clients, across web, mobile and TV. The work is bounded by how many devices you retest, not by the player.

### Do I have to re-encode my content?

No. Bradmax plays the HLS, DASH and Smooth Streaming manifests you already produce. Your packaging, delivery and DRM servers stay as they are; the player reads what is already there.

### What happens to my DRM and ad configuration?

Your licence servers and ad tags are reused. You point the player at the same endpoints, and the migration guides map the old integration concepts (source setup, DRM, events, UI) to the Bradmax equivalents one by one.

### Will there be downtime?

No. You run Bradmax against your own streams on the free plan, on the devices you support, before you switch any traffic. The change is the embed, not the delivery.

### What does it cost to migrate?

The free plan is enough to prove the migration on your own manifest and devices. Paid plans start at EUR 99 a month and include support, analytics, ad insertion and multi-DRM.

## Sources and method

- TISA case study Bradmax customer story, vendor replacement without interruption

- Migration guides Bradmax documentation for hls.js, Shaka Player and Video.js

### Prove the migration on your own stream

Run Bradmax against your manifest, your DRM and your devices on the free plan before you switch any traffic. If you get stuck, an engineer answers.