Migrate from Mogi to Flicknexs
To migrate from Mogi 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 Mogi I/O customers move their videos, users, pricing tiers and apps with the Flicknexs team doing the mapping and imports.
Trusted by industry leaders
50+ streaming companies powered by Flicknexs
Why teams move from Mogi I/O
Both platforms serve micro-drama and vertical video. Teams move when they want published pricing, a self-serve trial, and cloud playout for linear channels alongside the on-demand library.
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 Mogi I/O and what you keep.
| Asset | From Mogi I/O | Into Flicknexs | You keep |
|---|---|---|---|
| Video library and metadata | Library and metadata exported from the Mogi I/O admin | Bulk import toolkit maps titles, descriptions, categories, artwork, captions and series structure | Every title, its artwork and its taxonomy |
| Subscribers and entitlements | Subscriber export with plan and status | User import with plan mapping; passwords are reset by secure link on first login | Every account and what it is entitled to watch |
| Pricing tiers and payments | Plans and gateway configuration | SVOD, TVOD, AVOD and hybrid tiers recreated; gateways connected; renewal dates preserved | Your prices, your renewal calendar, your gateway |
| Apps and store listings | Mogi-built apps in your store accounts | White-label Android, iOS, Android TV and Fire TV apps; Samsung, LG, Roku and Apple TV as add-ons | Your developer accounts, listings and ratings history |
| Live channels and schedules | Live streams and any channel line-up | 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.
Find the confirmation mail that set your rate
Get written confirmation of which Mogi document governs your account
Inventory your original masters — Mogi publishes no bulk export
Draft the post-termination transfer request, with the blanks filled in
Decide how you will get the subscriber list out of the console
Establish who owns the app listings and the in-app subscriptions
Reconcile the contracted app surfaces against what you actually run
Document your current protection stack so you can match it, not guess at it
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.
Fix the contract clock before you touch any data
Send the transfer and subscriber request while the contract is still live
Rebuild the catalog from your masters, not from the console
Move subscribers, then rebuild billing under your own gateway
Stand up live, apps and cutover
Both streaming platforms run in parallel until your team tests and signs off on every device app.
A Mogi migration, week by week
Two weeks is the common case for a Mogi catalog of a few hundred titles and a few thousand subscribers. Larger libraries add days to the import, not to the plan.
diligence on your own paperwork
Reviews your Mogi annexure, confirmation mail and current catalog shape; sizes the destination platform and identifies which surfaces and monetisation models must exist on day one.
Retrieve the confirmation mail that sets your fee structure and the signed OTT Agreement with its Annexure 1; ask Mogi in writing which document governs your account, given that the OTT Agreement names India and New Delhi (https://mogiio.com/ott-agreement-2/) while the Terms & Conditions name Israel, California or England and Wales (https://mogiio.com/terms-conditions/). Do not send termination notice yet.
gather what Mogi does not export
Provides the metadata template and ingest targets; begins bulk import of whatever masters you have already located, transcoding from the original source files.
Send the written transfer and subscriber request while the contract is still live. Capture the catalog metadata and subscriber list from the backend console — the OTT Agreement's Annexure 1 lists only a "Backend console (portal based) for Admin management, Content management & Subscriber Management" and describes no export mechanism (https://mogiio.com/ott-agreement-2/), and the "For Developers" documentation URL 404s (checked 16 Sep 2026). Confirm which store account holds your app listings and any in-app-purchase subscriptions.
build and import
Completes catalog import with metadata, configures SVOD/TVOD/AVOD or hybrid to match your current tiers, wires your own payment gateway, imports subscribers with plan mapping and secure-link login, and submits the white-label apps under your developer accounts.
Supply remaining masters, sign off tier-by-tier entitlement mapping, open your own Apple and Google developer accounts if the current apps sit in Mogi's, and provide gateway credentials. Give Mogi written notice only once you are satisfied the destination is built — the agreement requires 30 days' notice by email to the two signing authorities (https://mogiio.com/ott-agreement-2/).
parallel run and testing
Runs the full post-migration check list with you, rehearses live from your existing encoder against the new RTMP endpoint, and fixes gaps found in catalog, entitlement or playback.
Test on real devices across every surface, verify renewals on your own gateway, and communicate the new app to viewers while the old one is still running. Keep paying Mogi on its normal cycle — its agreement invoices monthly in arrears, due "latest by the seventh day of the following month", and non-payment allows removal or termination after seven days' notice (https://mogiio.com/ott-agreement-2/).
cutover, then close out Mogi
Moves DNS, monitors playback, sign-in and billing through the first live days, and stays on the catalog and subscriber reconciliation until the numbers match.
Confirm the content transfer you requested has actually been delivered and verified before service ends, since the OTT Agreement obliges both parties on termination to "use commercially reasonable efforts to delete all copies of the other's Confidential Information" (https://mogiio.com/ott-agreement-2/), and settle pending dues as the agreement requires prior to the last date of service. Send any data-deletion request to [email protected] per the Privacy Policy, which allows up to 45 days to respond plus up to 45 more, and warns residual copies take time to clear from active servers and backups (https://mogiio.com/privacy-policy/).
Mogi I/O-specific things to check first
- Confirm what export Mogi I/O provides for your library and users; where an export is not available, Flicknexs rebuilds from your own records and source files.
- Micro-drama episode unlocks, coins or pay-per-episode rules are recreated as Flicknexs monetization rules; document the current rules first.
- Check which developer accounts own your apps; new listings are needed if they were published from the vendor account.
- Keep original vertical video files at full resolution for re-encoding.
The five ways a migration goes wrong, and how each is prevented
Two Mogi documents state different governing law — so your exit terms are ambiguous until confirmed
Mogi's OTT Agreement is made with "Cutting Edge Digital Pvt Ltd" in New Delhi, governed by "the laws of India, the courts at New Delhi only shall have the exclusive jurisdiction", with disputes resolved "by binding arbitration in accordance with the provisions of Arbitration and Conciliation Act, 1996 under the aegis of a single arbitrator jointly appointed by the Parties" (https://mogiio.com/ott-agreement-2/). The Terms & Conditions instead name Israel, California (for "Mogi I/O Inc. a Delaware corporation") or England and Wales (for "Mogi I/O UK Ltd."), with competent courts in Tel Aviv, Santa Clara County or London (https://mogiio.com/terms-conditions/). If a transfer goes wrong, you do not want to be establishing which document governs at that moment. Confirm it in writing at the start of the project.
The transfer right activates after termination and specifies nothing
The published exit path — "Post Termination, the content uploaded to Mogi can be transferred back to the Clients storage as and when requested" (https://mogiio.com/ott-agreement-2/) — names no format, no medium, no timeline and no cost. Practically, that is a window where your service has ended and your delivery has not yet arrived, on terms nobody wrote down. It also sits alongside the mutual obligation at termination for each party to "use commercially reasonable efforts to delete all copies of the other's Confidential Information". Mitigate by agreeing the transfer terms in writing before notice, and by treating your own masters, not the transfer, as the primary source for the catalog.
Your app listings live in Mogi's store account, so installs and reviews do not travel
Annexure 1 states "The app would be published in your name from the Mogi IO developer a/c." (https://mogiio.com/ott-agreement-2/). New apps published under your own Apple and Google accounts are new listings: existing installed users are not automatically carried across, and review history and ratings accumulated on the old listing belong to that listing. Plan an in-app and email campaign telling viewers to install the new app, and keep the old one functioning until adoption is proven. If any subscriptions were sold through app-store billing — listed as a payment instrument on https://mogiio.com/ott-iptv-solution/ — those renewals also sit in that store account and need a deliberate plan.
Rights-flagged content can be removed on 48 hours' notice with no backup kept
Mogi's OTT Agreement states that where it believes content may violate a third party's rights: "Prior to removing the said content, Mogi will block access to it and provide you a 48 hours prior notice before removing the said content without maintaining any backup copy." The same clause says Mogi may act "in its sole discretion, or receives a notice, from a third party" (https://mogiio.com/ott-agreement-2/). If you hold licensed or third-party-sourced titles, that is a reason to complete your own copy of the catalog early rather than relying on the platform to still hold it at the end of the term.
Nothing refunds, and the service-level remedy is days, not money
Both of Mogi's published documents state "You acknowledge that fees are not refundable" (https://mogiio.com/ott-agreement-2/ and https://mogiio.com/terms-conditions/), and the OTT Agreement's SLA remedy for uptime below 99.9% in a subscription month is "an extension of your Mogi plan ("Service Extension") of 5 days", claimable by email "within 10 days of becoming eligible to receive it" with "supporting documentation, such as log files showing the non-availability of the Service", stated to be "your sole and exclusive remedy". Non-payment also moves fast: upon failure to make any payment, "following a seven (7) days prior notice of due payments sent to you, Mogi may remove, disable or terminate your account." Practically: leaving mid-term costs you the remainder, so time the exit to the term, and never run the cutover while a payment is in dispute.
A codec licence obligation may sit with you, not with the platform
Mogi's Terms & Conditions state that "if you use Mogi I/O's video distribution solutions and have more than 100,000 subscribers, or use Mogi I/O's video distribution solutions to distribute 12 minutes in length or longer videos, you may need an additional third party license per the current terms of MPEG LA license for AVC/H.264 (required for encoding MP4 files)." (https://mogiio.com/terms-conditions/). If that applied to your library on Mogi, check with your own counsel whether it follows the content rather than the vendor before you assume a platform change settles 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.
- Title-for-title reconciliation: every asset in your Mogi console metadata sheet exists on Flicknexs, with matching season/episode order — this is the only count that proves a catalog assembled from masters rather than from an export is complete.
- Spot-play 20 titles picked across your oldest and newest uploads and confirm the transcode from your master is at least the quality viewers saw on Mogi, since Flicknexs transcodes from the original source file rather than re-wrapping a delivered rendition.
- Subtitle, audio-track and artwork presence per title — items that a hand-captured metadata sheet loses most easily when there is no bulk export to diff against.
- Entitlement tier per title matches the old tier: a free title that silently becomes paid, or a paid title that becomes free, is the commonest error when plan mapping is rebuilt by hand.
- Imported subscribers can sign in via secure link without setting a new password, and their remaining paid days match the extract taken from Mogi's backend console.
- Renewal test on a live card through your own gateway: one real low-value subscription renews end to end and the money lands in your account, not in a platform's, since Mogi billed you monthly in arrears by bank transfer (https://mogiio.com/ott-agreement-2/) and that relationship no longer carries subscriber revenue.
- Separately verify every subscriber who was billed through app-store billing — listed as a payment instrument on https://mogiio.com/ott-iptv-solution/ — and confirm each one is either migrated deliberately or still served, because a database import does not move a store-held subscription.
- Protection parity check: confirm which DRM or encryption actually protects each tier on the new platform and that it is at least equivalent to what Mogi confirmed in writing, given that Mogi's agreement names only "Mogi's proprietary DRM" and "Video Encryption" (https://mogiio.com/ott-agreement-2/) while its product page names "HLS AES128 Encryption" and "Multi-DRM on request" (https://mogiio.com/mott/).
- Playback on every surface actually written into your Mogi annexure — Annexure 1 lists "Branded OTT App on Android, iOS, web app" (https://mogiio.com/ott-agreement-2/) — plus each additional surface you are adding (Android TV, Fire TV, Roku, Samsung, LG), tested on real devices, not emulators.
- Live rehearsal from your existing encoder: repoint the RTMP target, run a full-length stream, and confirm the recorded VOD asset appears and plays — Mogi's LIVEU page describes "Auto Recording For Later Access" producing "a transcoded, recorded file of the live stream, which you can use as VoD content" (https://mogiio.com/liveu/), so that behaviour must be proven, not assumed.
- Deep links and shared URLs: check that links your viewers already hold, and any links embedded in past emails or social posts, resolve to the right title after cutover, with redirects in place where the path shape changed.
- Search, category browse and continue-watching behave on a full catalog, not on a 50-title test set — ordering and category assignment are the fields most likely to have been transcribed rather than exported.
- Analytics and reporting produce the same shape of numbers as your last Mogi console report for an overlapping week, so finance can reconcile across the boundary.
- Run the old platform and the new one in parallel through at least one full billing cycle before sending termination notice, since the OTT Agreement requires 30 days' notice to the two signing authorities and settlement of pending dues before the last date of service (https://mogiio.com/ott-agreement-2/).
What you pay after the move, with a worked example
A worked monthly cost for a Mogi service of 1,500 subscribers
Take a Mogi 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.
Mogi I/O prices after a demo, so no competitor figure appears here; use the quote you were given.
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 Mogi move.
| Task | Owner | Why that owner |
|---|---|---|
| Export from Mogi | 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.
Mogi next to the other platforms teams migrate from
Teams rarely compare only two platforms. The row for Mogi 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 | 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 Mogi 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 Mogi exports it, in which case continue-watching positions are imported for the titles that exist on both sides.
Apps update through the stores as normal updates, so the icon on the home screen stays where it was. Live channels keep their line-up. Rentals bought before the move remain watchable for the period you set at import.
What the admin tells you in the first month
- Login rate on the secure-link email, so you can resend to anyone who did not complete it
- Plays and watch time by title and by device, compared with the last export you took
- Revenue by tier and by gateway, with failed renewals listed for follow-up
- Channel viewing for linear playout, if you run one
- Redirect hits on old title URLs, which fall as search engines pick up the new pages
Your apps on the web, phones and TVs.
Launch your OTT apps now→Simple, Transparent Pricing
Choose the perfect plan for your streaming business. No hidden fees.
F1 Standard
Perfect for startups and small businesses
- 20 TB Bandwidth per year
- 300 GB Storage
- Video on Demand Website
- Video APIs
- Content Delivery Network
- Pre, Mid & Post Roll Ads
- upto 50 channels*. via m3u8
- Multiple Monetization Options
- Third Party Integration
F2 Super
Most popular for growing businesses
- 20 TB Bandwidth per year
- 300 GB Storage
- Video on Demand Website
- Video APIs
- Content Delivery Network
- Pre, Mid & Post Roll Ads
- upto 50 channels*. via m3u8
- Multiple Monetization Options
- Third Party Integration
- Mobile Apps (Android, iOS)
F3 Premium
For established streaming platforms
- 10 TB Bandwidth per month
- 1 TB Storage
- Video on Demand Website
- Video APIs
- Content Delivery Network
- Pre, Mid & Post Roll Ads
- upto 100 channels*. via m3u8
- 5 Youtube Channels Streaming
- upto 5 RTMP Channels using Flicknexs RTMP
- DVR
- Multiple Monetization Options
- Third Party Integration
- Mobile Apps (Android, iOS)
- Android TV & Fire TV
F4 Enterprise
Enterprise-grade streaming solution
- 20 TB Bandwidth per month
- 2 TB Storage
- Video on Demand Website
- Video APIs
- Content Delivery Network
- Pre, Mid & Post Roll Ads
- upto 100 channels*. via m3u8
- 5 Youtube Channels Streaming
- upto 5 RTMP Channels using Flicknexs RTMP
- DVR
- Multiple Monetization Options
- Third Party Integration
- Mobile Apps (Android, iOS)
- Android TV & Fire TV
- Custom Features & Priority Support
Every plan includes
- SSL certificate
- 99.5% uptime
- 24/7 support
More TV screens
Samsung, LG, Roku and Apple TV apps, each added to your plan.
24×7 TV channels
Cloud playout for always-on channels, priced by the number of channels you run.
Trusted by high-growth brands globally on G2 reviews
FLICKNEXS is recognized by thousands of users for delivering exceptional scalability, support and direct ROI.
Metehan D.
Inna Segal T
Robert G
Frequently Asked Questions
Everything you need to know about migration from Mogi 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.
Mogi I/O does not publish pricing; every call to action on its website is a demo booking, according to mogiio.com, checked 2026-09-03.
That depends on your contract with Mogi. Check the notice period and renewal date before the audit call so the cut-over lands before the next billing cycle. Flicknexs does not contact the vendor on your behalf.
They keep receiving the secure link for as long as you choose to resend it, and their entitlement waits for them. The admin shows who has and has not completed login so you can follow up.
Yes. Flicknexs serves your existing domain, and public title pages are redirected one-to-one to the new pages, so search rankings and shared links are preserved rather than dropped.
The plan does not change; the import does. Large libraries run through the bulk import toolkit in batches over more days, and the audit call sets the schedule before anything is exported.
Yes. Flicknexs has a dedicated micro-drama app product with vertical playback, episodic unlocks, subscriptions, pay-per-episode and advertising.
Other migration guides
Ready to leave Mogi I/O?
Start free, import a sample of your library, and see the admin with your own content before you commit.