Migrate from Kaltura to Flicknexs
To migrate from Kaltura 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 Kaltura customers move their videos, users, pricing tiers and apps with the Flicknexs team doing the mapping and imports.
Trusted by industry leaders
50+ streaming companies powered by Flicknexs
Why teams move from Kaltura
Kaltura is built for enterprises and universities with large internal video estates. Media companies and creators running a consumer subscription service move when they need a simpler, published-price platform with subscriber apps rather than an enterprise video portal.
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 Kaltura and what you keep.
| Asset | From Kaltura | Into Flicknexs | You keep |
|---|---|---|---|
| Video library and metadata | Entries and metadata via the Kaltura management console or API | Bulk import toolkit maps titles, descriptions, categories, artwork, captions and series structure | Every title, its artwork and its taxonomy |
| Subscribers and entitlements | Users from your Kaltura MediaSpace or identity provider | 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 from your Kaltura or third-party commerce setup | SVOD, TVOD, AVOD and hybrid tiers recreated; gateways connected; renewal dates preserved | Your prices, your renewal calendar, your gateway |
| Apps and store listings | Kaltura-built or custom 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 entries and schedules | 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.
A Rich Media CMS admin login plus a working API client keyed to your partner ID
An access-control and entitlement audit done before you try the first download
A paging plan that survives Kaltura's 10,000-result ceiling
A decision on which flavor you are actually carrying across
A separate collection plan for captions, thumbnails, related files and custom metadata
Both of your user populations identified, because Kaltura exports them separately
If you are on Cloud TV / OTT: a household-by-household extraction route
Your Order Form dates, notice mechanics and post-termination retention read in advance
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.
Five steps, usually spread over one to two weeks. The Flicknexs team runs steps 2 through 5 with you; your side supplies exports and store credentials.
Build the entry inventory — CSV for the shape, API for the detail
Pull the masters, one asset at a time or via your own storage profile
Collect the assets the export path leaves behind
Extract subscribers, entitlements and the billing picture
Rebuild live, apps and DRM on Flicknexs, then wind Kaltura down in the right order
Both streaming platforms run in parallel until your team tests and signs off on every device app.
A Kaltura migration, week by week
Two weeks is the common case for a Kaltura catalog of a few hundred titles and a few thousand subscribers. Larger libraries add days to the import, not to the plan.
Access, inventory and the security map
Stands up your Flicknexs tenant, reviews your Kaltura entries report and category export, and tells you exactly which metadata fields map where. Sizes the catalog and flags whether you are over the 10,000-result windowing threshold.
Provide a Rich Media CMS admin account and partner ID, install a Kaltura client library (https://developer.kaltura.com/api-docs/Client_Libraries), run the entries CSV export — remembering Kaltura's note that "the CSV download link sent via email is available only for 24 hours" (https://knowledge.kaltura.com/help/the-kmc-entries-tab) — and list your access control profiles and entitlement-enforced categories. Pull your Order Form dates at the same time.
Media extraction
Receives files as they land, verifies checksums and durations against your inventory, and reports back per-title gaps rather than a single pass/fail.
Run the per-asset pull (flavorAsset.getUrl, one `id` per call, https://developer.kaltura.com/api-docs/service/flavorAsset/action/getUrl/) or configure a remote storage profile and drive baseEntry.export with entryId + storageProfileId (https://developer.kaltura.com/api-docs/service/baseEntry/action/export/). Unblock the restricted entries your Week 1 audit flagged. If you are on Kaltura's published Media Services plan, the egress is billable at the $0.17/GB outbound rate on https://corp.kaltura.com/pricing/media-services/, so get it signed off before the pull starts.
Catalog rebuild: captions, artwork, metadata, taxonomy
Runs the bulk import of video plus metadata from your original source files, rebuilds the category and collection structure, and loads caption tracks and artwork against the right entries.
Complete the second pass Kaltura's export path does not cover — captionAsset actions for subtitles, metadata service for custom profile fields, thumbnails and related files (https://knowledge.kaltura.com/help/kalturas-remote-storage-configuration-and-information-guide). Review the field mapping and sign off on how series, seasons and rights windows are represented.
Subscribers, monetisation, apps and live
Imports subscribers with plan mapping and secure-link login, configures SVOD/TVOD/AVOD or hybrid to match your existing products, connects your own payment gateway, and submits your white-label Android, iOS, Android TV, Fire TV, Roku, Samsung and LG apps.
Supply the user exports (both populations if you run a portal: https://knowledge.kaltura.com/help/add-and-manage-users and https://knowledge.kaltura.com/help/user-management) or the OTT USERS export — remembering Kaltura's note that KSQL "cannot be used for USERS filtering" (https://raw.githubusercontent.com/kaltura/ott-developer-platform-generated/master/api-docs/service/exportTask/action/add/index.html) — plus per-household entitlements. Provide gateway credentials and store credentials, and run your encoders into Flicknexs live in parallel with Kaltura.
Cutover, then a deliberate Kaltura wind-down
Runs the full post-migration check list with you, switches DNS and app builds to production, and monitors the first live event and the first billing cycle on the new gateway.
Work the testing list, repoint every embed and cdnapisec.kaltura.com link you found, and stop renewals cleanly with entitlement.cancelRenewal rather than deleting anything (https://raw.githubusercontent.com/kaltura/ott-developer-platform-generated/master/api-docs/service/entitlement/action/cancelRenewal/index.html). Only then act on Section 7.2(a) — "providing us notice and… closing your account" (https://corp.kaltura.com/legal/tos/customer-agreement/). Keep your own archive of everything you extracted: Kaltura's GDPR FAQs state content and user data "will be deleted at the end of the subscription term" (https://corp.kaltura.com/legal/privacy/gdpr-faqs/), and its Customer Agreement Section 8.1 confirms "you, your End Users or your licensors own all right, title, and interest in and to Your Content."
Kaltura-specific things to check first
- Kaltura metadata profiles are rich; build the mapping sheet before export so custom fields land in the right Flicknexs fields.
- Single sign-on users need a decision: keep your identity provider and connect it to Flicknexs, or move to Flicknexs accounts with a password-reset link.
- Captions and transcripts generated inside Kaltura should be exported as files so they travel with the videos.
- Contract terms are typically annual; time the cut-over to the renewal date.
The five ways a migration goes wrong, and how each is prevented
A large library silently truncates at 10,000 results
This is the single most common way a Kaltura catalog arrives incomplete. Kaltura documents that a call rendering more than 10,000 results returns 'CRITERIA EXCEEDED MAX MATCHES ALLOWED' because "the eSearch results are limited to 10,000", and prescribes ordering by created_at and re-windowing the time filter from the last object in each batch (https://knowledge.kaltura.com/help/api-results-limitation). A script that paginates naively will look successful and simply stop. Reconcile your extracted count against media.count (listed on https://developer.kaltura.com/api-docs/service/media/) before anyone declares the export done.
Access control and default entitlement enforcement block the download of exactly your most valuable titles
Kaltura's own guidance on the no-API download URL is conditional — "if the entry is not set with any access control restriction" — and attributes failure to "enhanced security turned on", to Access Control, or to the entry being "in a Mediaspace category with 'Default Entitlement Enforcement' enabled on your account (default)" (https://knowledge.kaltura.com/help/how-to-download-a-raw-file). The protected content is by definition the premium content. Expect the restricted tier to need a deliberate profile change, and expect that change to need an internal approval you did not schedule.
Captions, thumbnails, related files and custom metadata are outside the export path entirely
Kaltura states that it "won't export caption files, thumbnails and related files", and its remote storage table lists Image entry, Thumbnails, Caption files, Related files and Meta-data as "Kaltura's DC only" while only video/audio source and transcoded flavors may live on customer storage (https://knowledge.kaltura.com/help/kalturas-remote-storage-configuration-and-information-guide). Teams that plan the migration around 'getting the videos out' finish the video pull, relaunch, and then discover every subtitle track and every hand-picked poster frame is gone. These need their own pass through captionAsset and metadata actions (https://developer.kaltura.com/api-docs/service/captionAsset/, https://developer.kaltura.com/api-docs/service/metadata/).
You may be pulling a flavor when you wanted the master — and the delete policy is account-wide
Kaltura's remote storage guide says that when flavors are exported "Kaltura can keep a copy of the file on its own cloud… or delete it after the file was exported", and warns that "While it is possible to selectively choose the file formats (flavors) that are exported to the remote storage, the 'delete after export' policy is across the entire account." It also states "Kaltura recommends keeping the source file stored on Kaltura's cloud (and not to export and delete it)", because otherwise "the source must be re-ingested in order to re-transcode to additional flavors" (https://knowledge.kaltura.com/help/kalturas-remote-storage-configuration-and-information-guide). If a previous administrator turned delete-after-export on, the highest-quality file you can retrieve today may be a transcoded rendition, not your original. Check per title before you assume you are re-encoding from a master.
The commercial clock runs independently of the technical one
Kaltura's Customer Agreement, Section 5.3, states minimum commitments are "non-cancelable" and "cannot be decreased during the specified term", with fees for minimum commitments and actual usage "not refundable"; Section 7.3 confirms that on termination "you will not receive a refund of any pre-paid fees, including… pre-purchased credits, monthly or annual fees paid in advance, or minimum commitments" (https://corp.kaltura.com/legal/tos/customer-agreement/). Kaltura's GDPR FAQs state that on termination "customer content and user data will be deleted at the end of the subscription term" (https://corp.kaltura.com/legal/privacy/gdpr-faqs/). Note also that Section 4.2 puts backup on you: "You are responsible for… taking your own steps to maintain appropriate security, protection and backup of Your Content." And budget the egress if your account sits on the published plan: Kaltura's Media Services pricing page lists outbound bandwidth at $0.17 per GB with "no upload charges" (https://corp.kaltura.com/pricing/media-services/), while the main pricing page shows the Media & Telecom / Cloud TV line with no published price at all (https://corp.kaltura.com/pricing/), so your own Order Form governs.
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.
- Entry-count reconciliation: compare titles live on Flicknexs against a fresh, unfiltered Kaltura entries report — Kaltura warns "The entries report is created based on any filters you applied to the data" (https://knowledge.kaltura.com/help/the-kmc-entries-tab), so re-run it with filters cleared and cross-check against media.count.
- 10,000-boundary audit: for a library above 10,000 entries, count imported entries per created_at month and look for a month with a suspicious cliff — that is the signature of the documented 'CRITERIA EXCEEDED MAX MATCHES ALLOWED' ceiling (https://knowledge.kaltura.com/help/api-results-limitation).
- Restricted-tier spot check: take a sample from every Kaltura access control profile and every MediaSpace category that had Default Entitlement Enforcement on (https://knowledge.kaltura.com/help/how-to-download-a-raw-file) and confirm those specific titles play on Flicknexs, since these are the ones most likely to have failed the download quietly.
- Source-versus-flavor check: for your top titles, confirm the file Flicknexs ingested is the original master and not a downstream rendition — relevant if delete-after-export was ever enabled, which Kaltura notes is an account-wide policy (https://knowledge.kaltura.com/help/kalturas-remote-storage-configuration-and-information-guide).
- Caption parity: count caption tracks and language labels per entry against captionAsset.list output, because Kaltura states it "won't export caption files" (https://knowledge.kaltura.com/help/kalturas-remote-storage-configuration-and-information-guide) and they only arrive if you pulled them separately (https://developer.kaltura.com/api-docs/service/captionAsset/).
- Poster and thumbnail check: confirm hand-chosen thumbnails survived rather than auto-generated frames — Kaltura lists Thumbnails and Image entry as "Kaltura's DC only" (https://knowledge.kaltura.com/help/kalturas-remote-storage-configuration-and-information-guide).
- Custom metadata field-by-field: verify every field from your Kaltura custom metadata profiles (pulled via metadata.list / metadata.get, https://developer.kaltura.com/api-docs/service/metadata/) landed in the right Flicknexs field — series, season, cast, rights window — since none of it appears in the nine-column entries report.
- Taxonomy diff: compare the Flicknexs category and collection tree against Kaltura's category.exportToCsv output (https://developer.kaltura.com/api-docs/service/category/), including empty and hidden categories that do not show up in a browse-based check.
- Embed and link sweep: search your websites, newsletters and partner pages for Kaltura player embeds and cdnapisec.kaltura.com/p/{PID}/… URLs — the host and path shape Kaltura documents at https://knowledge.kaltura.com/help/how-to-download-a-raw-file — and repoint every one, because they keep resolving to Kaltura while that account is open and stop when it closes.
- DRM playback matrix: Kaltura's uDRM covered PlayReady, Widevine and FairPlay via its on-the-fly packager (https://knowledge.kaltura.com/help/drm-support), so test the Flicknexs equivalent on a Windows browser, an Android device and a Safari/iOS device before cutover, not after.
- Live rehearsal: run a full live event on Flicknexs end to end and confirm the DVR seek-back behaviour and that the recording appears as a playable VOD asset — Kaltura's documented behaviour is "Records your live broadcast for instant VOD access once the live event is complete via the same embed code" (https://knowledge.kaltura.com/help/kaltura-live-streaming-overview---kmc-ng), and viewers will expect the same.
- Subscriber and renewal reconciliation: for a sample of households, compare Kaltura entitlement.list output (filtering isExpiredEqual to separate live from lapsed, https://raw.githubusercontent.com/kaltura/ott-developer-platform-generated/master/api-docs/service/entitlement/action/list/index.html) against the plan each account now holds on Flicknexs, take a live test transaction through your own gateway, and only then stop the old billing — Kaltura documents entitlement.cancelRenewal as "Cancel a household service subscription at the next renewal. The subscription stays valid till the next renewal." (https://raw.githubusercontent.com/kaltura/ott-developer-platform-generated/master/api-docs/service/entitlement/action/cancelRenewal/index.html), which is the safe way to stop double-billing; note that household.purge is documented as deleting "all of the household information, including users, devices, entitlements, payment methods" (https://raw.githubusercontent.com/kaltura/ott-developer-platform-generated/master/api-docs/service/household/action/purge/index.html), so keep it out of any migration script.
What you pay after the move, with a worked example
A worked monthly cost for a Kaltura service of 1,500 subscribers
Take a Kaltura 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.
Kaltura prices most media deployments by contract, so no figure appears here; use your current agreement divided by twelve.
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 Kaltura move.
| Task | Owner | Why that owner |
|---|---|---|
| Export from Kaltura | 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.
Kaltura next to the other platforms teams migrate from
Teams rarely compare only two platforms. The row for Kaltura is highlighted; every other row links to its own guide.
| Platform | Primary shape | Pricing model published | Usual trigger to move |
|---|---|---|---|
| Brightcove migration guide | 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 | 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 Kaltura 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 Kaltura 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
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.
Inna Segal T
Robert G
Frequently Asked Questions
Everything you need to know about migration from Kaltura 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.
Kaltura publishes pricing for some products on its corporate pricing page and quotes the rest by contract, according to corp.kaltura.com, checked 2026-09-03.
That depends on your contract with Kaltura. 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. Flicknexs runs education and training channels with courses, series, subscriptions and live classes, and its online-courses and education OTT pages describe that setup.
Other migration guides
Ready to leave Kaltura?
Start free, import a sample of your library, and see the admin with your own content before you commit.