List the configuration you need to preserve
Before reinstalling OTT Navigator, identify which configuration matters: providers, channel changes, application settings or media-library information. A configuration backup is different from a copy of recordings or a video archive. Keep one small private inventory so the expected restore can be checked later.
Record the current application version and the device being replaced. If another person owns the provider account, retain the authorized login process rather than exporting credentials without agreement. A backup can carry sensitive access details even when its visible purpose is simply to preserve favorites.
Create a backup through the documented settings route
The developer documents Settings, Extended settings and Backup and restore. Simplified mode can hide this section. Choose Backup current configuration and deliberately select the components to include. Keep the original setup intact while the backup is created; a code is useful only if it represents the state you intended to preserve.
Review the password and one-use restore options described in the app. Choose them according to how the backup will be used and keep any password separately from a publicly visible screenshot. The developer warns that possession of an unprotected code can permit restoration, so do not paste it into a public support post.
Read the receiving installation’s restore scope
On the intended receiving device, open the same section and use Load a previously made configuration backup with the actual code. Read the available component choices before proceeding. The documented merge choice for providers has a different purpose from replacing all configuration.
For an original example, a second device may already contain its own working source. If the intention is to add another authorized provider, preserve that existing state and inspect the merge scope. Choosing Everything without considering the receiving setup can change more than the missing favorite list.
Verify the restored result and retain a longer-term plan
After a restore, compare the private inventory with the actual providers, channel properties and settings. Check one authorized item and its guide separately from the mere presence of a source name. The application may restart when settings are restored; retain the code and password until the result is understood.
The developer describes code backups as time-limited rather than permanent archives. Use the current retention information when planning a later migration and choose an appropriate supported longer-term route if needed. The expected outcome is a recoverable, scoped configuration—not an assumption that a code backs up every recording or guarantees the source account remains valid.
Questions answered
Does a configuration backup copy all my videos and recordings?
Do not assume that. Inventory configuration and media separately, and verify the documented coverage of the chosen backup route.
Should I post the restore code when asking for help?
No. It can expose a restorable configuration. Describe the error and scope while keeping the code and any password private.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.