Inventory the state that needs to move
Before changing computers, separate saved source definitions from media files and machine preferences. A list of subscriptions, a set of favorites, a local video folder and the selected player engine are different parts of a viewing setup. Decide which of these you need on the destination.
Use a private migration checklist with a few representative items: one source, one favorite, one relevant saved position and any local media or guide file. This provides a reviewable acceptance check. It is more useful than assuming a copied application icon establishes a complete migration.
Export a versioned snapshot from each relevant profile
The IPTVnator 0.24 backup guide uses Settings, Backup, Import/export playlist backups, Export to create a JSON snapshot. Save the source computer’s export outside the app data folder. If the receiving computer already has valuable state, export that profile too before importing.
Keep the exports dated and distinguish which computer produced each one. The file contains connection secrets, so use a transfer location you control. Do not attach the export to a public issue or send it as a sample playlist. A separate redacted example is more appropriate when a support question needs an illustrative entry.
Plan for the documented exclusions
The developer distinguishes supported source state from downloaded media, cached catalogues, imported guide data and most application preferences. Local media and local XMLTV files must be handled separately; a playlist entry containing a path does not put the referenced file inside the JSON.
On the destination, check the actual storage location before opening a local-path item. Reapply the intended player and other machine choices deliberately. For an original acceptance example, a restored favorite may be correct while its original drive letter no longer exists; that is a storage-path issue rather than proof that the favorite was lost.
Import and read the result before repeating it
Install a current supported desktop version, open Settings, Backup and Import the versioned file. Read the result summary and allow restored catalogues to initialize before assessing individual saved items. Keep a note of imported, merged, skipped and failed entries.
If a source appears but its catalogue is still loading, wait for that stage to complete before comparing favorites. If it cannot connect, verify the restored account and the provider’s device rules privately. Repeated imports during an incomplete connection attempt can blur which snapshot you are actually examining.
Verify the migration with a short acceptance check
Open each important restored source and inspect the representative items chosen earlier. Check local media through its new storage route and inspect any guide file selected on the destination. Retain the original computer until the required outcomes are understood.
A completed migration record should say what source state was restored, what files moved separately and which preferences were reapplied. It should also preserve unresolved items. This procedure has not been executed against a real profile, and a successful JSON import alone would not justify claiming a complete playback test.
Questions answered
Does the JSON backup contain my downloaded movies?
No. The developer separates media files from the playlist snapshot. Keep downloads and other local files recoverable through a separate plan.
Should I back up the receiving computer too?
Yes when it already holds state you value. A restorable record of each pre-import profile makes the result easier to assess.
Can an old raw playlist-array dump be assumed equivalent to the current export?
No. Use the current versioned Settings, Backup export format described by the developer rather than treating every JSON file as the same backup.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.