A settings export can depend on the software version that created it. A newer release may add fields or change how configuration is represented, while an older release may not understand the result. The export’s extension alone does not establish cross-version compatibility.
Read the actual player’s documented restore support before applying a backup. A playlist exchange format and a complete application-settings backup can have different portability rules. Keep their purposes and origins labelled clearly.
Preserve the export’s context
Record the app identity, version, export date and scope without putting credentials in filenames. That context helps distinguish a backup intended for the same product from a similarly named file from another player.
A destination can accept part of an export while ignoring unsupported fields. The import dialog completing does not prove every profile, guide mapping or preference was restored. Choose representative checks based on the setup’s actual needs.
Review compatibility deliberately
Do not change a version field merely to bypass an importer’s rejection. That does not convert the underlying data model. If a supported intermediate migration is required, use the genuine instructions instead of inventing one.
- Identify the source application and version that created the export.
- Read the destination’s supported import or migration path.
- Preserve the destination’s current working configuration privately.
- Restore through the documented route rather than editing version markers by hand.
- Verify specific settings and relationships after import.
Keep source and account data separate
A settings backup can contain private URLs or tokens as well as ordinary preferences. Review how it is transferred and stored. A file that restores successfully on another device can also expose access data to that device’s users.
A backup can preserve historical account values that are no longer current. After restoration, confirm the intended authorized configuration through the established route. Successful format import does not establish current entitlement or URL validity.
For support, provide the source and destination app versions, export type and exact non-secret error. State which fields restored and which did not. That evidence distinguishes unsupported format evolution from a corrupted transfer or an account problem, and it keeps the recovery claim tied to the data actually verified.
Useful answers
Does changing an export’s version marker convert its data model?
No. It can hide a compatibility check without performing a valid migration.
Does import completion prove every field was restored?
No. Verify the settings and relationships that matter.
Can a valid old backup contain expired account values?
Yes. Format validity and current access are separate.