Migrate from Uscreen to Flicknexs
Quick answer: To migrate from Uscreen 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 Uscreen customers move their videos, users, pricing tiers and apps with the Flicknexs team doing the mapping and imports.
Trusted by industry leaders
50+ OTT platforms powered by Flicknexs
Why teams move from Uscreen
Uscreen is strong for creator memberships. Teams move when they outgrow the creator model: they need live and linear channels, multiple content partners, advertising revenue, or a vendor that will build custom features rather than wait for a roadmap.
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 Uscreen and what you keep.
| Asset | From Uscreen | Into Flicknexs | You keep |
|---|---|---|---|
| Video library and metadata | Videos, collections and metadata from the Uscreen admin | Bulk import toolkit maps titles, descriptions, categories, artwork, captions and series structure | Every title, its artwork and its taxonomy |
| Subscribers and entitlements | Member export with plan and status | User import with plan mapping; passwords are reset by secure link on first login | Every account and what it is entitled to watch |
| Pricing tiers and payments | Subscription and one-time products from Uscreen checkout | SVOD, TVOD, AVOD and hybrid tiers recreated; gateways connected; renewal dates preserved | Your prices, your renewal calendar, your gateway |
| Apps and store listings | Uscreen-published branded apps in your store accounts | White-label Android, iOS, Android TV and Fire TV apps; Samsung, LG, Roku and Apple TV as add-ons | Your developer accounts, listings and ratings history |
| Live channels and schedules | Live streams and scheduled events | Live events, M3U8 linear channels and cloud playout schedules | Your channel line-up and program grid |
| Domains, DRM and analytics | Custom domain, DRM policy and analytics exports | Custom domain on Flicknexs, Widevine and FairPlay via the DRM add-on, analytics from day one | Your domain authority and your historical numbers |
Source: Flicknexs migration playbook and our pricing page, 2026-09-03.
What to have ready before the first call
Migrations stall on missing access, not on missing video. Gather these eight items before the audit call and the first week is the export, not the chase.
Your original master files, gathered before you touch anything else
Clarity on whether your plan actually has Publisher API access
An API client that reads pagination from response headers, not the body
Owner-level access to your own Stripe account
Admin rights on the app store developer accounts you already own
The full set of Uscreen CSV exports pulled and archived
A calendar built around the post-cancellation retention window
A decision on the in-app subscriber cohort before you schedule anything
The migration plan, step by step
Five steps, usually spread over one to two weeks. The Flicknexs team runs steps two to five with you; your side supplies exports and store credentials.
Five steps, usually spread over one to two weeks. The Flicknexs team runs steps 2 through 5 with you; your side supplies exports and store credentials.
Inventory the store through the Publisher API (or the admin exports, if you are not on a plan with API access)
Assemble the media from your masters, and use "Request Download" only for the gaps
Rebuild catalog metadata from the Content object, not by hand
Split the member base by billing rail before importing anyone
Run in parallel, then cut over inside your paid period
Both streaming platforms run in parallel until your team tests and signs off on every device app.
A Uscreen migration, week by week
Two weeks is the common case for a Uscreen catalog of a few hundred titles and a few thousand subscribers. Larger libraries add days to the import, not to the plan.
inventory and access
Onboarding team scopes the catalog from your Content export, confirms which titles have usable masters and which will need retrieval, and sizes the subscriber import including the app-store split.
Request your Publisher API authorization key if you are on a plan that includes API access (Uscreen's API article says access is available to stores on UscreenPlus and that you get the key from your Customer Success Manager or Support), pull the People, Subscription Members, Bundle Customers and Live Stream exports from Settings > Exported Files, and audit your own master-file archive against the title list.
media and metadata assembly
Runs the bulk import of masters plus the metadata sheet, rebuilds collections and playlist order, maps price_cents / rental_price_cents / rental_period into your SVOD, TVOD, AVOD or hybrid setup, and stages the redirect map from your old permalink slugs.
Work the retrieval queue for titles missing from your archive — Content > Videos > Edit > "Request Download" per video, in sitting-down sessions, because Uscreen's article states the request may take up to 15 minutes and the link lasts only 24 hours — and confirm poster art, category and tag mappings.
apps and live
Builds and submits your white-label Android, iOS, Android TV, Fire TV, Roku, Samsung and LG apps into your existing developer accounts, and configures live or cloud playout to match the delivery path you used on Uscreen.
Grant the developer-account access Uscreen's responsibilities article already puts in your name across Roku, Amazon, Apple, Google and Samsung, supply store assets, and shepherd platform review. Nothing from the existing Uscreen apps transfers, since that article states Uscreen does not provide app artifacts or source code.
parallel run and verification
Imports subscribers with plan mapping and secure-link login against a dated re-pull, connects your payment gateway, and runs the post-migration checks with you while your Uscreen store is still live.
Re-pull deltas using GET /customers with from / to and date_field=updated_at, sign off catalog and playback checks, and send the app-store cohort their cancellation instructions — Uscreen states admins cannot cancel in-app subscriptions on members' behalf and refunds must be requested from the store.
Cutover, then the retention window
Switches your domain to the Flicknexs storefront, monitors the first billing cycle on your own gateway, and holds the rollback path until the first renewals clear.
Cancel through the route your plan uses (Starter and Growth self-serve under Billing; App Essentials and All Access via Success Manager or billing@uscreen.tv; Plus via Success Manager), knowing the account stays active to the end of the current billing period — then finish any last exports well inside the roughly 60 days Uscreen says it retains uploads and account data after cancellation, before permanent deletion.
Uscreen-specific things to check first
- Community posts and comments do not map one-to-one to an OTT catalog; decide what you archive and what you rebuild before export.
- Uscreen collections become Flicknexs categories and series; agree the taxonomy first so the import is clean.
- Check which store accounts own your current apps; if Uscreen published them, new listings may be needed under your own accounts.
- Export your email marketing lists separately, since Flicknexs connects to your own email tool.
The five ways a migration goes wrong, and how each is prevented
Media retrieval is the schedule, and it is serial
If your master archive has holes, every missing title is an individual round trip: Uscreen's "Download a Video" article documents Content > Videos > Edit > "Request Download" per video, says the request "may take up to 15 minutes to process", says the link "will only be available for 24 hours after we finish processing the request", and states plainly that "at the moment, it is not possible to download all of your videos at once." A 400-title catalog with a 30% archive gap is not a weekend; it is staffed sessions across days, because links expire while you sleep. Audit your archive against the Content inventory before you promise anyone a date.
App-store subscribers cannot be moved, cancelled, or refunded by you
Uscreen's in-app subscriptions article states that app-store payments "cannot be managed through the Uscreen dashboard", that "Admins cannot cancel in-app subscriptions on behalf of the members," that "We do not have access to the billing information or the ability to manage these subscriptions," and that "Refunds for in-app purchases must be requested directly from the app store." The practical failure mode is double-billing complaints: a member signs up on your new platform while their Apple or Roku subscription keeps renewing because nobody told them to cancel it at the source. Size that cohort from the Subscription object's platform enum first, then write to them individually with store-specific cancellation instructions.
The Stripe linkage is one-directional, and your currency may be frozen
The Publisher API exposes payment_user_id only on the customer create body ("For matching Stripe accounts, you can transfer Stripe User ID here") and the PUT /customers/{id} update body — it is not a field on the Customer object returned by GET /customers — so you cannot read Uscreen-to-Stripe customer mappings out of the API and must reconcile from Stripe by email. Separately, Uscreen's "Connect to Stripe" article states "Once you run 1 transaction through your Uscreen storefront, you will be locked into that currency," which means any multi-currency ambition you shelved on Uscreen is a fresh pricing decision on migration, not a carry-over. And because Uscreen plans "automatically appear as a Product in Stripe," tidying those Products in Stripe mid-migration risks checkout errors on the store that is still taking your money.
Your apps must be rebuilt from nothing, even though the store accounts are yours
Uscreen's "Developer Account and App Responsibilities" article states verbatim: "Uscreen does not provide app artifacts (build packages, bundles) or any other means of access to the app's source code. This code is our legal property, and we reserve the right to keep it under our control." There is no binary to hand over and no codebase to fork. What does carry over is the account layer — the same article puts developer account setup and ongoing account management on you across Roku, Amazon, Apple, Google and Samsung — so a replacement white-label build can go into the same listings. Budget for store review cycles per platform, and do not cancel Uscreen while your users' only TV app is still the Uscreen one.
Cancelling starts a ~60-day clock on data you may not have finished pulling
Uscreen's cancellation article states "We retain your uploads and account data for ~60 days following cancellation," after which "your account and data will be permanently deleted," alongside "Stores are solely responsible for migrating any data they wish to off the platform" and "We currently do not provide direct offboarding support." Two things bite here: the per-plan cancellation route (Starter/Growth self-serve, App Essentials and All Access via Success Manager or billing@uscreen.tv, Plus via Success Manager) can add days before cancellation is even effective, and the historical record is the part people forget — invoices, analytics and the customer objects behind them go with the account. Export everything you might need for tax, accounting or churn analysis before the clock starts, not during it.
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.
- Row-count reconciliation per object: the Total-Count response header from GET /contents, GET /customers, GET /offers and GET /groups against the imported counts in Flicknexs — and treat /invoices separately, since the Publisher API spec notes it caps the count at 10 000 and reports "Total-Count: 10000+" beyond that, so invoice completeness must be proven by walking Link until next disappears, not by a total.
- Play a sample from each content_type in the Content enum — collection, live_event and video — and confirm that collections retain their member order as returned by GET /contents/{content_id}/playlist_items.
- Spot-check every title whose Video "source" field was vimeo or wistia rather than upload, since those originated outside Uscreen and are the likeliest to have been re-encoded or to have a better original sitting in the source account.
- Request a 301 on each old permalink slug from the Content object and confirm it lands on the matching Flicknexs URL, so existing search rankings and customer bookmarks survive.
- Confirm meta_title and meta_description carried across, and that main_poster_url, secondary_poster_url and square_poster_url each have a corresponding artwork in the new catalog at the right aspect — square posters in particular are easy to lose in a bulk import.
- Test geo-blocking from inside a country listed in a title's blocked_countries field, using a title you know was restricted on Uscreen, and confirm it is still blocked.
- Verify the "downloadable" boolean ("Whether the content can be downloaded by end users") is honoured per title — anything that allowed offline download on Uscreen should still allow it, and anything that did not should still refuse.
- Subscriber import audit against the People CSV columns: for a sample of members, check Status, Subscription Plan and Next Invoice Date against the plan and renewal date now held in Flicknexs, and confirm Tags, User Fields, UTM Parameter Values, Lead Source and Email Marketing Opt-In survived the mapping.
- Log in as a migrated member using the secure-link login path, on both web and a new app build, before any member is asked to do it for real.
- Billing-rail segregation check: confirm every subscription whose Uscreen platform value was apple, roku, android or amazon is flagged in your new system as app-store-billed and is NOT being charged again by your own gateway, and that those members received the store-specific cancellation instruction.
- Revenue reconciliation across Invoice "origin" values (stripe, native_paypal, paypal, authorizenet, uscreen, amazon, android, apple, roku, braintree) for a closed month — and expect some rows to have no person attached, because Uscreen's GDPR article states that after a self-deletion "Invoices and records will show as 'Deleted User' with a number".
- Stripe-side check after first live checkout: a new charge lands in your own Stripe account from the Flicknexs gateway connection, while the Uscreen-created Stripe Products are still untouched and still serving any member whose final Uscreen cycle has not closed.
- Run one live event end to end on the new stack using the same production path you used on Uscreen — Live Studio, RTMP from stream software, Zoom, mobile, or XML / Custom CDN with a hardware encoder — and confirm your Live Stream Preregistration list was imported and receives the notification.
- If you were paying for Uscreen's DRM add-on, confirm protected playback on each device class before cutover; Uscreen's DRM article describes it as applied automatically at upload and as re-encoding existing content in the background, so DRM status on the new platform is a fresh setup, not a migrated attribute.
What you pay after the move, with a worked example
A worked monthly cost for a Uscreen service of 1,500 subscribers
Take a Uscreen 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.
Uscreen publishes plan prices on its own pricing page; compare the plan that includes apps against the Flicknexs figure above using your current invoice.
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 Uscreen move.
| Task | Owner | Why that owner |
|---|---|---|
| Export from Uscreen | 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.
Uscreen next to the other platforms teams migrate from
Teams rarely compare only two platforms. The row for Uscreen 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 | Creator membership platform | Published plans | Outgrowing the creator model; need live, linear, partners or ads |
| Muvi migration guide | Several OTT products, each priced separately | Published per product, apps billed per app | Consolidating several product bills into one platform |
| VPlayed migration guide | Customizable OTT framework, customer-managed | Quote-based | Engineering upkeep; want a managed platform with custom builds on request |
| Dacast migration guide | Live streaming and hosting with a paywall | Published plans, bandwidth metered | Business becomes a subscription service needing apps and a catalog |
| Wowza migration guide | Streaming infrastructure and engine | Published, usage and license based | Want the whole service layer, not only delivery |
| Kaltura migration guide | Enterprise and education video platform | Partly published, mostly contract | A consumer subscription service needs a simpler, published-price platform |
| Mogi I/O migration guide | White-label OTT and micro-drama SaaS | Not published; demo-led | Want a published price, a self-serve trial and cloud playout |
| Vodlix migration guide | White-label VOD SaaS | Published plans | Roadmap adds linear or FAST channels or custom features |
| Wistia migration guide | Business video hosting and marketing | Published plans, media-count sized | Video becomes the product and needs subscribers, billing and apps |
| Vimeo On Demand migration guide | Sell-your-video storefront, closing | Per-sale fees; shutting down Nov 20, 2026 | The storefront is shutting down and sellers must move |
| Shift72 migration guide | White-label VOD and virtual cinema for festivals | Not published; demo-led | A festival window becomes a year-round subscriber service |
Source: each vendor's public website, checked 2026-09-03.Pricing model column reflects what the vendor publishes, not a quote.
What changes for your viewers, and what does not
For a viewer, the move from Uscreen 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 Uscreen 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
Start free
Your apps on the web, phones and TVs.
Launch your OTT apps now→Simple, Transparent Pricing
Choose the perfect plan for your streaming business. No hidden fees.
F1 Standard
Perfect for startups and small businesses
- 20 TB Bandwidth per year
- 300 GB Storage
- Video on Demand Website
- Video APIs
- Content Delivery Network
- Pre, Mid & Post Roll Ads
- upto 50 channels*. via m3u8
- Multiple Monetization Options
- Third Party Integration
F2 Super
Most popular for growing businesses
- 20 TB Bandwidth per year
- 300 GB Storage
- Video on Demand Website
- Video APIs
- Content Delivery Network
- Pre, Mid & Post Roll Ads
- upto 50 channels*. via m3u8
- Multiple Monetization Options
- Third Party Integration
- Mobile Apps (Android, iOS)
F3 Premium
For established streaming platforms
- 10 TB Bandwidth per month
- 1 TB Storage
- Video on Demand Website
- Video APIs
- Content Delivery Network
- Pre, Mid & Post Roll Ads
- upto 100 channels*. via m3u8
- 5 Youtube Channels Streaming
- upto 5 RTMP Channels using Flicknexs RTMP
- DVR
- Multiple Monetization Options
- Third Party Integration
- Mobile Apps (Android, iOS)
- Android TV & Fire TV
F4 Enterprise
Enterprise-grade streaming solution
- 20 TB Bandwidth per month
- 2 TB Storage
- Video on Demand Website
- Video APIs
- Content Delivery Network
- Pre, Mid & Post Roll Ads
- upto 100 channels*. via m3u8
- 5 Youtube Channels Streaming
- upto 5 RTMP Channels using Flicknexs RTMP
- DVR
- Multiple Monetization Options
- Third Party Integration
- Mobile Apps (Android, iOS)
- Android TV & Fire TV
- Custom Features & Priority Support
Every plan includes
- SSL certificate
- 99.5% uptime
- 24/7 support
More TV screens
Samsung, LG, Roku and Apple TV apps, each added to your plan.
24×7 TV channels
Cloud playout for always-on channels, priced by the number of channels you run.
Trusted by high-growth brands globally on G2 reviews
FLICKNEXS is recognized by thousands of users for delivering exceptional scalability, support and direct ROI.
Metehan D.
Inna Segal T
Robert G
Frequently Asked Questions
Everything you need to know about migration from Uscreen 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.
Uscreen publishes its plan pricing on its own pricing page, according to uscreen.tv, checked 2026-09-03; figures are not repeated here because they vary by plan and billing period.
That depends on your contract with Uscreen. 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. You get subscription tiers, free trials, coupons and pay-per-view built in, and the content partner portal add-on supports multiple creators with revenue sharing.
Other migration guides
Ready to leave Uscreen?
Start free, import a sample of your library, and see the admin with your own content before you commit.