Migrate from Brightcove to Flicknexs
Quick answer: To migrate from Brightcove to Flicknexs, export your library and metadata, bulk-import them into Flicknexs (a white-label OTT platform with web, mobile and TV apps), rebuild your subscription tiers, re-publish your apps under your brand, and run both platforms in parallel until cut-over. Most catalogs complete in one to two weeks, driven more by subscriber and billing mapping than by video transfer.
Flicknexs provides a managed OTT platform with a guided migration service, so Brightcove customers move their videos, users, pricing tiers and apps with the Flicknexs team doing the mapping and imports.
Facts checked on 3 September 2026. Flicknexs prices are from our pricing page.
Trusted by industry leaders
50+ OTT platforms powered by Flicknexs
Why teams move from Brightcove
Teams usually leave Brightcove at contract renewal, when the annual commitment no longer matches the size of the service, or when they want subscriber apps and billing in the same platform as hosting rather than assembled from several enterprise modules.
Flicknexs (a video-on-demand, live and cloud-playout platform sold on published monthly plans) is a common landing point because its plans are flat fees with no commission, you get live and linear channels from the first plan, and the same vendor runs the infrastructure, builds the apps and does the migration.
What moves, and how
Six asset classes make up a migration. Each row says how Flicknexs receives it from Brightcove and what you keep.
| Asset | From Brightcove | Into Flicknexs | You keep |
|---|---|---|---|
| Video library and metadata | Video Cloud library, metadata and custom fields via CMS API or CSV export | Bulk import toolkit maps titles, descriptions, categories, artwork, captions and series structure | Every title, its artwork and its taxonomy |
| Subscribers and entitlements | Subscriber records from your Brightcove Beacon or third-party identity system | User import with plan mapping; passwords are reset by secure link on first login | Every account and what it is entitled to watch |
| Pricing tiers and payments | Entitlements and prices from the payment provider connected to Brightcove | SVOD, TVOD, AVOD and hybrid tiers recreated; gateways connected; renewal dates preserved | Your prices, your renewal calendar, your gateway |
| Apps and store listings | Beacon or custom-built apps in your store accounts | White-label Android, iOS, Android TV and Fire TV apps; Samsung, LG, Roku and Apple TV as add-ons | Your developer accounts, listings and ratings history |
| Live channels and schedules | Live module events and any linear feeds | Live events, M3U8 linear channels and cloud playout schedules | Your channel line-up and program grid |
| Domains, DRM and analytics | Custom domain, DRM policy and analytics exports | Custom domain on Flicknexs, Widevine and FairPlay via the DRM add-on, analytics from day one | Your domain authority and your historical numbers |
Source: Flicknexs migration playbook and our pricing page, 2026-09-03.
What to have ready before the first call
Migrations stall on missing access, not on missing video. Gather these eight items before the audit call and the first week is the export, not the chase.
Video Cloud Studio Administrator access plus an OAuth client for the CMS API
Two different keys open two different doors. Commercial facts live behind the Studio Administrator role: Brightcove's Viewing Billing Information page states "to access the Billing page, you must be a Video Cloud Studio user with the Administrator role and you must have an annual contract associated with your account." Everything programmatic runs off a separate credential — the CMS API overview documents authentication via an "Authorization: Bearer {access_token}" header whose token "must be obtained from the Brightcove OAuth service." Get both issued before migration week, to a named person on your side, not to an agency seat you may lose access to.
A written answer to "do we still have the digital masters?"
This is the single question that decides whether your migration is a file copy or a re-encode. Brightcove's Download Video Masters page warns that "All standard ingest profiles store the video master, but if you are using a custom ingest profile, it is possible that it specifies that masters should not be stored", and notes it is possible via the CMS API to delete video masters, which some customers have done "in order to reduce data storage costs." Brightcove's Digital Master Delete API page is blunt about the consequence: "Deleting a digital master is a permanent operation. We cannot restore deleted digital masters" and "You will no longer be able to re-transcode a video after its master is deleted." Pull the has_digital_master and digital_master_id fields for every asset — both are documented in the CMS API Video Fields Reference — and treat the no-master list as a separate workstream.
The account's DRM state, confirmed with Brightcove before you start pulling files
DRM changes what a download even returns. Brightcove's DRM overview states "When videos are enabled for DRM, MP4 sources/renditions are automatically hidden (meaning that they exist, but are not sent to player as sources) in Studio, the CMS API, and the Playback API", and the Downloading Videos page adds that "If DRM is toggled on, any MP4 renditions that exist will be hidden; any m3u8 content downloaded will be encrypted." It is also not a self-serve switch: the DRM overview states "DRM requires an additional fee" and "DRM must be configured for your account by Brightcove Support and your Customer Success Manager", so any change to that state needs a ticket and a calendar slot, not an afternoon.
Export batches sized to Brightcove's documented Studio limits
The Media module's CSV export has two published ceilings that shape your inventory plan. Brightcove's Exporting Video Data page states that if you check "Include current URLs for video renditions", "video metadata for a maximum of 1000 videos can be exported" — and separately that "Brightcove recommends exporting less than 15K videos at a time. If you need to export more than 15K videos, use the search feature to return a subset of videos and export multiple 'batches' at a time." Decide up front which saved searches slice your library into those batches (folder, tag, or created_at range) so the export is repeatable rather than a one-off click.
An API rate budget that respects the CMS API's published limits
Anything you script against Brightcove has to fit inside numbers Brightcove publishes. The CMS API overview states "no more than 20 concurrent calls to the CMS API are allowed per account. Access frequency should be less than 10 requests per second", and that "If either the rate or concurrency limit is exceeded, a 429 - TOO_MANY_REQUESTS error will be returned." Paging is tighter still: Brightcove's CMS API paging page states "A maximum of 100 records will be returned from a single request to the CMS API, but for large result sets, we recommend fetching 25 items per request for better performance", and the Retrieve Video Data page notes, for fetching multiple videos by id, "Note that no more than 10 video ids can be included." Brightcove also states the CMS API "provides uncached read access to the data" and "is not appropriate for high scale runtime usage" — so build the extractor with backoff and resume, not a tight loop.
A Beacon registered-user export and a per-subscriber answer to "who bills this person?"
If you run Brightcove Beacon, the audience export is documented: the Exporting Registered User Data page covers exporting registered user data as a CSV from the Registered Users module in Video Cloud Studio, with fields Email, Name, User external ID, User token, Date joined, Last login, Subscription details and Marketing consent — and per that page, "Subscription details - Includes subscription name, start/end dates, status, payment gateway, and transaction ID". That payment gateway column is the one that matters, because billing is split. Beacon's Stripe Purchase page states "Stripe Connect is a service Stripe offers to facilitate payments in Brightcove Beacon", while its In-App Subscription Resources page lists in-app purchase documentation for four platform stores — Apple Store (iOS/tvOS), Google Play Store (Android/Android TV), Amazon IAP (Amazon Fire TV) and Roku. Split your subscriber list by gateway before you plan anything, because the store-billed group cannot be moved the same way.
Your contract dates, the notice deadline, and a realistic read of the Billing module
Migration timing is a contract question first. The Brightcove Service Agreement, section 7.2 (Term of Orders), states "If indicated in an Order, the Order shall automatically renew for successive periods on the first day following the end of the Initial Term (each, a 'Renewal Term') unless either party hereto has provided notice to the other of non-renewal at least 60 days in advance of the end of the Initial Term or Renewal Term (as applicable)", with the initial term itself running "for the duration set forth in the Order". Section 5.2 (Obligation to Pay) states "All fees are non-refundable." Note also what the Billing module will and will not tell you: Brightcove's Viewing Billing Information page states "Storage is cumulative. At the end of each month, Brightcove records a snapshot of your total storage and adds it to a running total for your contract... The total is never reset; it only grows as each monthly snapshot is added", and "The billing information for the last month of the contract period is not displayed in the Billing module."
An inventory of every downstream feed that currently points at Brightcove
Your catalog is probably syndicated somewhere you have forgotten. Brightcove Beacon's OTT Catalog Export page states the feature "generally assists in getting your OTT assets available on platform searches, for instance Apple and Roku, as well as in search engines", and lists its syndication types as Apple UMC Catalog CSV, Apple UMC Availability CSV, Google site map XML, Sitemap index XML and Roku Search Feed 2.0 (JSON). Each of those is a consumer of your Brightcove catalog that has to be re-pointed or retired on cutover day, and each has its own refresh lag on the far side.
The migration plan, step by step
Five steps, usually spread over one to two weeks. The Flicknexs team runs steps two to five with you; your side supplies exports and store credentials.
- 1
Take the inventory out of Studio, then deepen it with the CMS API
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.
- 2
Pull the media itself — masters first, renditions as fallback, DRM titles handled apart
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.
- 3
Map Brightcove's field model onto the Flicknexs catalog before a single title is imported
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.
- 4
Move registered users, subscriptions and entitlements out of Beacon — splitting by who bills them
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.
- 5
Rebuild live, Cloud Playout and the store apps, then cut over
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.
A Brightcove migration, week by week
Two weeks is the common case for a Brightcove catalog of a few hundred titles and a few thousand subscribers. Larger libraries add days to the import, not to the plan.
| When | Flicknexs does | You do |
|---|---|---|
| Week 1 — access, contract clock, and the master audit | Onboarding team scopes the library, sets up the extraction runner inside Brightcove's published CMS API limits (20 concurrent, under 10 requests per second, 25-100 records per page), and starts the batched Studio CSV export plan. | Issue a Studio Administrator login and an OAuth client for the CMS API. Find the Initial Term end date in your Brightcove Order and put the 60-day non-renewal notice deadline from Service Agreement section 7.2 on a shared calendar. Confirm in writing whether the account is DRM-enabled — and if it is, open the ticket with Brightcove Support and your CSM now, since the DRM overview states DRM configuration is done by them. |
| Weeks 2-3 — extraction | Runs the batched metadata export and CMS API pull, builds the master manifest (including has_digital_master and digital_master_id per title), and pulls source files through the Social Syndication MRSS universal feed with fetch_digital_master set to true, paging with offset because Brightcove states MRSS feeds are limited to 100 items. | Approve creating the syndication feed on the account. Review the no-master list and decide, title by title, which ones you can re-supply from your own archive and which migrate from an MP4 rendition. Identify the DRM titles that will run as a separate phase. |
| Weeks 3-4 — mapping and catalog rebuild | Produces the field-mapping table from Brightcove's documented video fields (custom_fields, tags, text_tracks, transcripts, images, schedule, geo, economics, reference_id, folder_id, cue_points) to the Flicknexs catalog, then imports into a staging environment for you to walk through. | Sign off the mapping table — especially custom_fields, availability windows, geo rules and which titles are ad-supported versus paid. Walk the staging catalog yourself against a list of titles you know well, rather than approving a summary. |
| Weeks 4-5 — audience, apps and live | Imports the Beacon registered-user export with plan mapping and secure-link login, wires your own payment gateway, rebuilds the live jobs and any Cloud Playout linear channels and EPG, and prepares the white-label Android, iOS, Android TV, Fire TV, Roku, Samsung and LG builds. | Export registered users from the Beacon Registered Users module and split them by the payment gateway inside Subscription details. Confirm your organisation holds the Roku developer account (Brightcove's Roku submission page ties developer rights to the organisation email used at channel setup) and the Apple account owner seat, and clear any outstanding Tax and General Agreements at appstoreconnect.apple.com/agreements/#/. Draft the re-subscribe message for store-billed viewers. |
| Cutover week and the 30 days after | Runs the full post-migration checklist with you, keeps both catalogs readable during the overlap, watches the first billing cycle and the first live event, and fixes what the checks surface. | Work the checklist rather than sampling it. Re-point or retire every downstream feed that pointed at Brightcove (the OTT Catalog Export types: Apple UMC Catalog CSV, Apple UMC Availability CSV, Google site map XML, Sitemap index XML, Roku Search Feed 2.0 JSON). Archive your Audience API view_events and leads data and your Beacon viewing history before account access ends — Brightcove states that history is saved for 1 year and the Billing module does not display the last month of the contract period. Only then send the non-renewal notice, ahead of the deadline you diaried in week 1. |
Source: Flicknexs onboarding schedule for catalog migrations, 2026-09-03. Durations are typical, not guaranteed.
Brightcove-specific things to check first
- Confirm your renewal date and notice period before exporting; Brightcove contracts are annual, so time the cut-over to the end of the term.
- Custom fields in Video Cloud need a mapping sheet before import so nothing is lost into a generic description field.
- If your player is embedded on third-party sites, list those embeds; each one is replaced with the Flicknexs player embed at cut-over.
- Analytics history stays in Brightcove; export the reports you need for year-over-year comparison before access ends.
The five ways a migration goes wrong, and how each is prevented
The master you need may not exist, and that is unrecoverable
Everything downstream of a missing master is a compromise. Brightcove's Download Video Masters page states "All standard ingest profiles store the video master, but if you are using a custom ingest profile, it is possible that it specifies that masters should not be stored", and notes masters can be deleted via the CMS API, which some customers have done "in order to reduce data storage costs." The Digital Master Delete API page states "Deleting a digital master is a permanent operation. We cannot restore deleted digital masters" and "You will no longer be able to re-transcode a video after its master is deleted." Mitigation: query has_digital_master across the whole library in week one, not week four. Titles without masters migrate from the best available MP4 rendition, which means a transcode of a transcode — acceptable for a library long-tail, not acceptable for your hero titles, which may need re-supply from your own archive.
DRM turns a straightforward file pull into a support-ticket dependency
On a DRM-enabled account the files you expect to find are deliberately not there. Brightcove's DRM overview states that when videos are enabled for DRM, "MP4 sources/renditions are automatically hidden (meaning that they exist, but are not sent to player as sources) in Studio, the CMS API, and the Playback API", and the Downloading Videos page adds "any m3u8 content downloaded will be encrypted." The documented alternative — the clear_sources endpoint from Brightcove's CMS API download-links sample — is explicitly labelled "not certified for production use nor officially supported." And you cannot change the account's DRM state yourself: the DRM overview states "DRM must be configured for your account by Brightcove Support and your Customer Success Manager." Mitigation: open that conversation at the start of the project, and sequence DRM titles as their own phase with its own dates.
The inventory phase takes longer than teams expect, because of published limits rather than anything going wrong
Three separate documented ceilings compound on a large library: the Exporting Video Data page's "video metadata for a maximum of 1000 videos can be exported" when rendition URLs are included, and its recommendation to export "less than 15K videos at a time"; the Download Video Masters page's "MRSS feeds are limited to 100 items", paged via offset; and the CMS API overview's "no more than 20 concurrent calls to the CMS API are allowed per account. Access frequency should be less than 10 requests per second", returning "429 - TOO_MANY_REQUESTS" when exceeded. None of that is a fault — it is just arithmetic that has to be in the plan. Mitigation: size the extraction against your actual title count on day one, run it with resume and backoff, and schedule it before the contract-notice deadline rather than after.
Store-billed subscribers do not transfer, and Brightcove's own flow shows why
A subscriber paying through Apple, Google Play, Amazon or Roku has a contract with that store. Beacon's In-App Subscription Resources page lists in-app purchase documentation for exactly those four stores, and its account-deletion flow requires that the viewer "must cancel all active subscriptions with other platform's stores before Beacon account deletion can occur", with the Beacon backend then verifying there are no active store subscriptions. Beacon's deletion flow also covers "Removal of viewer information from Stripe and other connected payment gateways, excluding native stores" — note the exclusion. Mitigation: treat store-billed subscribers as a re-subscribe campaign with its own messaging and its own success metric, not as a data import, and do not let the card-billed migration's success rate hide that group's churn.
Contract timing can cost you a full renewal term if the notice window slips
The Brightcove Service Agreement, section 7.2, states an Order "shall automatically renew for successive periods on the first day following the end of the Initial Term (each, a 'Renewal Term') unless either party hereto has provided notice to the other of non-renewal at least 60 days in advance of the end of the Initial Term or Renewal Term (as applicable)", and section 5.2 states "All fees are non-refundable." Because Brightcove does not publish figures on its Studio Packages page — which lists Marketing Studio (Starter, Essential, Premium), Communications Studio (Essential, Premium) and Media Studio (Essential, Premium) with "Request a Demo" and "Contact Sales" as the calls to action — you cannot model your own exposure from public information; it has to come from your Order. Mitigation: find the Initial Term end date in your Order in week one, set the notice deadline on a shared calendar, and keep in mind that section 15 points data-processing obligations at the Data Processing Agreement at brightcove.com/en/legal/cdpa/, which governs how subscriber personal data is handled on the way out.
The cut-over checklist Flicknexs signs before DNS moves
We check every item on the parallel sub-domain with your real content and a real payment. Both sides sign the checklist before DNS moves.
- Reconcile counts three ways: rows in the Studio Media CSV export (run in batches under the documented 15K-per-export recommendation), the count returned by the CMS API /videos endpoint, and titles live in Flicknexs. Investigate every gap by id before go-live — do not accept a percentage.
- Confirm reference_id survived the move unchanged for every title. It is the documented CMS API field your own downstream systems most likely key on, and a silently regenerated id breaks them after cutover, not during it.
- Spot-check custom_fields end to end. Brightcove's CMS API Video Fields Reference documents custom_fields per video; these are your taxonomy and have no automatic equivalent, so verify a sample from every field you defined, not just the first title in the list.
- Verify text_tracks and transcripts. Pick titles in each language you carry and confirm captions load, are selectable in the player, and are not offset — caption loss is the most common thing nobody notices until a viewer complains.
- Re-test every schedule and geo rule. Brightcove stores both as per-video fields; after migration, confirm a title whose window has not opened is genuinely unplayable, and that a geo-restricted title is blocked from a restricted territory, using a real check rather than reading the admin screen.
- Check the economics field mapping: every title Brightcove had marked one way should sit in the matching Flicknexs monetisation bucket. Pull the list of titles where the mapped value differs from the source CSV and clear it to zero.
- For each DRM title, play it on the device classes that required DRM in the first place, after Flicknexs has re-encrypted it. Brightcove's DRM overview lists Apple FairPlay, Google Widevine Modular and Microsoft PlayReady as the supported DRM types — test at least one device per family you actually serve.
- Flag and review every title that migrated from an MP4 rendition rather than a digital master. Brightcove's Downloading Videos page notes a rendition download is only available where the ingest profile created an MP4 rendition; these titles are a generation removed from source, so eyeball your top-viewed ones on a large screen before you call the migration complete.
- Before regenerating catalog feeds, confirm every asset has artwork. Brightcove's OTT Catalog Export page states of the Roku Search Feed type: "Assets that don't contain images would not be included on the feed JSON generated as a mandatory requirement from Roku" — the same gap that silently shrank your old feed will shrink the new one.
- Test subscriber login as a real subscriber, not as an admin. Take a sample from each plan in the Beacon export's Subscription details column, confirm the mapped Flicknexs plan matches the subscription name and status, and confirm the secure-link login lands the viewer straight into entitled content.
- Reconcile the card-billed subscriber list against your own gateway dashboard after the first billing cycle, and separately confirm the store-billed cohort (Apple, Google Play, Amazon IAP, Roku, per Brightcove's In-App Subscription Resources page) has been handled as re-subscription rather than counted as migrated.
- Run a live end-to-end test from your actual encoder. Brightcove's NextGen Live API lists rtmp, rtp and srt as the allowed input protocols, so test the same protocol your encoders are configured for today, including a stop and restart, before you point a real event at it.
- If you run Cloud Playout, export the EPG through the API Brightcove documents for it and diff the rebuilt Flicknexs schedule against it programme by programme for at least a full 24-hour loop — including the overnight hours nobody watches while testing.
- Archive your Brightcove analytics baseline before access ends. Brightcove's Audience API overview documents view_events and leads at https://audience.api.brightcove.com/v1, and the Working with Registered Users page states viewing history "is captured and saved for 1 year" — once the account closes, that comparison baseline is gone and you cannot tell whether post-migration numbers are good or bad.
What you pay after the move, with a worked example
According to our pricing page, Flicknexs provides transparent platform tiers covering web-only platforms, mobile apps (Android and iOS), and connected TV apps (Android TV, Fire TV, Roku, Apple TV, Samsung, and LG). See our pricing page for current plan and pricing details.
Every plan carries flat monthly fees and no commission on your subscriber or transactional revenue. You can add additional TV apps and the bulk import toolkit for migrations as modules; see our pricing page for current plan and pricing details.
A worked monthly cost for a Brightcove service of 1,500 subscribers
Take a Brightcove service with 1,500 paying subscribers, a web platform, Android and iOS apps, and one Roku app. According to our pricing page, that service sits on the F2 plan covering web plus Android and iOS, with the Roku app configured as an add-on, with flat platform pricing and no commission on subscriber revenue. See our pricing page for current plan and pricing details.
Brightcove does not publish a price for a comparable configuration, so no competitor figure appears here; use your current annual invoice divided by twelve as the comparison.
Subscription revenue is untouched on Flicknexs because plans are flat fees with no commission, according to our pricing page, so the comparison is between one fixed monthly platform cost and whatever your current bill scales with.
Who does what
A migration fails when a task has no owner. This is the split Flicknexs uses on every Brightcove move.
| Task | Owner | Why that owner |
|---|---|---|
| Export from Brightcove | You | It is your account and your data. Flicknexs never logs in to a competitor platform. |
| Metadata mapping and bulk import | Flicknexs | The import toolkit and the content model are ours to operate. |
| Recreate tiers and connect gateway | Flicknexs, with your keys | Prices and renewal logic are configured by us; the gateway account is yours. |
| Subscriber import and login emails | Flicknexs | Plan mapping and secure-link flow are platform functions. |
| Brand assets and store listings | You | Logo, screenshots and listing copy carry your identity. |
| App builds and store submission | Flicknexs, from your accounts | We build and submit; you own the listing. |
| Cut-over checklist sign-off | Both | A named person on each side signs before DNS moves. |
| DNS change and subscriber announcement | You | Domain control and customer communication stay with the brand. |
Source: Flicknexs migration playbook, 2026-09-03.
Brightcove next to the other platforms teams migrate from
Teams rarely compare only two platforms. The row for Brightcove is highlighted; every other row links to its own guide.
| Platform | Primary shape | Pricing model published | Usual trigger to move |
|---|---|---|---|
| Brightcove | Enterprise online video platform with OTT apps by contract | Not published; enterprise quote | Contract renewal, module count, want apps and billing in one place |
| Vimeo OTT migration guide | Subscription video platform, web-first, apps on Enterprise | Per subscriber plus a share of one-time purchases | Subscriber growth makes per-seat pricing costly; need branded apps or ads |
| Uscreen migration guide | Creator membership platform | Published plans | Outgrowing the creator model; need live, linear, partners or ads |
| Muvi migration guide | Several OTT products, each priced separately | Published per product, apps billed per app | Consolidating several product bills into one platform |
| VPlayed migration guide | Customizable OTT framework, customer-managed | Quote-based | Engineering upkeep; want a managed platform with custom builds on request |
| Dacast migration guide | Live streaming and hosting with a paywall | Published plans, bandwidth metered | Business becomes a subscription service needing apps and a catalog |
| Wowza migration guide | Streaming infrastructure and engine | Published, usage and license based | Want the whole service layer, not only delivery |
| Kaltura migration guide | Enterprise and education video platform | Partly published, mostly contract | A consumer subscription service needs a simpler, published-price platform |
| Mogi I/O migration guide | White-label OTT and micro-drama SaaS | Not published; demo-led | Want a published price, a self-serve trial and cloud playout |
| Vodlix migration guide | White-label VOD SaaS | Published plans | Roadmap adds linear or FAST channels or custom features |
| Wistia migration guide | Business video hosting and marketing | Published plans, media-count sized | Video becomes the product and needs subscribers, billing and apps |
| Vimeo On Demand migration guide | Sell-your-video storefront, closing | Per-sale fees; shutting down Nov 20, 2026 | The storefront is shutting down and sellers must move |
| Shift72 migration guide | White-label VOD and virtual cinema for festivals | Not published; demo-led | A festival window becomes a year-round subscriber service |
Source: each vendor's public website, checked 2026-09-03. Pricing model column reflects what the vendor publishes, not a quote.
What changes for your viewers, and what does not
For a viewer, the move from Brightcove to Flicknexs shows up as one email asking them to set a new password by secure link, and then the same catalog under the same brand at the same address. Their plan, price and renewal date are unchanged. Their watch history starts fresh unless Brightcove exports it, in which case continue-watching positions are imported for the titles that exist on both sides.
Apps update through the stores as normal updates, so the icon on the home screen stays where it was. Live channels keep their line-up. Rentals bought before the move remain watchable for the period you set at import.
What the admin tells you in the first month
- Login rate on the secure-link email, so you can resend to anyone who did not complete it
- Plays and watch time by title and by device, compared with the last export you took
- Revenue by tier and by gateway, with failed renewals listed for follow-up
- Channel viewing for linear playout, if you run one
- Redirect hits on old title URLs, which fall as search engines pick up the new pages
Conclusion: what to do next
Audit your catalog
If you are on Brightcove and the bill, the roadmap or the app footprint no longer fits, the move to Flicknexs is a two-week project with a fixed price at the end of it. Start free: import twenty titles, sign in as a test subscriber, and look at the admin with your own content.
Start free
Then book the audit call. The onboarding team scopes the Brightcove exports, agrees the timeline in writing and names the signers for cut-over. Nothing is switched off on Brightcove until the checklist is signed.
Your apps on the web, phones and TVs.
Launch your OTT apps now→Simple, Transparent Pricing
Choose the perfect plan for your streaming business. No hidden fees.
F1 Standard
Perfect for startups and small businesses
- 20 TB Bandwidth per year
- 300 GB Storage
- Video on Demand Website
- Video APIs
- Content Delivery Network
- Pre, Mid & Post Roll Ads
- upto 50 channels*. via m3u8
- Multiple Monetization Options
- Third Party Integration
F2 Super
Most popular for growing businesses
- 20 TB Bandwidth per year
- 300 GB Storage
- Video on Demand Website
- Video APIs
- Content Delivery Network
- Pre, Mid & Post Roll Ads
- upto 50 channels*. via m3u8
- Multiple Monetization Options
- Third Party Integration
- Mobile Apps (Android, iOS)
F3 Premium
For established streaming platforms
- 10 TB Bandwidth per month
- 1 TB Storage
- Video on Demand Website
- Video APIs
- Content Delivery Network
- Pre, Mid & Post Roll Ads
- upto 100 channels*. via m3u8
- 5 Youtube Channels Streaming
- upto 5 RTMP Channels using Flicknexs RTMP
- DVR
- Multiple Monetization Options
- Third Party Integration
- Mobile Apps (Android, iOS)
- Android TV & Fire TV
F4 Enterprise
Enterprise-grade streaming solution
- 20 TB Bandwidth per month
- 2 TB Storage
- Video on Demand Website
- Video APIs
- Content Delivery Network
- Pre, Mid & Post Roll Ads
- upto 100 channels*. via m3u8
- 5 Youtube Channels Streaming
- upto 5 RTMP Channels using Flicknexs RTMP
- DVR
- Multiple Monetization Options
- Third Party Integration
- Mobile Apps (Android, iOS)
- Android TV & Fire TV
- Custom Features & Priority Support
Every plan includes
- SSL certificate
- 99.5% uptime
- 24/7 support
More TV screens
Samsung, LG, Roku and Apple TV apps, each added to your plan.
24×7 TV channels
Cloud playout for always-on channels, priced by the number of channels you run.
Trusted by high-growth brands globally on G2 reviews
FLICKNEXS is recognized by thousands of users for delivering exceptional scalability, support and direct ROI.
Metehan D.
"I would like to thank Rajeev for his effort and collaboration from our initial meeting to the platform development stage. We were in search of a white label OTT platform for our brand, and Flicknexs provided us with everything we needed to know right from the beginning of the process. They mentioned that they are open to all kinds of customization and integration when we want to integrate different partners into the OTT Platform. Everything went smoothly for us in all stages. Their collaboration and platform methods are very consistent. What I like best about Flicknexs is that they provide very quick and accurate responses to every question. Their response times for taking action are very fast. They seek solutions to all kinds of real industry problems and provide our company’s needs to the platform in the most accurate way. The software interface is quite easy to use and multifunctional. So far, we haven’t encountered any drawbacks. Our platform was quickly soft-launched, and once we go live with the apps, our process will be complete. We wanted to transfer our bootcamp videos, which currently operate on a pay-per-view model on our existing website, to the OTT platform. This way, we aim to provide our customers with a better experience through multi-functional memberships and purchasing models than other platforms."
Inna Segal T
"We've been working with FLICKNEXS, and I've got to say, they're really good. Their platform has heaps of features (150 or so, they reckon), and it's awesome for streaming – works a treat on any gadget you've got. Big shoutout to Rajeev from their end. Top bloke. He's given us some solid advice and even sorted us out with a coder to help in the first month. Champion effort. Early days yet, but I reckon we're on to a winner with FLICKNEXS. If you're looking to stream your stuff and want the real deal, give 'em a bell. Top-notch."
Robert G
"Phase 1 of our release has been seamless. From initial enquiry with Rajeev through to hand-holding all the way from Manoj and his support team. In less than two months we have developed and published on Android , Ios and Amazon Fire , with Android TV publishing imminent. We are now moving onto Phase 2, adding Samsung, Roku and LG into the mix. We already run a successful OTT platform on another service; and FLICKNEXS has so far proved to be a good alternative"
Frequently Asked Questions
Everything you need to know about migration from Brightcove on Flicknexs.
One to two weeks for most catalogs. Very large libraries or many subscription tiers can take longer; the Flicknexs team scopes the timeline after the audit in step one.
No. Accounts are imported with their entitlements. Subscribers receive a secure link to set a new password on first login, because passwords are never exported in readable form.
Guided migration is part of onboarding. Large catalogs use the bulk import toolkit, which our pricing page lists as a monthly module you can switch off once the import is complete. See our pricing page for current plan and pricing details.
Yes. New app builds are submitted as updates from your own developer accounts, so listings, ratings and install base carry over. Both platforms run in parallel until you cut over.
No. All plans are flat monthly fees with no commission on subscriptions, rentals or advertising.
Web-only services start on the web platform plan, mobile-app services on F2, and services with TV apps on F3 or F4, according to our pricing page. The migration team confirms the fit during the audit. See our pricing page for current plan and pricing details.
Brightcove does not publish OTT pricing; its OTT product page directs buyers to a sales conversation, according to brightcove.com, checked 2026-09-03.
That depends on your contract with Brightcove. Check the notice period and renewal date before the audit call so the cut-over lands before the next billing cycle. Flicknexs does not contact the vendor on your behalf.
They keep receiving the secure link for as long as you choose to resend it, and their entitlement waits for them. The admin shows who has and has not completed login so you can follow up.
Yes. Flicknexs serves your existing domain, and public title pages are redirected one-to-one to the new pages, so search rankings and shared links are preserved rather than dropped.
The plan does not change; the import does. Large libraries run through the bulk import toolkit in batches over more days, and the audit call sets the schedule before anything is exported.
Yes. Hosting, player, apps, subscriptions and analytics are one platform on Flicknexs, so the modules you licensed separately from Brightcove land in one admin.
Other migration guides
Ready to leave Brightcove?
Start free, import a sample of your library, and see the admin with your own content before you commit.