State the actual migration
Write the old operating system, new operating system and Kodi versions. A point update on the same platform and a Windows-to-Linux migration are different jobs. Include any change in hardware, storage locations and sound output.
For an illustrative move, a source path valid on Windows may not name the same location on a Linux installation. A full archive can faithfully preserve that old path without making it meaningful on the new system. Archive completeness and cross-platform applicability are separate questions.
Choose the scope to carry
Consult Kodi’s current backup and library-export guidance for the state you need. A library export and a full configuration backup have different purposes. Keep the original setup intact while identifying which sources, metadata and preferences can be recreated or transferred appropriately.
Start with a small permitted collection and one authorised source on the new platform. Verify file access, artwork, track choices and playback before attempting a broad migration. Avoid overwriting the only working data folder with a cross-platform copy based on an untested tutorial.
Retain a recovery trail
Keep the original backup, version record and source inventory privately. If the new environment fails, that record supports a reasoned recovery rather than a sequence of blind reinstalls. Hardware differences can also require output settings to be reconsidered even on the same operating system.
A useful support request states the exact migration, chosen method, successfully restored state and first failing step. Redact private paths where possible and never publish credentials contained in configuration files. This article applies the project’s documented transfer limits; it does not claim to have performed the reader’s migration or guarantee every add-on’s portability.