A customer moving to a new screen needs a device setup handover and an account decision. Those are separate tasks. Record the old and new device context without collecting unnecessary secrets, then ask support how the existing account may be used under its actual conditions. A new installation does not automatically grant an extra connection, transfer a player licence or preserve local favourites.
Identify what lives where
A service account is separate from the player installation and any player-store licence. Favourites, watchlists and settings may live only on the old device. The replacement device can also use a different operating system. Make those layers visible in the handover so a customer does not expect an Android backup to install directly on a webOS or Apple platform.
Keep the old setup available until the route is clear
Do not advise erasing the old device as the first troubleshooting step. Retain the private activation reference and establish the supported installation route on the new screen. If a transfer or licence change is needed, follow the relevant publisher’s actual process. Do not assume that copying files or a device identifier creates a valid transfer.
Resolve simultaneous use before testing
A temporary overlap during setup can still count as simultaneous playback under the account rules. Ask about the allowance before opening streams on both screens. Use a controlled test and record which device is active. The aim is a clear handover, not a workaround for an unverified connection limit.
A practical sequence
0 of 4 steps completed on this page.
An example to work through
A customer replaces an Android box with an Apple TV. The service enquiry can refer to the same existing account, but the Android APK and local player preferences are not an Apple TV installer or a guaranteed settings transfer.
