Persona 5 Royal is another title where the storefront determines the storage model. Steam keeps user-scoped files under the SEGA P5R directory, while the Microsoft Store/Xbox app build relies on WGS. A useful backup must therefore capture the correct container for the copy you actually play. SaveEditor.com does not present the existence of third-party conversion workflows as proof that every platform save is directly compatible; the Game Hub separates location facts from conversion claims.
Prepare the source PC
On the source system, identify the actual Persona 5 Royal save root: Windows: Steam: %APPDATA%SEGAP5RSteam<user-id>savedata
Microsoft Store: %LOCALAPPDATA%PackagesSEGAofAmericaInc.F0cb6b3aer_s751p9cej88mtSystemAppDatawgs<user-id> | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/1687950/pfx/. The expected file/folder pattern is Steam savedata directory records; Microsoft Store WGS container records. 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, Microsoft Store / Xbox app. The Steam and Microsoft Store versions use different storage systems. Account/profile IDs are part of the path and should be preserved when documenting or restoring a backup. 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 complete Steam savedata directory or the complete Microsoft Store WGS data for the active profile. Keep the original untouched before any cross-platform conversion experiment. 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 for the corresponding storefronts. 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 exposes a normal account-scoped savedata directory. The Microsoft Store build uses WGS. Decrypted PlayStation 4 saves have separate conversion considerations and are not treated as byte-compatible with the PC storefront containers. Compatibility note: Do not assume Steam, Microsoft Store, or decrypted PlayStation saves can be interchanged by filename. Conversion is a separate operation from backup. If the destination does not see the transferred progress, If the game starts without expected system/save data, verify the storefront, active user ID, and cloud state before overwriting anything. Proton users should also use a current compatibility layer when diagnosing old save-creation issues. Verify game edition/version, store, profile IDs, redirected folders, and mod/DLC dependencies before editing the save itself.
Verification context: Storefront-specific PC paths, cloud support, and the documented note about decrypted PS4 conversion were reviewed against current PCGamingWiki coverage.