Migrate from Vodlix to Flicknexs
Quick answer: To migrate from Vodlix 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 Vodlix 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 Vodlix
Vodlix is a capable on-demand platform. Teams move to Flicknexs when the roadmap adds scheduled linear channels, FAST distribution or custom features that need a development team behind the SaaS.
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 Vodlix and what you keep.
| Asset | From Vodlix | Into Flicknexs | You keep |
|---|---|---|---|
| Video library and metadata | Library and metadata exported from the Vodlix admin | Bulk import toolkit maps titles, descriptions, categories, artwork, captions and series structure | Every title, its artwork and its taxonomy |
| Subscribers and entitlements | Subscriber export with plan and status | 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 | Plans and gateway configuration | SVOD, TVOD, AVOD and hybrid tiers recreated; gateways connected; renewal dates preserved | Your prices, your renewal calendar, your gateway |
| Apps and store listings | Vodlix-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 streams and any IPTV configuration | 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.
Your own master files — Vodlix will not return the originals
Vodlix's Publisher License Agreement states that "The publisher must maintain a backup of all files posted to Vodlix since after a file has been encoded, Vodlix will not enable the publisher to download or recover the original file that was uploaded to Vodlix" (https://vodlix.com/vodlix-license-agreement). The same agreement states that "The publisher is solely responsible for maintaining a copy and backup of any films and content published to the Vodlix platform." So the first prerequisite is not an export credential — it is locating your archive: the drives, NAS, LTO or cloud bucket holding the mezzanine or camera-native files you originally uploaded. Flicknexs imports from original source files, so a clean master inventory mapped to Vodlix titles is what makes the rest of the move mechanical.
A check on whether downloadable renditions were ever kept
Vodlix's Media Upload & Encoding page documents encoding settings including "Keep MP4" ("Keep the MP4 without conversion") and "Keep downloadable files" ("Retain downloadable files for HLS and DASH"), and says these "live under Settings → Vodlix Settings → Uploading & Conversion on installs that expose it" (https://docs.vodlix.com/content-management/media-upload-encoding). Vodlix's Video & Playback settings page documents an "Allow Video Download" setting and states "Downloading is off by default" (https://docs.vodlix.com/settings-configuration/video-playback). Check both before you assume anything is retrievable: if Keep MP4 was on for part of your catalogue, those titles have a non-transcoded file; if it was never on, the only pixels on the platform for those titles are streaming renditions.
Akuna S3 bucket credentials, if that integration was ever switched on
Vodlix's Streaming & Storage integrations page documents an integration named cb_akuna that "Sync[s] originals and HLS assets to Akuna S3 storage", with a requirements table listing "Akuna S3 / S3 uploader — Bucket and credentials" (https://docs.vodlix.com/integrations/streaming-storage). If your cloud has that integration configured, the bucket is the one place a copy of your originals may exist outside Vodlix's own storage. Get the bucket name, region and access keys from whoever set it up, and confirm coverage title by title rather than assuming the sync ran for the whole library.
REST API access at a plan tier that actually includes it
Vodlix's pricing comparison table shows REST API as "Not included" on Launch, "Basic" on Grow and "Full" on Scale, Professional, Business and Enterprise, with monthly API request allowances of 250k (Launch), 2M (Grow), 10M (Scale), 10M (Professional), 20M (Business) and 30M (Enterprise) (https://vodlix.com/pricing). If you are on Launch, catalogue extraction is an admin-screen and manual-record exercise, not a scripted one. Vodlix's Plan Entitlements page also states that after a plan change "the cloud picks up its new entitlements on the next licence refresh — daily on hosted installs, weekly on-premises" (https://docs.vodlix.com/permissions/plan-entitlements), so a tier change made to enable API extraction is not instant.
An API key of the right type, captured at creation
Vodlix's API Keys & Webhooks page states that keys come in two types — Server ("Full access: inherits all permissions of the assigned user, including create / update / delete on the admin surface") and Client ("Origin-locked, and blocked from every administrative route regardless of user level") — and that a key is shown once at creation: "Copy this key now. It will NOT be shown again" (https://docs.vodlix.com/settings-configuration/api-keys-webhooks). Extraction needs the Server type, issued against a user whose permissions cover the admin surface you intend to read. The same page notes "Keys are active on this cloud and will authenticate requests — no switch to flip", so treat the key as live credentials from the moment it is created and plan its revocation as part of cutover.
A client that handles Vodlix's cookie authentication and its cloud-name prefixes
Vodlix's API documentation states that authorisation "is based on cookies": on login the API returns phpid, sess_salt and token, which "are stored in cookies and must be included in subsequent requests to authenticate the user", and that on a cloud setup the cookies carry the cloud-name prefix — its example being mycloudphpid, mycloudsesssalt, mycloudtoken — while a non-cloud setup uses phpid, sesssalt, token (https://documenter.getpostman.com/view/6478073/2s946ffYtT). A stock bearer-token HTTP client will not work against it. The same documentation's "Rate limit" section states that "The specific limit would depend on the API's policy" and that exceeding it means "the server will typically respond with a 429 Too Many Requests HTTP status code", and states no request-per-period figure — so your client needs backoff on 429 rather than a tuned request rate.
Admin access to the Subscribers screen and its export scopes
Vodlix's Subscribers documentation page documents an "Export Subscribers" control offering the scopes "Export All", "Export Active", "Export Inactive", "Export Cancelled" and "Export CSV", and states that "Exports run in the background, and you'll get a report of success, failure, or that no data matched the current filters" (https://docs.vodlix.com/revenue-management/subscribers). Pull each scope separately rather than only "Export All", because the scope split is what lets you reconcile counts later. The same page lists the Manage Subscribers columns as User / Username, Package, Amount, Status (Active / Inactive / Cancelled), Processed and Actions, which tells you exactly which fields you will have to map into Flicknexs plans — and which you will not.
Clarity on who is merchant of record for your subscribers
Vodlix's pricing page FAQ states: "On Pay as You Grow we act as merchant of record: we bill your subscribers, keep $0.99 per active subscriber per month, and pass the rest to you" (https://vodlix.com/pricing). The same page's comparison table shows "Revenue share" as 0% and "Per-subscriber fee" as None for all six fixed plans and marks "Own payment gateways" as included on all six. Which of those two shapes you are on decides the whole billing side of the migration: if you hold the gateway, you can migrate the mandates; if Vodlix is billing your subscribers, the paying relationship sits with them and your viewers will need to subscribe again on your own gateway. On Flicknexs you connect your own gateway and pay no commission on subscriber or transactional revenue.
Your notice position and the deletion clock that follows it
Vodlix's Publisher License Agreement states: "If your contract with Vodlix is month-to-month, either party has the right to discontinue service at any time with 30 days' notice. All data and access are deleted from our systems at the conclusion of the 30-day notice period once the account is ended" (https://vodlix.com/vodlix-license-agreement). For annual terms it states that "any party may terminate the auto-renewal of the agreement with at least 30 days' notice before the term renewal date", and that you are then switched to month-to-month. Establish which of those you are on, and the exact renewal date, before you plan any cutover — the notice you serve starts a countdown on the data you still need.
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
Inventory the cloud through Vodlix's documented read endpoints and admin screens
Vodlix does not publish a bulk catalogue export endpoint; its API documentation documents paginated read-by-listing calls including GET {{apiBase}}/v2/videos/list/?limit=24&page=1, GET {{apiBase}}/v2/series/list/?limit=24&page=1, GET {{apiBase}}/series/list/?page=1&paginate=1&limit=24, GET {{apiBase}}/season/list/31, GET {{apiBase}}/artists, GET {{apiBase}}/videos/categories/?type=is_video and GET {{apiBase}}/v2/contentList/3 (https://documenter.getpostman.com/view/6478073/2s946ffYtT), and states that the API "is RESTful... It returns data in JSON format." So the catalogue is walked page by page and reassembled locally into a single manifest of videos, series, seasons, artists and categories. Vodlix's Admin Page Index does list "importer.php · content_importer.php · exporter.php" under the purpose "Import and export" and "import_users.php · old_import_users.php" under "User import", but the same page warns that "Presence does not mean availability" — some listed screens belong to the older admin template, exist only on self-hosted installs, or sit behind a plan entitlement (https://docs.vodlix.com/reference/admin-page-index). Open those screens on your own cloud before you plan around them; if they are not there, the API manifest is your inventory. Flicknexs onboarding takes that manifest as the metadata side of the bulk import.
- 2
Assemble the actual video files from your archive, not from Vodlix
This is the step that is unlike most platform moves, and it is the one to start first. Because Vodlix's Publisher License Agreement states it "will not enable the publisher to download or recover the original file that was uploaded" after encoding (https://vodlix.com/vodlix-license-agreement), the video side of the migration is sourced from your own masters and matched against the manifest from step 1. Work the exceptions deliberately: titles where "Keep MP4" or "Keep downloadable files" was enabled under Settings → Vodlix Settings → Uploading & Conversion (https://docs.vodlix.com/content-management/media-upload-encoding), and titles covered by a cb_akuna sync to Akuna S3 (https://docs.vodlix.com/integrations/streaming-storage), may have a file you can still retrieve. Everything else needs a master, and any title with no master is a re-source or re-master decision to make now rather than at cutover. Flicknexs's bulk import toolkit ingests the video plus its metadata from those original source files.
- 3
Export subscribers, then translate Vodlix's subscription states into plans
Run each scope of the "Export Subscribers" control — Export All, Export Active, Export Inactive, Export Cancelled and Export CSV — and wait for the background job's success/failure/no-data report (https://docs.vodlix.com/revenue-management/subscribers). Map the exported columns User / Username, Package, Amount, Status and Processed onto your Flicknexs plans, and treat Vodlix's own lifecycle definitions as the mapping rules: its Subscription Lifecycle page lists the states as Trial, Active, Grace, Cancelled and Expired / Inactive, defines Cancelled as "Renewal stopped; access continues to the end of the paid period plus grace", and states "Access runs for the billed period plus grace, regardless of when within it the viewer cancelled" (https://docs.vodlix.com/revenue-management/subscription-lifecycle). Cancelled-but-still-entitled viewers therefore have to arrive on Flicknexs with access, not without it. Flag manual subscriptions separately, because the Subscribers page states that "Adding a subscriber here grants access without taking any payment" — those records have no gateway agreement behind them at all. Flicknexs imports subscribers with plan mapping and gets viewers back in via secure-link login rather than a password reset.
- 4
Move the billing relationship at the gateway, not only in the records
Exported subscriber rows do not carry the money. Vodlix's Subscription Lifecycle page states that "a price change on a package doesn't re-price existing gateway agreements — those keep running on their agreed terms until you change them at the gateway", that "In-app purchase subscriptions are cancelled in the app store, not in Vodlix", and that where a viewer is billed after cancelling the likely cause is "The gateway-side agreement was not cancelled", resolved by "Cancel at the gateway or through its portal" (https://docs.vodlix.com/revenue-management/subscription-lifecycle). Work three lists in parallel: agreements on your own gateway (re-point or re-consent to your Flicknexs-connected gateway), app-store IAP subscribers (who must be handled in App Store Connect and Google Play, not in either platform's admin), and — if you were on Pay as You Grow, where Vodlix's pricing page FAQ states "we act as merchant of record: we bill your subscribers" (https://vodlix.com/pricing) — subscribers whose paying relationship is with Vodlix and who will need to subscribe again on yours. Capture your pre-move revenue baseline while you still have the account: Vodlix's Reports page states each report's data table carries buttons to "copy, export CSV, save a PDF or print" and that "Downloads include exactly what's on screen: if a filter is applied, the downloaded file is filtered too", across General Revenue, New Orders, Churn Rate, Growth Rate, New Users and Content Ratings (https://docs.vodlix.com/dashboard-insights-reports/reports).
- 5
Re-provision apps, live channels, DRM and webhooks, then serve notice last
Collect the app identity from Vodlix's App Settings screen at /admin_area/app_settings.php, which its documentation says covers App Configurations (App Name, App Bundle ID, Alias), Store links, Credentials — "Apple Developer credentials for signing, Apple TV credentials, Android API key file" — Builds per platform and API credentials (https://docs.vodlix.com/settings-configuration/mobile-app-settings). Keeping the same bundle IDs and store listings is what lets existing installs update to your Flicknexs-built Android, iOS, Android TV, Fire TV, Roku, Samsung and LG apps instead of becoming new listings. For live, note that Vodlix's Streaming & Storage page states a channel bound to a Flussonic slot has its "Stream Provider field lock[ed] to Flussonic" reporting "Locked to Flussonic (slot linked)" and that "You can't change the provider on a live channel bound to a provider slot until the slot is unlinked" — so unlink slots before you try to re-point ingest, and record each channel's HLS URL and Stream Provider first (https://docs.vodlix.com/live-tv/live-channels). Re-point your DRM licence URLs — Vodlix's Video & Playback page documents PlayReady, Widevine and FairPlay License URL fields plus a FairPlay Certificate URL — and rewire anything consuming the outbound webhook events listed on the API Keys & Webhooks page (Video, Series, User and Artist Create/Update and Delete, plus Email Send). Only once Flicknexs is serving your viewers do you serve the 30-day notice, because Vodlix's Publisher License Agreement states "All data and access are deleted from our systems at the conclusion of the 30-day notice period once the account is ended" (https://vodlix.com/vodlix-license-agreement).
A Vodlix migration, week by week
Two weeks is the common case for a Vodlix 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, inventory and the masters audit | Onboarding team sets up your Flicknexs environment, takes your catalogue manifest, and starts the master-coverage audit: which Vodlix titles have a source file you hold, which are covered by a Keep MP4 or Akuna S3 retrieval path, and which need re-sourcing. | Issue a Server-type API key in Vodlix and copy it at creation, since its documentation states "Copy this key now. It will NOT be shown again" (https://docs.vodlix.com/settings-configuration/api-keys-webhooks). Walk the documented list endpoints to build the manifest, open /admin_area/members.php and the Subscribers screen to confirm what you can see, and check whether exporter.php or importer.php actually exist on your cloud — Vodlix's Admin Page Index warns that "Presence does not mean availability" (https://docs.vodlix.com/reference/admin-page-index). Confirm your contract shape and renewal date, and freeze your plan for the duration. |
| Weeks 2-3 — catalogue and video ingest | Bulk-imports video plus metadata from your original source files, rebuilds the series / season / episode structure, artists and categories from the manifest, and reports back any title where the master is missing or fails QC. | Deliver masters in batches, retrieve anything available from the Akuna S3 bucket or from titles where "Keep downloadable files" was enabled (https://docs.vodlix.com/content-management/media-upload-encoding), and make the call on titles with no master — re-source, re-master, or retire. Keep the Vodlix account fully paid while this runs. |
| Week 3 — subscribers, plans and gateway | Imports the subscriber files with plan mapping, preserves period-and-grace entitlements for viewers exported under the Cancelled scope, connects your own payment gateway, and configures your SVOD, TVOD, AVOD or hybrid model on a flat monthly plan with no commission on subscriber or transactional revenue. | Run each Export Subscribers scope and wait for its background report (https://docs.vodlix.com/revenue-management/subscribers), export the General Revenue, New Orders and Churn Rate reports as your baseline, and split subscribers into three lists: your own gateway, app-store IAP, and — on Pay as You Grow, where Vodlix's pricing page FAQ states "we act as merchant of record: we bill your subscribers" (https://vodlix.com/pricing) — those who will need to subscribe again on your gateway. |
| Week 4 — apps, live, DRM and parallel run | Builds and submits the white-label Android, iOS, Android TV, Fire TV, Roku, Samsung and LG apps under your own developer accounts, stands up live and cloud playout, wires your DRM licence URLs, and runs both platforms in parallel while you verify. | Hand over the App Bundle ID, Alias, store links and signing credentials recorded from /admin_area/app_settings.php (https://docs.vodlix.com/settings-configuration/mobile-app-settings), unlink any Flussonic provider slots so live channels can be re-pointed (https://docs.vodlix.com/integrations/streaming-storage), and work the post-migration checklist — playback, DRM, subscriber counts, gateway reconciliation — until it is clean. Note Vodlix's pricing footnote that on Enterprise, "LG and Samsung apps are included on Enterprise subject to agreed terms... store approval is the store's decision" — store review timing is outside either platform's control. |
| After sign-off — notice, then shutdown | Switches your domain and traffic to Flicknexs, monitors the first full billing period against the Vodlix baseline, and stays on the reconciliation until the numbers agree. | Only now serve notice: Vodlix's Publisher License Agreement states that month-to-month either party may discontinue "with 30 days' notice" and that "All data and access are deleted from our systems at the conclusion of the 30-day notice period once the account is ended", while on an annual term auto-renewal must be terminated "with at least 30 days' notice before the term renewal date" (https://vodlix.com/vodlix-license-agreement). Revoke your Vodlix API keys, cancel residual gateway agreements at the gateway, and — if you want the account data actively removed — note that Vodlix's Privacy Policy states "You can make a deletion request directly in your account on client.Vodlix.com" while logged in, confirmed by e-mail within the legal deadlines (https://vodlix.com/privacy-policy). |
Source: Flicknexs onboarding schedule for catalog migrations, 2026-09-03. Durations are typical, not guaranteed.
Vodlix-specific things to check first
- Map Vodlix feature toggles to Flicknexs modules before the move so nothing your subscribers use today is missing on day one.
- Export subscriber records with plan and status fields intact; renewal dates are preserved on import.
- Confirm app ownership in the stores; re-publish from your own accounts where possible.
- If you plan a linear channel, schedule its build in the parallel-run week so it launches with the cut-over.
The five ways a migration goes wrong, and how each is prevented
Your masters are the migration — and Vodlix has told you in writing it keeps no recoverable copy
Vodlix's Publisher License Agreement states that after encoding "Vodlix will not enable the publisher to download or recover the original file that was uploaded to Vodlix", that backups are the publisher's responsibility, and that Vodlix "disclaims all responsibility and liability for any videos or material that is lost on the Vodlix network and is solely the publisher's obligation to re-upload and restore in the event of any loss of data" (https://vodlix.com/vodlix-license-agreement). The failure mode is a library that has been on the platform for years, an archive that was tidied at some point, and a block of titles for which nothing exists but streaming renditions. Audit master coverage against the catalogue manifest in week one, not at cutover, so any re-source or re-master work has runway.
The 30-day notice is also a 30-day deletion timer — and fees can shorten it
Vodlix's Publisher License Agreement states that on a month-to-month contract "All data and access are deleted from our systems at the conclusion of the 30-day notice period once the account is ended", and separately that Vodlix "maintains the right to completely terminate your account, erase all of the data connected to it, and remove it from our servers if the fees owed to us are more than 14 days overdue" (https://vodlix.com/vodlix-license-agreement). The same agreement states in capitals: "ALL VODLIX FEES ARE FINAL. THERE ARE NO REFUNDS FOR ANY MONTHLY FEES, PLATFORM FEES, OR DEVELOPMENT FEES PAID TO VODLIX." Practically: keep the account paid and current until extraction is verified complete, and do not serve notice as the first act of the migration. Vodlix's Terms of Service section 14 also states that after the initial three days of a paid subscription "no refunds will be provided for subsequent monthly or yearly payments" (https://vodlix.com/terms-of-service), so the overlap month is a cost to plan for, not one to recover.
Subscribers keep billing — or keep access — after you think you have moved them
Vodlix's Subscription Lifecycle page states that "a price change on a package doesn't re-price existing gateway agreements — those keep running on their agreed terms until you change them at the gateway", that in-app purchase subscriptions "are cancelled in the app store, not in Vodlix", and that a viewer billed after cancelling usually means "The gateway-side agreement was not cancelled" (https://docs.vodlix.com/revenue-management/subscription-lifecycle). Two opposite errors follow from the same gap: viewers double-billed because the old mandate was never cancelled at the gateway, and viewers cut off early because Cancelled on Vodlix still means "access continues to the end of the paid period plus grace." Reconcile at the gateway and the app stores, not from the admin list. Note too that Vodlix's Subscribers page warns "Removing a subscription deletes the record outright rather than cancelling it, so reach for Cancel first" (https://docs.vodlix.com/revenue-management/subscribers) — a tidy-up during migration can destroy the very record you were about to reconcile.
Downgrading mid-migration to save money can erase the settings you were copying
Vodlix's Plan & Usage page carries the warning "Downgrading your plan can erase related settings", stating that when a plan change removes a feature "the platform clears the settings that depended on it rather than quietly keeping them", with the example that if a downgrade removes pay-per-view "the prices and rental periods you'd set on titles are cleared too" (https://docs.vodlix.com/platform-housekeeping/plan-usage). The reverse timing hurts too: its Plan Entitlements page states that after a plan change "the cloud picks up its new entitlements on the next licence refresh — daily on hosted installs, weekly on-premises" (https://docs.vodlix.com/permissions/plan-entitlements). So an upgrade taken to unlock API extraction may not be usable immediately, and a downgrade taken to trim the overlap bill can delete PPV pricing and other configuration before you have captured it. Freeze the plan until extraction is signed off.
Live, DRM and app entitlements are wired to the plan you are leaving, and unwind in a specific order
Vodlix's pricing comparison table shows Live streaming, FAST channels and Linear TV as "Not included" on the three Web & API plans (Launch, Grow, Scale) and included on the three Apps+ plans (Professional, Business, Enterprise), and shows "Multi-DRM (Widevine+FairPlay)" as "Not included" on Launch and Grow and marked "*T&C" on Scale and above; its footnote states "Enterprise DRM is available at an additional cost of $500/month, plus DRM licence fees charged per view" (https://vodlix.com/pricing). On the operational side, a live channel bound to a Flussonic slot reports "Locked to Flussonic (slot linked)" and its provider cannot be changed until the slot is unlinked (https://docs.vodlix.com/integrations/streaming-storage), and Vodlix's Video & Playback page states that "DRM without valid licence URLs prevents playback rather than falling back to unprotected delivery" (https://docs.vodlix.com/settings-configuration/video-playback). Half-migrating any of these produces a black player rather than a degraded one — capture the configuration, then unwind slot bindings and licence URLs deliberately.
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 subscriber counts scope by scope: Vodlix's Subscribers page documents Export All, Export Active, Export Inactive and Export Cancelled as separate scopes (https://docs.vodlix.com/revenue-management/subscribers), so check that Flicknexs's imported active count matches Export Active, and that All minus Active accounts for the Inactive and Cancelled files rather than disappearing.
- Spot-check viewers who were Cancelled on Vodlix but still inside their paid period plus grace — its Subscription Lifecycle page states "Access runs for the billed period plus grace, regardless of when within it the viewer cancelled" (https://docs.vodlix.com/revenue-management/subscription-lifecycle) — and confirm they can still sign in and play on Flicknexs until that date.
- Identify every subscriber that was added manually in Vodlix, since its Subscribers page states "Adding a subscriber here grants access without taking any payment", and confirm each one landed on the intended Flicknexs plan rather than on a paid plan with no gateway agreement behind it.
- Confirm no viewer is billed twice: check at your own payment gateway's portal that migrated mandates were cancelled there, because Vodlix's Subscription Lifecycle page names "The gateway-side agreement was not cancelled" as the cause of post-cancellation charges (https://docs.vodlix.com/revenue-management/subscription-lifecycle).
- Verify app-store subscribers separately in App Store Connect and Google Play, since the same Vodlix page states "In-app purchase subscriptions are cancelled in the app store, not in Vodlix" — an IAP subscriber cannot be migrated from either admin panel.
- Compare the pre-move revenue baseline you exported from Vodlix's Reports screen — General Revenue, New Orders and Churn Rate, downloaded as CSV or PDF with filters recorded, since "Downloads include exactly what's on screen" (https://docs.vodlix.com/dashboard-insights-reports/reports) — against the first full billing period on Flicknexs, and explain any delta.
- Reconcile catalogue counts against the paginated Vodlix listings you walked: videos (/v2/videos/list), series (/v2/series/list), seasons (/season/list/{id}), artists (/artists) and categories (/videos/categories/?type=is_video) per its API documentation (https://documenter.getpostman.com/view/6478073/2s946ffYtT), so that episode-level records inside series are counted, not just top-level titles.
- Play a sample from every source class in your archive — masters you re-uploaded, titles retrieved because "Keep MP4" was enabled (https://docs.vodlix.com/content-management/media-upload-encoding), and titles pulled from an Akuna S3 bucket (https://docs.vodlix.com/integrations/streaming-storage) — on web plus at least one TV app, and check resolution and audio track against the Vodlix original.
- Test every DRM title end to end on each platform, because Vodlix's Video & Playback page states "DRM without valid licence URLs prevents playback rather than falling back to unprotected delivery" (https://docs.vodlix.com/settings-configuration/video-playback) — a missed licence URL surfaces as a dead player, not as unprotected streaming.
- Re-test link-sharing protection: Vodlix's cb_vodlix_token integration "signs media URLs so that a copied link expires and can't be shared around indefinitely", with the expected behaviour that "a copied link stops working once the signature lapses" (https://docs.vodlix.com/integrations/streaming-storage). Copy a playback URL out of the Flicknexs player, wait past the signature window, and confirm it fails.
- Start every live channel on Flicknexs ingest and confirm it is no longer dependent on a Vodlix provider slot — its Streaming & Storage page states a bound channel reports "Locked to Flussonic (slot linked)" until the slot is unlinked (https://docs.vodlix.com/integrations/streaming-storage).
- Install the new apps over an existing install using the same App Bundle ID recorded from Vodlix's /admin_area/app_settings.php screen (https://docs.vodlix.com/settings-configuration/mobile-app-settings), and confirm existing users receive an update rather than being asked to find a new listing.
- Rewire and fire each integration that consumed Vodlix webhooks — its API Keys & Webhooks page lists Video Create/Update, Video Delete, Series Create/Update, Series Delete, User Create/Update, User Delete, Artist Create/Update, Artist Delete and Email Send (https://docs.vodlix.com/settings-configuration/api-keys-webhooks) — and confirm no downstream system is still waiting on the old source.
- Audit and revoke your Vodlix API keys at the end, remembering that its documentation states Server keys carry "Full access: inherits all permissions of the assigned user, including create / update / delete on the admin surface" and that "Keys are active on this cloud and will authenticate requests — no switch to flip" (https://docs.vodlix.com/settings-configuration/api-keys-webhooks).
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 Vodlix service of 1,500 subscribers
Take a Vodlix 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.
Vodlix publishes plan prices on its own pricing page; compare the plan that includes the apps you need with the Flicknexs figure above.
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 Vodlix move.
| Task | Owner | Why that owner |
|---|---|---|
| Export from Vodlix | 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.
Vodlix next to the other platforms teams migrate from
Teams rarely compare only two platforms. The row for Vodlix 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 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 | 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 Vodlix 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 Vodlix 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 Vodlix 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 Vodlix exports, agrees the timeline in writing and names the signers for cut-over. Nothing is switched off on Vodlix 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 Vodlix 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.
Vodlix publishes plan pricing on its own pricing page, according to vodlix.com, checked 2026-09-03.
That depends on your contract with Vodlix. 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.
Cloud playout for 24/7 linear and FAST channels, an in-house development team for custom features, and multi-DRM through the DRM add-on, all on the same platform as your on-demand library.
Other migration guides
Ready to leave Vodlix?
Start free, import a sample of your library, and see the admin with your own content before you commit.