Hogwarts Legacy needs more careful path checking than a single copy-and-paste instruction suggests. Different PC storefronts and packaging contexts can produce `Hogwarts Legacy`, `HogwartsLegacy`, `Hogwarts`, or `Phoenix` paths, while Microsoft Store uses WGS. The safest backup begins by finding which directory changed most recently after an in-game save, then copying the entire user-ID folder. Keep alternate folders until you have positively identified the live one.
Which storefront context matters
Documented Hogwarts Legacy PC launchers/storefronts: Steam, Epic Games Launcher, Microsoft Store / Xbox app. PCGamingWiki documents multiple folder-name variants, including launcher/streaming-specific paths. Identify the active storefront and actual modified folder before restoring anything. The active storefront/account should be identified before any restore because cloud and local storage may not use the same path or container across editions.
Documented cloud behavior
Steam Cloud, Epic cloud, and Xbox Cloud are documented for the corresponding releases. Cloud synchronization is useful for continuity, but it can also turn a restore into a conflict-resolution event. Let synchronization settle before making a manual backup, and keep an offline copy outside any folder monitored by the launcher or operating-system sync service.
Local save roots still matter
The researched local save boundary is Windows: Steam: %LOCALAPPDATA%Hogwarts LegacySavedSaveGames<user-id>
Epic may use %LOCALAPPDATA%HogwartsLegacySavedSaveGames<user-id>
Microsoft Store: %LOCALAPPDATA%PackagesWarnerBros.Interactive.PHX_ktmk1xygcecdaSystemAppDatawgs<user-id> | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/990080/pfx/; the known file or folder pattern is *.sav. A cloud-enabled game still has concrete local data involved in ordinary play, and that local context is what you need when identifying which copy was modified most recently.
Avoid accidental overwrite loops
Copy the full active SaveGames user-ID folder. If more than one Hogwarts/Phoenix path exists, compare modification times and preserve all candidates before cleanup. When restoring, close the game and launcher, preserve both the current local copy and the backup you want to test, then place the intended data in the matching profile/storefront location. Do not repeatedly open the game between different copies without noting which side the cloud client selected.
Compatibility and conflict checks
Microsoft Store WGS data should not be treated as a renamed Steam/Epic .sav file. Storefront migration is a separate conversion problem. If progress disappears or rolls back, If the expected path is empty, search the documented alternate HogwartsLegacy/Hogwarts/Phoenix directories and check the storefront. Do not delete the older folder until the active save set is confirmed. Resolve identity/path/cloud questions first. A cloud conflict is not proof that the save itself is corrupt, and a successful upload is not proof that files from another storefront are compatible.
Verification context: Multiple Windows storefront paths, Steam Play behavior, and cloud services were reviewed against current PCGamingWiki coverage.