Migrate from Wowza to Flicknexs
Quick answer: To migrate from Wowza 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 Wowza 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 Wowza
Wowza gives you the pipes. Teams move when they want the whole service: catalog, subscriber accounts, billing, branded apps and DRM, without building and maintaining that layer on top of a streaming engine.
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 Wowza and what you keep.
| Asset | From Wowza | Into Flicknexs | You keep |
|---|---|---|---|
| Video library and metadata | Assets stored in Wowza Video or your own origin storage | Bulk import toolkit maps titles, descriptions, categories, artwork, captions and series structure | Every title, its artwork and its taxonomy |
| Subscribers and entitlements | Users from whatever front end you built on top of Wowza | 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 | Billing from your own front end or gateway | SVOD, TVOD, AVOD and hybrid tiers recreated; gateways connected; renewal dates preserved | Your prices, your renewal calendar, your gateway |
| Apps and store listings | Custom apps, if any, 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 applications, stream targets and transcoder settings | 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.
Decide first which Wowza you are actually leaving — Streaming Engine or Wowza Video
The two products produce completely different export jobs, and most of the migration plan follows from this one answer. On self-hosted Wowza Streaming Engine the media is already yours on your own disk: Wowza's docs state that "By default, Wowza Streaming Engine creates and uses streaming files—such as SDP, SMIL, and .stream files—in the [install-dir]/content directory" and that "By default, this location is also used for storing other types of content, such as VOD files and some types of recordings" (https://www.wowza.com/docs/configure-the-location-of-streaming-files). On hosted Wowza Video the files sit behind the Video details page, and Wowza documents a "Video Files List" there: "Review the stored original and encoded video files for the video with file size and URLs on the CDN and download any of the files" (https://www.wowza.com/docs/video-details-page-in-wowza-video). Accounts that run both need two parallel exports.
A Wowza Video REST API access token, and a check that your scripts are not on deprecated paths
The documented bulk-retrieval route is the Wowza Video REST API. Wowza's own OpenAPI reference lists a single server entry, https://api.video.wowza.com/api/v2.0, secured by a Wowza-generated bearer access token (JWT) (https://developer.wowza.com/docs/wowza-video/api/video/openapi). Before you start, check what your existing tooling calls: Wowza groups assets, players, recordings, vod_streams, storage and usage_vod_streams under a tag it labels "Deprecated in 2.0", and the recordings tag states "The recordings operations are deprecated in 2.0. Use the /videos endpoints instead" (same URL). Repoint any export script at /videos before the migration rather than during it.
Wowza Streaming Engine admin credentials if you are rebuilding application config, not just moving files
For self-hosted Engine there is a separate Wowza Streaming Engine REST API, documented with server http://localhost:8087 and paths under /v2/servers/{serverName}/..., secured by "HTTP Basic Authentication using Wowza Streaming Engine admin credentials" or HTTP Digest (https://developer.wowza.com/docs/wowza-engine/rest-api/openapi). GET /v2/servers/{serverName}/vhosts/{vhostName}/applications/{appName} is documented as "Retrieves the specified application configuration" — that is the documented way to read your application setup out so it can be rebuilt. Note that in that whole published spec the only path containing a file download is /v2/servers/{serverName}/logfiles/{logName}/download, for log files, so the media itself still comes off disk, not out of that API.
Untouched master files — do no trimming in Wowza once the migration starts
Wowza's docs carry an explicit warning on the Video details page: "Warning! If you select Clip video, Wowza Video trims the video based on the start point and end point and overwrites the source video. This action cannot be undone. If you need to access your source video, ensure you store a copy of it" (https://www.wowza.com/docs/video-details-page-in-wowza-video). Freeze editorial work in Wowza and pull the stored originals before anyone clips anything, because Flicknexs imports from original source files and a trimmed master is what you would be importing instead.
Your own DRM vendor account and license server URLs — Wowza does not hold them for you
The DRM relationship is with a third party. Wowza states "Currently, Wowza Streaming Engine supports the following key management systems" and lists BuyDRM KeyOS, the BuyDRM KeyOS MultiPack Wowza module ("Separate, paid module from BuyDRM"), EZDRM FairPlay Streaming, EZDRM Universal and Verimatrix VCAS (https://www.wowza.com/docs/about-digital-rights-management-and-wowza-streaming-engine). For hosted Wowza Video, Wowza documents EZDRM FairPlay Streaming and EZDRM Universal and states "you must have an EZDRM account, configured appropriately for the device types you want to stream to" and "For FairPlay, you'll need verification from Apple that you're approved to use Fairplay" (https://developer.wowza.com/docs/wowza-video/guides/stream-security/about-digital-rights-mgmt-in-wowza-video). Collect the values behind Wowza's published DRM config keys com.widevine.alpha, com.apple.fps.1_0 and com.microsoft.playready — each takes a "license_server" ("URL to the license server that can validate the license") and, for FairPlay, a "certificate" (https://developer.wowza.com/docs/wowza-video/api/video/openapi). Those URLs are yours, so they travel with you.
A subscriber and entitlement source that is not Wowza
Wowza's published Wowza Video REST API spec contains no subscriber, member, customer, end-user, entitlement or billing resource — its complete top-level path list is /analytics, /asset_tags, /assets, /categories, /clipping, /live_streams, /playback_tokens, /players, /real_time, /recordings, /schedules, /stream_sources, /stream_targets, /transcoders, /usage, /videos and /vod_streams (https://developer.wowza.com/docs/wowza-video/api/video/openapi). There is therefore no documented subscriber list to export. The "Server Users" group in the Engine API is not audience data either: GET /v2/servers/{serverName}/users "Retrieves the list of server users" and POST "Adds a new server user to the list" — these are server admin accounts (https://developer.wowza.com/docs/wowza-engine/rest-api/openapi). Assemble your member list from wherever billing and login actually live today (your payment gateway, membership site or CRM) so Flicknexs subscriber import with plan mapping has a real source file.
An inventory of every place a Wowza playback token or embed is pasted
Access control in Wowza Video is token-based rather than account-based. Wowza documents playback_token_behavior options NO_TOKEN, BASIC_TOKEN, ADVANCED_TOKEN and FOLLOW_DEFAULT, where BASIC_TOKEN means "the embed URL, which has the token as part of the URL, will only be playable for 48 hours" and ADVANCED_TOKEN means "You add the stream's JS embed code (Share Stream) and a token to your site to provide tokenization" (https://developer.wowza.com/docs/wowza-video/api/video/openapi). Every page, LMS, app screen or email carrying one of those embeds is a cutover task, so list them before you start.
Your contract anniversary, cancellation route, and staging storage sized for originals plus renditions
According to the FAQ on Wowza's Flowplayer OVP pricing page, the hosted platform is not month-to-month: "You always sign for a one year contract. You can choose between monthly or annual upfront payment. If you choose annual, you can use your committed volumes over the whole 12 month period, and thus handle any seasonality better" (https://www.wowza.com/pricing/video). Wowza's Billing and Renewals page states subscriptions "will automatically renew for consecutive subscription periods ("Renewal Periods"), unless you provide Wowza with at least thirty (30) days' prior written notice of termination", with requests submitted on the "My Support page" in "My Account" or at https://support.wowza.com/cancel-request (https://www.wowza.com/legal/billing-and-renewals). Size staging storage from the numbers Wowza already gives you: each entry in a video's encodings array carries size_in_bytes (https://developer.wowza.com/docs/wowza-video/api/video/openapi/videos).
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
Step 1 — Enumerate the catalog: page GET /videos, or walk [install-dir]/content
On Wowza Video, build the title list from the API. Wowza's published spec documents a 'page' parameter and a 'per_page' parameter whose description reads "For use with the page parameter. Indicates how many records should be included in a page of results. A valid value is any positive integer. The default and maximum value is 1000", plus filters created_at, updated_at, published_at, state, query, sort_column, sort_direction, origin_id and categories, which takes up to four category IDs comma-separated (https://developer.wowza.com/docs/wowza-video/api/video/openapi/videos). Page through it in 1000-record pages and keep the raw JSON — that is your reconciliation baseline later. On self-hosted Streaming Engine there is no list call to make: the catalog is the contents of [install-dir]/content on your own disk (https://www.wowza.com/docs/configure-the-location-of-streaming-files), so take a file manifest with sizes and checksums instead. Also pull taxonomy now, while the account is live: Wowza documents GET /categories and GET /categories/{id}, with categories carrying id, name, description and parent_id, and an 'only_top_level' boolean described as "Only categories without parent categories will be returned if set to true" (https://developer.wowza.com/docs/wowza-video/api/video/openapi/categories).
- 2
Step 2 — Resolve real download URLs with one GET /videos/{id} per title
The list call will not give you files. In Wowza's published schema the list response (VideoListModel) carries only id, name, description, duration_in_ms, unpublish, unpublished_at, published, published_at, tags, category_id, no_ads, ad_keywords, created_at, updated_at, state and playback_token_behavior — no encodings. The per-video fetch (VideoResponseModel) adds 'encodings', documented as "Array containing all available video files and their metadata", whose entries carry video_file_url ("URL to the video file. We accept HTTP and HTTPS addresses"), width, height, video_codec, video_container, total_bitrate_in_kbps, created_at and size_in_bytes (https://developer.wowza.com/docs/wowza-video/api/video/openapi/videos). Practically: page GET /videos, then issue one GET /videos/{id} per title to collect download URLs. Capture the full metadata set while you are there — Wowza's video object carries exactly 32 fields (id, name, description, duration_in_ms, unpublish, unpublished_at, published, published_at, tags, category_id, ad_insertion_points, no_ads, ad_keywords, created_at, updated_at, state, encoding_progress, upload_progress, error_message, deactivated, images, encodings, drm, shallow_copy, shallow_copy_source_id, multiple_audio_tracks, audio_only, version, thumbnails, animated_previews, playback_token_behavior and origin) and that is the whole of what an export can carry out (same URL). Prefer the stored original over a rendition wherever both exist, since the Flicknexs bulk import toolkit re-encodes from original source files.
- 3
Step 3 — Hand-collect what has no bulk route: recordings, subtitles, previews and 2.0 assets
Budget operator time here, because parts of this are click-work by design. Live recordings come down one at a time: Wowza lists the per-row actions on the Recordings page as "Download – Download the MP4 file. Delete – Delete the MP4 file in Wowza Video", and documents multi-select only for deletion — "To delete multiple recordings, select them by using the box in the left column of the table and then click Delete Recordings in the Actions column of one of the selected recordings" — with no bulk-download control on that page (https://www.wowza.com/docs/record-live-streams-and-transcoders). Subtitles and preview assets come off the Video details page, where Wowza documents a "Text Files List – Review text files, including subtitle files. the label language, URL, and whether the video is published or not" and an "Animated preview files list – Review generated animated preview files available for the video with their URLs and the ability to download the files. Both WebP and MP4 formats are listed in multiple resolutions" (https://www.wowza.com/docs/video-details-page-in-wowza-video). For older assets, Wowza's support article "How to Download and Delete my Wowza Video 2.0 Assets" documents a manual, per-file, browser-based retrieval: "1. Select Manage Files 2. Choose "File" or "URL" 3. When the asset opens in the browser, right-click, select "Save Video As"", with no bulk mechanism and no API route given (https://support.wowza.com/hc/how-to-access-and-delete-my-wowza-video-assets). Ship the collected files and the metadata JSON from Step 2 to the Flicknexs onboarding team as one batch per tranche.
- 4
Step 4 — Rebuild the live and linear side from stream targets, playback URLs and schedules
Inventory delivery before you touch encoders. Wowza documents two stream target families, Wowza CDN and custom, and states "Custom stream targets connect to external CDNs to deliver streams to viewers. You manually create custom stream targets and associate them to a transcoder", with POST and GET on /stream_targets/custom and GET, PATCH and DELETE on /stream_targets/custom/{id} (https://developer.wowza.com/docs/wowza-video/api/video/openapi/stream_targets). Read out the existing endpoints too: Wowza documents 'direct_playback_urls' on a live stream as "A list of direct playback URLs for the live stream's delivery protocols. Each protocol has a URL for the source and a URL for each output rendition", with per-entry name, output_id, url and (WebRTC only) application_name (https://developer.wowza.com/docs/wowza-video/api/video/openapi/live_streams). Then re-express your schedule: Wowza's scheduling is transcoder/live-stream based — POST and GET /schedules, GET/PATCH/DELETE /schedules/{id}, PUT /schedules/{id}/enable and /disable, GET /schedules/{id}/state, with recurrence_type described as "A schedule can run one time only (once) or repeat (recur) until a specified end_repeat date. The default is once" and day-level recurrence_data — and no VOD-playlist or linear-playout schedule object anywhere in that spec's path list (https://developer.wowza.com/docs/wowza-video/api/video/openapi/schedules). If you run a 24x7 channel, note that Wowza states "24x7 streams cannot be recorded" (https://www.wowza.com/docs/record-live-streams-and-transcoders) and that "24x7 streaming isn't available in a trial account" with "To enable 24x7 streaming for your account, contact 720.279.8163 or schedule a call" (https://www.wowza.com/docs/stream-a-247-channel-with-wowza-video) — so the channel is rebuilt in Flicknexs cloud playout from your masters, not from any Wowza-side archive.
- 5
Step 5 — Stand up audience, apps and monetisation in Flicknexs, run in parallel, then serve notice
Because Wowza's API exposes no subscriber resource (https://developer.wowza.com/docs/wowza-video/api/video/openapi), the audience side is a fresh build rather than a transfer: Flicknexs subscriber import takes your billing/CRM export with plan mapping and issues secure-link logins, and you connect your own payment gateway for SVOD, TVOD, AVOD or a hybrid mix. Device reach is the other rebuild. Wowza ships player SDKs you embed — the Wowza Flowplayer Apple SDK "provides an easy-to-use API that enables developers to create iOS and tVOS applications that use the Wowza Flowplayer to play audio and video locally and over the internet", listing iOS 14.0+, iPadOS 14.0+, tvOS 14.0+, Swift 5.7, macOS 13.0+ and Xcode 15 and later (https://developer.wowza.com/docs/wowza-flowplayer/apple-sdk/about-the-apple-sdk), and the React Native SDK "allows you to seamlessly integrate the Wowza Flowplayer into your native Android and iOS applications", supporting "Android 4.4+ (API level 19+)" and "iOS 14.0+ and iPadOS 14.0+", with "There's no current support for TV platforms, such as tvOS and Android TV" (https://developer.wowza.com/docs/wowza-flowplayer/react-native-sdk/about-the-react-native-sdk). On Wowza's Flowplayer OVP pricing page the platform list published for the Player Only Plan is "Web/HTML5, iOS SDK, Android SDK" (https://www.wowza.com/pricing/video), so Roku, Fire TV, Android TV, Samsung and LG are new store submissions on the Flicknexs side, which is the long pole — start them in parallel with the file pull, not after it. Keep both platforms live until your checks pass, then cancel: at least thirty days' prior written notice, submitted via My Account or https://support.wowza.com/cancel-request (https://www.wowza.com/legal/billing-and-renewals).
A Wowza migration, week by week
Two weeks is the common case for a Wowza 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 — scope and freeze | Onboarding team runs a discovery session to establish which Wowza product is in play (Streaming Engine on your own disk vs hosted Wowza Video), sizes the catalog from your GET /videos paging output or your [install-dir]/content manifest, and maps your categories, plan structure and device wish-list onto the Flicknexs build. | Freeze clipping in Wowza — Wowza warns that Clip video "overwrites the source video. This action cannot be undone" (https://www.wowza.com/docs/video-details-page-in-wowza-video). Issue a Wowza Video API bearer token for https://api.video.wowza.com/api/v2.0, or Engine admin credentials for http://localhost:8087, and find your contract anniversary — Wowza's Flowplayer OVP pricing FAQ states "You always sign for a one year contract" (https://www.wowza.com/pricing/video) and Billing and Renewals requires "at least thirty (30) days' prior written notice of termination" (https://www.wowza.com/legal/billing-and-renewals). Do not cancel anything yet. |
| Weeks 2-3 — the export (the long pole on hosted Wowza) | Provides the staging target for the bulk import toolkit, ingests each tranche of original files plus the metadata JSON as it lands, and flags any file whose transferred size does not match the size_in_bytes Wowza reported, so re-pulls happen while the account is still live. | Page GET /videos, then issue one GET /videos/{id} per title to collect encodings[].video_file_url — Wowza's list response carries no encodings, only the per-video fetch does (https://developer.wowza.com/docs/wowza-video/api/video/openapi/videos). Assign someone to the click-work: recordings download one at a time ("Download – Download the MP4 file"), with multi-select documented only for deletion (https://www.wowza.com/docs/record-live-streams-and-transcoders), and 2.0 assets come via "Manage Files" and right-click "Save Video As" (https://support.wowza.com/hc/how-to-access-and-delete-my-wowza-video-assets). Self-hosted Engine customers instead rsync [install-dir]/content, which is usually days faster. |
| Weeks 3-5 — rebuild what has no export (runs in parallel) | Rebuilds the catalog structure, monetisation and channel: categories re-created with their parent_id nesting, SVOD/TVOD/AVOD/hybrid plans configured against your own payment gateway, cloud playout stood up for any linear channel, and white-label app builds started for Android, iOS, Android TV, Fire TV, Roku, Samsung and LG. | Export your member list from wherever billing actually lives, because Wowza's published API has no subscriber or entitlement resource (https://developer.wowza.com/docs/wowza-video/api/video/openapi). Read out your delivery setup for reference — custom stream targets (https://developer.wowza.com/docs/wowza-video/api/video/openapi/stream_targets), 'direct_playback_urls' per protocol and rendition (https://developer.wowza.com/docs/wowza-video/api/video/openapi/live_streams) and your /schedules recurrence (https://developer.wowza.com/docs/wowza-video/api/video/openapi/schedules) — and supply store accounts, artwork and DRM vendor details. Store review timing is outside anyone's control, so start app submissions here, not later. |
| Weeks 5-6 — parallel run and verification | Runs the post-migration checklist with you: count and byte reconciliation, category nesting, subtitle labels, multiple-audio and audio-only titles, artwork and animated previews, DRM playback on FairPlay and Widevine/PlayReady against your own license servers, a live ingest rehearsal, and subscriber import with a real test payment. | Keep Wowza running. Sweep every site, app build, LMS and email for old Wowza embeds — anything on BASIC_TOKEN is playable only 48 hours and anything on ADVANCED_TOKEN dies with the account (https://developer.wowza.com/docs/wowza-video/api/video/openapi). Watch the linear channel for a full day in Flicknexs, since Wowza states "24x7 streams cannot be recorded" (https://www.wowza.com/docs/record-live-streams-and-transcoders) and the archive is new. Snapshot any Wowza analytics you want to keep: Wowza states it "will endeavor to retain detailed usage data... for a period of 30 days following its creation" (https://www.wowza.com/legal/streaming-cloud-terms-of-use). |
| Week 6+ — cutover, then notice (never the other way round) | Switches DNS and playback to Flicknexs, keeps the old catalog mapping in place for redirects, and monitors the first live event and the first renewal cycle on your gateway. | Only once every check has passed, submit cancellation — Wowza requires "at least thirty (30) days' prior written notice", via the "My Support page" in "My Account" or https://support.wowza.com/cancel-request (https://www.wowza.com/legal/billing-and-renewals). Do not let this slip past the anniversary. Engine customers should also shut down parallel instances, since Wowza documents that "Your monthly invoice will adjust based on the number of concurrently active server instances" and that "Wowza's licensing system tracks peak usage for each day in your billing cycle" (https://support.wowza.com/hc/en-us/articles/5515942463643-subscription-license-billing). Keep your own archive of the exported files: Wowza's terms state it "may permanently and irretrievably delete all Content" on termination, and that recordings are deleted 90 days after an account is suspended or terminated (https://www.wowza.com/legal/streaming-cloud-terms-of-use, https://www.wowza.com/docs/record-live-streams-and-transcoders). |
Source: Flicknexs onboarding schedule for catalog migrations, 2026-09-03. Durations are typical, not guaranteed.
Wowza-specific things to check first
- Document every Wowza application and stream target; Flicknexs recreates live channels and linear outputs, and each needs its ingest and output mapped.
- If you run Wowza Streaming Engine on your own servers, plan the decommission date so hosting costs stop after the parallel run.
- Your subscriber and billing layer lives outside Wowza; export it from that system, not from Wowza.
- Latency requirements should be stated up front so the Flicknexs live configuration matches what your audience expects.
The five ways a migration goes wrong, and how each is prevented
Clipping in Wowza during the migration destroys the master you were about to export
This one is irreversible and easy to trigger by habit. Wowza's docs warn: "Warning! If you select Clip video, Wowza Video trims the video based on the start point and end point and overwrites the source video. This action cannot be undone. If you need to access your source video, ensure you store a copy of it" (https://www.wowza.com/docs/video-details-page-in-wowza-video). Mitigation: freeze editing in Wowza for the duration, pull originals first, and do any trimming after import on the Flicknexs side.
Long broadcasts and 24x7 channels have no complete Wowza-side archive to carry across
Recording length is capped. Wowza documents that "Recordings created from the live stream or transcoder workflow capture up to eight hours of content. If a live stream or transcoder runs for longer than eight hours, the most recent eight hours are recorded", and that "To record more than eight hours of a single broadcast, stop the live stream or transcoder and start it again to create multiple recordings"; Real-Time Streaming at Scale recordings "capture up to twelve hours of content in a single MP4 file"; and "24x7 streams cannot be recorded" (https://www.wowza.com/docs/record-live-streams-and-transcoders). So a long event may exist only as split MP4s that need reassembling in order, and a linear channel has nothing to migrate at all — it is rebuilt from your masters in Flicknexs cloud playout.
Cancelling before the files are out puts your content inside Wowza's deletion rights
Wowza's Streaming Cloud Terms of Use disclaim ownership of your media — "We don't claim ownership of any audiovisual content that is uploaded or transmitted to, or stored, distributed, processed, or displayed by the Service" — but also reserve deletion: "Upon suspension or termination of Your account with Wowza or of your access to the Service, Wowza may permanently and irretrievably delete all Content associated with You or Your account(s) with Wowza", and Wowza "may, in its sole discretion, for any or no reason, and without penalty suspend or terminate any account (or any part thereof) You may have with Wowza" (https://www.wowza.com/legal/streaming-cloud-terms-of-use). One concrete window is published for recordings: "Wowza Video deletes recordings 90 days after the account is suspended or terminated", while "Wowza Video saves recordings in active accounts until you delete them" (https://www.wowza.com/docs/record-live-streams-and-transcoders). Wowza also cautions against relying on later retrieval: "Wowza does not intend for its data collection and retention efforts in connection with Your use of the Services to be exhaustive or redundantly-managed and there is a chance Wowza will fail to collect or be unable to retrieve Your data even upon request", and states it "will endeavor to retain detailed usage data, with the most granular information about events and viewers, for a period of 30 days following its creation" (https://www.wowza.com/legal/streaming-cloud-terms-of-use). Export first, verify, then cancel — and snapshot any analytics you care about, since only a 30-day granular window is described.
A slow migration can outlive the API version your export script was written against
Wowza publishes a fixed API lifecycle: its lifecycle page states "4 versions of our REST API are available at any time" and "Every 6 months, we test and finalize the Beta version and then move all existing API versions along to the next lifecycle stage", defining Deprecated as "A deprecated version isn't guaranteed to work in production environments. Also, all relevant documentation is no longer accessible" and Discontinued as "A discontinued version is no longer accessible" (https://developer.wowza.com/docs/wowza-video/about-the-rest-api/lifecycle/api-lifecycle). A migration stretched across quarters, or resumed months after a first attempt, can hit a rotation — and the docs you were working from disappear with it. Run the export as a short, contiguous project, and check the deprecated tag group (assets, players, recordings, vod_streams, storage, usage_vod_streams) before you rely on any older path (https://developer.wowza.com/docs/wowza-video/api/video/openapi).
Two cutover surprises: exposed default-token files, and a one-year contract that keeps billing
Wowza documents the default playback setting as unprotected — "NO_TOKEN - Video files are accessible and can be downloaded and played by anyone at any time. This is the default" (https://developer.wowza.com/docs/wowza-video/api/video/openapi) — so an account left on the default has directly fetchable files that stay fetchable until you actually close it. In the other direction, anything on BASIC_TOKEN ("the embed URL, which has the token as part of the URL, will only be playable for 48 hours") or ADVANCED_TOKEN breaks the moment the account ends, so every embed must be swapped, not just redirected. On money: according to the FAQ on Wowza's Flowplayer OVP pricing page, "You always sign for a one year contract" (https://www.wowza.com/pricing/video), and Wowza's Billing and Renewals page requires "at least thirty (30) days' prior written notice of termination", with "All cancellation and refund requests need to be submitted at least thirty (30) days prior to the end of the subscription period or then-current Renewal Period" (https://www.wowza.com/legal/billing-and-renewals). Miss that date and you carry both platforms for another term. Self-hosted Engine customers have the same arithmetic in a different shape: Wowza documents that for monthly subscriptions "Your monthly invoice will adjust based on the number of concurrently active server instances" and "Wowza's licensing system tracks peak usage for each day in your billing cycle" (https://support.wowza.com/hc/en-us/articles/5515942463643-subscription-license-billing), so instances left running during a parallel run keep billing.
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 against the source of truth you captured in Step 1: the number of titles live in Flicknexs should match the total returned by paging GET /videos, whose 'per_page' Wowza documents with "The default and maximum value is 1000" (https://developer.wowza.com/docs/wowza-video/api/video/openapi/videos) — or, for self-hosted Engine, your file manifest of [install-dir]/content (https://www.wowza.com/docs/configure-the-location-of-streaming-files).
- Byte-check every pulled file against the size_in_bytes value Wowza returns on each encodings entry, and confirm the imported title's runtime matches duration_in_ms from the video object (https://developer.wowza.com/docs/wowza-video/api/video/openapi/videos). A truncated CDN download is the most common silent failure in a per-file pull.
- Confirm you imported the stored original, not a rendition, wherever Wowza's Video Files List offered both — Wowza describes that list as "Review the stored original and encoded video files for the video with file size and URLs on the CDN and download any of the files" (https://www.wowza.com/docs/video-details-page-in-wowza-video). Spot-check the highest-resolution titles by opening the Flicknexs source file and comparing resolution against the original's width/height.
- Rebuild and verify the category tree, including nesting: Wowza's categories carry parent_id and GET /categories takes 'only_top_level' — "Only categories without parent categories will be returned if set to true" (https://developer.wowza.com/docs/wowza-video/api/video/openapi/categories). Walk each parent and confirm its children landed under the same parent in Flicknexs, not flattened.
- Play a subtitled title on web and on one TV app and confirm the track appears with the right label and language — Wowza's Text Files List shows "the label language, URL, and whether the video is published or not" (https://www.wowza.com/docs/video-details-page-in-wowza-video), so also check that anything unpublished in Wowza did not arrive published.
- Check titles Wowza flagged as multiple_audio_tracks or audio_only (fields on the video object, https://developer.wowza.com/docs/wowza-video/api/video/openapi/videos) — confirm every audio track is selectable, and that audio-only entries render correctly rather than as a black video.
- Verify poster and preview assets survived: Wowza's video object carries images, thumbnails and animated_previews (https://developer.wowza.com/docs/wowza-video/api/video/openapi/videos), and its animated preview list is documented as "Both WebP and MP4 formats are listed in multiple resolutions" (https://www.wowza.com/docs/video-details-page-in-wowza-video). Browse the Flicknexs catalog for missing artwork before launch, not after.
- If you run ads, confirm ad behaviour transferred deliberately: Wowza's video object carries ad_insertion_points, no_ads and ad_keywords (https://developer.wowza.com/docs/wowza-video/api/video/openapi/videos). Check that every title marked no_ads in Wowza is still ad-free in Flicknexs AVOD, and that mid-roll points land at the intended timecodes.
- Reassemble and play back any broadcast that exceeded Wowza's recording cap — Wowza states recordings "capture up to eight hours of content" with "the most recent eight hours" retained, and recommends stopping and restarting to "create multiple recordings" (https://www.wowza.com/docs/record-live-streams-and-transcoders). Confirm the parts are in the right order and that no eight-hour boundary lost material.
- Test DRM playback end to end against your own vendor, since the account is yours: play a protected title on Apple (FairPlay) and on a Widevine or PlayReady device, pointing at the license_server URL and FairPlay certificate you carried over from Wowza's DRM config keys com.widevine.alpha, com.apple.fps.1_0 and com.microsoft.playready (https://developer.wowza.com/docs/wowza-video/api/video/openapi). Wowza's Video docs require "you must have an EZDRM account, configured appropriately for the device types you want to stream to" (https://developer.wowza.com/docs/wowza-video/guides/stream-security/about-digital-rights-mgmt-in-wowza-video), so confirm that account is now authorising Flicknexs playback.
- Sweep every embed for dead Wowza playback tokens: anything on BASIC_TOKEN ("the embed URL, which has the token as part of the URL, will only be playable for 48 hours") or ADVANCED_TOKEN must be replaced, not redirected (https://developer.wowza.com/docs/wowza-video/api/video/openapi). Crawl your own site, LMS and app builds for the old embed strings and confirm zero hits before you cancel.
- Run a live rehearsal on the new ingest before cutover, then compare against the endpoint list you read from Wowza's 'direct_playback_urls' — documented as "A list of direct playback URLs for the live stream's delivery protocols. Each protocol has a URL for the source and a URL for each output rendition" (https://developer.wowza.com/docs/wowza-video/api/video/openapi/live_streams) — so every protocol and rendition your viewers use today has a working replacement.
- Re-create and fire your recurring schedule at least one cycle early: Wowza's schedules carry recurrence_type, where "A schedule can run one time only (once) or repeat (recur) until a specified end_repeat date. The default is once", plus day-level recurrence_data (https://developer.wowza.com/docs/wowza-video/api/video/openapi/schedules). Confirm the equivalent Flicknexs schedule starts and stops on the right days and timezone.
- If you run a linear channel, watch it for a full day in Flicknexs and confirm it now produces an archive — Wowza states plainly that "24x7 streams cannot be recorded" (https://www.wowza.com/docs/record-live-streams-and-transcoders), so this is new capability to verify rather than a like-for-like check.
- Test subscriber import against reality, not the spreadsheet: pick a sample across each plan, confirm the mapped plan and renewal date, complete a secure-link login, and take one live payment through your connected gateway. Nothing about this can be validated against Wowza, because its published API has no subscriber, entitlement or billing resource (https://developer.wowza.com/docs/wowza-video/api/video/openapi).
- Install and sign in on each device target you did not have before: Wowza's Flowplayer OVP pricing page publishes "Web/HTML5, iOS SDK, Android SDK" for the Player Only Plan (https://www.wowza.com/pricing/video), and Wowza states of the React Native SDK that "There's no current support for TV platforms, such as tvOS and Android TV" (https://developer.wowza.com/docs/wowza-flowplayer/react-native-sdk/about-the-react-native-sdk) — so Roku, Fire TV, Android TV, Samsung and LG builds need first-run testing on real hardware, including purchase and playback.
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 Wowza service of 1,500 subscribers
Take a Wowza 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.
Wowza publishes platform and engine pricing on its pricing page; the subscriber, billing and app layer is built and paid for separately by you, so add those costs when you compare.
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 Wowza move.
| Task | Owner | Why that owner |
|---|---|---|
| Export from Wowza | 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.
Wowza next to the other platforms teams migrate from
Teams rarely compare only two platforms. The row for Wowza 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 | 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 Wowza 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 Wowza 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 Wowza 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 Wowza exports, agrees the timeline in writing and names the signers for cut-over. Nothing is switched off on Wowza 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 Wowza 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.
Wowza publishes pricing for its video platform and its Streaming Engine software on its pricing page, according to wowza.com, checked 2026-09-03.
That depends on your contract with Wowza. 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.
Flicknexs is a full OTT platform that includes the delivery layer. You get ingest, transcoding, CDN delivery and playback plus the catalog, subscriber accounts, billing and apps that Wowza leaves to you.
Other migration guides
Ready to leave Wowza?
Start free, import a sample of your library, and see the admin with your own content before you commit.