Migrate from Muvi to Flicknexs

The two generations have completely different export paths, so this decides your whole plan. On current Muvi One, the CMS can hand you files: Muvi's help page says to "navigate to 'Content Management' --> 'Content Library' in the CMS", open the "Assets" tab and "click on the 'Download Icon' on the right-hand side of a video to download it" — and the same Muvi page states "You can only download a single video/audio/image/file at a time." On Muvi One Classic, Muvi's help page states "At present, there is no option available in the CMS to download the videos from the video/audio library" and that "To download the videos, form the 'Video Library' or audios from the 'Audio Library' in the CMS, you need to add a support ticket." Establish which one your account runs before anyone books a cutover date.

Muvi does not publish a bulk media export API or a whole-library download, so for any catalog past a handful of titles the practical source of pixels is your own masters. This also matters for quality: Muvi's Classic help page says library files are held "in their original format (i.e. .avi, .wmv, .mov, .mpeg, .wav, .acc, .aiff, .m4a, )" and that "During the process of encoding, the video files are converted to .mp4 format and audio files are converted to .mp3 format" — so what you retrieve may be a delivery derivative rather than the master you would want re-encoded. Flicknexs imports from original source files, so pull masters from your archive, editor or MAM in parallel with the Muvi export rather than after it.

Muvi's Muvi One feature page states that "metadata, reports, users, etc. can be exported at the click of a button using the CMS itself" and that "CSV, Txt, Excel, and MRSS feeds, Muvi supports it all." Export in that shape and keep Muvi's own field names, because the same vocabulary is documented on Muvi's bulk metadata import article, whose field table marks four columns Mandatory — "Content Name", "Content Types", "Metadata Type" and "Content Category". Those four are the spine we map your Flicknexs catalog structure from; anything you hold only in Muvi's UI and not in the export has to be re-typed.

Muvi One Classic documents the subscriber export as: "Click on 'Export'. All the details of the users including 'User', 'Email', 'Type', 'Plan' will be downloaded in MS Excel format." The same Muvi page documents a second button, "Export Update History", where "All the updated user history data will be downloaded in MS Excel format" — take that one too, because it is where late plan changes show up. Note what those four columns do not contain: any credential. Password hashes are not part of the documented export, so budget for re-authenticating every subscriber rather than assuming logins carry over.

Muvi documents retrieving the key in the CMS: "navigate to 'Dev Center' --> 'API & Webhooks' in the CMS. Click on the 'APIs' tab. You can find the API Authorization Key." Muvi's developer portal groups Muvi One's APIs as "Content, Billing, User, Analytics", lists the common parameters app_token, product_key, store_key and user_uuid, and warns that "Some routes may use REST while others follow GraphQL query patterns" — so budget integration time rather than assuming one uniform REST surface. The capabilities Muvi documents for the API are to "get embed codes for the video/Audio player to display under your apps, add/Manage Subscribers, Manage User Authentications, send search request and get results"; there is no published bulk catalog-export endpoint, so treat the API as a reconciliation and subscriber tool, not as the migration pipe.

This is the part of leaving Muvi that works in your favour. Muvi documents that the gateway is connected by you under "Monetization" --> "Payment Gateways", and states "The payment gateways are linked directly to your bank account and hence the revenue that you make goes directly from your subscribers to you!"; Muvi's payment gateway feature page lists "No Muvi Revenue Share" and says "Payments go through your connected gateway account, with no Muvi revenue share." Your recurring mandates therefore already sit in your own gateway account. Get the person who actually administers that account — the gateways named in Muvi's coverage table are Stripe, PayPal, Braintree, Razorpay, Paystack, Iyzico, Paytech, Flutterwave, GlobalPay and StarPay, plus carrier billing and mobile wallet options MTN, M-Pesa, Singtel and Unifi — into the project from day one, because they, not Muvi, control renewal continuity.

For Android, Muvi's help page says "We will publish the App in the Google Play Store either by using our Developers ID or by using your Developers ID", and that "If you use your Developers ID, then the App will show your company or brand name in the app store" — set up by selecting "Use My Android Developers ID" and saving your username and password in the CMS. For iOS, Muvi states "We will publish the App in the App store either by using our Developer ID or by using your Developer ID", and specifically that "Muvi can use its own Apple Account to publish your iOS application in the Test Flight mode, however, you need to have your own Apple Developer Account to publish your iOS application to the iTunes App store (live)." Open both consoles and confirm which account each live build was shipped from before you assume the listing, its reviews and its install base travel with you.

On Muvi, DRM is not one global toggle: Muvi documents that "You can enable DRM for video while adding a video encoding profile" and that "You can select the DRM profile while creating new content or updating the existing content", so protection is attached per title through the profile it was encoded with. Muvi One states it uses "industry-standard DRMs including Google Widevine, Apple FairPlay, and Microsoft PlayReady." On Muvi One Classic, Muvi adds that "To enable the DRM, you must add a Support Ticket" and that "DRM is a paid feature" requiring Standard or higher. Produce the list of which titles carry a DRM profile, so the same titles come up protected on Flicknexs and nothing quietly ships in the clear.