You can leave Vimeo OTT without losing your subscribers, but only if you stop treating them as one list. Each subscriber pays in one of three places: your website, an app store, or nowhere at all, and each group moves differently. App-store subscribers can stay put if your new provider updates the listing you already own. Web subscribers usually have to take an action, because Vimeo publishes no way to move their cards out. This guide covers what Vimeo lets you export, what each store's own rules say about changing vendors, what to ask for in writing, and how to run the switch so nobody is charged twice or locked out.
Start here: where does each subscriber pay?
Before you compare a single vendor, export your customers and count them by billing rail. Vimeo's customers CSV has a platform column with values such as web, ios, tvos, Android, android_tv, amazon_fire_tv and Roku. That one column tells you how much of your revenue is at risk.
- Moves: name, email, plan, dates
- Does not move: the card
- Expect: a fresh sign-up at their next renewal
- Moves: nothing needs to, if you keep the listing
- Expect: billing carries on, though they may need to sign in again
- Moves: nothing automatically
- Expect: you grant access again on the new platform
The split changes the whole plan. Here is a worked example, with made-up numbers, for a service with 1,000 subscribers at $9.99 a month:
What Vimeo lets you take
Run these exports early, and again just before you switch. Vimeo's data terms say customer data is deleted as soon as reasonably practicable after the services agreement ends.
| Export | Where | What you get | What you do not get |
|---|---|---|---|
| Customers CSV | Admin, Customers, All Customers, Export | Email, name, location, product, status, frequency, platform, promo codes, expiration date, marketing opt-in | Card data or a Stripe customer ID |
| Transactions CSV | Same Export button | Amounts, fees, status, next renewal date, refunds, per purchase | Card data. Exports can be limited to the last 30, 60 or 365 days |
| Videos | Content, Videos, open the video, Distribution panel, Download | MP4 renditions, up to the quality of your source | A bulk download, or a master over 20 GB. Videos linked from a Vimeo library are not copies, so keep that plan until you have them |
| Scheduled exports | Manage, Exports | A full customer export and video data, by email or S3 | Enterprise accounts only |
Web subscribers: plan for a fresh sign-up
The honest position on stored cards is short. Vimeo says OTT does not store or receive card details directly, because Stripe holds them. Its only public card-migration document is for moving customers in, and even that cannot move PayPal-funded customers. We found no official statement that Vimeo will move your subscribers' cards to another processor. A competing vendor, Uscreen, says of platforms like this that subscriber data is typically released only near shutdown. That is a vendor's view, not Vimeo's.
So ask Vimeo in writing, and plan as if the answer is no. Vimeo gives you two switches on each subscription product, and using them in the right order is what protects you:
- Pause subscription stops new sign-ups. Existing subscribers keep renewing and keep access.
- Cancel all subscriptions removes everyone's access, and they are no longer charged.
- 1. Grant accessGive each paid-up subscriber access on the new service, ending on their current paid-through date.
- 2. Tell themEmail what is changing, where to watch, and the date their new subscription starts.
- 3. PausePause the Vimeo product, so nobody new joins the old service.
- 4. Cancel allOnce the new service is live, cancel at Vimeo so nobody is billed in both places.
Here is how that works on OTTEngine. The subscriber management add-on, $299 a month from Studio up and included on Enterprise, has a CSV import that takes an email address, name, end date, price and billing period. An import creates access until that date and nothing else: it sends no email and sets up no billing, so your announcement has to do that job. Viewers sign in with a code sent to their email, so there are no passwords to migrate. When the end date arrives, access stops and the viewer can subscribe through your own Stripe account.
If your subscribers already bill through a Stripe account you own, you are in a better position, because billing can stay where it is. Vimeo says only Enterprise contracts can collect payments through their own stack, so most services will not be in this group.
App-store subscribers: keep the listing, keep the subscriber
This is where a move can be far less painful than vendors make it sound. Vimeo says your branded apps are published under your own developer accounts, which you registered and own, with Vimeo invited in to publish. That means the listing, with its installs and reviews, is yours. A new provider can ship an update to that same listing instead of asking you to start again.
Two cautions. First, no store says in so many words that subscriptions keep renewing when a vendor changes. What they document is that subscriptions belong to the app and its product IDs, so keep those identical and test before you rely on it. Second, the details differ by store, and two of them have real traps:
| Store | Keep the same | Signing and access | Same listing? |
|---|---|---|---|
| Apple (iOS, tvOS) | Bundle ID, subscription product IDs | Apple documents no rule that an update needs the old vendor's certificate. Valid distribution certificates come from your own account | Yes |
| Google Play (Android, Android TV) | Package name, subscription product IDs | An update must match the original signing certificate. With Play App Signing, Google holds that key and you can request an upload key reset. Older self-signed apps need the old key | Yes, check the key |
| Amazon (Fire TV) | Package name, a higher version code, in-app SKUs | Amazon re-signs apps with your account's own signature, so stay in your account. A transfer to another account can break updates for existing users | Yes, in your account |
| Roku | The app and Channel ID in your dashboard, Roku Pay SKUs | Roku warns that registry data is lost if an update uses a different Dev ID. To keep it, rekey using the previous package and its password | Yes, sign-ins may reset |
| Samsung (Tizen) | Seller Office app, Tizen ID | The exception: Vimeo runs Samsung apps in its own group account, and starts a transfer to an account you create. An update must carry the same author certificate, or it needs a new app | Transfer first |
| LG (webOS) | App ID, a higher version number | You create the seller account. LG documents no public signing or transfer rules, and each update goes through QA again | Largely undocumented |
Roku's registry warning needs a word of explanation. The registry is storage on the viewer's device, and apps often keep sign-in details there. Roku does not say what your app stores, but a new key could mean viewers have to sign in again, so plan for that in your email. Our guide on transferring a Roku channel covers the Roku account side in detail.
On reviews and installs, the documents are thinner than you might expect. Amazon says ratings and download statistics carry across versions. Apple's and Google's transfer pages say reviews and ratings and users, ratings and subscriptions move with the app. Roku, Samsung and LG do not address it. A brand-new listing is the outcome to avoid: Google treats a changed package name as a completely different app, and in-app products cannot be shared between Apple app records.
If you publish a new listing instead of updating the old one, store-billed subscribers do not come with you. Treat that as the last resort, for the one store where you have no other choice.
What to ask Vimeo for, in writing
Vimeo publishes no exit process for Apple, Google, Roku, Amazon or LG apps, and it does not say who holds the signing keys for the apps it builds. Its own guide for taking over apps from another developer is a useful checklist, because a provider taking over from Vimeo needs the same things. Ask your account manager for:
- The Android signing details, if the app is not on Play App Signing: the keystore file, its password, the key alias and key password. Vimeo asks new customers for exactly this from their previous developer.
- The Roku signed package and its password, so the new build can be rekeyed to the same Dev ID.
- The Samsung transfer, plus how the author certificate will be handed over.
- Every in-app product ID, per store, and confirmation of what is configured in each store account.
- The date Vimeo stops maintaining your apps, so you know how long your parallel run can last.
- Its answer on stored cards. Ask directly whether subscribers' cards can move to another Stripe account, and get the answer in writing.
Then check your contract. Vimeo's pricing page says Enterprise requires an annual agreement, so your renewal date may set your deadline.
What your new provider needs from you
Because you own the store accounts, you can grant this access yourself. It is also the checklist for removing Vimeo at the end.
| Store | Give the new provider | Remove at the end |
|---|---|---|
| Apple | App Store Connect access and an In-App Purchase key (issuer ID, key ID, private key), then update the Server Notifications address | The VHX Apps user and the API key in the Vimeo admin |
| Google Play | A Play Console invite and a service account with financial and subscription permissions | apps@vhx.tv, cs-ott-apps@vimeo.com and the vhx service account |
| Amazon | A Developer role, the app's public key file, and your shared secret | The apps@vhx.tv user |
| Roku | An Administrator or App management role and your Roku Pay API key | The apps@vhx.tv administrator |
On OTTEngine, each app is built with the identifiers you give it, and in-app product IDs are entered per platform in the dashboard, so an existing product ID can be typed in as it is. The Roku, Fire TV, Android TV, Android, Apple TV and iPhone apps all ask the store what the account already holds. Confirm the plan for each of your stores before you commit, and treat the first renewal on each one as a test you watch closely.
A cutover plan
- PrepareExport, count and askRun the exports, split subscribers by billing rail, send Vimeo your written questions and check your renewal date.
- BuildWebsite and appsUpload your catalog and create the same plans. On OTTEngine, apps are ready for store submission in about a week, or about two for Samsung and LG.
- SubmitUpdates to your existing listingsSame identifiers, same product IDs, higher version numbers. Each store's review sets the date, so allow days to weeks per store.
- Run in parallelBoth services liveTest sign-in, a real purchase and a restore on every platform, with your own account.
- SwitchGrant, tell, pauseImport paid-through subscribers, send the email below and pause the Vimeo products.
- Stop the old billingCancel all at VimeoDo this only when the new service is carrying your viewers. It removes everyone's access on the old service.
- Clean upRemove Vimeo's access and keep your recordsTake the final exports first, redirect old pages and links, and watch the first renewal on each store.
An email like this does most of the work. Send it before the switch, and again a few days before their access date:
Subject: [Your service] is moving. Your access is safe.
We're moving [Your service] to a new home on [date].
If you pay on our website:
Your current access continues until [their end date] at no extra cost.
Before then, sign in at [new address] with this email address and
start your subscription. We'll stop your old billing, so you
won't be charged twice.
If you pay through Apple, Google, Roku or Amazon:
You don't need to do anything. Update the app when prompted. You may
be asked to sign in again.
Questions? Reply to this email and a real person will help.
The bottom line
Moving off Vimeo OTT is three separate jobs. Store subscribers mostly take care of themselves, as long as you update the listings you already own and keep your product IDs and keys in order. Web subscribers need a clear, well-timed request to sign up again, with their paid time honoured. People with free access need to be added back by hand. Start with the platform column in your export, then estimate what a new setup costs. When you are ready, start a free trial, or see how the alternatives compare. Hands-on migration support is part of our Enterprise plan.
Frequently Asked Questions
Can I export my subscribers from Vimeo OTT?
Yes. Admin, Customers, All Customers, Export gives you a CSV with email, name, product, status, frequency, platform and expiration date. A separate transactions export adds amounts and renewal dates. Neither includes card data or a Stripe customer ID.
Will my subscribers have to re-enter their card?
Plan on yes for anyone who pays on your website. Vimeo says Stripe holds the cards, and it publishes no process for moving them to another provider. Ask Vimeo in writing, but build your plan around a fresh sign-up. Subscribers who pay through an app store are billed by that store instead.
Will App Store and Google Play subscribers keep paying after I switch?
Their subscriptions belong to your app and its product IDs, not to Vimeo, so keeping the same listing and product IDs is what protects them. No store states in so many words that renewals continue across a vendor change, so test on each store and watch the first renewal. On a new listing, they do not come with you.
Do I keep my reviews and installs?
If you update the same listing, that is the expected result. Amazon says ratings and download statistics carry across versions, and Apple and Google say they move with a transferred app. Roku, Samsung and LG do not address it. A brand-new listing starts again.
What happens to my Samsung app?
Vimeo runs Samsung apps in its own group account, so yours is the one app you do not already hold. Vimeo says it can start a transfer to a Samsung developer account you create, and an update must then be signed with the same author certificate. Raise this early.
Do I need Vimeo's signing keys?
It depends on the store. Apple documents no such need, and Amazon re-signs apps itself. Google needs the key only if the app is not on Play App Signing. On Roku a different key loses on-device data, and Samsung needs the original author certificate. Ask Vimeo who holds them.
How do I avoid charging subscribers twice?
Give each paid-up subscriber access on the new service until their current paid-through date, then cancel at Vimeo before that date. Vimeo's Cancel all subscriptions stops charges and removes access on the old service, so do it once your viewers have moved.
How long does it take to move from Vimeo OTT?
It depends on how many stores you use and on their reviews, which nobody controls. On OTTEngine, apps are ready for store submission in about a week, or about two for Samsung and LG. Uscreen quotes 30 days for a website and 60 for a website and apps. Keep both services running until every new app is live.