Octopath Traveler uses a clear SaveGames directory on the conventional Steam PC build, but the user-ID layer and numbered slot names are important when restoring progress. Community guides consistently identify SaveData0.sav as the autosave and subsequent numbered files as manual slots. SaveEditor recommends backing up the entire directory so slot context and Steam cloud metadata remain available. Microsoft Store uses WGS, so its files are described as a separate container rather than an ordinary .sav location.
Prepare the source PC
On the source system, identify the actual Octopath Traveler save root: Windows: Steam: %USERPROFILE%DocumentsMy GamesOctopath_Traveler<user-id>SaveGames ; Microsoft Store: %LOCALAPPDATA%Packages39EA002F.FrigateMS_n746a19ndrrjgSystemAppDatawgs. The expected file/folder pattern is SaveData0.sav is commonly the autosave; numbered SaveData*.sav files represent manual slots on Steam.. 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. Storefront paths differ. Steam/Epic PC save data can resemble ordinary .sav files while Microsoft Store uses WGS containers. 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
Back up the full SaveGames folder, including every SaveData*.sav and steam_autocloud.vdf if present. Keep the original slot numbering when testing a restore. 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 and Xbox Cloud are documented; OneDrive may also synchronize Documents. 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
The Steam release uses an Unreal-style Documents SaveGames directory under a user ID. Microsoft Store uses WGS. Slot numbering matters when replacing a particular save. Compatibility note: Switch/PC and Microsoft/Steam transfers reported by the community are migration workflows, not proof that all storefront containers are byte-identical. If the destination does not see the transferred progress, If a save does not appear, verify the user-ID folder, exact SaveData slot number, and cloud state. For Microsoft Store, identify the correct WGS payload before any conversion. Verify game edition/version, store, profile IDs, redirected folders, and mod/DLC dependencies before editing the save itself.
Verification context: Reviewed against current PCGamingWiki Octopath Traveler save path plus long-running community slot/file-name documentation.