Migrate from Wistia to Flicknexs
Quick answer: To migrate from Wistia 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 Wistia 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 Wistia
Wistia is a marketing video tool: hosting, embeds, webinars and lead capture for a company website. Teams move when the video itself becomes the product and they need subscriber accounts, recurring billing, a structured catalog and apps on phones and televisions, which is not what Wistia is built to sell.
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 Wistia and what you keep.
| Asset | From Wistia | Into Flicknexs | You keep |
|---|---|---|---|
| Video library and metadata | Original files, titles, descriptions, thumbnails and captions downloaded from Wistia projects | Bulk import toolkit maps titles, descriptions, categories, artwork, captions and series structure | Every title, its artwork and its taxonomy |
| Subscribers and entitlements | Usually none; Wistia holds viewers and leads, not subscriber accounts | 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 | None on Wistia; subscription and rental tiers are built new on Flicknexs | SVOD, TVOD, AVOD and hybrid tiers recreated; gateways connected; renewal dates preserved | Your prices, your renewal calendar, your gateway |
| Apps and store listings | None; Wistia is embed and channel led | 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 | Webinar recordings, exported as files | 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.
An Account Owner (and the Manager seats that can actually download)
Wistia's media management article states that by default "Account Owners and Managers are the only users with access to download media", though permissions can also be granted at folder level (https://support.wistia.com/en/articles/8264610-media-management). A separate Wistia article states "Only Account Owners can cancel a Wistia account" (https://support.wistia.com/en/articles/9397312-cancel-account). Name both people before day one: the person who pulls the media and the person who ends the subscription are not necessarily the same seat, and a migration stalls when the only Owner is on leave.
A Data API token, and a request budget that respects the published rate limit
According to Wistia's API request documentation, "The API has a rate limit of 600 requests per minute. If there are more than 600 requests in a minute for a particular account, the service will respond with HTTP error 429 Service Unavailable" (https://docs.wistia.com/docs/making-api-requests). The same page documents paging via a page parameter and a per_page parameter with a maximum of 100 results per request, plus sort_by accepting name, created or updated. Plan the inventory crawl around 100-item pages with backoff on 429 rather than a naive loop.
Bandwidth headroom for the export itself
Wistia's account usage and bandwidth article lists "A media being downloaded" and "A media being loaded and played by your own internal views" among the activities that consume account bandwidth (https://support.wistia.com/en/articles/8264552-account-usage-and-bandwidth). A bulk migration pull therefore draws on the same monthly allowance your viewers do. Check where you sit in the current billing period before starting, and schedule the heavy pull so it does not collide with a campaign launch.
A folder layout that fits Wistia's two export ceilings
Wistia's media management article documents an "Export All Media" option on any folder that exports the original media files in that folder as a ZIP with, in Wistia's words, "a 4GB size limit", and for bulk download from the Video Library via the bulk actions toolbar states "This exporting method has a limit of 1,000 files", advising that above that you "recommend exporting at the folder level" (https://support.wistia.com/en/articles/8264610-media-management). If you plan to use the UI rather than the API, reorganise into folders that stay under 4GB each before you export anything.
A storage inventory that includes archived media and non-video files
Wistia's storage-limits article states that what counts toward storage is "Any file that you upload to your account, including video, audio, document, and image files", and that "If you choose to archive any media within your account, these still count towards your storage total" (https://support.wistia.com/en/articles/13944217-understanding-storage-limits). Your Wistia account is very likely holding assets that are not on-catalog video. Decide up front which of those move to Flicknexs, which go to plain object storage, and which are simply retired — before the account is closed.
A caption and transcript pull plan, per language
Wistia's media management article documents transcript download in three formats: "SRT (SubRip subtitle), VTT (Video Text Tracks), TXT (Plain text)" (https://support.wistia.com/en/articles/8264610-media-management). Wistia also documents a List Captions endpoint whose media_id parameter is optional, so captions can be listed across the account; each caption object carries language (ISO-639-2), english_name, native_name, is_draft, id and text, where text is "The text of the captions for the specified language in SRT format" (https://docs.wistia.com/reference/get_captions). Decide in advance whether is_draft captions travel or stay.
Exports of the lead and audience data that lives beside the video
Wistia's analytics export article states that analytics exports are delivered as CSV files and that the Audience export lets you export "either identified leads or your entire audience", and documents that the Media Conversion export contains "First and last name, email, date submitted, and more" for form submissions (https://support.wistia.com/en/articles/8218982-exporting-analytics). Wistia's Channel Subscribers article states the Subscribers page shows "Name (if enabled), Email, and Subscribe date" and that "You will also find the option to export the subscriber list to a CSV" (https://support.wistia.com/en/articles/8229027-channel-subscribers-and-notifications). Pull these before anything is cancelled — they are the part of a Wistia account that has no equivalent in your video files.
A renewal calendar built from Wistia's notice window, not your instinct
Wistia's Terms state that at the end of the initial term "the Agreement will be extended automatically for additional terms equivalent to your billing cycle (i.e. 1-month terms or 1-year terms, as applicable)", and that "Either party may elect not to have this Agreement extend automatically by giving notice of such election to the other party at least 2 months prior to the end of the then current initial or renewal term" (https://wistia.com/terms). The same Terms state "Wistia will not provide refunds or credits in the case of cancellations, downgrades, or when there are unused portions of the Services on an open account." On an annual plan, the migration schedule is driven by that two-month notice date.
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
Build a manifest from the Data API before you download a single file
Wistia's Media List response includes an assets array in which each asset carries url ("A direct-access URL to the content of the asset"), type, width, height, file_size and content_type (https://docs.wistia.com/reference/get_medias). Page the media list at the documented maximum of 100 per request with sort_by set to updated, and write out one row per media: hashed_id, name, folder, content_type, file_size, and the asset list. This manifest is the thing you reconcile against at the end — not the Wistia dashboard, which you will lose access to. Keep the crawl inside the documented 600-requests-per-minute limit and handle 429 as a signal to back off, per https://docs.wistia.com/docs/making-api-requests.
- 2
Pull the OriginalFile masters, not the player renditions
Wistia's Asset URLs documentation states "The OriginalFile asset is the source media that was uploaded to Wistia", that it is returned with a direct URL in the assets array from the Data API's medias:show method, and that it "is never used for video streaming/playback in the Wistia player" (https://docs.wistia.com/docs/asset-urls). Take those masters — Flicknexs imports from original source files and re-encodes on its own ladder, so pulling anything Wistia shaped for its player would mean transcoding a transcode. If you are working through the UI instead, use "Export All Media" per folder and keep each folder under the 4GB ZIP limit, or the Video Library bulk toolbar within its 1,000-file limit (https://support.wistia.com/en/articles/8264610-media-management).
- 3
Harvest captions account-wide and reconcile language codes
Rather than clicking through media one at a time, use the List Captions endpoint with media_id omitted, which Wistia documents as optional so captions can be listed across the account; each object carries language as ISO-639-2 plus english_name, native_name, is_draft, id and text in SRT format (https://docs.wistia.com/reference/get_captions). Two decisions belong to you here: whether is_draft captions ship as live subtitle tracks on Flicknexs, and how ISO-639-2 codes map onto the language labels your viewers will see in the Flicknexs player and apps. Wistia also offers per-media transcript download as SRT, VTT or TXT if you prefer files over API output (https://support.wistia.com/en/articles/8264610-media-management).
- 4
Rebuild channel structure and carry the audience across with its consent state
Wistia's List Channels endpoint returns id, hashed_id, name, description, media_count, created and updated, plus optional auto_publish_enabled, podcast_enabled, custom_url, podcast_settings and live_stream_event_count (https://docs.wistia.com/reference/get_channels). Use name, description and media_count to lay out the matching Flicknexs categories and collections; where a channel carries a custom_url or podcast_settings, that is a separate destination decision, not a video import. In parallel, export the subscriber CSV — Wistia's Channel Subscribers article states "If you export your list of subscribers, those who are unsubscribed will be included, but marked as unsubscribed" (https://support.wistia.com/en/articles/8229027-channel-subscribers-and-notifications), so the suppression flag must be carried into the Flicknexs subscriber import and honoured, not dropped on the way in. Wistia's channel response does not publish the per-channel media ordering, so if running order matters, capture it by hand before you leave.
- 5
Cut over embeds first, close the Wistia account second
Every Wistia embed on your site references a hashed_id, so the swap to Flicknexs playback is a page-by-page sweep of your CMS, landing pages and email templates — do it while both platforms are live. Only then cancel. Wistia's cancel-account article states "Once you cancel your Wistia account, you'll no longer be able to access your media" and "We recommend downloading the media in your account before cancelling to make sure you don't lose anything important" (https://support.wistia.com/en/articles/9397312-cancel-account). Wistia's billing overview documents two cancellation timings: selecting "Cancel Now" to stop billing immediately, or "Cancel at the end of the billing cycle", which "will keep your subscription active until the cycle ends, and billing will continue through that period" (https://support.wistia.com/en/articles/8265066-wistia-billing-overview). Given that Wistia's Terms state no refunds or credits for unused portions, the end-of-cycle option is usually the one that matches what you have already paid for.
A Wistia migration, week by week
Two weeks is the common case for a Wistia 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 |
|---|---|---|
| Weeks before anything technical — contract clock | Onboarding team scopes the catalog with you from a Data API sample, confirms which Flicknexs monetisation model and which app platforms are in scope, and sets the target cutover date backwards from your Wistia notice date. | Find your renewal date and count back the two months Wistia's Terms require for notice of non-renewal (https://wistia.com/terms). Confirm who your Account Owner is, since Wistia states only Account Owners can cancel (https://support.wistia.com/en/articles/9397312-cancel-account), and confirm which seats can download media at all. |
| Inventory week | Receives your manifest, sizes the import, maps folders and channels to Flicknexs categories, and flags anything that is not on-catalog video for a separate decision. | Run the Data API crawl (100 per page, inside the documented 600 requests per minute, per https://docs.wistia.com/docs/making-api-requests) to produce the full manifest of hashed_id, file_size and content_type. Export captions account-wide, and pull the Audience, Media Conversion and channel subscriber CSVs while the account is fully active. |
| Export and import week | Runs the bulk import from your original masters, builds the encode ladder, applies metadata, categories and subtitle tracks, and reports back any file that failed integrity checks so you can re-pull it while Wistia access still exists. | Pull the OriginalFile masters, keeping folder ZIPs under Wistia's stated 4GB limit and bulk downloads under its stated 1,000-file limit (https://support.wistia.com/en/articles/8264610-media-management). Watch your bandwidth position, since Wistia counts a media being downloaded against account bandwidth (https://support.wistia.com/en/articles/8264552-account-usage-and-bandwidth). |
| Parallel-running week — both platforms live | Stands up your Flicknexs site and white-label apps for review, wires your payment gateway, loads subscribers with plan mapping and secure-link login, and walks the post-migration checks with you. | Work the testing list: manifest reconciliation, caption parity, channel counts, suppression of unsubscribed contacts, a real test transaction. Sweep your site and email templates for Wistia hashed_id embeds and replace them. Do not cancel anything yet. |
| Cutover and close-out | Switches live traffic to Flicknexs playback, monitors the first days of real viewing and billing, and keeps your migration manifest on file as the reconciliation record. | Only once the checks pass, cancel in Wistia — noting Wistia's documented choice between "Cancel Now" and "Cancel at the end of the billing cycle" (https://support.wistia.com/en/articles/8265066-wistia-billing-overview), and that Wistia states you lose access to your media on cancellation. Keep your own copies of the masters and CSV exports: Wistia states media in cancelled accounts "generally remain untouched" but that it can't guarantee indefinite storage (https://support.wistia.com/en/articles/9397312-cancel-account). If your policy requires deletion of the old data, raise it explicitly. |
Source: Flicknexs onboarding schedule for catalog migrations, 2026-09-03. Durations are typical, not guaranteed.
Wistia-specific things to check first
- Wistia has no subscriber base to import, so the move is also a launch: settle the pricing tiers, the sign-up flow and the announcement to your existing email list before the import starts.
- Download the original file from each Wistia media item rather than the streamed rendition; Flicknexs transcodes from source into its adaptive bitrate ladder.
- Wistia embeds on your website and in email campaigns keep working until you delete the media; swap them for the Flicknexs embed or a link to the catalog at cut-over, then remove them.
- Captions created inside Wistia should be downloaded as a file per video so they travel with the titles.
- Wistia Channels, lead forms and viewer email lists have no direct equivalent on a subscriber platform; export the leads before you close the account and import them as prospects, not as subscribers.
The five ways a migration goes wrong, and how each is prevented
The person who can download is not the person who logs in daily
Wistia's media management article states that by default "Account Owners and Managers are the only users with access to download media", though permissions can also be granted at folder level (https://support.wistia.com/en/articles/8264610-media-management). Migrations stall in week one when the marketer running the project turns out not to hold a seat that can export, and the Owner is the CFO who set the account up years ago. Confirm the seat can actually download a file on day one, not the day the export is scheduled.
Silent truncation at 4GB and at 1,000 files
Wistia's media management article puts "a 4GB size limit" on the folder-level ZIP export and states of the Video Library bulk method "This exporting method has a limit of 1,000 files", recommending folder-level export above that (https://support.wistia.com/en/articles/8264610-media-management). The failure mode is not an error you notice — it is a ZIP that arrives, looks fine, and is missing the tail of a large folder. This is exactly why step one builds an API manifest: a count you can diff against, rather than trusting the archive you received.
The export bills against the same bandwidth your viewers use
Wistia's account usage and bandwidth article lists "A media being downloaded" and "A media being loaded and played by your own internal views" among the activities that consume account bandwidth (https://support.wistia.com/en/articles/8264552-account-usage-and-bandwidth). A whole-library pull is therefore not a free background task on the last week of a billing period. It can also be self-inflicted twice over: internal QA playback while you verify the migration counts against the same allowance.
Cancelling in the wrong order closes the door on your own masters
Wistia's cancel-account article states "Once you cancel your Wistia account, you'll no longer be able to access your media" and recommends downloading before cancelling (https://support.wistia.com/en/articles/9397312-cancel-account). Wistia's billing overview documents a "Cancel Now" option that stops billing immediately (https://support.wistia.com/en/articles/8265066-wistia-billing-overview). Choosing it mid-export ends the export. Combined with the Terms statement that "Wistia will not provide refunds or credits in the case of cancellations, downgrades, or when there are unused portions of the Services on an open account" (https://wistia.com/terms), an early cancellation costs you both the access and the remaining paid term. The same article notes "It's not possible to temporarily pause billing on a Wistia account, but you may be able to switch to a lower cost plan instead" — a downgrade, not a pause, is the only holding pattern documented.
Treating the old account as your backup
Wistia's cancel-account article states "Cancelling your Wistia account won't automatically erase all of your data from our system", that "While media in cancelled accounts generally remain untouched, we can't guarantee they'll be stored on our servers indefinitely", and that Wistia is "legally required to keep billing records for accounts with payment history for 7 years" (https://support.wistia.com/en/articles/9397312-cancel-account). Wistia's Terms state that following termination "Wistia may, but shall not be obligated to, delete archived Customer Data" (https://wistia.com/terms), and Wistia's privacy policy states "Media is hosted and stored for the life of the relevant Customer account, plus up to three years" (https://wistia.com/privacy). Read that in both directions: it is not a guarantee your files stay retrievable, and it is not automatic erasure either — if your retention policy requires deletion, that is a request you have to make 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.
- Diff the imported catalog against the Data API manifest from step one, media by media on hashed_id — not against a screen count in either dashboard, since the Wistia UI will be gone after cancellation (manifest fields per https://docs.wistia.com/reference/get_medias).
- Compare each downloaded master's byte size and type against the file_size and content_type reported in Wistia's assets array, to catch files truncated by the 4GB ZIP ceiling or a dropped transfer.
- Confirm every file you pulled is an OriginalFile asset, since Wistia documents that asset as the source media that "is never used for video streaming/playback in the Wistia player" (https://docs.wistia.com/docs/asset-urls) — if a player rendition slipped into the import set, replace it before the Flicknexs encode runs.
- Account for the non-video items: Wistia's storage-limits article states that video, audio, document and image files all count toward storage, and that archived media still counts (https://support.wistia.com/en/articles/13944217-understanding-storage-limits). Each one should have a recorded destination — Flicknexs, other storage, or retired — and none should be discovered after the account closes.
- Check caption parity per language using the ISO-639-2 language, english_name and native_name fields from Wistia's List Captions response (https://docs.wistia.com/reference/get_captions), and verify that anything marked is_draft went where you decided it should go rather than silently becoming a live subtitle track.
- Spot-check SRT timing at the start, middle and end of at least one long title per language — a caption file that survives the copy can still drift once the master is re-encoded on a different ladder.
- Compare each Wistia channel's media_count (https://docs.wistia.com/reference/get_channels) against the item count in the matching Flicknexs category or collection, and confirm the running order matches the notes you captured, since the channel response does not publish per-channel ordering.
- Resolve every channel that carried a custom_url, podcast_enabled or podcast_settings value: a podcast feed and a vanity URL are separate cutover items from the video import, and each needs a live check on its own.
- Crawl your own website, landing pages and email templates for remaining Wistia embed references by hashed_id, and confirm the count is zero before cancellation rather than after.
- Verify the subscriber import honours consent: Wistia's Channel Subscribers article states that exported lists include unsubscribed people "but marked as unsubscribed" (https://support.wistia.com/en/articles/8229027-channel-subscribers-and-notifications), so pick several of those rows and confirm they are suppressed on Flicknexs, not merely imported.
- Confirm the Media Conversion CSV data — which Wistia documents as containing "First and last name, email, date submitted, and more" (https://support.wistia.com/en/articles/8218982-exporting-analytics) — has landed in your CRM or marketing system before Wistia forms stop collecting, so there is no gap in the lead record.
- Archive the Audience and analytics CSV exports (Wistia documents these as CSV, with the Audience export covering "either identified leads or your entire audience", https://support.wistia.com/en/articles/8218982-exporting-analytics) as your historical record, and agree internally that Flicknexs reporting starts from zero on cutover day rather than expecting a merged history.
- Play a sample spanning your longest, shortest and most recently uploaded titles on the Flicknexs web player and on each white-label app you are launching — Android, iOS, Android TV, Fire TV, Roku, Samsung, LG — before announcing the move.
- Run one real test transaction through your own connected payment gateway on the Flicknexs monetisation model you have chosen (SVOD, TVOD, AVOD or hybrid), including a refund, before the first real subscriber arrives.
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 Wistia service of 1,500 subscribers
Take a Wistia 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.
Wistia is priced on its pricing page for hosting and marketing features rather than for a subscriber service, so the honest comparison is your Wistia plan plus whatever you would pay elsewhere for a paywall, billing and apps, set against the single 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 Wistia move.
| Task | Owner | Why that owner |
|---|---|---|
| Export from Wistia | 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.
Wistia next to the other platforms teams migrate from
Teams rarely compare only two platforms. The row for Wistia 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 migration guide | White-label VOD SaaS | Published plans | Roadmap adds linear or FAST channels or custom features |
| Wistia | 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 Wistia 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 Wistia 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 Wistia 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 Wistia exports, agrees the timeline in writing and names the signers for cut-over. Nothing is switched off on Wistia 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 Wistia on Flicknexs.
Guided migration is part of Flicknexs onboarding. According to our pricing page, Flicknexs offers flat monthly plans with no commission on revenue, alongside a bulk import toolkit for large libraries you can switch off once the import is done. See our pricing page for current plan and pricing details.
Original video files, titles, descriptions, thumbnails and caption files from your Wistia projects, plus the viewer email list Wistia collected for you. Wistia holds no subscriber accounts or price tiers, so those are created new on Flicknexs rather than imported.
One to two weeks for most libraries. Because there is no subscriber or billing mapping, a Wistia move is mostly download, import and tier setup, and the exact timeline is agreed at the audit call.
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.
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.
Wistia publishes a Free plan, a Business plan, a Business + Lead gen plan and a custom-priced Enterprise plan on its pricing page, according to wistia.com/pricing, checked 2026-09-03; the plans are sized on media count and marketing features, not on subscribers.
That depends on your contract with Wistia. Check the notice period and renewal date before the audit call so the cut-over lands before the next billing cycle. Flicknexs does not contact the vendor on your behalf.
They keep receiving the secure link for as long as you choose to resend it, and their entitlement waits for them. The admin shows who has and has not completed login so you can follow up.
Yes. Flicknexs serves your existing domain, and public title pages are redirected one-to-one to the new pages, so search rankings and shared links are preserved rather than dropped.
The plan does not change; the import does. Large libraries run through the bulk import toolkit in batches over more days, and the audit call sets the schedule before anything is exported.
Yes. Many teams keep website and webinar video on a marketing host and run the subscriber service on Flicknexs. The migration then covers only the titles you intend to sell, and the two accounts do not need to know about each other.
Other migration guides
Ready to leave Wistia?
Start free, import a sample of your library, and see the admin with your own content before you commit.