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.
Prepare the source PC
On the source system, identify the actual Hogwarts Legacy save root: 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 expected file/folder pattern is *.sav. Close the game, let the active launcher finish writing and synchronizing, then make a complete offline copy rather than transferring a file that may still be open.
Preserve storefront and profile identity
Documented 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. A transfer between two PCs is simplest when both systems use the same storefront/account/profile context. If the destination uses a different store or container, treat that as a migration problem rather than an ordinary restore.
Move the complete save boundary
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. Put the copied data on the destination only after confirming the destination save path. If the game creates a new empty save first, keep that new folder as another backup so you can compare structures and revert.
Handle cloud sync deliberately
Steam Cloud, Epic cloud, and Xbox Cloud are documented for the corresponding releases. Decide whether the local transferred copy or cloud copy should be authoritative before launching the game. If possible, preserve both. After the transferred save loads correctly, make a fresh in-game save and let the launcher synchronize normally.
Check compatibility before blaming the transfer
Steam/Epic PC saves are .sav files under Unreal Engine-style Saved/SaveGames directories. Microsoft Store uses WGS instead of the same visible-file layout. Compatibility note: Microsoft Store WGS data should not be treated as a renamed Steam/Epic .sav file. Storefront migration is a separate conversion problem. If the destination does not see the transferred progress, 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. Verify game edition/version, store, profile IDs, redirected folders, and mod/DLC dependencies before editing the save itself.
Verification context: Multiple Windows storefront paths, Steam Play behavior, and cloud services were reviewed against current PCGamingWiki coverage.