Migrate from Shift72 to Flicknexs
Quick answer: To migrate from Shift72 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 Shift72 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 Shift72
Shift72 is a strong fit for a festival window: a virtual cinema that opens, sells passes and bundles, and closes. Teams move when the service becomes year-round, with a subscriber base, linear channels or a broader catalog, and they want published monthly pricing, a self-serve trial and a vendor that also builds custom features.
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 Shift72 and what you keep.
| Asset | From Shift72 | Into Flicknexs | You keep |
|---|---|---|---|
| Video library and metadata | Films and metadata from the Shift72 platform management console | Bulk import toolkit maps titles, descriptions, categories, artwork, captions and series structure | Every title, its artwork and its taxonomy |
| Subscribers and entitlements | Customer records with passes, rentals and subscriptions | 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 | Pass, bundle, rental and subscription price points | SVOD, TVOD, AVOD and hybrid tiers recreated; gateways connected; renewal dates preserved | Your prices, your renewal calendar, your gateway |
| Apps and store listings | Shift72-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 | Event streams and premiere schedules | 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 admin-role X-Auth-Token, not just an admin login
Your original video masters, because Shift72 documents no master-file export
The user CSV plus a second pass for everything the CSV omits
Admin access to your own Stripe account
Your Special Terms and Price List, and the notice date calculated from them
A decision from your licensors on content protection level
An inventory of anything consuming Shift72 webhooks or feeds
A record of licensor revenue-split obligations that outlive the platform
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.
Take a full admin inventory through Shift72's documented read APIs
Export people, orders and money while the account is still live
Rebuild the catalog on Flicknexs from your masters, mapped to the Shift72 slug
Rebuild entitlements and move the Stripe wiring, in that order
Stand up your own apps, run in parallel, then serve notice on the clock the contract sets
Both streaming platforms run in parallel until your team tests and signs off on every device app.
A Shift72 migration, week by week
Two weeks is the common case for a Shift72 catalog of a few hundred titles and a few thousand subscribers. Larger libraries add days to the import, not to the plan.
contract and access
Flicknexs onboarding reviews your Shift72 Special Terms and Price List with you and works backwards from your Subscription End Date to fix a notice date and a cutover date; no notice is sent yet.
Retrieve your Special Terms and Price List (Shift72's Terms of Service clause 23.6 defines Fees by reference to those documents, and no amounts are published on the site), generate an admin API key in the Shift72 Admin app for the X-Auth-Token header, and confirm you hold administrator access to your own Stripe account.
export and inventory
Runs the documented admin reads with you — film index (including drafts), show_multiple metadata, Discovery availability, the ingestion source file list and the media encoding index — and normalises everything into one migration sheet keyed on film slug.
Pull the admin user CSV and cross-check it against the users search totals, pull the reporting CSVs (orders, items, refunds, discount usages, summary, analytics, telemetry streams) and the Revenue Split Details report, and confirm your own master archive covers every title on the inventory. Freeze all deletions in the Shift72 admin for the rest of the project.
catalog rebuild
Bulk-imports video from your original masters and attaches the exported metadata — crew, cast, studio, genres, tags, trailers, artwork, per-country classifications — then rebuilds availability windows and pricing regions and configures DRM to the protection level your licensors specify.
Supply masters, approve artwork and metadata mapping on a first batch before the rest runs, and get written confirmation from your rights holders on the content protection level to apply — Shift72's own guidance is to check with license holders before making that decision.
accounts, billing and apps
Imports subscribers with plan mapping and secure-link login, loads TVOD ownership from the orders export, connects your payment gateway, and submits your white-label apps for Android, iOS, Android TV, Fire TV, Roku, Samsung and LG.
Reconcile a sample of real subscribers and real buyers by name, brief your Shift72 account manager on any webhook changes (Shift72 documents that each webhook is configured by Shift72 and that event subscriptions change via your account manager), and prepare the customer email explaining that everyone will sign in fresh because no password can be migrated.
Cutover week, then a monitored tail
Runs the full post-migration test list with you, switches DNS, and monitors playback, sign-in and billing daily through the first renewal cycle; rollback stays available until you sign off.
Repoint or retire the Stripe webhook that fed https://[WebsiteURL]/services/shopping/v1/webhook, send your written termination notice so it lands no less than 60 days before the Subscription End Date as clause 12.3 of Shift72's Terms of Service requires, keep the old platform live and undeleted until that date, and archive your exports permanently — clause 13.7 makes you "solely responsible for maintaining a copy of all Data".
Shift72-specific things to check first
- Festival passes and bundles are time-boxed products; decide whether current pass holders receive a subscription entitlement on Flicknexs and for how long before the customer import.
- Studio delivery terms often require DRM and geo-blocking; Flicknexs geo-fencing is built in, and DRM is arranged through the delivery layer on request as part of an enterprise plan, so confirm that arrangement with your distributor before cut-over.
- Screening windows and territory rights per film must be re-entered; export a rights sheet with start date, end date and allowed countries per title so the import sets them in one pass.
- Check who owns the app listings in the stores; re-publish from your own developer accounts where possible so ratings and installs carry over.
- Confirm what export Shift72 provides for library and customers; where none exists, Flicknexs rebuilds from your own records and the original source files.
The five ways a migration goes wrong, and how each is prevented
Deleting encodings to free space destroys the only copy you have on the platform
Shift72's "How to Delete Media Content" article states that after clicking the red trash can icon and clicking Save, "the files will be deleted from the servers which will reduce storage space", and warns "If you delete the encoding that is currently set to live, your users won't be able to view the content." During a migration there is a natural temptation to clean up storage on the outgoing platform. Do not touch that trash can until every title has been re-ingested and played end to end on the new platform, because Shift72's documented download endpoint returns DRM-bound streams (carrying drm_key_encoded), not a mezzanine file you can re-ingest elsewhere. Mitigation: freeze all deletions on the old platform for the whole project, and verify your own master archive against the file list from GET /services/content/ingestion/v3/source before the first title is touched. Sources: https://docs.shift72.com/en/articles/2151377-how-to-delete-media-content, https://apidocs.shift72.com/services/content/
Your contract owes you no data safety net, and the clock auto-renews
Three clauses of Shift72's Terms of Service compound. Clause 13.7: "You are solely responsible for maintaining a copy of all Data. Shift72 has in place for its own purposes policies and procedures to prevent data loss (and recovery) but does not make any guarantee around loss of your Data and as such Shift72 expressly excludes any liability for any loss of Data." Clause 12.2: the agreement "shall automatically renew (on a recurring basis)". Clause 12.5: you agree "Upon termination of this Subscription Agreement to immediately cease accessing the Subscription and Platform", and "that, if this Subscription Agreement is terminated prior to the end of the Initial Subscription Period or any Renewed Subscription Period (as applicable), Shift72 shall not be obliged to refund any part of the Fees that you have paid in advance for such period." Miss the 60-day notice in clause 12.3 and you pay for another full term; serve it too early and you may lose admin API access before your exports are complete. Mitigation: finish every export first, then send notice; put the Subscription End Date and the notice date on one calendar. Source: https://www.shift72.com/terms-of-service
Nobody's password comes with them, and sign-on is shared across Shift72 platforms
The Shift72 user CSV export's documented columns are Email, Name, Created at, Gender, DOB, Sign In Attempts, Last Signed In, Email Opt In, ID and External ID — no credential of any kind. Separately, clause 13.4 of Shift72's Terms of Service states "All Shift72 platforms share a single database of sign-on information for customers. This means Shift72 may access and store information on your customers." In practice that means an account your subscriber uses on your site may not be an account created for your site, and your migration cannot carry the login itself. Mitigation: Flicknexs subscriber import uses secure-link login so people re-enter your platform without inventing a new password on day one; pair it with a pre-cutover email to the exported address list, and hold External ID against any external auth provider you use, since Shift72 documents it as "An external id for a user, often used to link to external auth providers." Sources: https://apidocs.shift72.com/services/user/, https://www.shift72.com/terms-of-service
TVOD ownership and rental windows silently break if only subscribers are migrated
Shift72 sells across all three models — its ecommerce page describes SVOD as "Offer unlimited access to a library of content for a monthly or yearly fee", TVOD as "Allow your audience the freedom to purchase or rent individual pieces of content" and AVOD as "Provide free access to content supported by advertisements", and GET /services/shopping/configuration returns a platform_type that "Can be tvod, svod or avod". A subscriber-only migration is fine for a pure SVOD site and quietly disastrous for a TVOD one, where a customer who bought a title expects it in their library forever. The entitlement evidence lives in the orders export, whose documented columns include "Ownership", "Pricing Region" and "Currency". Mitigation: treat the orders CSV as an entitlement source, not a finance artefact; migrate ownership records alongside accounts, and reconcile a sample of real buyers by name before cutover. Sources: https://www.shift72.com/features/ecommerce, https://apidocs.shift72.com/services/shopping/, https://apidocs.shift72.com/services/reporting/
Live events and integrations do not lift and shift the way VOD does
Two Shift72-specific mechanics need explicit re-planning rather than data migration. First, live: Shift72's live streaming page describes hosting, monetising and broadcasting "live events on your own white-labelled platform, in real-time", while its help article "How to Embed a YouTube Live Link into Your Platform" documents a different route — adding {{youtube id=id-of-video class="never"}} into the Synopsis box of a film or TV episode record — and states "Note: This is currently available only for YouTube. This feature is also unavailable on your apps." If any of your live schedule runs through that embed, it exists as text inside a metadata field and will not appear in any content export. Second, webhooks: Shift72's documentation states "Currently, each webhook needs to be configured by SHIFT72" and "Contact your SHIFT72 account manager to change the list of subscribed events", so any downstream system fed by upload_started, upload_completed, ingestion_updated or shopping_order_success — verified via the X-Shift-Signature HMAC SHA-256 header — needs a coordinated change, not a self-service toggle. Mitigation: grep your synopsis fields for embed syntax, and open the webhook conversation with your account manager at the start of the project. Sources: https://www.shift72.com/features/delivery/live-streaming-virtual-events, https://docs.shift72.com/en/articles/5125875-how-to-embed-a-youtube-live-link-into-your-platform, https://apidocs.shift72.com/services/webhooks/
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: compare the record count from Shift72's admin CSV export (GET /services/users/v2/users/csv) against the totals returned by GET /services/users/v2/users/search, per Shift72's User Service documentation, and confirm the imported subscriber count on Flicknexs matches both — investigate any difference before cutover rather than after.
- External ID integrity: spot-check migrated accounts that carried a value in the CSV's External ID column, documented by Shift72 as "An external id for a user, often used to link to external auth providers", and confirm the external auth provider still resolves the same person on the new platform.
- Catalog completeness including drafts: Shift72's Meta Service says GET /services/meta/v2/film/index "will include films that are in a draft status" — reconcile that full list against the destination, and deliberately confirm which drafts you chose not to migrate, so the gap is a decision and not an omission.
- TVOD ownership proof: pick a sample of real orders from the reporting orders CSV (documented columns include "Invoice Number", "Ownership", "Currency" and "Pricing Region"), then log in as those migrated accounts on Flicknexs and confirm each purchased or rented title is present with the right access type.
- Rental expiry behaviour: for any rental-type entitlement, confirm an unexpired rental still plays and an expired one is correctly refused, so the move neither extends nor truncates a window the customer paid for.
- Availability windows and geo: replay the fields from Shift72's Discovery API (GET /services/discovery/v1/films returns available_from, available_to and country_codes) and test playback from inside and outside each permitted country, so a title that was geo-restricted on Shift72 stays restricted.
- Multi-currency and pricing regions: Shift72's API reference lists a Pricing API that "Provides multi currency pricing and region controls", and its orders CSV carries "Currency" and "Pricing Region" — check the checkout price shown in each region you sell into against the price you charged before, currency by currency.
- Per-country classifications: Shift72's Meta Service documents classifications as "A list of classification records, indexed alphabetically by country code" — confirm the correct rating badge renders per territory on web and on each app, since this is a compliance obligation rather than cosmetics.
- DRM across all three systems: Shift72's "DRM Device Support" article names Widevine, PlayReady and Fairplay — test playback on a device covered by each, and re-confirm with your licensors which of Shift72's Standard / Studio 1 / Studio 2 equivalents your titles are contractually required to run at, given its "Content Protection" article states "By default for new sites, the default Content Protection is Studio 1" and advises checking "with your license holders before making Content Protection decisions".
- Stripe cutover, tested for double billing: confirm the Shift72 webhook endpoint documented as https://[WebsiteURL]/services/shopping/v1/webhook no longer drives plan changes, then take one renewal through a full cycle and verify exactly one charge, with the same amount and renewal date as before.
- Refund path continuity: Shift72 documents POST /services/shopping/v1/refund, where "You can choose to refund the user's credit card through Stripe, or choose to only have the refund recorded" — run a test refund on the new platform and confirm your finance process knows which system owns refunds for orders placed before cutover.
- Webhook and feed consumers: for every internal system previously fed by Shift72's upload_started, upload_completed, ingestion_updated or shopping_order_success events (verified via the X-Shift-Signature HMAC SHA-256 header), confirm it now receives and validates events from the new platform — and for any ad or syndication partner reading GET /services/discovery/v1/ad-manager-mrss-feed, confirm the replacement feed parses on their side.
- Slug-level URL continuity: Shift72 addresses content by slug (its Content Service exposes /services/content/v4/media_content/download/[slug] and its Licensor Reports include the film slug) — crawl your live title URLs and confirm each resolves or redirects on the new site, so search rankings and shared links survive.
- App sign-in on TV devices: test a migrated account signing in on Apple TV, Android TV, Fire TV and Roku — Shift72 markets native apps on each — and confirm the library, entitlements and resume points behave the same as on web.
- Licensor reporting parity: reproduce one historical period of Shift72's Revenue Split Details report, which includes the licensor, release window, price and currency, pricing region, "The percentage and floor revenue splits on the release window" and "The revenue split type used in the transaction (floor or percentage)", and confirm the new platform's reporting produces figures you can defend to the same rights holder.
What you pay after the move, with a worked example
A worked monthly cost for a Shift72 service of 1,500 subscribers
Take a Shift72 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.
Shift72 prices after a demo, so no competitor figure appears here; use the quote or contract you hold and divide an annual figure by twelve.
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 Shift72 move.
| Task | Owner | Why that owner |
|---|---|---|
| Export from Shift72 | 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.
Shift72 next to the other platforms teams migrate from
Teams rarely compare only two platforms. The row for Shift72 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 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 | 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 Shift72 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 Shift72 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 Shift72 on Flicknexs.
Guided migration is part of Flicknexs onboarding. According to our pricing page, Flicknexs offers transparent platform tiers with no commission on revenue, and a bulk import toolkit for large catalogs you can switch off after the import. See our pricing page for current plan and pricing details.
Films with metadata, artwork and caption files, customer records with their passes, rentals and subscriptions, your price points and rights windows per title, and your apps re-published from your own store accounts. Anything Shift72 does not export is rebuilt from your records.
One to two weeks for most catalogs. Rights windows and territory rules add mapping time rather than calendar time; the audit call sets the schedule so the cut-over lands between festival editions, not during 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.
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.
Shift72 does not publish pricing; its website sells by demo booking, according to shift72.com, checked 2026-09-03.
That depends on your contract with Shift72. 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 supports rental windows with start and expiry dates, pay-per-view on live premieres, free-preview minutes, subscriptions and geo-fencing per title, so a festival edition can run inside a year-round catalog under one brand.
Other migration guides
Ready to leave Shift72?
Start free, import a sample of your library, and see the admin with your own content before you commit.