Yakuza: Like a Dragon separates PC save storage by storefront more clearly than many games: standard/Steam, GOG, and Microsoft Store each have different roots. That means a generic instruction such as “copy the Sega folder” is too broad. SaveEditor records the user-ID level and the GOG-specific suffix so a backup can be put back into the environment that created it. Microsoft Store remains a WGS container and is not described as file-compatible with the normal AppData layout.
Which storefront context matters
Documented Yakuza: Like a Dragon PC launchers/storefronts: Steam, GOG, Microsoft Store. GOG deliberately uses a different YakuzaLikeADragon_GOG root. Microsoft Store data is not a normal AppData file set. 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, GOG Galaxy cloud, and Xbox Cloud are documented. 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/Windows: %APPDATA%SegaYakuzaLikeADragon<user-id> ; GOG: %APPDATA%SegaYakuzaLikeADragon_GOG<user-id> ; Microsoft Store: %LOCALAPPDATA%PackagesSEGAofAmericaInc.Yazawa_s751p9cej88mtSystemAppDatawgs<user-id>; the known file or folder pattern is User-ID-specific save records inside the active storefront directory.. 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
Back up the complete storefront-specific user-ID folder. Do not flatten files from GOG and Steam into one Sega directory because each edition has its own expected root. 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
Cross-store copies are not guaranteed by identical game content. The WGS edition in particular should be treated as a separate container until a tested transfer workflow is available. If progress disappears or rolls back, If progress is missing, confirm the storefront and user ID first. Then check whether the launcher restored cloud data after the local folder was changed. 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: Reviewed against current PCGamingWiki Yakuza: Like a Dragon save paths and cloud-sync table.