How to migrate customers to another IPTV app without disrupting your reseller business
Switching the player of an active base takes more planning than just sending a new link. The migration must consider the devices customers use, the commercial model, installation on each platform, activation, authorized DNS and communication in batches so support is not overloaded.
Group customers by platform, status and priority before sending any instructions.
Validate the new flow on a few representative devices before expanding the switch.
Migrate in batches, track questions and fix the script before the next group.
1. Take a real inventory of your base
Start by listing customer, device, platform, commercial status and any dependency on a server or DNS. Do not group everything as “Smart TV”: Android TV, Roku, Samsung and Fire TV may require different processes. The inventory shows how many installation instructions you really need to prepare and which customers should be handled first.
Also include customers on trial, active and expired. It is not worth spending time migrating an account that is no longer part of the base. If the operation uses a Smart Code, write down which authorized DNS must remain available in the new flow.
2. Split the migration by platform
Create groups such as Android/Android TV/TV Box, Windows, Roku, Samsung and Fire TV. For each group, write a short script with where to install, how to open, what data will be entered and how to confirm the activation is correct. Platform-specific instructions reduce back-and-forth messages.
On Fire TV with Vega OS, for example, 2T Play reselling requires Monthly or Postpaid with a Smart Code. This rule must be checked before including Fire TV customers in a migration based only on credits.
3. Run a pilot batch before the mass change
Choose a small group that represents the most common platforms in your base. Install the app, test the sign-in flow, confirm activation and see which questions come up. The pilot should simulate real support, including when the customer has to find the app in the device's store.
Write down the average time and the pain points. If an instruction raises questions in almost every test, fix the script before moving on. This step is cheaper than discovering a problem after notifying the whole base at the same time.
4. Tell trials, active customers and final activation apart
During the migration, some customers may only be evaluating the new player. When a playlist is identified as a test or trial, it must not be confused with an active commercial customer. In the 2T Play ecosystem, trials identified by the portal do not enter the Monthly/Postpaid commercial count and should not consume a credit just because they are being evaluated.
When the customer confirms they will continue, activation follows the reseller's model. This separation helps avoid spending balance on those who have not decided yet and keeps the active count aligned with the real base.
5. Keep only authorized data and sources
Migrating the player does not change the responsibility for the content. The user and the reseller must use only playlists, DNS and credentials they are authorized to access. If the operation has several own or authorized DNS, the Smart Code can help organize the contracted capacity and the sync supported by the app.
Avoid copying data unnecessarily. Transfer only what is essential for the customer to keep using the player within the existing authorizations. Passwords and access data must be handled carefully and should not circulate in open groups or spreadsheets.
6. Migrate in batches and track the results
After the pilot, move forward in controlled groups. A batch can be defined by platform, service region or commercial priority. Wait long enough to observe support tickets before releasing the next group. This way the team learns from each round and reduces the volume of simultaneous support.
At the end of each batch, check how many customers finished installation, how many were activated, how many are still on trial and which problems repeated. These numbers show whether the script is ready to scale or needs adjustment.
Frequently asked questions about customer migration
Do I need to migrate all customers on the same day?
No. Switching in batches reduces risk and lets you fix instructions before affecting the whole base.
What information should I gather first?
Start with each customer's platform, commercial status, device and dependencies on an authorized DNS or server.
Do customers on trial need to be activated immediately?
No. First validate the new player. The final activation should happen when the customer really stays in the operation.
Does the Smart Code help with migration?
It can organize the reseller's authorized DNS within the contracted capacity and support the sync flows supported by the ecosystem.
Can I migrate playlists from any source?
No. Migrate only playlists, DNS and credentials that the user or the reseller is authorized to use.
Which platform deserves special attention?
Fire TV with Vega OS has its own commercial rule for resellers on 2T Play: Monthly or Postpaid with an active Smart Code.
2T Play is only a media player and a platform to manage its own licenses. It does not sell, provide, host or distribute channels, movies, series, IPTV playlists or any other content. Users and resellers must use only sources they are authorized to access.
Want to see the 2T Play dashboard?
Create your account, check the current plans and choose the model that fits the volume and platforms of your operation.