Migrate from Brightcove to Flicknexs

Start with the Media module export, because it is the fastest complete picture. Brightcove's Exporting Video Data page describes exporting video metadata as a .csv — "The .csv file will be named with the account number" — and instructs you to click Download "to download the video data file to your local computer". That page lists the exported fields in a table, including id, account_id, created_at, cue_points, custom_fields, delivery_type, description, digital_master_id, duration, economics, folder_id, geo, has_digital_master, images, name, original_filename, reference_id, schedule, state, tags and text_tracks. Run it in batches inside the documented ceilings (1000 videos when you include rendition URLs; under 15K per export). Then fill the gaps with the CMS API, whose Retrieve Video Data page gives base URL https://cms.api.brightcove.com/v1/accounts/{account_id}/{endpoint} and documents /videos, /videos/{video_id}, /videos/{video_id}/sources and /videos/{video_id}/images. The combined CSV plus /sources pull is the manifest the Flicknexs onboarding team works from — nothing else in the project starts until that manifest reconciles to your own count of titles.

There is no single "download my library" button, and Brightcove says so. The Downloading Videos page states "Video masters are the original source files that were ingested, saved for retranscoding. Video masters cannot be downloaded using Studio, but it can be done using the Social Syndication API if you need to." The documented route is on Brightcove's Download Video Masters page: create an MRSS feed of the "universal" type with fetch_digital_master set to true (POST https://social.api.brightcove.com/v1/accounts/{account_id}/mrss/syndications), set a template that includes the digital master, then read the feed at https://social.feeds.brightcove.com/v1/accounts/{account_id}/mrss/syndications/{syndication_id}/feed. Plan for paging: that page states "MRSS feeds are limited to 100 items" and that you page through a larger library using the offset parameter (for example offset=100 for the second 100 videos). Where no master exists, fall back to a rendition — the Downloading Videos page states "You can download a video rendition using the Media module if an ingest profile that creates at least one MP4 rendition was selected when the video was uploaded", and that "a clickable download link will only display if MP4 renditions have been created". DRM titles come last and separately: Brightcove's CMS API download-links code sample states "this API would work only for non-DRM'ed content. For DRM'ed content, the end-point should be clear_sources instead of sources", i.e. https://cms.api.brightcove.com/v1/accounts/[account id]/videos/[video id]/clear_sources — and Brightcove labels that sample "provided as a guide for your production development. The code is not certified for production use nor officially supported", so treat it as a path to discuss with your CSM rather than something to lean on silently. Flicknexs' bulk import toolkit ingests from the original source files, so every title you can supply as a master lands as a master.

Brightcove's per-video model is richer than a title-and-thumbnail import assumes, and the mapping decisions are yours, not the tool's. The CMS API Video Fields Reference documents per-video metadata fields including custom_fields, tags, text_tracks, transcripts, images, schedule, geo, economics, reference_id, digital_master_id, has_digital_master, drm_disabled, folder_id, cue_points and variants. Four of those drive real behaviour and need an explicit decision each: custom_fields (your own taxonomy — it has no automatic equivalent anywhere), schedule and geo (availability windows and territory rules that must be re-expressed as Flicknexs rules, not silently dropped), economics (which titles are ad-supported versus paid), and reference_id (your stable external key — carry it across unchanged so any system you own that references titles by it keeps working). Folders and tags become the Flicknexs catalog structure. The Flicknexs onboarding team writes this mapping as a table you sign off on, then the import runs against the signed table.

Export the audience from Beacon as documented (Registered Users module in Video Cloud Studio, CSV, with Email, Name, User external ID, User token, Date joined, Last login, Subscription details and Marketing consent). Then split the list on the payment gateway value inside Subscription details, because the two halves migrate differently. Card subscribers billed through Stripe — Beacon's Stripe Purchase page states "Stripe Connect is a service Stripe offers to facilitate payments in Brightcove Beacon" — are a gateway conversation you can plan. Store-billed subscribers across the four stores Brightcove lists (Apple, Google Play, Amazon IAP, Roku) are governed by those stores, not by either platform; Beacon's own account-deletion flow shows how firmly they sit outside, alerting the viewer "that they must cancel all active subscriptions with other platform's stores before Beacon account deletion can occur", after which the "Beacon backend verifies all of the viewer's active subscriptions with other platform's stores that there are no active subscriptions." Flicknexs imports the subscriber list with plan mapping and issues secure-link logins so nobody has to remember a password on cutover night; Flicknexs' plans are flat monthly with no commission on subscriber or transactional revenue, and you connect your own payment gateway. Pull your history before you go, too: Brightcove's Working with Registered Users page states of per-user viewing history that "History is captured and saved for 1 year", and the Audience API overview states "The Audience API allows you to retrieve viewing event and lead data", with base URL https://audience.api.brightcove.com/v1 and view_events and leads resources.

Live and linear are configuration, not data, so they are rebuilt rather than exported. Brightcove's NextGen Live API overview gives base URL https://api.live.brightcove.com and documents job endpoints POST /v2/accounts/{account_id}/jobs to create, PUT .../jobs/{id}/start and /stop, DELETE .../jobs/{id}, and GET .../jobs to list; its input protocol allowed values are rtmp, rtp and srt, and the job type is an enum of "channel" or "event". List your existing jobs through that GET before you lose access — that list plus your encoder settings is the spec Flicknexs rebuilds against, including the ingest protocol your encoders already speak. For linear, Brightcove's Cloud Playout overview describes compiling and scheduling "a combination of videos-on-demand and live feeds as a live linear channel", lists 24x7 Linear Channels, Pop-Up / Virtual Channels and Simulated Live Events, and states "an EPG service is built into Cloud Playout" with an "API to retrieve the EPG (electronic program guide) for a channel" — export that EPG as your schedule reference. Apps are the longest pole because the stores gate them. Beacon's Roku submission page instructs "At the start of the Channel setup, make sure that you use your organization's email address that will be used for developer rights", and states "Package File - The package file can be uploaded by you or by Brightcove", with a new package requiring "a unique id and password". Its Apple submission page notes "Periodically you will need to accept Tax and General Agreements as the account owner" at appstoreconnect.apple.com/agreements/#/. Confirm today that your organisation — not a Brightcove-held or agency-held identity — owns the Roku developer account and the Apple account owner seat; Flicknexs publishes white-label Android, iOS, Android TV, Fire TV, Roku, Samsung and LG apps into those same accounts.