One Library Instead of Several, With Retention

What you can do together

• Bring the library and the metadata that matters across, with what must survive agreed with the team that uses it.
• Import existing renditions so the move is not a re-encode of everything.
• Put the material under one retention and access model, which is usually the reason for consolidating.
• Replace published embeds deliberately rather than discovering them after the source is gone.

How it connects

An existing library and its metadata would be brought across. Metadata is the part worth scoping carefully, because a Brightcove library often carries custom fields, tags and playlist structures that a marketing team relies on and that mean nothing to anyone else. An engagement would establish what must survive the move and what can be dropped, which is a conversation with the team that uses it rather than a technical decision.

Existing renditions can be imported during migration, so material moves without re-encoding everything.

Published embeds are the part that catches people. Brightcove players are embedded in live pages, campaigns and emails, and migrating the library does not change those. An engagement would establish where the material is currently embedded and sequence the replacement, because a migration that leaves a hundred pages pointing at a decommissioned player is a worse outcome than not moving at all. Brightcove stays in place until the material and its embeds are verified across.